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
-
"Sum over Sub-items" For Dates / Aggregate Dates - with the ability to choose Max or Min Date
I'd like to see my dates roll up the hierarchy so that I can see higher level estimates as they roll up. For example, if I have a folder for a project and I have a number of tasks underneath, I'd like to see the latest due date in the project, or the earliest start date.
3 votesAlready possible with latest Structure – see comments for details. More improvements are coming.
-
Support a User Story Map View
User Story Mapping is becoming a very popular way to organize your product backlog: http://www.slideshare.net/nashjain/user-story-mapping
It basically uses a 3 level structure but displays tickets in a vertical layout, as illustrated here:
There are only a few tools that support this online, and only one that is part of JIRA. The market is ripe for a tool that is robust, simple, and flexible. Since Structure already organizes tickets hiearchically, all that would be required would be to create a new view of a Structure, with a possible limit of 3-4 levels. (The Story Map structure only supports 3, but I…
25 votes -
allow filtering a centralized time period for a view with multiple worklog columns
when you report worklogs with structure, you want to use the worklog column and specify a time period.
If you add multiple columns, it is quite an effort to change the time period from eg. dates of jan to feb. (currentmonth is helpful, but somewhat too dynamic if you want to compare months)To easily switch between months it is necessary to switch the time period you look on on the view level and influence alle worklog columns this way.
3 votesThanks!please read the comment
-
provide "root element of column x" in the variable selection list of formula column editor
E.g. to calculate a percentual distribution over all rows of a structure, for the formula you need the 100% value which is typically shown on the root element.
Therefore it would make a lot of sense, to be able inside "formula column A" to use a columns B's value, but the root element value! This should be possible even if column B is a formula itself.
As we can already use variables like "Column B ..." in formulas it would be nice to add "Root Value of Column B ..." to the variable selection list3 votesThank you for the idea! Read the comment, please
-
Documentation Update - How to create a new View
The Structure 4.5 documentation is lacking when describing how to create new views.
For example, if I take "Basic View" and copy it to my Structure, I would expect that I could edit it, but the View Details screen says
Access: Use - you can use this view but you cannot update it.
There is no "Save As" button as indicated by the documentation.
1 votethanks! please see comments for more information
-
notes
To fully take advantage of the new Notes field it would be really nice to make it independent of the issues to which it is added. As it works now, if a structure contains a multiple of the same issue and a note is added this note is attached to all of these issues.
Separating this is actually the only thing left to be able to use the structure plugin as a product structure documenting an entire product portfolio. One issue for each part and the notes field (renamed "Qty" or similar) to hold the amount of parts of the…
9 votesThank you! Please see the comment
-
Would really like to be able to color fields, columns or rows in structure chart (without having to pay for expensive plugin)
I create some rather large Structure charts with multiple levels of nesting. Want to be able to highlight aspects of the chart (Rows, Cells, Columns) with color. This helps with focus (these items are critical), organization and overall visual appeal.
1 voteThank you for suggestion! It is under review
-
prevent double counting
When an issue appears multiple times in a structure (e.g. epic link and issue link),the progress calculation should be configurable to prevent / allow double counting
3 votesplease see the comments
-
Limit the issuetypes for automators so you can use multiple link automators per structure
With Synchronizers it is possible to limit the issuetypes. Therefore it is possible to have multiple link synchronizers for different issuetypes.
Example:
one could defined a parent/child link between epics and features and use a is blocked link between features and bugs. with automators this scenario can not be implemented at the moment.1 vote -
Use different fonts for the levels in the hierarchy to make them more distinct
It would be great for easier differentiation to make the font larger for higher level issues in the hierarchy. E.g.
Level 0 - H1 Bold
Level 1 - H2 ...
Level 3 - H3
etc12 votes -
Hide empty folders
In structure folders created based on custom fields will show "no value"-folder in case issues haven't set the related custom field. It would be nice to get an option to define whether to show such "no value" folders or to show such issues without a folder under their parent.
2 votesPlease see the comments for a workaround.
-
Can Structure use Portfolio Data
Structure would be a great supplement to the information provided by Portfolio. It would be great if this data could be used by Structure ... perhaps even have a Portfolio Structure Template?
7 votescollecting requirements – please see comments
-
be able to copy directory path
This feature can help a user orientate an issue in a structure, or share the path with another user easily.
1 votecollecting requirements — see comments
-
Add ability to synchronize at the Project category level
A structure is set up across multiple JIRA projects and when I add a new project, I have to redo the synchronizer. If I could select a Project Category instead of individual projects, then I would only need to add the new project to the project category.
4 votes -
Enable you to specify a parent issue when doing "+ Add to Structure"
Currently in the Issue Page you can only add the issue at the end of the structure.
Parent issue input could be equal to the way we Link issues in JIRA.
19 votes -
Sync task to add Tasks to Folders
Folders is a great new feature in 3.0 (long awaited) but the sync tasks do not allow tasks to be added to folders which is an obvious feature for auto adding tasks to structure and also a huge use of ordering and sorting tasks in structure.
3 votescollecting requirements – please see comments
-
improve support for Quick Transformations
Currently you can save transformations as quick transformations which is a great feature. I see however certain potential to make it even better:
- Combine several transformations into a single Quick Transformation (e.g. filtering and grouping)
- Define Quick Transformations for the "Jira" part of the double grid: I often look for items assigned to a version in order to add them to my structure. It would be super convenient if I could save it as a Quick Transformation.
Thanks for your consideration and keep up the great work!
3 votes -
...have separators, or sticky issues, that stay on top.
My idea is that I want specific issues to not be affected by the sorting. Not affected, so that they can stay on top (or bottom).
Another cool way to do this may be a separator or separators, that can be added similar to the way folders are added. Except these separators allow their content to stay where the user assigns it to.
2 votesConsidering the feature — please see the comments.
-
Progress Bar changes color by ontime or overdue
Allowing users a quick view of the status for more than completion percentage for [insert your object of choice] if they are overdue or nearing completion deadlines
3 votescollecting requirements — see comments
-
Be able to propagate up a risk value
If a sub task had a custom field which indicated it's current risk or similar be able to propagate that up to the top level to show the worst of the risks or some other flag
e.g. if a single subtask of a item is red risk, be able to show that red risk in all of it's parents in the structure. choose the worst value of all sub nodes to show at the parent level.
3 votescollecting requirements — please see comments
- Don't see your idea?