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
-
Intergation width standard JIRA filters
Allowing in JIRA filters can be filtered by issues that you belong to a structure.
3 votesplease see the question in the comments
-
Extend Sub-Task Synchronizer with JQL filter
The Sub-Tasks Synchronizer only allows to select the Issue-Type to be selected. It would be helpful to have a JQL field to filter out more and also to have a JQL field when a Sub-Task should be removed from the Structure.
3 votes -
Add link to documentation and resources from toolbar drop down menu
I'm the admin and know of and installed structure, however, my JIRA users don't know what it is or how to use it. To help educate all please include links to helpful resources in your toolbar drop down such as documentation, etc.
Thank you
3 votes -
Automatically clear multi-selection after a move/paste operation is completed.
The structure plug-in allows users to select multiple, dis-contiguous issues using the multi-select mode, whereby the user clicks on the little radio button next to every issue they want to select. The selection can then be operated on as a whole, for example, to reposition the issues in the structure.
This feature works great, however, I find it annoying because the selection 'sticks', even after I've completed the operation I wanted to perform. Then, when I move onto select other issues, the previous ones, which are still selected, unintentionally come along for the ride.
Let me provide a use-case. Assume…
4 votes -
Create a method to prevent parental and causal links to sub-tasks unless those sub-tasks have sub-issues
if you have issues with sub-task type issues there's no way to pull those sub-tasks and any child or resulted in linked issues into a structure without structure creating child and resulted in links for all sub-task tasks of those parent issues. It appears that any configuration of the links synchronizers will results in the sub-tasks getting child and resulted in links to the parent issue. If this is true, I propose the following feature request.
In the Links Synchronizer, create a sub filtering feature that uses the logic of: "don't create parental or causal links for sub-task type issues…2 voteswaiting for clarification
-
I suggest the structure gadget displays the full name of the structure in the dashboards
Currently it truncates the names so it is difficult to tell which structure is displayed.
2 votes -
1 vote
Will review after Structure 3.0 release
-
Ability to weight Progress column by number of issues
(e.g. a parent’s progress is just based on the progress of its children, but if one of those children has 10x more children than the other, it would be nice to weight it that way)
3 votesrequirements gathering
-
Queries based on structure, especially ones that make roll-up easier
- All issues that are direct children of this issue
- All issues that are children, grandshildren, etc. of this issue
- Parent of this issue
- Store the structure information in the same tables as other JIRA information, so it can be queried the same way.
3 votes -
3 votes
planned as the Structure Board with preview
-
Support wildcard in structure() S-JQL function
I would like a way to use a 'wildcard' in the structure() S-JQL function so that it searches all matching structures. Specifically, I am trying to solve the following problem: find all leaf nodes in any structure.
Here's a potential use-case: I want to have a task backlog implemented in Structure. I also want to be able to organize my tasks in a hierarchical manner, also using Structure. In my task backlog, I only want to track the 'leaf' tasks which appear in my hierarchical structure.
I know I can do this now using the structure() function, but I must…
0 votesalso tracked as https://jira.almworks.com/browse/HJ-1365
-
Limit Structure Depth for "Master" Structures
With all the work being done to create sub-structures or copy portions of structures, the master or enterprise view typically does not need all the detailed subtasks, those will even make that view less usable. It would make that view more useful to have a default depth to open the tree, so if I have
Issue-1 - Project
Issue-11 - Milestone
Issue-111 - task 1
Issue-112 - Task 2
Issue-2 - Project 2
Issue-21 - Milestone
etc.I can have structures for the projects with all the details, and the structure for multiple projects defaulting to open to a depth…
2 votes -
Option to always include Epic Link in the Structure
Same as the option to automatically include sub-tasks in the Structure, also add the option to always include the Epic Link.
3 votesrequirements gathering
-
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 -
Search Filters Should Retain At A Structure Level
If you have several structures that you are attempting to manage when you switch between them your search panel tries a filter / set of search criteria from the previous structure. Then you have to figure out that you want to apply filter=29121 or whatever when you go from structure A to structure B.
Easy fix.
3 votes -
Use JIRA Structure as navigation tree on linked Confluence content
JIRA & Confluence are often used hand-in-hand... e.g. new ideas are formulated on CFL, leading to linked tasks in JIRA & followed by documentation etc.. on Confluence again..
The need to reorder issues in JIRA, & use structure to navigate them, can be projected to linked confluence contents as well.
The way i see it, structure widget could replace the space navigation panel.
JIRA issues & corresponding Confluence pages could be linked via labeling (value == structure item ID)
This is the idea in a nutshell, I'd be happy to discuss in more detail if helpful.
6 votes -
Support hierarchy of projects
Can I display a hierarchy of projects? I have a project x that is a sub project of a, b, c. Is this possible?
8 votes -
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 -
Show some type of visual indicator when the progress rollup contains interpolated data
I love the ability of the structure plug-in to roll-up numerical fields of children into their parents (thank you!). As I understand it, if some of the children do not have values, the roll-up algorithm estimates values for those children based on the values set in their peers (i.e the value of the unset children is the average value from all of their peers). Essentially, the structure plug-in is making estimates for the children even if users haven't entered any information.
When that happens, it would be nice if the plug-in offers some kind of indicator on the rolled up…
2 votes -
Limit parent-child relationship to specific types of issues
Let JIRA admin specify what issue types could contain what other issue types. For example, a Test Suite may contain Test Cases, which can contain other Test Cases, but not Feature Requests.
86 votes
- Don't see your idea?