Structure currently only supports permission groups but not project roles. If a project is set to support project roles then there could be surprises if some users are part of the right role but do not belong to the groups that Structure has been permitted to.

The status synchronizer allows as of today(2.0.0) only a rollup of the status to the parent when all children have reached this status (i.e. all children are "done" > parent is set to "done").

Imagine a workflow like: open > in progress > done.

For the status "in progress" it would be great to have a "roll-up once the first subitem enters a new state". So the parent reflects the new status once the first sub-item has been moved from "open" into "in progress".

e.g. all 'Blocked By' issues added via Extend automator grouped together under parent.

This makes the Jira relationship between Structure parent/child issues clearer.

Currently when editing a structure (Operations->Configure), you are throw into a new page for editing. When you are finished and go back, the structure list reloads and moves you to the top and I cannot find my place anymore. This is a problem when you are viewing a list of over a thousand structures.

A popup lightbox would make things much better and allow me to keep my place in the list of structures. This could apply to sync settings, and all other management operations.

Currently only the Actitvity Stream "gadget" has the option to configure filters.
The standard (non-gadget) Jira Activity Stream on the Project Summary page & on the User profile page does not have this option. Hence these Activity Streams are heavily 'polluted" with Syncronizer updates and are becoming useless..

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.

When working with external partners they often use their own JIRA instance. You can connect them via the JIRA application link feature with your own JIRA instance and are able to set links between issues in the two JIRA instances this way.

It would be great to be able to display linked issues from the remote JIRA in your own structures.

By specifying some fields e.g, priority and assignee as well as the indendation level of the issue while entering the summary text of the issue will speed up the data capturing with structure. Please consider having a look at www.checkvist.com for effective keyboard support for increased speed and useability.

Eg use the @ to specify the person eg @john
use the # sign to specify the priority
Eg #0 - blocker
#1 critical
Tab indentation in the summary for instance indentation level 1 specified by 1> indendation level of 2 specified by >2

>1

Budgets are often not added as issues. Structure could add value by allowing some limited amount of named custom fields on structure-folders (like notes, but some more). They would bind to a structure and could be accessed from formula columns.

We want to have the feature to go to the next issue in the stucture.

The scenario is:
1. You have a structure open
2. You open up the first issue in a full screen mode
3. You go to the next issue in the structure. Without jumping back to the structure.

In the same way as you can jump to the next/previous issue after you have performed a filter/search in plain JIRA.

Currently it truncates the names so it is difficult to tell which structure is displayed.

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.

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.

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.

Do you have prepared structure for translating structure. SWe need a German version.