Structure for JIRA: Ideas
Thank you for visiting our feedback website! Feel free to vote or post your own ideas. Make sure you turn on the option to notify you about changes and comments in your account settings, so that you can stay updated about the progress of the ideas you’re interested in.
384 results found
-
Ability to connect to more that one Confluence instance (Structure.Pages)
Current (unless I'm doing something wrong) we can only link one Confluence instance when setting up Structure Pages integration.
It would be nice to have the ability to link more than one. This should come though with the proper UI to select the server when adding a page or searching.
1 vote -
Not override the functionality of the JIRA Create button
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…
1 voteReviewing options – please see comments
-
Creating structures from agile boards with Epics and Epic-less tickets
When creating a structure from an Agile board it would be nice to be able to add as well Epic as stories not assigned to an Epic.
Creating a structure with Epics and adding an JQL-Inserter for the Epic-less Stories is not sufficient. I am not able to move Stories into an Epic later on the structure board this way. ("Cannot remove issues from JQL query result. ")
3 votesplease see the comment for an alternative setup
-
Structure lite
Have you ever thought about a lite version of structure with reduced functionality? e.g. only supporting parent / subtask or epic / story relations or homogenous link hierarchies for example.
1 vote -
Reinstate search on the issue page
In Structure 3, search and filtering functionality was removed from the issue page. But sometimes we need that to rearrange structure without leaving a specific issue.
More feedback:
But with the loss of the toolbar we can no longer filter or search the structure from the issue view.
We frequently need to unpin, search then re-org the structure, and we like to do it from the issue view. At my work we are considering rolling back to 2.x to get the search/filter feature back on the issue view.
7 votes -
Name in issue viewer
When beeing displayed in the issue viewer and the default structure name should be "None" to avoid confusion as another structure name makes it seem to belong to one.
3 votes -
Show progress of selected issue/task in Confluence
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…
2 votes -
Integration on Jira Agile
It's very useful the integration with Jira Agile (on Jira 6 and next releases), so I can see near the tab Epic and Version (in the backlog view) also the other structure that I can build.
Actually, I have to manage two different views: Structure view and Backlog view. It's better to integrate this two views.1 voteplease see comments
-
Auto-Convert Perspective-Link into Structure-Gadget on Confluence-Pages
In this way one is able to create whatever view of the Structure in the structure itself and share this on Confluence pages without dealing with the UI of the gadget (which needs some improvements).
1 vote -
Allow Better Transitions
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}…1 vote -
Print Structure Cleanly
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…
2 votes -
Custom structure template based on 1 or more JIRA fields
The plugin allows users to create arbitrary structure and also structure based on JIRA links. It would be nice if there is a way to create structure based on JIRA fields like Reporter, Assignee, version, status. So user can drill down the issues by reporter, By Assignee, By version or any such combination and order.
1 votePlanned in Structure 3
-
custom row heights and the ability to export to ms word/view in web layout mode
custom row heights and the ability to export to ms word/view in web layout mode
0 votesCollecting requirements – please see comment
-
have the ability to control the visible amount of a custom field
I currently use a custom field for scope statements and wkly highlight reports. As far as I know, Structure only allows me to see a small excerpt of this field. I would like to be able to control the amount I can see (maybe in number of characters / lines). That way I can view issues listed in a Structure and see at least 2 or 3 paragraphs of the report/statement at once.
1 votecollecting requirements
-
Let user to zoom in and focus on just one hierarchy level
One of the features that makes Workflowy so great, is the possibility to zoom-in to one hierarchy level only. I think this could work for Structure as well.
1 votecollecting requriements – please see comments
-
Report or filter on accumulated fields
FIelds like 'progress', 'estimate' or 'logged' are calculated (accumulated) over the sub-structure under the issue. I would like to be able to report those values in reports (e.g. accumulated estimate) or use them in JQL queries (e.g. accumulated_estimate > 2w)
5 votesCollecting requirements, please see comments.
-
allow us to synchronize links between sibling and cousin issues
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…
3 votesPlease see the comment
-
Testy: ability to creatae multiple test sessions/cycles without cloning tests and/or test results
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 buildsOPTIONS 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 1Option 2:
Use columns for each test run (no need to clone the tree and browser makes put in the hierarchy)
Problem 1: after a…1 votecollecting requirements
-
Keep backlog always up-to-date with notifications
I think it would be nice to have possibility to notify Scrum Master and Product Owner that some of UserStories are holding in a backlog for quite a long period of time (could be specified in extra settings), for example 3 moths.
It should help to keep backlog always with actual UserStories.3 votescollecting requirements
-
Add view setting to specify level of expansion
When creating or editing views, allow specifying the degree of expansion. My use case is that I want to show all issues in the top three levels by default. Furthermore, I want the expansion setting to apply to the Confluence gadget.
Alternatively, a perspective can be used to achieve the same result, but there is currently no way to use a perspective for the Confluence gagget. If the perspective could be used in the gadget, then I would recommend combining with http://structure.uservoice.com/forums/43181-structure-plugin-for-jira-ideas/suggestions/1773075-add-controls-to-expand-contract-one-level-at-a-t to allow an unlimited customization of gadget presentations.
3 votesLikely planned for 3.0
- Don't see your idea?