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.
118 results found
-
Propagate field values down the hierarchy
Let the user specify, for example, that all sub-issues of the issue X should have the same Security Level and Project and Priority.
65 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 -
Expose broken dependencies via JIRA native 'Integrity Checker'
ever seen this in the jira log?
2013-07-30 11:44:07,812 Structure-Jobs-aea1f3 Queue-Thread#1 WARN wama 642x189704x1 156cgam 10.7.30.226 /rest/plugins/self-update/1.0/ [ext.sync.filter.FilterSynchronizer] Filter autosync #52 for structure 'Quoting structure' (#138) failed to run: filter 14610 does not exist or is not available to wama
In my opinion, such notifications could be added to the 'Integrity Checker', section 'Check for invalid filter subscriptions'
Fix is straightforward -> remove the dependency
alternative: provide the same on the Structure administration page
1 vote -
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 -
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 -
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 -
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
-
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 -
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 -
When I change the query (the Find field), I would like the URL to be updated accordingly.
So that I can restore the state of the view from browser history (using back button etc.).
7 votes -
Open structure issues in Issue Navigator
Similar to functionality in Greenhopper and other plugins, add a button to structure to allow opening the list of issues visible in the structure in the Issue Navigator.
I use the Agile Cards plugin. It's possible to print cards from the Issue Navigator. I would like to be able to print cards for a portion of the hierarchy in a Structure but I have no way to get from the structure to that functionality. One possibility is to allow opening the issues currently visible in the Structure in the Issue Navigator.
It seems like this would be useful for other…
12 votes -
Use tokens in the summary to capture recurring fields and indendation levels
By specifying some fields e.g, priority and assignee as well as the indendation level of the issue while entering the summary text of the issue will speed up the data capturing with structure. Please consider having a look at www.checkvist.com for effective keyboard support for increased speed and useability.
Eg use the @ to specify the person eg @john
use the # sign to specify the priority
Eg #0 - blocker1 critical
Tab indentation in the summary for instance indentation level 1 specified by 1> indendation level of 2 specified by >2
1
2 votes -
Create sub-issue should work similar to Link New Issue Operation (LNIO)Valiantys
I typically want to create issues of another issuetype, and probably in another project.
Just cloning is too trivial, and it requires to much work to change issuetype, and project.Alternative (even better): automatically detect sub-issues for certain link-types
13 votesplanned after 1.0
-
Allow CSV Output of Information from Structure Board
It would be nice to have the ability to dump the structure board to a csv. Thinking that it would be something quick and dirty, with ' - ' noting structure, like this:
"Name", "Est Hours", "Progress"
"Mars Colony", "10h", "80%"
" - Terraform", "6h", "50%"
" - - Make Oxygen", "2h", "100%"
" - Create Colony", "4h", "0"Once this was CSV, it could be manipulated in other programs. Right now, I don't see a way to get the Hierarchy or estimate roll-up data out of the system for project managers to use.
3 votes -
7 votes
HJ-177
- Don't see your idea?