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.
173 results found
-
In a multi project
In a multi project scenario can we have a scattered epic(collection of stories implemented by different projs) to be tracked as part single structure this will allow big programs to be tracked for their distributed progress in individual queues and collective status at one place for decision making.
1 votewaiting for reply
-
Retain hyperlinks when printing a Printable to a PDF
The Excel report retains hyperlinks back to the issues. The preview of the printable also does, but these are lost when printing to an actual PDF.
1 votewaiting for reply
-
Add a ShortCut to "Show in Structure" inside a Jira structure section
Currently, clicking on the Structure: <structure name> text colapse / expand the structure section inside a Jira. What would be very usefull is for the Arrow to Colapse/Expand and the Text to link to the Full Structure page (Since some actions are better executed in the Full Structure)
1 vote -
1 vote
-
Allow me to include explanatory text
I build Structures for people to look at. There is always a type of interpretation I need them to make.
So, I need the ability to put at the top and bottom of the page an explanation of what they are looking at and how they should read it.
For instance, on a budget, to say "this sum of Remaining Estimate field is shown as 1w1d5h but should be interpreted as X hours; Export to Excel, total the field and multiply by our hourly rate * 24/8 for a billing number"
Else people land on the screen and say "so…
1 vote -
Ability to compare percentage realized versus percentage predicted (as a new calculated column) on the structure.
Igor,
I wonder if it is possible to create some kind of calculated column to show the percentage of the predicted structure for the current moment.
Obviously if the issue had any reference date (ie due date) for comparison and the grand parent issue too. Just like we do on a project via MS Project.
This is to compare how we are, in percentage terms (functionality already implemented) versus how we supposed to be (forecast until the present day).
I leave here the challenge to improve (even more) this fantastic ADD-ON.
Cheers!
1 vote -
Add a "quick search" feature in structure drop down menu
Currently if you want to find a structure that isn't in your most recent or top favorite you have to go to the more... option in the structure menu to find it. This means navigating around to other pages to search for a structure. It would be much nicer if there were a filter / quick search at the top of the menu that lets you quickly find and view a structure.
1 vote -
1 vote
Will review after Structure 3.0 release
-
Improved User Interface of the STRUCTURE Plug-In
The font and back ground colour should be customizable.
1 vote -
1 vote
-
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 -
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)
-
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.
-
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
-
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
-
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
-
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 -
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
-
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 -
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
- Don't see your idea?