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.
373 results found
-
Allow admin to set default permission scheme for new structures
Structure defaults to no permissions to anyone. Admins should be able to set a default permission scheme for any new structure that is created from that point on.
3 votes -
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
-
support project roles in JIRA
Structure currently only supports permission groups but not project roles. If a project is set to support project roles then there could be surprises if some users are part of the right role but do not belong to the groups that Structure has been permitted to.
3 votes -
Use lightboxes when managing structure properties
Currently when editing a structure (Operations->Configure), you are throw into a new page for editing. When you are finished and go back, the structure list reloads and moves you to the top and I cannot find my place anymore. This is a problem when you are viewing a list of over a thousand structures.
A popup lightbox would make things much better and allow me to keep my place in the list of structures. This could apply to sync settings, and all other management operations.
3 votes -
allow a status synchronizer to allow rollups based the first subitem entering the next stage
The status synchronizer allows as of today(2.0.0) only a rollup of the status to the parent when all children have reached this status (i.e. all children are "done" > parent is set to "done").
Imagine a workflow like: open > in progress > done.
For the status "in progress" it would be great to have a "roll-up once the first subitem enters a new state". So the parent reflects the new status once the first sub-item has been moved from "open" into "in progress".
3 voteswaiting for reply
-
Allow to see the structure in the issue type 'Test'
When viewing an issue of type “Test”, created by Zephyr and assigned to a Structure, we are not able to see the corresponding Structure section as expected. If we change the type of the issue to anything else (Bug, Story, Epic, etc.) then the Structure section becomes visible. It seems that either Structure or Zephyr is not playing well together. This is critical to our organization as we try to integrate structured testing into our organization.
3 votes -
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 -
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
-
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 -
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
-
Add link to documentation and resources from toolbar drop down menu
I'm the admin and know of and installed structure, however, my JIRA users don't know what it is or how to use it. To help educate all please include links to helpful resources in your toolbar drop down such as documentation, etc.
Thank you
3 votes -
Extend Sub-Task Synchronizer with JQL filter
The Sub-Tasks Synchronizer only allows to select the Issue-Type to be selected. It would be helpful to have a JQL field to filter out more and also to have a JQL field when a Sub-Task should be removed from the Structure.
3 votes -
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
-
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
- Don't see your idea?