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.
374 results found
-
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
-
Reorganize the ManageStructure page
- allow us to specify a short name for each synchronizer
- move the items which appear once per structure, i.e., Name, Owner, Access, Popularity, Operations, out of the table to a header, so that the information in the Sync With column could be expanded: this would allow more room so that the Sychronizer Short Name could be displayed, and the type of synchronizer would not line-wrap. Thanks !
1 vote -
Add ability to right click on selected item(s) to move to top, to bottom, down/up by like 50/100/200 rows at a time
This will save time in organizing one's Structure especially those items that are completed and need to be moved way down or those items that are open and need to be brought way up. This would especially be useful when initially setting up one's structure.
3 votes -
Indent Structure based on JIRA Issue Type as is done with Summary field based on Issue Type
epic TP icon
story TP icon
story task TP icon1 voteNeeds clarification – please see comments.
-
Allow "Active Sprint" option for the Work Logged field
Currently, the options are current and prior day, week, month, year. Can we have current and prior sprint?
3 votes -
Deactivate Cut, Copy, Delete
See: https://answers.atlassian.com/questions/12918198/deactivate-cut-copy-delete-in-structure-plugin
The actions should be deactivatable via permission-level or global setting.
1 vote(please see comments)
-
import from excel
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…
2 votesNeeds more details – please see comments.
-
Allow users of the Tempo Plugin to see a per-user summation of time usage
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…
7 votesshould be possible with Structure 3.0
-
Drag and Drop Structure Nodes into JIRA Sprints
It'll be great if I can drag my structure into my sprint and have all the sub issues displayed nicely (incl estimated story points or hours for all sub issues) under that sprint.
1 vote -
Show more results to allow me to use the browsers scroll function.
The view port of the structure plugin is rather small. I can only see a max of 12 rows on my screen (1360x768). I need to export to excell to see more stories in my epic. It would be nice if more results are displayed on the screen. And to be able to use the browser's scroll bar to scroll, that's why it's there. Or did I miss a config option?
4 votesinvestigating – please see comment
-
[Structure+Testy] Make it possible to have a type of parent child relation inside an issue
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…4 votesCollecting requirements – please see the comment.
- Don't see your idea?