Sometimes someone deletes stuff from the structure and we do not know how the structure looked before (no version management exists).

In this case, as a workaround we would like to have a log to see what has changd.

This idea is a to provide a way to display only (or to hide) some fixVersion instead off all of them when we use the grouping feature. If it is possible to choose the storing order (asc, dsc) it would be awesome !

I would suggest you to resort exclusively to the AUI objects for your interface instead of your custom ones that clearly gives the impression that you are exiting the Jira world to step into another one.
I think you user would deserve a smoother user experience, with the same kind of buttons, icons, tables to which they are already used to. I'm especially talking about the transformation/filters features that should be improved in that direction to my mind. Thanks for you great achievement!

I assume a lot of people want to use structure for reporting as well. Most teams work with sprints and therefore it is essential to be able to select "sprints" as a filter for worklogs in structure views. A structure/or view could show worklogs for a certain sprint only and besides also for the involved team as well

I'd like to see my dates roll up the hierarchy so that I can see higher level estimates as they roll up. For example, if I have a folder for a project and I have a number of tasks underneath, I'd like to see the latest due date in the project, or the earliest start date.

* All issues that are direct children of this issue
* All issues that are children, grandshildren, etc. of this issue
* Parent of this issue
* Store the structure information in the same tables as other JIRA information, so it can be queried the same way.

Allowing users a quick view of the status for more than completion percentage for [insert your object of choice] if they are overdue or nearing completion deadlines

(e.g. a parent’s progress is just based on the progress of its children, but if one of those children has 10x more children than the other, it would be nice to weight it that way)

Duration depends of the availability of resources. Gantt should show how long the issue will take to close, For Stories the duration is given by the sprint. For Epics there is no possibility to hold this information and show it in the Gantt, using the Effort field for this information is completely the wrong way.

Use case: I have an existing filter that is the basis for a board. The board dynamically updates, whenever I change the criteria of the filter upon which the board is based. However, if I want to use that same existing filter with a Structure, I must replicate the criteria in structure, and then perform dual maintenance, whenever I want to change filter criteria. If the saved filter could be used by Structure, I would only have to modify the filter itself. This might be addressed in the process of solving the following existing idea:
https://structure.uservoice.com/forums/43181-structure-for-jira-ideas/suggestions/31928860-link-a-structure-to-a-jira-board-not-just-a-proje

When an issue appears multiple times in a structure (e.g. epic link and issue link),the progress calculation should be configurable to prevent / allow double counting

When beeing displayed in the issue viewer and the default structure name should be "None" to avoid confusion as another structure name makes it seem to belong to one.

when auto scheduling in gantt, start and finish dates are not synced with Start Date and End Date of the issue and later when generating reports, we cant have a realistic report

Allowing in JIRA filters can be filtered by issues that you belong to a structure.

Structure currently only supports permission groups but not project roles. If a project is set to support project roles then there could be surprises if some users are part of the right role but do not belong to the groups that Structure has been permitted to.

The status synchronizer allows as of today(2.0.0) only a rollup of the status to the parent when all children have reached this status (i.e. all children are "done" > parent is set to "done").

Imagine a workflow like: open > in progress > done.

For the status "in progress" it would be great to have a "roll-up once the first subitem enters a new state". So the parent reflects the new status once the first sub-item has been moved from "open" into "in progress".