The structure plug-in allows users to select multiple, dis-contiguous issues using the multi-select mode, whereby the user clicks on the little radio button next to every issue they want to select. The selection can then be operated on as a whole, for example, to reposition the issues in the structure.

This feature works great, however, I find it annoying because the selection 'sticks', even after I've completed the operation I wanted to perform. Then, when I move onto select other issues, the previous ones, which are still selected, unintentionally come along for the ride.

Let me provide a use-case. Assume I want to move 3 issues in the structure using cut-and-paste. I select the 3 issues using multi-select mode, cut them, and paste them in the new location in the structure. Everything is OK so far. Now, I move elsewhere in the structure and start to select additional issues for another move. I start selecting the new issues using multi-select. Since the previous 3 issues remain selected, they are added into the new list I'm building. Since I've forgotten about the previous 3 issues, I don't notice that they are 'tagging' along for a ride in my new list. When I finally complete my new list and cut-n-paste, I find out that the 3 issues from my first cut-n-paste operation have come along for the ride. :(

I can't count how many times this has happened to me and it's frustrating. If I forget to clear the previous multi-select with "ESC" those issues will tag along in future multi-select operations.

Somehow, it would be nice if Structure could clear a multi-select after certain operations, like a cut-n-paste, or dragging to a new location.

Use Case 1:
As a tester I would like to use a unique test case and run it several times and after every run I would like to add my test data/environment to it. (E.g. Result and what format, browser, platform, DB that was used during test run...)

Use Case 2:
As a Test Manager I would like to be able to create a dashboard report or filter based on specific data and the outcome of the result with that test data/environment.

Current solution with testy today (https://marketplace.atlassian.com/plugins/com.almworks.testy)
has some good features but you still lack the method to add specific test data/environment to a test run without making a clone of the original test case and without having to plan and create a complex setup based on strict test with env/data defined on test and many test run columns.

Test results presented on a run in structure with Testy cannot be collected and presented in a report outside use of the structure.

I would like to create a Structure of Structures for structure navigation, whereby specific child elements allow you open the referenced structure. I have many structures that contain the same data, just displayed differently for different user groups.

The use case is in essence:
Parent - Folder (a name listing a group of similar or related structures)
Child - New Structure Link - simply a mechanism to either open or navigate to the referenced structure - includes description.

Implementation:
Is it possible to add a new Structure element into the "Add" Dropdown called "New Structure Link". (i.e. New Issue, New Folder, New Memo, New Structure Link) allows the building of an index structure.

First iteration could allow manual creation only, but with use of metadata in future could allow auto generation.

The Formula column is a killer feature, but it can get tricky when the formula expression grows larger than the size of the editing area, and has a few levels of nested expressions.

Beyond just the ability to enlarge the editor, it would be fantastic to have a more advanced editor to assist here, and the obvious candidate is the https://microsoft.github.io/monaco-editor/

My suggestion for iterations for this would be:
- Just replacing the actual editor and make sure it's still working when editing and not (so no functional changes)
- Adding config and definitions needed for highlighting brackets and auto indentation
- Adding syntax highlighting of functions, operators, variables and value literals
- Auto-complete and intellisense tooltips of functions

Greenhopper's Agile plugin allows for nested "versions" to define Agile Sprints within a top-level planned release. This is represented in JIRA as comma-separated items in the Fix Version/s column.

The Agile Planning Board is smart enough to show the last Version in that comma-separated list indicating the current sprint to which an issue is assigned. Structure is showing all the comma-separated versions which takes up a lot of column width space (particularly considering the Structure view does not wrap text in columns...).

Would you consider creating an Agile Version column that is essentially the last item in the Fix Version/s list?