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
-
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
-
Allow the secondary panel to show another structure
When copy/cut and pasting between structures, it's useful to be able to see two structures on screen at the same time.
Currently it's not possible to show two structures side by side, and then copy or move between them. This should be achieve fairly easily by allowing the secondary panel to view a secondary structure.
1 vote -
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 -
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 -
Testy: need IN PROGRESS status for test coverage
Some of our tests may run for hours and none of the existing statuses (Passed, Failed, Blocked, Skipped) are applicable.
Please add IN PROGRESS status for test execution.1 vote -
Allow parent and child issues with different issue types
In fact, if you have a parent issue of type X (with field 'aa' mandatory) and create a child of type Y in another project that does not have 'aa' field, Structure disallows to create child issue saying that 'aa' field is mandatory...but it's not in type Y
1 vote -
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 -
6 votes
This 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 -
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.
-
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 -
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
-
Create a new Youtube video!
The video on youtube is 2 years old. The look of Jira has changed and I'm sure your features have also. For training purposes, it would be great if I could point to an official video instead of having to make my own.
Cheers
4 votes -
When "COPY"ing a Structure, provide the OPTION to "COPY" the Syncronizers
The ability to COPY these synchronizers provides the ability to keep all the roll-up and issue synchs consistent across all structures. currently, we need to rebuild all the "status rool up" synchs for all structures, having to make sure we keep them consistant - we utilize a KanBan type process so we have about 25 different status' that need to be rolled up properly, for EACH structure. The COPY SYNCH will allow us to create a TEMPLATE that will have all the SYNCHS consistent across all Structures.
1 vote -
i need a view that allows full view of the description column.
i need a view that allows full view of the description column. that way I can have the power of the Structure add-on with a view similiar to the descriptions column of the issue navigator.
1 vote -
Enter JQL instead of a filter in confluence structure gadget
It would be great to enter JQL or S-JQL instead of only filters like in the jira-issues-macro. In this case you wouldn´t be forced to create a filter first before adding a structure to a page. In the dashboard-structure-gadget in jira it is possible to select "Advanced" options, but not in Confluence.
13 votesReleased in Structure 3.5
-
Create a setting that will disable the plugin's ability to delete links.
When using multiple synchronizers sometimes a lot of links get deleted and we are unable to restore them without a bulk undo functionality. We use Structure mostly to visualize hierarchies and never to edit them. Therefore, it will be great to have a setting that would prefer the board from deleting links and allow our users to use Structure at a broad scale. As of now, we have to restrict its usage to a select few who know how to use it without breaking links
5 votes -
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 -
In the gadget, provide a link to the full structure (at the bottom, like the results filter gadget)
The structure gadget is helpful for building a dashboard of important lists, but it doesn't have full functionality of a structure. It would be nice to have a link at the bottom of the gadget you can click to go directly to the full structure for all the needed functionality
1 vote -
Have a way to show Release and Sprint parent level in the structure
I couldn't find my way to do that so I am guessing it is not yet available.
Trying to use Structure to show a Plan of the activities in an Agile/Iterative way, I am expecting that my full Project/Product Plan would show the different Releases, each one with their Sprints and underneath the collection of issue types that relates to the Sprint.
Today I can create an issue type and name it Sprint X and indent all the issue types from a defined Sprint but Jira uses Release and Sprint already in the Agile Board. Unfortunately, these are not issue…
14 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 -
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”
- Don't see your idea?