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
-
1 vote
fixed in 1.7
-
Under the structure gadget allow hiding resolved issues
Right now you can show/hide resolved in the structure page, but you can't on the gadget page. The shortcut "rr" does not appear to work.
1 vote -
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
-
Define additional Fields to aggregate Information (number Fields), e.g. suggested revenue
We use structure for many purposes like:
Artifact Structures (Epic, Story, Reqs) oder product based views on many projects. So it would be very useful if one can define a field in a strcuture, that ist aggregated to its parents (if possible) likewise the time aggregation.
There could be a Aggregate Field be defined, that uses the Value(numbered) from a custom field and aggregates it to the parent with options for the aggregates (sum, avg, max,min)14 votesDone in version 2.5: https://wiki.almworks.com/x/3ILR
-
Allow more advanced calculations to determine progress
Allow more advanced calculations to determine progress.
Not all User Stories or tasks are equal. The current calculation is a percentage of total tasks/stories. We should be able to weight the calculation based on Story Points, or any other field which contains a numeric value within the story.
30 votesReleased in version 2.5 – https://wiki.almworks.com/x/3ILR
-
Need to have a capability to hide the structure
Need a capability to hide the structure within the Issue itself.
Yes the structure group can be collapsed but we would prefer for structure not be even loaded when we view the issues.
Ideally this should be configurable by issue type.1 voteachieved by disabling structure module
-
When custom fields are required on ticket create, copy over the selected parent ticket's values
We recently upgraded to 1.4.1 from 1.1, and noticed that when creating new tickets we were forced to add columns in the structure for our required custom fields. Otherwise, we got an error. Can logic be added to copy over the selected ticket's custom values like it does for the standard fields?
1 voteIn 1.6, required custom fields are copied in “clone” mode: http://wiki.almworks.com/x/bYM3
-
Customs columns for every user
Changing the number and order of colums changes it globaly to all users. It wil be great to have an option to change it for every users too.
6 votesDelivered in Structure 2.0 – see release notes at https://wiki.almworks.com/x/9Aqf
-
91 votes
This suggestion has been implemented in Structure 3.4! Check out release notes: https://wiki.almworks.com/x/AYvrAQ
-
Associate a structure with a project
The structure-tab on a project page should (configurable) always show it's associated structure and not the "current" structure. If there is no associated structure, the tab should be hidden or show a creation view.
7 votesCompleted in 1.6: project can be assigned a “default” structure, and the Structure tab can be forced to switch to the default structure when opened: http://wiki.almworks.com/x/vIaF
-
Use filter to automatically add/delete children of a Structure
Say I have a Feature1, and I created a "Outstanding Feature1 Bugs" structure. I also create a "Outstanding Feature1 Bugs" filter which shows bugs in status other than Resolved nor Closed. I want to assign the filter to the structure so when I look at the structure, I only see the results of the filter. As bugs get resolved and closed, they get taken away from the structure automatically. Make sense?
1 votecan be done with Saved Filter Synchronizer
-
Allow to use issue hierarchy level in structure
We would like to add a parameter to structure function in order to specify the number of levels the function will retrieve.
For example, given the following structure:
Structure: 101
ISS-1
ISS-2
ISS-3
ISS-4
ISS-5
ISS-6
ISS-7
ISS-8
ISS-9structure(101, ISS-1) will return all the issues
structure(101, ISS-1, 1) will return issues ISS-1, ISS-2 and ISS-5
structure(101, ISS-1, 2) will return issues ISS-1, ISS-2, ISS-3, ISS-4, ISS-5, ISS-6, ISS-9
structure(101, ISS-1, 3) will return all the issues8 votes -
1 vote
Done as “Perspectives” – use “Share” button
-
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
-
Allow structures to be created via the REST API
I should be able to create structures via a POST request to the REST API and get back the newly-created structure details (id, name, etc) in the response. Also, if "templated" structures are added as a feature in the future, I should be able to specify which structure to template a new structure off of via this API request.
4 votesDelivered in Structure 2.0 – https://marketplace.atlassian.com/34717
-
Tags
A flat list of items, where each item can be tagged with tags, would be great.
Item should be filterable on multiple tags.
The problem with hierarchy is that you tend to waste much time wondering where to put or look for an item.
Also, often is the case where an item belongs to multiple categories, which is difficult, if not impossible, to represent in a hierarchy.
The ability to tag an item with multiple tags solves this issue.
0 votesJIRA’s Labels work as tags
-
direct editing of estimates
I enjoy using structure for summing of estimates. Often I find my self tweeking estimates and would love to be able to do direct inline editing of those fields too. In my version I can edit the title of the issue.
9 votesdone in version 1.4
-
Make the "Structure" entity available for JQL Queries
So that I can easily create filters in other parts of Jira. For example: I have a Structure called "Widget 1.3" which included Jira items from multiple projects. It would be nice to be able to write a JQL query like Structure = "Widget 1.3", and it would grab all the Jira items in the Structure.
2 votes -
I would like to be able to copy an existing issue and paste it under a different hierarchy in the same structure
I would like to be able to copy an issue and paste it under a different hierarchy in the same structure
8 votesThis suggestion has been implemented in Structure 3.0! 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 -
Add comment from Structure widget without page reload
Title was: Page reload after creating a new items should preferably be faster when working over slow speed connections
I sometimes work on my IPAD over slow speed link and the update of the page after creating a new item is quite long
2 votesDone in version 1.7 (although it is still a way to go for a smooth iPad experience)
- Don't see your idea?