When using multiple extensions (for instance the link types "is blocked by" and "blocks") it would help a lot to have a way of showing why an issue in question is extended. Allowing each extender to have a background color on the items it adds, or a symbol next to the summary would be great.
Example:
An automated structure that inserts "type=epic and project=projectA"
Extension 1: Extend with Linked Issues, type: Blocker, "is blocked by"
Extension 2: Extend with Linked Issues, type: Blocker, "blocks"

The extensions might be permanent or quick transformations. For each of them it would be nice if the configuration setup allowed for background color or a prefix in the summary column

I really appreciate the ability to edit tasks directly in the structure view. However, doing so results in two undesired side effects:

1. If the user needs to change multiple fields, they have to do so one field at a time. Depending on the notification scheme, this can result in a lot of email spam.

2. It encourages users to change fields on the issues without entering associated comments. For example, if somebody is changing the Fix Version/s for a task, in our team, we expect them to enter a comment explaining/justifying the change. There is no way to enter a comment for an associated change when the change is done directly in the structure.

The first issue is particularly a problem when creating an issue. Structure's issue creation window only allows the user to populate a couple of fields (or copy fields from other issues, which is often not what we want). It would be really nice if Structure popped up the native JIRA Create Issue window so that the user could populate all of the needed fields in one go.

For changes to other fields, it would be nice if structure popped up a little window which allowed the user to change the field and enter an associated comment.

I would like a way to use a 'wildcard' in the structure() S-JQL function so that it searches all matching structures. Specifically, I am trying to solve the following problem: find all leaf nodes in any structure.

Here's a potential use-case: I want to have a task backlog implemented in Structure. I also want to be able to organize my tasks in a hierarchical manner, also using Structure. In my task backlog, I only want to track the 'leaf' tasks which appear in my hierarchical structure.

I know I can do this now using the structure() function, but I must provide a specific structure name. Requiring a structure name makes it difficult to write a general building block filter since the structure() function is always linked to a specific structure.