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.
-
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 -
Add progress aggregation based on the number of sub-items
Parent issue progress % seems incorrect based on underlying children progress % values, assuming equal weighting per child.
Example screenshot: imgur.com/a/43lgW
3 votes -
Option to always include Epic Link in the Structure
Same as the option to automatically include sub-tasks in the Structure, also add the option to always include the Epic Link.
3 votesrequirements gathering
-
Log changes
Sometimes someone deletes stuff from the structure and we do not know how the structure looked before (no version management exists).
In this case, as a workaround we would like to have a log to see what has changd.
3 votesThank you, please check the comment
-
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
-
Use the standard Atlassian User Interface objects
I would suggest you to resort exclusively to the AUI objects for your interface instead of your custom ones that clearly gives the impression that you are exiting the Jira world to step into another one.
I think you user would deserve a smoother user experience, with the same kind of buttons, icons, tables to which they are already used to. I'm especially talking about the transformation/filters features that should be improved in that direction to my mind. Thanks for you great achievement!3 votesplease see the comment
-
allow showing worklogs for a specific sprint and team
I assume a lot of people want to use structure for reporting as well. Most teams work with sprints and therefore it is essential to be able to select "sprints" as a filter for worklogs in structure views. A structure/or view could show worklogs for a certain sprint only and besides also for the involved team as well
3 votesThank you for idea! please check the comment
-
Create column for Greenhopper Agile version
Greenhopper's Agile plugin allows for nested "versions" to define Agile Sprints within a top-level planned release. This is represented in JIRA as comma-separated items in the Fix Version/s column.
The Agile Planning Board is smart enough to show the last Version in that comma-separated list indicating the current sprint to which an issue is assigned. Structure is showing all the comma-separated versions which takes up a lot of column width space (particularly considering the Structure view does not wrap text in columns...).
Would you consider creating an Agile Version column that is essentially the last item in the Fix Version/s…
3 voteswill be possible with configurable and extendable columns
-
"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.
-
3 votes
planned as the Structure Board with preview
-
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 -
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
-
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
-
Separate Effort from Duration. Gantt should show the duration independent from the effort estimation.
Duration depends of the availability of resources. Gantt should show how long the issue will take to close, For Stories the duration is given by the sprint. For Epics there is no possibility to hold this information and show it in the Gantt, using the Effort field for this information is completely the wrong way.
3 votesHi Beat!
Thank you for the feedback. Please, see my update in the comments!
-
Enable use of existing, saved filters to populate a structure vs. having to manually enter filter criteria
Use case: I have an existing filter that is the basis for a board. The board dynamically updates, whenever I change the criteria of the filter upon which the board is based. However, if I want to use that same existing filter with a Structure, I must replicate the criteria in structure, and then perform dual maintenance, whenever I want to change filter criteria. If the saved filter could be used by Structure, I would only have to modify the filter itself. This might be addressed in the process of solving the following existing idea:
https://structure.uservoice.com/forums/43181-structure-for-jira-ideas/suggestions/31928860-link-a-structure-to-a-jira-board-not-just-a-proje3 votesThank you! check the comment, please
-
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
-
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
-
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 -
when auto scheduling in gantt, have start and finish dates synced with a field in issue.
when auto scheduling in gantt, start and finish dates are not synced with Start Date and End Date of the issue and later when generating reports, we cant have a realistic report
3 votesHello Zarei!
Thank you for a suggestion! This feature is already in our roadmap, but it will require some support from Structure itself so it probably won’t be available very soon (hopefully next year).
-
Allow "Inversion" of Quick Filters so they could effectively "add" rather than remove issues.
We need to use quick transformation filters that behave as if they are connected with an "OR" instead of an "AND" clause. I realize doing that would be problematic, but there would be a simple workaround if it were possible to merely invert the effect of selecting the filter buttons. Specifically, when the button is deselected (the default state) the filter would be applied, and when selected the filter would be deactivated.
This could be implemented by providing a single checkbox in the edit screen for a quick filter that inverts the effect of the filter. So instead of not…
3 votes
- Don't see your idea?