Right now, I have two choices, export to Excel or print from the structure board.

In our situation, the description and acceptance criteria have bullets, numbers and other items allowed in JIRA's rich editor.

When exporting to Excel, this renders as HTML tags which Office does not accept and render correctly.
When using the print functionality, JIRA Issues cross over page breaks (which we could fix if we could have it render in Excel)

The reason this is a concern for us is that or customers want to be able to review the technical architecture. ePrinting is our only real option and it doesn't look professional when presented this way.

If there is another way this can be done, I'm open to suggestions.

Thanks

By example, we use stories and have them implement features. Our final state for stories is "Closed" and when all stories are closed we want to have the feature change it's state to "Ready for Production" however there doesn't seem to be a way to do that.

To that end, it would be nice if we could say that for state X we could specify what transitions could go there given that its sub-items state may be different.

Example:
Feature Workflow has "In Progress" --- {Ready To Deploy} --->>> "Ready for Production"
Story Workflow has "Verify" --- {Ready To Deploy} --->>> "Closed"
Would want the "Ready for Production" State in the Allowed Transitions section to be able to choose 'Ready to Deploy' from the story workflow.

Right now the link synchronizer works only between parent and sub-issues. However, this is often not enough. For example, we would like to automatically link "development" and "system testing", which are usually sibling issues under a single "Change Reqest ### for system XYZ" issue.

A use case for "cousin" links is similar: "integration testing" should depend on all "system testing" issues within the same "Change Request ###" parent/grandparent issue.

Right now we work around this by using template structures, but this is fiddly and error prone, since issues like "integration testing" should be edited manually after N "change request for system" issues are added to the structure.

USE CASE:
1. Visualize Progress Bar functionality test coverage on diff browsers (following example @ https://marketplace.atlassian.com/plugins/com.almworks.testy)
2. Re-use the same test plan structure for multiple builds

OPTIONS FOR BUILD 2:

Option 1;
Use columns for each browser (next build requires cloning to track test execution)
Problem 1: Requires cloning of entire structure for next build
Problem 2: Cloning just test results will not work as new results will overwrite test results from build 1

Option 2:
Use columns for each test run (no need to clone the tree and browser makes put in the hierarchy)
Problem 1: after a dozen of builds I will run out of space to add new test runs.

DESIRED SOLUTION (Similar to Zephyr, SpiraTest, TestLink, etc…):
Ability to created new test runs/sessions/cycles without:
a) Cloning test cases (unnecessary dups)
b) Overwriting previous test results

We always have multiple coders on our projects, and almost always have multiple coders contributing to each piece of functionality within a project. We use the Tempo Plugin for JIRA to keep all that straight.

Structure's time summations are really helpful and beneficial. But for our multi-coder environment, we have to look at that summation in Structure, then look at every subtask and split out exactly who contributed how much to the Structure main task, because different coders are at different billing rates. This is not workable except on very small projects.

What would be ideal is if we could see a per-coder breakdown of the summed logged time at any level in the Structure.

Thanks for considering this. We will be hoping to roll our own with a combination of the Tempo and Structure APIs, but would love to see this as part of the product.

First set of columns each represent a structure level.
Following structure, top row includes field names for data entry (e.g. Story Points, Type=Epic, Story...

(not sure if this will come through or not, but something like this:

|Level1 |Level2|Level3 |Level4 ... |Type |Story Points|
|Jurassic Park| | | ... |Epic |
|Jurassic Park|T-Rex| | ... |New Feature|
|Jurassic Park|T-Rex|Goat Release| ... |Story |
|Jurassic Park|T-Rex|Goat Release| As a goat I can be raised up so the T-Rex can eat me|Story| 8 |
|Jurassic Park|T-Rex|Goat Release| As a goat I can NOT escape so that I will live|Story| 2 |

Note structure relates stories to stories.

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.