When an issue is shifted manually around in a generated hierarchy, it retrieves the "hand" symbol and the position seems to be memorized in an (invisible, structure internal) attribute. Sometimes this memorized position gets in conflict with updates generator rules etc. and I want to withdraw the manual relocation. But not for all relocated issues (which is possible) but only for individual ones.

Our users like to export their structures to .xlsx to use the full functionality of modern Excel.

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.

All the Expr language documentation shows semi-colons in formulas, but you can use commas. It would be good to indicate this somewhere as many people are in the habit of writing commas inside formulas to separate arguments and it is hard to get into the habit of typing semi-colons just when using a structure formula.

JIRA dashboard gadget would be good showing a pre-defined structure.

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.

When using the "Remove Inserter/Extender Duplicates" generator also non-hierarchical duplicates, based on different used linkage types like "child-of" and "resolved by" should be removed.

Are you working on developing the Structure.Gantt addition to be used on the cloud version?

Create an attribute "Rank" to allow a user to manually order stories.

Use case: I want to prioritise stories for a given release. e.g. I have 20 stories and want to rank them 1-20.

Benefits:
- the ranking is more transparent to a larger audience than the ability to move stories on screen
- if another user changes the order I can see what was changed

Currently we are using a different app for this but would prefer to use Structure.

Currently, there are no indicators of how long will it take to show up a structure and the 'spinning wheel' is showing up to several minutes (while uploading/reindexing a large number of tickets.
The progress bar will help to determine that the 'work in progress' and there are no issues/hangs during this process.

Would it be possible to somehow recognize different types of links in the structure? e.g. add an icon for issues which are linked by "is blocked by" or change the colour of the blocking ticket.

Structure recently added the ability to use "Status Category" as a column. As Categories can be pretty powerful tools, I would like to suggest bringing "Project Category" in as a column as well.

In addition to columns, the bigger need I have at the moment is to be able to "Group by" Project Category in the Automation options. I also noticed that Status Category is missing here as well, so I think it would be great to bring the existing work to the Automation section as well.

Use colour to show time remaining vs original estimate as in standard JIRA progress fields when using time for estimates

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.

The column widths of the printable page are set by Structure and often ones with a lot of text (like Description or Comments) end up too wide. Would be great to be able to set widths before exporting

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