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.
-
Deeper hierarchy in issue types
Our organization would like to have a possibility to create another tasks layer above Epics (like in Jira's advanced roadmaps). For example, I create a new issue type "Initiative" in Jira and then I can group in structure gantt all tasks in this hierarchy:
Initiative>Epics>Stories, Tasks>Subtasks.6 votesActually, that’s something Structure can already help you with!
Structure allows creating hierarchies using existing relationships between issues in Jira. If there is a link between two issues, Structure can visualize the relationships in the parent-child form, putting one issue above the other.
You just need to use standard Jira link functionality which is available in any Jira version by default – the ‘blocks’, ‘implements’, etc type of a link. You can configure them at Settings | issues | Issue linking and create links between issues using the Link option on any Issue Page.
And once links exist between Initiative and Epics, then you can build your structure with the desired hierarchy the following way:
1. Create a structure.
2. Click Automation | + | Insert and type a JQL query to match all Initiatives that you want to add.
3. Then click + | Extend | Linked Items and… -
5 votes
-
Report or filter on accumulated fields
FIelds like 'progress', 'estimate' or 'logged' are calculated (accumulated) over the sub-structure under the issue. I would like to be able to report those values in reports (e.g. accumulated estimate) or use them in JQL queries (e.g. accumulated_estimate > 2w)
5 votesCollecting requirements, please see comments.
-
Ability to hide the time line in the gantt chart view
It is a widely adopted practice to not share specific dates in long term planning and it would therefore be helpful if I could hide the dates/timeline in the gantt view.
The only option today is to zoom out but that is not practical as the feature-bars will become to small and the timeline is still visible but in years.
I want to be able to show how feature A is scheduled before Feature B and that it is dependent upon Feature C being completed without having to show when the features will be worked upon.
Simply hiding, or making…
5 votesHi Andreas!
Thank you for the feedback! We’ll definitely evaluate your idea.
-
removing a column sort is not easy. Make it simple.
Structure is sorted by Rank (through automation). I often click on Assignee column to sort by it. The only way to remove the sort is to click Transformation, Click the sort and click the remove. This is way too many steps to just remove a sort. One idea is to have each column have 3 states when clicked. Sort Ascending, Sort descending, Remove sort.
5 votesThank you for your suggestion!
-
start date
As a team lead, I want the Gantt view to show all unresolved issues as starting in the future irrespective of the view's "start date", so I can quickly visualise dependencies between teams that will impact their next sprint
5 votesHi Robert, thank you for the request! This feature is called a Backlog and planned to be available in one of upcoming releases!
-
Allow for shared filters similar to how views are managed
Similar to how views can be shared across different Structures, it would be great if Quick Transformations could be the same. Right now, we have 15+ separate, but related Structures. All should have consistent views and transformations. Managing views is very simple, but if you change a filter on one Structure, you must replicate that change X more times.
5 votesThanks for your suggestion!
-
Progress by status category
Currently progress by status is supported(among other statuses).
To simplify configuration in complicated jira setups it would be nice if one could filter by status category. Instead or in combination.
5 votesThank you for the suggestion.
Could you please share your use case and some details about your setup? What do you want to achieve with this functionality?
-
Have option to customize or hide what buttons are shown
Trying to get users to update information who are less familiar with Jira. Want to customize what options/buttons users see so it's less overwhelming.
5 votesthanks! please check the comment
-
Expand Editing from Gadget
Please add the ability to edit more fields especially custom fields from the Gadget (https://wiki.almworks.com/display/structure/Editing+from+Gadget). The ability to edit custom numeric fields via jira dashboards/confluence pages would be awesome!
5 votesThanks! check the comment, please.
-
Granular control over Automation grouping, particularly with Labels
Currently, grouping within Automation is kind of an "all or nothing" approach. For example, we use labels to identify which "product" our epics are for, but we also use the Labels field to track other information. For our main Structure, what we want to do is have the Automation grouping only look at the 6 labels we currently use for "product" tracking and ignore all of the others, but I cannot seem to find a way to do this without manually creating my own folders and setting up the Automation for each one; the drawback to this is we can't…
5 votesThank you!
Check the comment, please.Julia.
-
Feedback on Learning About Structures
I'm a product manager and have a technical background, but pretty much had to figure out how structures work using trial and error. I gave up the first few times I tried to build one because I just didn't get what was going on.
It wasn't until I had a need to look at data across teams in a specific way, that without a structure, would have resulted in a ton of duplicated effort in Excel, that I forced myself to figure out how they work. At that point, I also discovered the formula columns and found that documentation to…
5 votesThank for the request!
-
Propagate Due Date
Allow users to set due date based on due date of parent and estimated time. Plus when due date of parent is changed propagate change to all child issues accordingly
4 voteswaiting for clarification
-
When displaying subtasks in Structure, include parent jira # as part of summary (like Jira filters)
When displaying subtask in Structure, include parent jira # as part of summary (like Jira filters).
4 voteswaiting for clarification
-
Link issues in a hierarchy as you move issues around in the Structure view
Currently, when you clone a subtask and move it to another parent issue, it actually remains (for all intents and purposes of JIRA data) as part of the original parents issue.
This is a problem, because in Greenhopper on the planning board (where you move User Stories to actual date defined releases), they have to reflect the same structure as you created in Structure.
4 votesWaiting for response
-
Automatically create issues to represent structures
Allow structures to have attachments, comments, workflow, etc by creating an issue for each existing structure. This could be automated by the Structure plugin.
Let the administrator configure a special project / issue type for those issues.
4 votes -
Support entering data into mandatory fields on SubIssue creation
when you are creating a sub issue you might hit a wall when the creation of the issue have some mandatory fields which needs to be filled out.first.
it should be possible to enter data during sub issue creation.
it is already shown which fields that need to field out.4 votescollecting requirements
-
Keep carriage returns during Excel export or be able to save off the Printable Page.
We added 2 custom fields for testing steps. The carriage returns show up in Printable Page nicely. But we can just print that. The Excel export doesn't keep them and so the steps are jumbled in each cell instead of a clean representation.
4 votes -
Add a custom field on child issues to show the structures root element
I would like to see the root element in the structure in the custom fields of the children so I can use this when exporting data from jira
4 votes -
Have a Back to Structure button in Issues
When you open the Issue to view/edit the full details, a link back to the full structure would be nice
4 votes
- Don't see your idea?