Structure for JIRA: Ideas
Thank you for visiting our feedback website! Feel free to vote or post your own ideas. Make sure you turn on the option to notify you about changes and comments in your account settings, so that you can stay updated about the progress of the ideas you’re interested in.
170 results found
-
Display a collated view of multiple structures
As a release manager, I want to see multiple structures represented in one view so I can easily collate the work multiple teams are doing. Our planning and management of structures is distributed, but I need to be able to see them all for enterprise planning purposes. Additionally, I want to be able to filter the one "master" view so I can see only those items related to specific criteria (e.g. release or project or component).
3 votescollecting requirements
-
allow us to synchronize links between sibling and cousin issues
Right now the link synchronizer works only between parent and sub-issues. However, this is often not enough. For example, we would like to automatically link "development" and "system testing", which are usually sibling issues under a single "Change Reqest ### for system XYZ" issue.
A use case for "cousin" links is similar: "integration testing" should depend on all "system testing" issues within the same "Change Request ###" parent/grandparent issue.
Right now we work around this by using template structures, but this is fiddly and error prone, since issues like "integration testing" should be edited manually after N "change request for…
3 votesPlease see the comment
-
Creating structures from agile boards with Epics and Epic-less tickets
When creating a structure from an Agile board it would be nice to be able to add as well Epic as stories not assigned to an Epic.
Creating a structure with Epics and adding an JQL-Inserter for the Epic-less Stories is not sufficient. I am not able to move Stories into an Epic later on the structure board this way. ("Cannot remove issues from JQL query result. ")
3 votesplease see the comment for an alternative setup
-
allow filtering a centralized time period for a view with multiple worklog columns
when you report worklogs with structure, you want to use the worklog column and specify a time period.
If you add multiple columns, it is quite an effort to change the time period from eg. dates of jan to feb. (currentmonth is helpful, but somewhat too dynamic if you want to compare months)To easily switch between months it is necessary to switch the time period you look on on the view level and influence alle worklog columns this way.
3 votesThanks!please read the comment
-
Keep backlog always up-to-date with notifications
I think it would be nice to have possibility to notify Scrum Master and Product Owner that some of UserStories are holding in a backlog for quite a long period of time (could be specified in extra settings), for example 3 moths.
It should help to keep backlog always with actual UserStories.3 votescollecting requirements
-
Tempo Hours in Structure: Budget (planning) - Actuals (logged) - ETC (remaining)
As a Project manager, it's handy if the hours are visible in Mandays or Hours to check the financials. 3 columns if (not yet already available to see the Tempo Hours in Structure cloud: Budget (planning) - Actuals (logged) - ETC (remaining). And this is for each separate issue type and rolled-up based on hierarchy or grouping. And visible or reported not in weeks but accumulate in mandays and/or hours. Tom
3 votesHi Tom,
Thank you for your request.
I see that you require your columns to be in a specific format.
But could you please clarify, do you have the Budget (planning) column already or do you want it to be implemented? If you already have the Budget column, is it just a custom field in Jira?
Thank you,
Konstantin
-
Be able to propagate up a risk value
If a sub task had a custom field which indicated it's current risk or similar be able to propagate that up to the top level to show the worst of the risks or some other flag
e.g. if a single subtask of a item is red risk, be able to show that red risk in all of it's parents in the structure. choose the worst value of all sub nodes to show at the parent level.
3 votescollecting requirements — please see comments
-
Add ability to right click on selected item(s) to move to top, to bottom, down/up by like 50/100/200 rows at a time
This will save time in organizing one's Structure especially those items that are completed and need to be moved way down or those items that are open and need to be brought way up. This would especially be useful when initially setting up one's structure.
3 votes -
Possibility to disable/filter the Structure notifications in the project & user Activity Streams
Currently only the Actitvity Stream "gadget" has the option to configure filters.
The standard (non-gadget) Jira Activity Stream on the Project Summary page & on the User profile page does not have this option. Hence these Activity Streams are heavily 'polluted" with Syncronizer updates and are becoming useless..3 votes -
Option to change font style of Summary text for different levels of hierarchy
Formula column with Wikimarkup is great, but since you cannot use this on the Summary column (which must be included in the Structure as is) there isn't a way to clearly distinguish the different levels of your hierarchy. Would be great if you could opt to bold the Summary column for Level 0, for example.
3 votesThank you for your request! Please check the comment
-
Search Filters Should Retain At A Structure Level
If you have several structures that you are attempting to manage when you switch between them your search panel tries a filter / set of search criteria from the previous structure. Then you have to figure out that you want to apply filter=29121 or whatever when you go from structure A to structure B.
Easy fix.
3 votes -
Allow importing XRay tests creating a tree of folders corresponding to a test path in the XRay test repository
XRay instroduced a Test Repository in v3. Now every XRay test has a field 'Repository Path' looking like: '/Test Repository/Release 1/Phase 1/AAA/'.
However, the Structure view is still better than XRay repository. It would be great to be able to import XRay tests recreating the same folder structure as in the XRay test repository automatically. So that users can use both XRay test repository AND Structure.
3 votesThank you! please check tthe comment
-
Intergation width standard JIRA filters
Allowing in JIRA filters can be filtered by issues that you belong to a structure.
3 votesplease see the question in the comments
-
Support Wallboards
I would like the ability to use Structure gadgets also on wallboards. Technically you can already do that, but for example progress bars are not visible. I suppose this only requires a separate stylesheet?
3 votescollecting requirements in the comments
-
support project roles in JIRA
Structure currently only supports permission groups but not project roles. If a project is set to support project roles then there could be surprises if some users are part of the right role but do not belong to the groups that Structure has been permitted to.
3 votes -
Use lightboxes when managing structure properties
Currently when editing a structure (Operations->Configure), you are throw into a new page for editing. When you are finished and go back, the structure list reloads and moves you to the top and I cannot find my place anymore. This is a problem when you are viewing a list of over a thousand structures.
A popup lightbox would make things much better and allow me to keep my place in the list of structures. This could apply to sync settings, and all other management operations.
3 votes -
Ability to weight Progress column by number of issues
(e.g. a parent’s progress is just based on the progress of its children, but if one of those children has 10x more children than the other, it would be nice to weight it that way)
3 votesrequirements gathering
-
Queries based on structure, especially ones that make roll-up easier
- All issues that are direct children of this issue
- All issues that are children, grandshildren, etc. of this issue
- Parent of this issue
- Store the structure information in the same tables as other JIRA information, so it can be queried the same way.
3 votes -
prevent double counting
When an issue appears multiple times in a structure (e.g. epic link and issue link),the progress calculation should be configurable to prevent / allow double counting
3 votesplease see the comments
-
Progress Bar changes color by ontime or overdue
Allowing users a quick view of the status for more than completion percentage for [insert your object of choice] if they are overdue or nearing completion deadlines
3 votescollecting requirements — see comments
- Don't see your idea?