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.
374 results found
-
Use JIRA Structure as navigation tree on linked Confluence content
JIRA & Confluence are often used hand-in-hand... e.g. new ideas are formulated on CFL, leading to linked tasks in JIRA & followed by documentation etc.. on Confluence again..
The need to reorder issues in JIRA, & use structure to navigate them, can be projected to linked confluence contents as well.
The way i see it, structure widget could replace the space navigation panel.
JIRA issues & corresponding Confluence pages could be linked via labeling (value == structure item ID)
This is the idea in a nutshell, I'd be happy to discuss in more detail if helpful.
6 votes -
Include "Epic Link" in Categories that are copied when adding issues
The ability to add issues directly in structure is great. Especially when using the "Copy from" categories option to have a new ticket inherit a lot of values from another ticket. It would be REALLY useful to have "epic link" among the list of included fields that are copied. I've used the "required fields" workaround for other fields, but unfortunately "epic link" cannot be made required.
6 votes -
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
6 votesThank you for idea! please check the comment
-
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… -
Earn Value Management Formulas
Formulas for project tracking: Earn Value, Cost Performance Index, Schedule Performance Index, Estimate at completion, etc using cost from Tempo
6 votes -
"Remove Inserter/Extender Duplicates" generator should also work for non-hierarchical duplicates
When using the "Remove Inserter/Extender Duplicates" generator also non-hierarchical duplicates, based on different used linkage types like "child-of" and "resolved by" should be removed.
6 votesThank you! Check the comment, please
-
Group by Due Date
I need to be able to group by Due Date, so that we can see the progress of all items assigned to a particular date. It seems like this may have been solved in server but not in cloud.
6 votes -
Allow multiple simultaneous updates
The edit capability in the table view is very helpful but even more helpful would be ability to update multiple fields and/or multiple issues. Is copy a row or column or table from Excel into structure table.
6 votesthanks! please check the comment
-
add custom fields to structure-folders
Budgets are often not added as issues. Structure could add value by allowing some limited amount of named custom fields on structure-folders (like notes, but some more). They would bind to a structure and could be accessed from formula columns.
6 votesThanks! Check the comment, please
-
"Effectors" feature for Structure Cloud
Hello, our organization is using Structure apps for our projects management. We just discovered, that in Jira DC/Server the Structure app has a feature called "effectors" https://www.youtube.com/watch?v=oE1dSklL9D8 . Could you add this feature to the Jira Cloud Structure app? If there is any chance to raise the priority of this feature in your roadmap - it would be great!
This is one of the most important features for us.6 votes -
Flag items in the structure
Hello,
I would like to be able to flag items in my structure tree view in the same way as I can on my JIRA Kanban board and JIRA Kanban backlog. The original Atlassian feature is described in https://support.atlassian.com/jira-software-cloud/docs/flag-an-issue/Jens
6 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
6 votes -
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.
6 votesThank you for your suggestion!
-
show more bars for one issue in a row (use more than 2 datepicker fields)
In our issues we use more datepicker fields, e.g. Start Phase 1, End Phase 1, Starte Phase 2, End Phase 2 and so on.
I want to show that bars within structure gantt, so not only one bar for one issue but several bars next to each other for one issue to show that time periods.
5 votes -
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?
-
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.
-
5 votes
-
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!
-
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
-
Integration with insight
The step forward for structure development - adding a posibility to work with insight objects inside formulas or in more UX attractive way. Such integration will provide unlimited power for structure to produce any type of dashboard / timeline / resource plan etc.
5 votes
- Don't see your idea?