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 the ability to have grouping capabilities, so that I could manage larger structures easier
For example, to be able to group by Component, or Version, or a Tag.
26 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 -
51 votes
Available in version 1.4! Feature video: http://goo.gl/CMH8b
-
Show Calculated Estimated and Remaining Times on Structure Board
Currently, the Structure Board shows the Progress calculated from the roll-ups of the estimated times and remaining times, these should also be available as columns in the board.
13 votesAvailable in version 1.4
-
remember (de-)collapse state of structure section within the issue view
Currently when switching to another issue the structure section is always open. Also when I collapsed the section before. This is not the standard behavior within JIRA for collapsed sections which normally is remembered for the user.
2 votesfixed in 0.3, available for download
-
5 votes
Done in 0.4
-
Use columns (list and order) from JIRA filter
In JIRA I can set list of columns and order for each filter. Structure plugin can use filter result for view in Structure - it's greate! But it does not use columns setting of filter... :(
If I have some different project type I need to have different view for each type - filter settings provide me this possibility. I need to have different settings of columns set in Structure too.
17 votesViews feature delivered in Structure 2.0. The search panel now has “Column” button, which changes active view to columns configured in the Issue Navigator (default or per-filter).
See details in release notes:
https://wiki.almworks.com/x/9Aqf -
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.
-
68 votes
This feature has been provided via S-JQL based workflow validator / condition, available in Structure 2.8 and later. See https://wiki.almworks.com/x/Gq-rAQ for details.
-
let the creation of a structure be "templatable"
For a "new Feature" issue I always have the same structure: draw architecture, add/modify interfaces, implementation, qa, going live...
How about a Feature to "add a structure by template" that would generate the defined Issues and append the newly created issues as a structure to the current issue.0 votesDelivered in Structure 2.0 – see release notes at https://wiki.almworks.com/x/9Aqf
-
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.
-
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
-
Define link type(s) that will be set automatically when creating subissues or changing hierarchy
Define link type(s) that will be set automatically when creating subissues or changing hierarchy
22 votesLInks synchronization done in 0.4. Quick steps: open “Manage Structures”, click “Settings” in Synchronization column and add “Issue Links” synchronizer. Make sure to read through warning messages.
This does not cover GH interoperability (Epic/Theme is a label, not a link, isn’t it?) and it doesn’t address creating an issue of different Type – it’s a different improvement, also planned.
-
Also show subtask in the hierarchy (automatically define them as subissues)
Also show subtask in the hierarchy (automatically define them as subissues)
16 votes -
6 votes
We’ve done not all we wanted to do about this feature, but it’s good enough for this early stage. The new version is rolled out at demo42.
-
58 votes
It is now possible to build and share plans with Structure.Gantt planning app, please see https://almworks.com/gantt
-
Show live Gantt chart
The Structure Board could display Gantt chart instead of the aggregate progress.
However, this may need for additional data to be recorded for each issue (work logs may be not enough).
Also it would require a wide screen for effective use.
382 votesALM Works announced the availability of our new offering in this area today.
Structure.Gantt adds the power of Gantt charts to Jira projects through Structure work breakdown structures.
Learn more at http://alm.works/gantt
-
Mark parent issue resolved if all sub-issues are resolved
Also: mark parent issue non-resolved if its sub-issue becomes unresolved, or if parent issue gets a new non-resolved sub-issue.
Also: mark all sub-issues resolved when a parent issue is marked resolved.
35 votesSolved by Status Rollup synchronizer in version 1.2.
-
Provide API for creating and managing hierarchy
The API could be used to integrate JIRA+H4J with Microsoft Project, or enhance the existing connectors.
Also, the standard APIs could be supplemented by hierarchy-specific fields and methods.
13 votesAPI is available starting from Structure 1.3
- Don't see your idea?