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
-
Have columns that aggregate time information - total time spent, total estimate, etc
The column would aggregate time fields upward and display time spent, original estimate and remaining estimate for issue and all its sub-issues. Also we can use the colored bars as in the Issue Navigator
10 votesAvailable in version 1.4!
-
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
-
Allow us to make structures "sticky" for issues
It makes no sense to switch structures for a given issue, so why is it designed this way?
eg http://tracker.moodle.org/browse/MDL-30971
Once an issue is assigned to a structure, then that structure should be chosen by default whenever you visit that issue. At least make a setting that allows us to force this.
The other related problem is that issues not in structures show an error: "This issue is not in the selected structure.". This is extremely confusing to people viewing those issues, as it's not likely that this issue should belong to this or any other structure. I would like…
9 votesCompleted in 1.6 with auto-switch settings, see http://wiki.almworks.com/x/vIaF
-
Take into account the epic/story link type in GH
Take into account the epic/story link type in GH
9 votesThe GreenHopper synchronization has been introduced in Structure 1.0-rc1. One needs to set up synchronization for a structure, and then GH Rank and Epic/Theme field will be kept in sync between Structure and GreenHopper. Short video about how it works: http://youtu.be/QfTJruOYUE8?hd=1
-
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
-
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
-
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 -
That JQL button needs to be more visible!
Folks who are new to Structure can't tell what that JQL button is set to. The faint red border is no readily visible. They get confused as to which search mode is active.
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 -
Issue batch update for Status and Assagnee fields
It would be great if there was an option to update at the same time more than one issue. For example, parent issue and all child issues at once.
8 votesBulk change feature delivered in Structure 2.0. You can now select multiple issues and use JIRA’s bulk change wizard with them. See release notes link at https://marketplace.atlassian.com/34717
-
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 -
Add controls to expand / contract one level at a time
...in addition to the controls that expand / contract ALL. First click expands level 2; second click expands level 3; etc.
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 -
Provide an automated backup mechanism similar to Jira and/or a command line interface to initiate a backup.
Jira allows automated backups to take place. If I install Structure, I need to manually initiate Structure backups. It would be preferable to have automated Jira and Structure backups.
7 votesAvailable in 2.1
-
JIRA Dashboard gadget for cloud
JIRA dashboard gadget would be good showing a pre-defined structure.
7 votesThe feature has been implemented. Structure data can now be displayed on the Jira dashboard, alongside other reports.
-
BUG: Issue links are lost if the same issue is linked to more than one issues
GOAL
When I add a story/bug to Structure, I want all linked test cases to be added automaticallySETUP
Create and enable the following Synchronization
Issue Links
Links (Test Coverage)
Parent issue Test Coverage sub-issue
Parent issue JQL: issuetype in (story, bug)
Sub-issue JQL: issuetype = "Test Case"
Sync issues in structure and all sub-issues linked from them
Move sub-issues with no incoming links upwards
Links primacy
NOTE: “Test Coverage” is a custom link typeUSE CASE
a) Link TestCase1 and TestCase2 to StoryA through “Test Coverage” link type
b) Link the same TestCase1 and TestCase…
7 votes -
Save Transformations as Favourites for Re-Use
We've just got Structure plugin v3.0 for JIRA and the new Transformations function is great! Especially the JQL Query and the fact you can add multiple queries to build a filter - very handy for quickly switching back to a more general query.
The only problem is that when you go to a different JIRA section and come back, or you log out (to go home) and log in (in the morning) you have to rebuild the Transformation again. We're currently saving JQL in Notepad for easy copy and paste.
The ability to save Favourite JQL queries and apply one…
7 votesDelivered as Quick Transformations in Structure 3.4
-
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
-
Show a hierarchical view of the Epics/Stories/Tasks within one project
Show a hierarchical view of the Epics/Stories/Tasks within one project in Jira to provide an overall picture of the complete work package.
7 votes -
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)
-
Bulk edit for selected items
Structure Cloud should have the option to bulk change selected items in the structures or at least open the selected items in the Issue navigator.
This would be a massive time-saver!
7 votesHi Martin,
Thank you for reaching out!
I'm happy to let you know that now you can bulk edit up to a couple hundred items at a time.
You can learn more about our latest update here: https://structure-cloud.releasenotes.io/release/L10Ds-text-wrapping-and-quick-grouping-are-coming-to-structure-cloud
-
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
- Don't see your idea?