Currently you can save transformations as quick transformations which is a great feature. I see however certain potential to make it even better:

- Combine several transformations into a single Quick Transformation (e.g. filtering and grouping)
- Define Quick Transformations for the "Jira" part of the double grid: I often look for items assigned to a version in order to add them to my structure. It would be super convenient if I could save it as a Quick Transformation.

Thanks for your consideration and keep up the great work!

I would like the ability to use Structure gadgets also on wallboards. Technically you can already do that, but for example progress bars are not visible. I suppose this only requires a separate stylesheet?

E.g. to calculate a percentual distribution over all rows of a structure, for the formula you need the 100% value which is typically shown on the root element.

Therefore it would make a lot of sense, to be able inside "formula column A" to use a columns B's value, but the root element value! This should be possible even if column B is a formula itself.
As we can already use variables like "Column B ..." in formulas it would be nice to add "Root Value of Column B ..." to the variable selection list

I'm the admin and know of and installed structure, however, my JIRA users don't know what it is or how to use it. To help educate all please include links to helpful resources in your toolbar drop down such as documentation, etc.

Thank you

If you have several structures that you are attempting to manage when you switch between them your search panel tries a filter / set of search criteria from the *previous* structure. Then you have to figure out that you want to apply filter=29121 or whatever when you go from structure A to structure B.

Easy fix.

When creating or editing views, allow specifying the degree of expansion. My use case is that I want to show all issues in the top three levels by default. Furthermore, I want the expansion setting to apply to the Confluence gadget.

Alternatively, a perspective can be used to achieve the same result, but there is currently no way to use a perspective for the Confluence gagget. If the perspective could be used in the gadget, then I would recommend combining with http://structure.uservoice.com/forums/43181-structure-plugin-for-jira-ideas/suggestions/1773075-add-controls-to-expand-contract-one-level-at-a-t to allow an unlimited customization of gadget presentations.

As a release manager, I want to see multiple structures represented in one view so I can easily collate the work multiple teams are doing. Our planning and management of structures is distributed, but I need to be able to see them all for enterprise planning purposes. Additionally, I want to be able to filter the one "master" view so I can see only those items related to specific criteria (e.g. release or project or component).

When viewing an issue of type “Test”, created by Zephyr and assigned to a Structure, we are not able to see the corresponding Structure section as expected. If we change the type of the issue to anything else (Bug, Story, Epic, etc.) then the Structure section becomes visible. It seems that either Structure or Zephyr is not playing well together. This is critical to our organization as we try to integrate structured testing into our organization.

I think it would be nice to have possibility to notify Scrum Master and Product Owner that some of UserStories are holding in a backlog for quite a long period of time (could be specified in extra settings), for example 3 moths.
It should help to keep backlog always with actual UserStories.

Currently, the options are current and prior day, week, month, year. Can we have current and prior sprint?

If a sub task had a custom field which indicated it's current risk or similar be able to propagate that up to the top level to show the worst of the risks or some other flag

e.g. if a single subtask of a item is red risk, be able to show that red risk in all of it's parents in the structure. choose the worst value of all sub nodes to show at the parent level.

This will save time in organizing one's Structure especially those items that are completed and need to be moved way down or those items that are open and need to be brought way up. This would especially be useful when initially setting up one's structure.

It would be nice to have the ability to dump the structure board to a csv. Thinking that it would be something quick and dirty, with ' - ' noting structure, like this:
"Name", "Est Hours", "Progress"
"Mars Colony", "10h", "80%"
" - Terraform", "6h", "50%"
" - - Make Oxygen", "2h", "100%"
" - Create Colony", "4h", "0"

Once this was CSV, it could be manipulated in other programs. Right now, I don't see a way to get the Hierarchy or estimate roll-up data out of the system for project managers to use.

XRay instroduced a Test Repository in v3. Now every XRay test has a field 'Repository Path' looking like: '/Test Repository/Release 1/Phase 1/AAA/'.

However, the Structure view is still better than XRay repository. It would be great to be able to import XRay tests recreating the same folder structure as in the XRay test repository automatically. So that users can use both XRay test repository AND Structure.

when you report worklogs with structure, you want to use the worklog column and specify a time period.
If you add multiple columns, it is quite an effort to change the time period from eg. dates of jan to feb. (currentmonth is helpful, but somewhat too dynamic if you want to compare months)

To easily switch between months it is necessary to switch the time period you look on on the view level and influence alle worklog columns this way.

To provide a backlog forecast it is essential to show what content could be done within a certain time or time budget. If we configure the budget in a top level issues custom field, structure could SUM not only by level, but also the contents of the current list of elements (eg. by priority) and a formula could show from which element the budget is overspent.

Parent issue progress % seems incorrect based on underlying children progress % values, assuming equal weighting per child.

Example screenshot: imgur.com/a/43lgW

Same as the option to automatically include sub-tasks in the Structure, also add the option to always include the Epic Link.