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
-
Search Result Panel: option to display other structures with their hierarhies
It would be great if Structure has an option to display other structures in search result panel, not just list of available issues in JIRA by search criteria.
For example, user may select from the list of available structures to display in search result and add issue with all its hierarchy tree to his structure.
Permissions apply, of course.A few point that I thought of:
1) User must have "view" permissions to view and select the structure from the list and add issues to his structure.
2) Permissions should apply on the issue / project level. User should not…1 vote -
let users do Move up / Move down voting
We've been working with a structure for product planning. We rank candidate improvements top to bottom. I'd like to have a casual "vote up / vote down" button for each row. To use I'd reset the votes and then ask viewers to vote away. We'd all sit and watch the voting tally increment as the structure updated. After a few minutes we'd stop and then prioritize and reset the votes.
I'd like to be able to see who voted and when they vote prompt them for why.
1 votewaiting for requirements clarification
-
Deleting of items should also be possible with a short cut key combination - not only removing the items from the structure
Preferably without requiring an acknowledgement. The aim would be to mimic the speed of mind mapping tools for capturing information in meetings. One of the issues is if one wants to delete a item it should be as fast as creating one
1 vote -
Link issues in a hierarchy as you move issues around in the Structure view
Currently, when you clone a subtask and move it to another parent issue, it actually remains (for all intents and purposes of JIRA data) as part of the original parents issue.
This is a problem, because in Greenhopper on the planning board (where you move User Stories to actual date defined releases), they have to reflect the same structure as you created in Structure.
4 votesWaiting for response
-
Display a collated view of multiple structures
As a release manager, I want to see multiple structures represented in one view so I can easily collate the work multiple teams are doing. Our planning and management of structures is distributed, but I need to be able to see them all for enterprise planning purposes. Additionally, I want to be able to filter the one "master" view so I can see only those items related to specific criteria (e.g. release or project or component).
3 votescollecting requirements
-
Strikethrough on closed or resolved issue
A closed or resolved issue should have have a "strikethrough" on the summary.
10 votesPossible as per-user CSS customization feature
-
Header/Footer for Print & PDFs
Add ability to edit header and/or footer for print outs. Include fields for Date/Time Printed, Structure Name, Etc.
2 voteswaiting for comment reply
-
5 votes
-
When displaying subtasks in Structure, include parent jira # as part of summary (like Jira filters)
When displaying subtask in Structure, include parent jira # as part of summary (like Jira filters).
4 voteswaiting for clarification
-
Propagate Due Date
Allow users to set due date based on due date of parent and estimated time. Plus when due date of parent is changed propagate change to all child issues accordingly
4 voteswaiting for clarification
-
8 votes
-
1 vote
-
Create shortcut key for setting tasks on Resolved
A shortcut to set a task on resolved would be appreciated.
6 votes
- Don't see your idea?