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.
384 results found
-
Allow "Active Sprint" option for the Work Logged field
Currently, the options are current and prior day, week, month, year. Can we have current and prior sprint?
3 votes -
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 -
Add view setting to specify level of expansion
When creating or editing views, allow specifying the degree of expansion. My use case is that I want to show all issues in the top three levels by default. Furthermore, I want the expansion setting to apply to the Confluence gadget.
Alternatively, a perspective can be used to achieve the same result, but there is currently no way to use a perspective for the Confluence gagget. If the perspective could be used in the gadget, then I would recommend combining with http://structure.uservoice.com/forums/43181-structure-plugin-for-jira-ideas/suggestions/1773075-add-controls-to-expand-contract-one-level-at-a-t to allow an unlimited customization of gadget presentations.
3 votesLikely planned for 3.0
-
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
-
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
-
Name in issue viewer
When beeing displayed in the issue viewer and the default structure name should be "None" to avoid confusion as another structure name makes it seem to belong to one.
3 votes -
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
-
support grouping of issues by link type
e.g. all 'Blocked By' issues added via Extend automator grouped together under parent.
This makes the Jira relationship between Structure parent/child issues clearer.
3 votes -
allow me to define a story point budget for a folder / issue
I typically have rough estimates for bigger projects and I would like to be able to add them to the structure so that I can get an overview of what needs to be done. At the moment I can only do this by adding JIRA issues with estimates, but the problem is that at this stage I do not really want to create these issues yet (at least not for everything).
The closes thing to what I want is to create epics and set the rough estimates on the epics. Later I can refine my estimates by creating storys. The…
3 votessee comments for details
-
improve support for Quick Transformations
Currently you can save transformations as quick transformations which is a great feature. I see however certain potential to make it even better:
- Combine several transformations into a single Quick Transformation (e.g. filtering and grouping)
- Define Quick Transformations for the "Jira" part of the double grid: I often look for items assigned to a version in order to add them to my structure. It would be super convenient if I could save it as a Quick Transformation.
Thanks for your consideration and keep up the great work!
3 votes -
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
-
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
-
Sync task to add Tasks to Folders
Folders is a great new feature in 3.0 (long awaited) but the sync tasks do not allow tasks to be added to folders which is an obvious feature for auto adding tasks to structure and also a huge use of ordering and sorting tasks in structure.
3 votescollecting requirements – please see comments
-
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
-
have a aggregation modifier #fromTopToMe #fromBottomToMe
To provide a backlog forecast it is essential to show what content could be done within a certain time or time budget. If we configure the budget in a top level issues custom field, structure could SUM not only by level, but also the contents of the current list of elements (eg. by priority) and a formula could show from which element the budget is overspent.
3 votes -
provide "root element of column x" in the variable selection list of formula column editor
E.g. to calculate a percentual distribution over all rows of a structure, for the formula you need the 100% value which is typically shown on the root element.
Therefore it would make a lot of sense, to be able inside "formula column A" to use a columns B's value, but the root element value! This should be possible even if column B is a formula itself.
As we can already use variables like "Column B ..." in formulas it would be nice to add "Root Value of Column B ..." to the variable selection list3 votesThank you for the idea! Read the comment, please
-
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
-
"Sum over Sub-items" For Dates / Aggregate Dates - with the ability to choose Max or Min Date
I'd like to see my dates roll up the hierarchy so that I can see higher level estimates as they roll up. For example, if I have a folder for a project and I have a number of tasks underneath, I'd like to see the latest due date in the project, or the earliest start date.
3 votesAlready possible with latest Structure – see comments for details. More improvements are coming.
-
Choose what group label to display and which order for field fixVersion
This idea is a to provide a way to display only (or to hide) some fixVersion instead off all of them when we use the grouping feature. If it is possible to choose the storing order (asc, dsc) it would be awesome !
3 votesthank you! check the comment, please
-
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
- Don't see your idea?