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)

I have been searching for an option to subscribe to a structure (similar to a filter). If this is not available, it might be a good idea to add this as some of the structures cannot be created using filters.

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

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.

Whenever any issues in the structure is edited, notification should go to people subscribed for structure to indicate structure content is changed

When the maximum detailing of the gantt chart is done, the days and hours that do not end up representing a greater amount of columns in the gantt. It would be much more practical with great visualization without these columns. Especially when there is a need to visualize tasks that are defined with small loads of hours and to be executed on the same day.

Поскольку структура может включать в себя до 10000 задач, будет полезно иметь возможность в отдельном окне проводить анализ этих данных. Какова совокупная трудоемкость в разрезе: проектов, компонентов и т.п. , Какова продолжительность работы одной команды на структуру и т.п. Полезно так же создавать кастомные срезы для анализа типа: стратегические задачи, текущие задачи и т.п.

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

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.

Allow the ability to add hash marks to the parent time bar in Gantt based on child dates. This would allow to see milestones without cluttering the view with multiple child issues.

As a project planner I need to be able to define a dependency with an offset.
Example: Task 5 can start 3 days after Task 4 starts. I would define that as a Start-to-start dependency from Task 5 on Task 4 with a +3 day offset.

A regular express text function would be very useful to extract content from a Text field into a column.

For example, if a Description field has:

Name: Value
Name1: Value2

I can write a regex formula to extract out the value for Name: into a Column.

I know it's not likely that you can interface with every other add-on that structure customers might also use, but selfishly, I would love to be able to view all test cases associated with an issue under that issue (similar to Extend with linked issue).

Add a count of the number of comments.

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 !

These fields are of extreme importance for time management throughout the project.