Thanks Martin, I think the same. This requires that http://structure.uservoice.com/suggestions/2329637 is solved first, which is a very large piece of work. Hope to get to it soon.

> If grouped by Affected Version or Component, by the way, an issue can end up in different groups at the same time (if it has multiple versions or components in the field value). So you'll have more than one row in the grid that will show the same issue. Would that be expected behavior, from your point of view?

Yes, for me, it would. It might be good highlight that it appears in multiple contexts though.

Sebastian, thanks for the details! Indeed, we plan to have something like this.

If grouped by Affected Version or Component, by the way, an issue can end up in different groups at the same time (if it has multiple versions or components in the field value). So you'll have more than one row in the grid that will show the same issue. Would that be expected behavior, from your point of view?

On the other topics:

In the current version, the custom ordering is kept for sub-issues. The "roots" order is not stored. In the upcoming version, we'll fix that by introducing named structures, which will keep both order and the set of issues in the structure.

The sorting is also planned, as "reorder" action: it would rearrange issues by some field values, but then the user will be able to break sorting by moving issues around. Would that be what you expect, or do you need more persistent "sorted by" state?

I have not used Outlook for a while, but I think that would be similar to what I have thought of.

Essentially, when you have grid with columns, you can right click on a column and choose "Group by". Than, the rows are grouped by unique entries in that columns - so similar to e.g. Outlook by date grouping feature (this one I remember) - Today's emails, Yesterday, This Week, Last week etc.

This way I could group for example by Affected Version and have release-aware streamlined structure.

BTW, your plug-in currently lacks sorting capabilities. Not to mention, that custom ordering of issues does not seem to be remembered. I can order issues with up-down, right, but it is not remembered. Navigate away and it is lost.

Generally, what I am looking for is a replacement for MS Project tasks view. I need to be somehow able to see relationships between issues (task) when I am planning new projects in JIRA.

Sebastian, thanks for the idea! Could you please elaborate a bit, what do you understand by "grouping capabilities"? How would you group issues, what criteria would you use? We have in mind something resembling Outlook grouping of e-mails, but maybe your picture is different.

Igor