Our organization would like to have a possibility to create another tasks layer above Epics (like in Jira's advanced roadmaps). For example, I create a new issue type "Initiative" in Jira and then I can group in structure gantt all tasks in this hierarchy:
Initiative>Epics>Stories, Tasks>Subtasks.

FIelds like 'progress', 'estimate' or 'logged' are calculated (accumulated) over the sub-structure under the issue. I would like to be able to report those values in reports (e.g. accumulated estimate) or use them in JQL queries (e.g. accumulated_estimate > 2w)

Structure is sorted by Rank (through automation). I often click on Assignee column to sort by it. The only way to remove the sort is to click Transformation, Click the sort and click the remove. This is way too many steps to just remove a sort. One idea is to have each column have 3 states when clicked. Sort Ascending, Sort descending, Remove sort.

As a team lead, I want the Gantt view to show all unresolved issues as starting in the future irrespective of the view's "start date", so I can quickly visualise dependencies between teams that will impact their next sprint

Similar to how views can be shared across different Structures, it would be great if Quick Transformations could be the same. Right now, we have 15+ separate, but related Structures. All should have consistent views and transformations. Managing views is very simple, but if you change a filter on one Structure, you must replicate that change X more times.

Currently progress by status is supported(among other statuses).

To simplify configuration in complicated jira setups it would be nice if one could filter by status category. Instead or in combination.

Trying to get users to update information who are less familiar with Jira. Want to customize what options/buttons users see so it's less overwhelming.

Please add the ability to edit more fields especially custom fields from the Gadget (https://wiki.almworks.com/display/structure/Editing+from+Gadget). The ability to edit custom numeric fields via jira dashboards/confluence pages would be awesome!

Allow users to set due date based on due date of parent and estimated time. Plus when due date of parent is changed propagate change to all child issues accordingly

When displaying subtask in Structure, include parent jira # as part of summary (like Jira filters).

Currently, when you clone a subtask and move it to another parent issue, it actually remains (for all intents and purposes of JIRA data) as part of the original parents issue.

This is a problem, because in Greenhopper on the planning board (where you move User Stories to actual date defined releases), they have to reflect the same structure as you created in Structure.

Allow structures to have attachments, comments, workflow, etc by creating an issue for each existing structure. This could be automated by the Structure plugin.

Let the administrator configure a special project / issue type for those issues.

when you are creating a sub issue you might hit a wall when the creation of the issue have some mandatory fields which needs to be filled out.first.
it should be possible to enter data during sub issue creation.
it is already shown which fields that need to field out.

We added 2 custom fields for testing steps. The carriage returns show up in Printable Page nicely. But we can just print that. The Excel export doesn't keep them and so the steps are jumbled in each cell instead of a clean representation.

I would like to see the root element in the structure in the custom fields of the children so I can use this when exporting data from jira

When you open the Issue to view/edit the full details, a link back to the full structure would be nice