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.
31 results found
Be able to set icon other than green check mark for different resolutions
Currently if you resolve or close an issue and choose any option for the Resolution, the indicating icon is always a green check. I would like to be able to customize the resolution/icon combination. For example, set a red x if the resolution is incomplete, indicating that the task wasn't completed.
Also, there should be options about how this affects the progress of a parent issue.1 vote
Using Statuses instead of Resolutions seems the shortest path to solution
Field security concept is not supported by JIRA
It would be great if you can add Agile support.
Currently we use bugzilla for bug and feature requests tracking.
Deskzilla should have the ability organize the "bugs" and "features" into sprints, along with burndown charts etc.1 vote
Configurable fields for "+Sub+Issue"
We have the Component and Version fields configured as required for all issues, and so creating a sub-issue via the "+Sub+Issue" button fails since those fields are not available in the mini-create issue window. Is there some way to configure which fields are available in that window?1 vote
There is a way to enter the required fields: https://wiki.almworks.com/x/uoPE
Export to Excel File
Printing is fine, but, I also need to export to an Excel doc. Is that possible?1 vote
Don't break default browser functionality to open the links in a new tab
I show the Key and Summary columns in the Structure View. Both columns contain a link, but Control-licking the link doesn't open the link in a new tab, which is default behavior in all browsers. Somehow the Structure plugin must do something to break that1 vote
fixed in 1.7
If you manually change Epic field to point to a different Epic, the issue doesn't reposition under that Epic
If you manually move the ticket under an epic, it will change the epic field value to that Epic. However, if you manually just change the epic field value to something else it doesn't reposition the ticket under that epic.1 vote
not a problem
Support the control enter key for creating of new issues as specified in the keyboard short cuts
I really like the idea of mimicing the mindjet type keyboard shortcuts for creation of new issues. Control enter should create a new issue within the structure on the same level as the parent issue.1 vote
current keyboard shortcuts (Enter and Shift+Enter) are sufficient for creating issues and sub-issues
Add a slight delay during drag-and-drop (so that parent nodes don't expand instantly)
I think this will make it more easy to drag a child from one parent to another. It should behave like dragging files between folders in Mac OSX.1 vote
no reasonable improvement so far
Filter synchronizer should also scan newly created issues.
Newly created issues matching a filter are currently not added in structures synchronized with that filter. This causes issues to slip trough the cracks by not showing up in the structure.0 votes
already implemented; support investigation required
Preserve column selection & order in each individual Structure
Different Structures server different purposes: test plan, release status, planning board, etc.
Different goals call for different columns to be shown in each structure (based on purpose of each individual structure)
Currently column selection and order is saved globally and applies to all structures, whether it makes sense or not.
PROPOSAL: each structure keeps its own column selection/order0 votes
- Don't see your idea?