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
-
JIRA OnDemand installable
Right now this plugin is not available for JIRA OnDemand, having used this at a previous company, it's a big pain point that it is missing in the OnDemand version.
4 votesSee details in this suggestion: https://structure.uservoice.com/forums/43181/suggestions/15698640.
-
Be able to show sum of "unresolved story points" and other number fields
Since I can have a progress bar weighted by story points and a column that can show the sum of story points - can we add a column that shows the sum of story points that aren't resolved (that is, if a ticket is resolved, it counts as zero - otherwise, add up the story points). I would think this probably apply to other number/summable columns.
This would really help our tracking view to see that some Epic has 45 story points not resolved out of 90 total story points.
(Apologies if this already exists - I can't figure out…
4 votesThis suggestion has been implemented in Structure 3.0! Can be done via “After filter” option and adding an unresolved filter.
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 -
List structure in search/filter
In Filters it is possible to output the subissues of an issue as a column. It would be nice if something like this would be with structures, too. (Maybe list parent as one column and direct childs as another..)
3 votesThe problem is solved differently – with Views | Show in Structure.
If that does not completely solve the problem, feel free to comment or suggest more ideas.
-
Link existing issues into structure
Possibility to link existing issues into structure. (Could be an existing issue/subtask that was created before structure was enabled for the project).
3 votesAs of version 0.2, a structure can be constructed (and reconstructed several times) from the existing subtasks.
Use Administration | Structure | Import Structure menu.
-
...ucking amazing!
My mind is blown away =)
3 votes -
Creating a JQL query from a selection of issues in support of batch configuration within Jira
Currently there is a need to batch update certain items in a hierarchy e.g. assigning of tasks to different team members. It would be beneficial to allow a selection and then carry this selection over to Jira for batch configuration
3 votesDelivered in Structure 2.0. See details in release notes link from https://marketplace.atlassian.com/34717
-
3 votes
done with editing keyboard shortcuts in 1.4
-
Allow structures to be listed via the REST API
I should be able to request a list of all available structures via a GET request to the REST API, and get back a list of structure details (id, name, etc) for each structure in the response . Today I can query individual structures via the API, but there's no way to get a list of all available structures.
3 votesDelivered in Structure 2.0 – docs are at https://wiki.almworks.com/display/structure/Structure+Resource
-
Enable customizable, saveable views
In different situations one needs different sets of columns shown in the structure. To change the columns shown (and their width and position) in different recurring situations is inconvient.
So it would be perfect, if it was possible to save the columns (and position/ width) shown in a view (for the user only).
(Perhaps in a future version even as shareable view -> similar to the views in the greenhopper planning board)
3 votesDelivered in Structure 2.0 – https://marketplace.atlassian.com/34717
-
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.
-
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
-
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
-
It would be greate to have direct links for views
Hi,
we would like to present Structure in our TV's for public, etc. But we are unable to point webbrowser to exact view in structure. It would be great if link to structure board also contains view parameter to point directly to that view.
Thanks
3 votesImplemented as “perspectives”
-
Show or Separate available structure dropdown in issue details to structures containing that issue
When looking at an issue, if it exists in a board other than the default, you have to know the structure to switch to. It would be much easier if the structures that actually contained that issue were highlighted or somehow separated from the others.
3 votes -
Extend API to list/add/remove projects to "Structure enabled for projects"
In bigger environments projects are usually created with a script. If a project needs structure you have to manually add it to the list of Structure enabled projects.
It would be great to have this administration capabilities (list/add/remove) provided by an API (REST API preferred)3 votesfunctionality exists – see comment
-
Read-only structures that automatically resync monodirectional
When resyncing a synchronizer, it works monodirectional. But when it is enabled and running it works bidirectional.
When mixen different synchronizers (e.g. Agile and Link synchronizers), bidirectional synchronization may cause a cascade of changes from Jira to Structure and vice versa. This may have an undesired effect on the relationships between issues.
A read-only structure (or monodirectional synchronizers), the structure can be used as a real-time visualization of the relationships in Jira.
3 votesThis suggestion has been implemented in Structure 3.0! The feature is called “Automation”.
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 -
With Structure 3.x, it would be nice to be able to minimize the Header Tool Bar to give more real estate to the Structure
With Structure 3.x, there's too much space in the header now leaving almost half the screen for the Structure. It would be nice to be able to minimize the header tool bar like JIRA Agile allows.
Also, it would be good to minimize the Transformations tool bar with the quick filters selected still active. Currently, you have to click X to the right of the Transformations tool bar which deselects the highlighted transformations.
3 votes -
Allow reordering of the quick transition filters
When you need to add a new quick transition and save it as a quick transition, there is no option to drop and drag this new transition into the current order. We are trying to keep our quick transitions in alphabetical order to make it easier to navigate, this isn't currently possible.
3 votesThank you! please check the comment
-
Separate Effort from Duration. Gantt should show the duration independent from the effort estimation.
Duration depends of the availability of resources. Gantt should show how long the issue will take to close, For Stories the duration is given by the sprint. For Epics there is no possibility to hold this information and show it in the Gantt, using the Effort field for this information is completely the wrong way.
3 votesWith the release of Structure.Gantt 1.4 it is now possible to enter Effort and duration independently. Please, see https://wiki.almworks.com/x/C7W9Aw for more details
-
Filter work log author using groups
We can currently use the "Work Logged" column and specify an individual user to see his or her work log.
It would be very useful if we could have the option to specify a group instead of a user, and see all time logged by any member of that group.
For clarity, we'd like this in addition to the current functionality rather than replacing what's there.
3 votes
- Don't see your idea?