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.
158 results found
-
In Confluence gadget, specify the top issue to view for the selected structure
So, if I had:
ISS-1
- ISS-2
-- ISS-3
-- ISS-4
- ISS-5
-- ISS-6The result of specifying ISS-2 as the top-view issue for the structure (similar to pinning ISS-2) is that only this tree would be visible in the Confluence Gadget:
ISS-2
- ISS-3
- ISS-419 votesReleased in Structure 3.5
-
Ability to create template structure that has the synchronizations already in place.
In order to make it easy for our non-technical users to set up their structures, I would like to be able to create a template for them to copy.
An example of a template is to set up the following automatic synchronizers: linked issues, sub-tasks. The users can then copy the template and pull in whichever parent issues they want to using the search. The new structure will automatically synchronize off of the parent issues accordingly. The idea is that the users would not need to worry about the synchronizations - each structure would operate the same way for consistency.6 votesThanks for the feedback! Structure 2.9 is just released and it supports copying synchronizers from a template structure. See details in the release notes: https://wiki.almworks.com/x/uIQlAQ
-
Add last comment as a column
Comment can be used to know the current status along with status of jira. Therefore, it will be great if last comment can be displayed.
25 votesLast Comment column is available in Structure 6.2
-
Allow owner of a structure to be re-assigned after the structure is created
When we have someone leave the company or change roles it would be very useful to be able to re-assign structures they created to others. Also, we have some people that are good at creating structures and then pass them on to others for maintenance. It would be good to change the ownership at that time.
10 votesThanks everyone for supporting this request. Structure 2.9 is just released and now JIRA administrators can change the owner of a structure. Details in the release notes: https://wiki.almworks.com/x/uIQlAQ
-
Aggregate the number of sub-issues in the structure
The aggregated number of sub-issues should/could be visible in the Structure.
I don't care if the information is something you can annotate to the structure by "add column", or if it is something you get by default.
4 votesThis suggestion has been implemented in Structure 3.0! Use “Attribute” columns and “Sub-items count” attribute.
Note that Structure 3 has a lot of changes, check out release notes: https://wiki.almworks.com/x/5gquAQ
Quick start guide: https://wiki.almworks.com/x/zwquAQ -
You should be able to make multiple JIRA actions selecting several issues from the structure
I would like to select more than one options in the structure and make a JIRA action for all of them, like assign several issues to a developer.
3 votesimplemented in Structure 2.0
-
Entering Saved Filter in Search doesn't display results
In the Search area next to Find:, if you enter a Saved Filter, it doesn't bring back any results. When you hover over the text area it says "Enter text, Saved Filter Name, Issue Keys or JQL to search" but the option of typing in a Saved Filter Name doesn't appear to work. Currently using 2.7.
1 voteThanks Pat – we’ve fixed the misleading hint in version 2.1, coming up soon
-
Structure tab on RapidBoard should act the same as a structure section in issue details
Structure tab on Greenhopper's Rapid Board should act the same as a structure section in issue details, because it is not logical to show whole structure on a Rapid Board issue details - only issue concerned structure should be shown and there should be an ability to add sub-issues to it.
Whole structure should be shown in another place!
Please see the clarifying scrshot here: http://clip2net.com/clip/m19270/1356375863-clip-104kb.jpg3 votesstarting with Structure 2.1, “pinned” mode is on by default
-
Allow a structure to be deactivated
Once a project is complete, I'd like to be able to mark the associated structure as inactive so that it no longer shows in the drop-down menu on the Structure tab. I could do this by deleting the structure, but I'd like to be able to save it in an "archive" state so that I can view it for historical/reference purposes. I could also do this by backing it up and then deleting it, but it would be nice if it could be done with just an attribute on the structure.
23 votesImplemented in Structure 2.9
Documentation – https://wiki.almworks.com/display/structure/Archiving+a+Structure
-
Adapt aggregation of Time Tracking fields with filter
Sum up the Time Tracking fields of shown issues only.
When I apply a filter, I want to see th aggregation results of the resultset only (filtered issues).
So we can look at all aggregations (and sub-aggregations) for a specific Sprint or Release....115 votesThis suggestion has been implemented in Structure 3.0! There’s an option in the aggregate columns now, “After filtering”.
Note that Structure 3 has a lot of changes, check out release notes: https://wiki.almworks.com/x/5gquAQ
Quick start guide: https://wiki.almworks.com/x/zwquAQ -
Be able to link to a view such as Tracking, Basic, Planning
Much like http://structure.uservoice.com/forums/43181-structure-plugin-for-jira-ideas/suggestions/3057494-be-able-to-link-to-a-pinned-structure-view - I need to be able to send people who might never have seen JIRA straight to the right place.
Thanks,
M.4 votesImplemented as “perspectives”
-
provide a synchronizer option for the rapid GH boards to update the "Epic Link" field.
The new GH boards from 6.0.6 on feature a different implementation to link stories to epics. The new relation is kept in the "Epic Link" field. It would be very handy if structure could also provide an option to sync into this GH field and thereby fully support the new rapid boards.
8 votesImplemented in 2.1
-
support issue creation using extended form (CreateIssueDetails)
So that it could be possible to configure Structure Plugin to open extended form instead of the one with just a summary as it is by default.
31 votesImplemented in version 2.7
-
Deletion of items inside the structure should have a confirm dialog
Some one could by an accident hit the delete button and zap all the work done to build up the structure. And the trash isn't so trustable to solve this as it is empted when you navigate out of the structure screen.
7 votesSingle-action undo released in 2.1 (not a confirmation dialog)
-
a quicker way to create a new structure.
Im loving strucutre but one thing that green hopper has over structure is its ability to instantly be usable for a new project. For structure the quickest way I have to make a new project is i have to make a new filter searching for all assets for a project, then I need to create a structure and have it sync with that saved filter. It would be awesome if there was a single button that did that action for me so with a single click or selecting of a project name i could have a structure built.
1 voteIntroduced in Structure 3 as templates when you create a structure via Structure | Create Structure menu
-
a button in the tool bar to "show only my issues"
one of the most useful quick filters in Greenhopper is the "show only my issues" filter. It would be fantastic if Structure had this top level quick filter in its toolbar as well.
2 votesDone in Structure 3.4 with Quick Transformations
-
Be able to link to a pinned structure view
Once I "pin" a portion of a structure, I want to be able to email a URL link to someone so they go directly to the pinned view. With a large structure, this would be more useful than telling someone to find a particular branch in the structure.
5 votesThis suggestion has been implemented in Structure with a lot of other features!
Note that Structure 3 has a lot of changes, consider to look at the quick start guide: https://wiki.almworks.com/x/zwquAQ -
3 votes
Deleting a node with sub-tree is done with “Delete” button on the toolbar. Deleting all issues in a subtree is now possible with Structure 2.0 and Bulk Change feature.
-
be able to share Structure config info across browsers or users
Structure seems to store configuration info in cookies not server side so that the setup info isn’t shared across browsers or users. Not great for team collaboration.
1 voteDelivered in Structure 2.0 – https://marketplace.atlassian.com/34717
-
perform operations on multi-selection lists
In Structure there is the multi-selection capability but it seems like it has limited usefulness. For example, if I want to remove 10 issues from Structure I can't multi-select them and use the "remove" button at the top of the widget. Similar for other operations (indent, etc.). What would really be handy and a possible workaround would be a button that allowed multi-edit (simlar to the "Bulk Change" operation in the JIRA Filter View). A typical use case for this is wanting to update the "Fix Version" for a set of issues that have been deferred to a later relase…
12 votesBulk change (both hierarchy change and JIRA bulk change wizard) delivered in Structure 2.0.
https://marketplace.atlassian.com/34717
- Don't see your idea?