Structure Plugin 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.
-
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.
153 votes -
Allow an issue to be located in multiple places within the structure
This would accommodate issues that do not have a simple one-to-one relationship in the hierarchy.
141 votes -
Visualize hierarchichal structure in Issue Navigator and GreenHopper planning board
Structure looks promising. To make it truly usable for my needs, I would need to visualize the hierarchical structure in the Issue Navigator, GreenHopper planning board, and Filter Results dashboard gadget.
87 votes -
Option for issues to be sorted by column (mainly for search result)
1. Secondary Panel: It would be great if user could sort issues by column by clicking on it or selecting the option from column's dropdown.
2. Main Panel: In respect to hierarchy, would be also great if user could sort issues that are on same level of indentation, under selected parent.
Example steps for such action could be: 1. Select / highlight parent where sub-issues can be sorted; 2. Select Sort option;
For top level issues in hierarchy, sort could be available by clicking on column or selecting the option from column's dropdown, no issues should be selected in this…70 votes -
Adapt aggregation of Time Tracking fields with filter
Sum up the Time Tracking fields of shown issues only.
When I apply a filter, I want to see th aggregation results of the resultset only (filtered issues).
So we can look at all aggregations (and sub-aggregations) for a specific Sprint or Release....69 votes -
Allow a structure to be added to another structure.
I'd like to create individual structures for major initiatives or projects within the company. Then, I'd like to create a global structure that includes the individual "sub-structures" within it for an overall summary view.
57 votes -
Create parent issue that does not create jira issue
Creating a parent issue (at any hierachical level) simply to act as a container for sub-issues/sub-tasks should not necessarily create a new jira issue in many circumstances.
56 votesConsidering this for the next redesign iteration
-
Limit parent-child relationship to specific types of issues
Let JIRA admin specify what issue types could contain what other issue types. For example, a Test Suite may contain Test Cases, which can contain other Test Cases, but not Feature Requests.
54 votes -
53 votes
-
Propagate field values down the hierarchy
Let the user specify, for example, that all sub-issues of the issue X should have the same Security Level and Project and Priority.
49 votes -
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 votes -
25 votes
-
support issue creation using extended form (CreateIssueDetails)
So that it could be possible to configure Structure Plugin to open extended form instead of the one with just a summary as it is by default.
16 votes -
15 votes
-
Integrate structure in JiraClient
I'd love to see structure represented in jira client...
14 votesThanks! We’ll work on that some time after the initial release.
-
Allow you to wrap text in a column in the structure view.
I would like to be able to see 6 columns and have the option to see ALL the text wrapped not just the starting text. I'd like to retain the option to just see the starting text too though. I have used the full screen real estate but I can still only see the start of the wording.
Current work around is to only have 1 or 2 columns showing at once and add in the others as necessary later.
e.g. View currently shows:
Summary Description Labels Components Assignee
Client Doc Data in clie Docum Disclosure Sarah Sm
I'd like…
13 votescollecting requirements
-
Improve the administration (Synchronization Settings) for structures with many syncronizers
We have structures with many syncronizations and have had some problems maintaining them:
1. Fast way of resyncronize ALL syncronization rules for the structure
- In some cases the syncronizations needs to be "Resync"ed.
We have found that for example when a filter syncronizer refer via a 'filter' it doesn't take effect when we change the refered filter. After a forced Resync it works.
Example
JQL query: (project = DEVENVC2JIRA or label = Jira) and filter = "DEVENVC2 - Next month" and status = Assigned
In this case, when we change the "next month", we need to resync. To do…13 votes -
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.
12 votes -
Need additional mark for Closed issues
Structure shows check mark when issue is resolved, but I want another mark if issue is closed!
10 votes -
Create sub-issue should work similar to Link New Issue Operation (LNIO)Valiantys
I typically want to create issues of another issuetype, and probably in another project.
Just cloning is too trivial, and it requires to much work to change issuetype, and project.Alternative (even better): automatically detect sub-issues for certain link-types
10 votesplanned after 1.0
- Don't see your idea?
