This would accommodate issues that do not have a simple one-to-one relationship in the hierarchy.

The Structure Board could display Gantt chart instead of the aggregate progress.

However, this may need for additional data to be recorded for each issue (work logs may be not enough).

Also it would require a wide screen for effective use.

Structure looks promising. To make it truly usable for my needs, I would need to visualize the hierarchical structure in the Issue Navigator, GreenHopper planning board, and Filter Results dashboard gadget.

Allows users to create a set of new tasks via a previously saved structure template. In some production environments there are task hierarchies and dependencies that are already known and you need to create several versions of the same structure. Instead of creating all of the tasks and then reorganizing the structure each time a template would speed up the entry process.

Let JIRA admin specify what issue types could contain what other issue types. For example, a Test Suite may contain Test Cases, which can contain other Test Cases, but not Feature Requests.

Let the user specify, for example, that all sub-issues of the issue X should have the same Security Level and Project and Priority.

I'd like to create individual structures for major initiatives or projects within the company. Then, I'd like to create a global structure that includes the individual "sub-structures" within it for an overall summary view.

In JIRA I can set list of columns and order for each filter. Structure plugin can use filter result for view in Structure - it's greate! But it does not use columns setting of filter... :(

If I have some different project type I need to have different view for each type - filter settings provide me this possibility. I need to have different settings of columns set in Structure too.

The initial column set for structure is fixed for board, issue and gadget to be the same. It would be nice to be able to change the default configuration to something other than out of the box. It would be even nicer to be able to configure a default for each place a structure is displayed (board, issue, gadget). A simple mgmt interface would be need to configure it and a storage mechanism.

Creating a parent issue (at any hierachical level) simply to act as a container for sub-issues/sub-tasks should not necessarily create a new jira issue in many circumstances.

I'd love to see structure represented in jira client...

It would be nice if you go into bulk mode and then click the edit button that you get taken to the jira bulk editor.

I typically want to create issues of another issuetype, and probably in another project.
Just cloning is too trivial, and it requires to much work to change issuetype, and project.

Alternative (even better): automatically detect sub-issues for certain link-types

It would be great if there was an option to update at the same time more than one issue. For example, parent issue and all child issues at once.

So that I can restore the state of the view from browser history (using back button etc.).