I typically have rough estimates for bigger projects and I would like to be able to add them to the structure so that I can get an overview of what needs to be done. At the moment I can only do this by adding JIRA issues with estimates, but the problem is that at this stage I do not really want to create these issues yet (at least not for everything).

The closes thing to what I want is to create epics and set the rough estimates on the epics. Later I can refine my estimates by creating storys. The problem with this approach is that I need to reduce the story points of the epic or else the sum of the story points is too high. This of course also means that I loose my original estimate (budget).

I need to track business Epics, but these are usually large and I like to break them down into smaller-sub-epics to deliver and track (via multiple releases). Jira doesn't support Epics with Epics (unbelievable really) and I need to work at ira as well as structure level so I create folders in structure under the main epic to perform this partitioning. Each Jira story is still linked to the main epic so I can use Epic reporting in main Jira, but it does mean that I can now track sub-epics at the folder level in structure too. Unfortunately this means that I can use the Epic extension automation because it doesn't understand the folders. Because the stories are under the folders not directly under the epic, the automation doesn't realise and creates duplicates under the epic. I guess this is more of a bug than a feature request.

I think the decision to override JIRA's big, blue Create button in the top navigation is a mistake. And it's causing some headaches on our end. We have non-technical users who are using the Structure (with edit permissions) who aren't aware that creating a new issue will add it to the Structure they're viewing. They simply want to create an issue, not necessarily add it to their structure. We could remove the button easily, but then we'd have to have our users jump to another JIRA screen to create an issue. That's design breakage! My opinion is, leave the ubiquitous Create button alone. Users can use the grid to add issues to the structure. The Create button would be JIRA proper, not Structure overridden. If you must insist on modifying the Create issue button and dialog, why not make "add to structure" an OPTION, NOT the DEFAULT?

In our company we use very closely JIRA and Confluence. Structure allows us to properly organize issues based on our demands and workflows and it works perfectly for people who are assigning tasks or implementing them. But we use Confluence for executive summary of progress on specific builds where would be very helpful if we can display progress bar of a specific issue (counted from all issues below of selected issue in the hierarchy). This way we would be able to create great overviews like e.g. "Bug fixing of Feature1", "Implementing Feature2", ... with progress bars behind without a need of displaying complicated window with all issues in the hierarchy.

Having possibility to select display mode as in Roadmap for JIRA (displaying open, in-progress and resolved issues with different color) would be absolutely awesome :)

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

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