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

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.

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

The Structure 4.5 documentation is lacking when describing how to create new views.

For example, if I take "Basic View" and copy it to my Structure, I would expect that I could edit it, but the View Details screen says

Access: Use - you can use this view but you cannot update it.

There is no "Save As" button as indicated by the documentation.

Require the user to confirm a deletion of an issue before it is removed from the structure. Right now there is a message that an issue has been deleted, but my users aren't noticing the message. Need to make them verify the deletion before it will occur.

I create some rather large Structure charts with multiple levels of nesting. Want to be able to highlight aspects of the chart (Rows, Cells, Columns) with color. This helps with focus (these items are critical), organization and overall visual appeal.

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

Structure formulas are extremely useful. Now our users would like ways of using them in other places within Jira. This may be tough in some ways because they are specific to the structure they are part of, but even something simple like the ability to choose an menu option or call some API to commit formulas into an underlying custom field could be quite useful.

It would be useful to have folder metadata. There are many uses for this but at a high level you could definitely folder types (strategic vs. operational), provide folder owners etc.

With Synchronizers it is possible to limit the issuetypes. Therefore it is possible to have multiple link synchronizers for different issuetypes.

Example:
one could defined a parent/child link between epics and features and use a is blocked link between features and bugs. with automators this scenario can not be implemented at the moment.

In structure folders created based on custom fields will show "no value"-folder in case issues haven't set the related custom field. It would be nice to get an option to define whether to show such "no value" folders or to show such issues without a folder under their parent.

Structure would be a great supplement to the information provided by Portfolio. It would be great if this data could be used by Structure ... perhaps even have a Portfolio Structure Template?

This feature can help a user orientate an issue in a structure, or share the path with another user easily.

It would be great to be able to customize the appearance of the Structure Folders in order to have a possibility of manual highlighting the "problematic" folders.

Folders is a great new feature in 3.0 (long awaited) but the sync tasks do not allow tasks to be added to folders which is an obvious feature for auto adding tasks to structure and also a huge use of ordering and sorting tasks in structure.

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!

My idea is that I want specific issues to not be affected by the sorting. Not affected, so that they can stay on top (or bottom).

Another cool way to do this may be a separator or separators, that can be added similar to the way folders are added. Except these separators allow their content to stay where the user assigns it to.