I would like to be able to see 6 columns and have the option to see ALL the text wrapped not just the starting text. I'd like to retain the option to just see the starting text too though. I have used the full screen real estate but I can still only see the start of the wording.

Current work around is to only have 1 or 2 columns showing at once and add in the others as necessary later.

e.g. View currently shows:

Summary Description Labels Components Assignee

Client Doc Data in clie Docum Disclosure Sarah Sm

I'd like to see a layout like (not sure if this will work on here)

Summary Description Labels Components Assignee

Client Data in Docum Disclosure Sarah
Documentation client docs entation Smith

Many thanks

I would like the bottom line of the structure widget to also show the sum of remaining estimates for all (shown) issues in the structure.

For example, I have a structure with issues for our next release. I would like to enter a filter like "fixVersion=<currentSprint>" to see issues assigned to the current sprint, how they are spread across overall plan, and also see the remaining estimates for the sprint.

The bottom already say something like "Showing 25 issues (100 issues are not shown)", so there's quite enough space to say "Showing 25 issues (10 weeks remaining) | 100 issues are not shown".

The description of of Structure on the Project page (https://wiki.almworks.com/display/structure/Structure+on+the+Project+Page) is really misleading because this image is of viewing a JIRA board, not a project. With JIRA boards I can use JQL to divide a projects (or multiple projects) issues across many boards, but I do not have a way to link that board to a specific structure that also filters for the same set of issues.

Having a default structure for a project is fine, but I would also like to be able to correlate a structure to a board. This would help teams that for example split work on different component or releases have a direct link from their board to the related structure. At current, these different boards can only link to the single project level structure.

User Story Mapping is becoming a very popular way to organize your product backlog: http://www.slideshare.net/nashjain/user-story-mapping

It basically uses a 3 level structure but displays tickets in a vertical layout, as illustrated here:

There are only a few tools that support this online, and only one that is part of JIRA. The market is ripe for a tool that is robust, simple, and flexible. Since Structure already organizes tickets hiearchically, all that would be required would be to create a new view of a Structure, with a possible limit of 3-4 levels. (The Story Map structure only supports 3, but I think it could support 4, by stacking cards on top of each other.)

I believe this would be a very welcome addition to Structure, or even a new Plugin to JIRA to augment a Structure Board. Right now, I am using Structure to accomplish the same objective, but a new view would be highly beneficial.

Similar to functionality in Greenhopper and other plugins, add a button to structure to allow opening the list of issues visible in the structure in the Issue Navigator.

I use the Agile Cards plugin. It's possible to print cards from the Issue Navigator. I would like to be able to print cards for a portion of the hierarchy in a Structure but I have no way to get from the structure to that functionality. One possibility is to allow opening the issues currently visible in the Structure in the Issue Navigator.

It seems like this would be useful for other plugins that operate on lists of issue in the Issue Navigator.

Jira has a "issue filter subscription" feature, which runs a filter at a certain time of the day and email the user with the results. Structure could have a similar subscription feature tied to a particular structure's view, where a snapshot of that view would be taken at a certain time of the email and the results would be exported to excel and emailed to the user.

My company currently use structure to keep track of our day-to-day progress by manually exporting structures to excel at the same time each day. Automating the exporting would allow us to automate the remaining of the pipeline and remove any room for human error.

Ideally, when subscribing to a structure you would be able to not only choose a view (which determines the fields to be exported) but also any filters or transformations that are applied to that structure. So the act of subscribing would take a snapshot of all those settings, and then an "export to excel" would be run at a recurrent schedule and emailed to the user.