When displaying structures in a specific context (for example, after selecting a specific Version from the Project view), the Progress roll-up should be done in the context of that version.

For example, assume I have an Epic containing multiple stories which will be completed across several releases. If I view the structure in the context of the upcoming release, it would be nice if the Progress calculation were based solely on those stories targeted for the upcoming release.

Allow structures to have attachments, comments, workflow, etc by creating an issue for each existing structure. This could be automated by the Structure plugin.

Let the administrator configure a special project / issue type for those issues.

An ability to specify the fields to be exported such as due date etc etc.

We've been working with a structure for product planning. We rank candidate improvements top to bottom. I'd like to have a casual "vote up / vote down" button for each row. To use I'd reset the votes and then ask viewers to vote away. We'd all sit and watch the voting tally increment as the structure updated. After a few minutes we'd stop and then prioritize and reset the votes.

I'd like to be able to see who voted and when they vote prompt them for why.

Preferably without requiring an acknowledgement. The aim would be to mimic the speed of mind mapping tools for capturing information in meetings. One of the issues is if one wants to delete a item it should be as fast as creating one

Currently, when you clone a subtask and move it to another parent issue, it actually remains (for all intents and purposes of JIRA data) as part of the original parents issue.

This is a problem, because in Greenhopper on the planning board (where you move User Stories to actual date defined releases), they have to reflect the same structure as you created in Structure.

As a release manager, I want to see multiple structures represented in one view so I can easily collate the work multiple teams are doing. Our planning and management of structures is distributed, but I need to be able to see them all for enterprise planning purposes. Additionally, I want to be able to filter the one "master" view so I can see only those items related to specific criteria (e.g. release or project or component).

A closed or resolved issue should have have a "strikethrough" on the summary.

Add ability to edit header and/or footer for print outs. Include fields for Date/Time Printed, Structure Name, Etc.

When displaying subtask in Structure, include parent jira # as part of summary (like Jira filters).

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

Allow users to set due date based on due date of parent and estimated time. Plus when due date of parent is changed propagate change to all child issues accordingly

A shortcut to set a task on resolved would be appreciated.

It would be nice to have the ability to dump the structure board to a csv. Thinking that it would be something quick and dirty, with ' - ' noting structure, like this:
"Name", "Est Hours", "Progress"
"Mars Colony", "10h", "80%"
" - Terraform", "6h", "50%"
" - - Make Oxygen", "2h", "100%"
" - Create Colony", "4h", "0"

Once this was CSV, it could be manipulated in other programs. Right now, I don't see a way to get the Hierarchy or estimate roll-up data out of the system for project managers to use.