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.
384 results found
-
Allow ignoring specific projects from rolling up status to parent issue in status soll up synchronizer
We use the status roll up synchronizer to signalize on an story the status of the implementation task which are childs of the issue using the structure plugin.
But besides implemenation issues there also may be issues beneath that story which are not related to the implementation (e.g. project management tasks like verifying the implementation).
So it would be perfect to select the projects from which statuses are rolled up to the story.
Just like the selection on the parent itself, a selection of the childs (project/ issuetype) could be useful to take only the relevant child issues for the…
1 vote -
Retain hyperlinks when printing a Printable to a PDF
The Excel report retains hyperlinks back to the issues. The preview of the printable also does, but these are lost when printing to an actual PDF.
1 votewaiting for reply
-
show full name in issuetype's column, such as status
Now it's only icon...
1 vote -
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 -
Ability to default Structure gadget in Confluence to display fully expanded rather than Collapsed
Currently, when inserting this gadget in Confluence, the Structure is completely collapsed. Is there a way to give the user the ability to change the default setting for the structure to be fully expanded?
1 vote -
In a multi project
In a multi project scenario can we have a scattered epic(collection of stories implemented by different projs) to be tracked as part single structure this will allow big programs to be tracked for their distributed progress in individual queues and collective status at one place for decision making.
1 votewaiting for reply
-
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
-
Have a right click contextual menu instead of the gear and hover that sticks to the far right forcing me to scroll every single time I edit
Right now everytime you edit a structure item (eg change status or Link to another issue) when the screen redraws the focus is forced to the bottom right. This then requires the user to have to scroll first before they can take any further action on a structure item. I find I have to do 10 - 15 unnecessary mouse transaction to edit a test case, block it and then link it to the blocking item
1 votewaiting for reply
-
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
-
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 -
Need additional mark for Closed issues
Structure shows check mark when issue is resolved, but I want another mark if issue is closed!
11 votes -
Combine multiple filters for synchronization
Say I have two members in a structure, Epic1 and Epic2. I created two filters, Epic1 Resolved Bugs, and Epic2 Resolved Bugs, and created synchonized filters accordingly. Now I see all the Epic1 resolved bugs under Epic1, and Epic2 resolvedbugs under Epic2, as expected. Now I just want to see resolved bugs fixed at a certain version. I'll have to edit each filter to accomplish this. It'd be nice if I can AND a "Fixed by VersionX" filter to ALL the filters, and then just change this filter everytime.
1 votewaiting for response
-
Show native JIRA Screens when creating and/or editing tasks in the structure view
I really appreciate the ability to edit tasks directly in the structure view. However, doing so results in two undesired side effects:
If the user needs to change multiple fields, they have to do so one field at a time. Depending on the notification scheme, this can result in a lot of email spam.
It encourages users to change fields on the issues without entering associated comments. For example, if somebody is changing the Fix Version/s for a task, in our team, we expect them to enter a comment explaining/justifying the change. There is no way to enter a comment…
0 votes -
Combine structures
Structures Seouls be able to be added up
1 vote -
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
-
add user stories w/out subtasks automatically to the product backlog by using the greenhopper epic synchronization
There is a separate setting to auto include the sub-task, by I am sure I didn't tick the box (I tried it 3 times).
It looks like the synchronization is always adding the sub-task regardless if you want them or not. This has worked before but recently I get the sub-task in the product backlog as well. We recently upgraded from 5.7.2 to 5.8.6 so maybe something in 5.8 broke this.1 vote -
Make scheduled auto-resync with filters
For adding / deleting issues from the filter in background mode
1 vote -
Show hierarchy on filtered issues
When you filter with JQL in structure, the hierarchy below is not shown if sub issues don't match the filter.
1 vote -
Add editing roles for users
Lock specified users for editing just specified (or their) issues.
Give ability for specified user create issue subtasks, change estimates, etc. but lock title editing, assignee1 votecollecting requirements
-
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
- Don't see your idea?