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.
173 results found
-
Drag and Drop Structure Nodes into JIRA Sprints
It'll be great if I can drag my structure into my sprint and have all the sub issues displayed nicely (incl estimated story points or hours for all sub issues) under that sprint.
1 vote -
Show more results to allow me to use the browsers scroll function.
The view port of the structure plugin is rather small. I can only see a max of 12 rows on my screen (1360x768). I need to export to excell to see more stories in my epic. It would be nice if more results are displayed on the screen. And to be able to use the browser's scroll bar to scroll, that's why it's there. Or did I miss a config option?
4 votesinvestigating – please see comment
-
expose a structure's "order" so JQL queries and filters can be created to list issues in that order.
The order's created would be very handy to be able to query in JQL - something like: project = MARSCOLONY AND assignee = "cosmonaut" ORDER BY "taskorder1-structure" ASC
This would allow exposing structures in Confluence and other places in a useful way.
Not sure what to do about different levels, but initially just ignore issues that aren't at the top level?
9 votes -
Improved User Interface of the STRUCTURE Plug-In
The font and back ground colour should be customizable.
1 vote -
1 vote
-
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
-
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
-
Automatically clear multi-selection after a move/paste operation is completed.
The structure plug-in allows users to select multiple, dis-contiguous issues using the multi-select mode, whereby the user clicks on the little radio button next to every issue they want to select. The selection can then be operated on as a whole, for example, to reposition the issues in the structure.
This feature works great, however, I find it annoying because the selection 'sticks', even after I've completed the operation I wanted to perform. Then, when I move onto select other issues, the previous ones, which are still selected, unintentionally come along for the ride.
Let me provide a use-case. Assume…
4 votes -
Create a method to prevent parental and causal links to sub-tasks unless those sub-tasks have sub-issues
if you have issues with sub-task type issues there's no way to pull those sub-tasks and any child or resulted in linked issues into a structure without structure creating child and resulted in links for all sub-task tasks of those parent issues. It appears that any configuration of the links synchronizers will results in the sub-tasks getting child and resulted in links to the parent issue. If this is true, I propose the following feature request.
In the Links Synchronizer, create a sub filtering feature that uses the logic of: "don't create parental or causal links for sub-task type issues…2 voteswaiting for clarification
-
1 vote
Will review after Structure 3.0 release
-
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 -
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
-
Add a "quick search" feature in structure drop down menu
Currently if you want to find a structure that isn't in your most recent or top favorite you have to go to the more... option in the structure menu to find it. This means navigating around to other pages to search for a structure. It would be much nicer if there were a filter / quick search at the top of the menu that lets you quickly find and view a structure.
1 vote -
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 -
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 -
Ability to compare percentage realized versus percentage predicted (as a new calculated column) on the structure.
Igor,
I wonder if it is possible to create some kind of calculated column to show the percentage of the predicted structure for the current moment.
Obviously if the issue had any reference date (ie due date) for comparison and the grand parent issue too. Just like we do on a project via MS Project.
This is to compare how we are, in percentage terms (functionality already implemented) versus how we supposed to be (forecast until the present day).
I leave here the challenge to improve (even more) this fantastic ADD-ON.
Cheers!
1 vote -
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 -
Structure Filter improvement: project without structure enable need a hint from the plugin
When use a JQL with project field and the project have no flag to support structure show a hint warning the user that needs to enable the support to structure, or will be excellent to choose to enable it.
The current implementation only shows no search results.
The uses get confused and don't know if the plugin is working or they are doing some misconfiguration.9 votes -
Allow me to include explanatory text
I build Structures for people to look at. There is always a type of interpretation I need them to make.
So, I need the ability to put at the top and bottom of the page an explanation of what they are looking at and how they should read it.
For instance, on a budget, to say "this sum of Remaining Estimate field is shown as 1w1d5h but should be interpreted as X hours; Export to Excel, total the field and multiply by our hourly rate * 24/8 for a billing number"
Else people land on the screen and say "so…
1 vote
- Don't see your idea?