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.
387 results found
-
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 -
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 -
Not show tasks and subtasks when using the GreenHopper's Rank and Epic/Theme fields Syncronize w/ auto-add subtask deselected
when selecting the Greenhopper syncronize w/ the epic/theme field selected and the auto-add subtask option deselected, structure is still bringing in tasks and it's subtasks. We were expecting only to see Themes, Epics and Stories in our structure. In addition, when we have Rank syncronize selected as well, it doesn't always line up with Greenhopper.
1 votesupport request in progress
-
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 -
Possibility to disable/filter the Structure notifications in the project & user Activity Streams
Currently only the Actitvity Stream "gadget" has the option to configure filters.
The standard (non-gadget) Jira Activity Stream on the Project Summary page & on the User profile page does not have this option. Hence these Activity Streams are heavily 'polluted" with Syncronizer updates and are becoming useless..3 votes -
Calculate context-aware Progress
When displaying structures in a specific context (for example, after selecting a specific Version from the Project view), the Progress roll-up should be done in the context of that version.
For example, assume I have an Epic containing multiple stories which will be completed across several releases. If I view the structure in the context of the upcoming release, it would be nice if the Progress calculation were based solely on those stories targeted for the upcoming release.
2 votes -
Automatically create issues to represent structures
Allow structures to have attachments, comments, workflow, etc by creating an issue for each existing structure. This could be automated by the Structure plugin.
Let the administrator configure a special project / issue type for those issues.
4 votes -
Export to Excel is good. With a view to importing to Project need additional fields such as due date.option to configure fields to export?
An ability to specify the fields to be exported such as due date etc etc.
1 vote -
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
- Don't see your idea?