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.
375 results found
-
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.
18 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
-
allow me to define a story point budget for a folder / issue
I typically have rough estimates for bigger projects and I would like to be able to add them to the structure so that I can get an overview of what needs to be done. At the moment I can only do this by adding JIRA issues with estimates, but the problem is that at this stage I do not really want to create these issues yet (at least not for everything).
The closes thing to what I want is to create epics and set the rough estimates on the epics. Later I can refine my estimates by creating storys. The…
3 votessee comments for details
-
Allow user to make a new copy of multiple items from one structure in another structure with new keys.
We have several structures in place now, each with several epics (epic = enhancement for us). We need both an enhancement template and a test plan template, each having several tasks in their hierarchy, in a separate structure. For each new enhancement, we would copy the template into our structure, then edit it to be workable. So we either need the ability to copy a structure template into another structure, clone multiple issues from one structure to another, or make templates out of portions of a structure's hierarchy that we can then clone to another structure.
19 votes -
Filter the issues that aren't picked up by the generators
To force a rebuild of the structure based on generator rules only.
The filter would help to identify the issues manually added into the structure.
Then we can decide which issues (all or selected) to remove from the structure if not relevant.Problem: We cannot remove all the issues from the structure. There's a warning when removing at least one issue that is picked up by the generators, and when we acknoledge all the issues come back.
1 votecollecting requirements — see comment
-
Bulk Clone Part of the Structure
This is becoming a necessity as we move forward with Structure. In order for all users to easily make copies of sets of issues from a repository-type structure at different points in their structure, we need bulk clone. The current copy/clone process requires admin authority and too many steps to roll out to non-admins and expect the environment to stay clean.
13 votes -
1 vote
Collecting requirements — please see comments.
-
Folders within epics and Epic extension automation
I need to track business Epics, but these are usually large and I like to break them down into smaller-sub-epics to deliver and track (via multiple releases). Jira doesn't support Epics with Epics (unbelievable really) and I need to work at ira as well as structure level so I create folders in structure under the main epic to perform this partitioning. Each Jira story is still linked to the main epic so I can use Epic reporting in main Jira, but it does mean that I can now track sub-epics at the folder level in structure too. Unfortunately this means…
1 voteanalysis — see comments
-
It would be great to be able to clear out the clipboard..
RIght now there does not appear to be a away to remove issues from the clipboard (other than pasting). Seems like a user may try to do a cut / copy and decide they no longer want the issues. Seems like this could be a fairly simple fix (maybe a x button above the clipboard?).
1 vote -
Connnect more than one JIRA instance
When working with external partners they often use their own JIRA instance. You can connect them via the JIRA application link feature with your own JIRA instance and are able to set links between issues in the two JIRA instances this way.
It would be great to be able to display linked issues from the remote JIRA in your own structures.
2 votesCollecting requirements – please see comments.
-
Allow re-formatting aggregated time fields (e.g. into hours).
We are budgeting a project - so we need to show a rollup of hours and then an extension of these hours into costs.
So we need to be able to:
a) format time so that it doesn't simplify 60 hours spread over in a year into 1w 2d 4h - it needs to show as "60 hours"
b) provide a column that does math on the 60 hours. e.g. 60 hours at $125/hr = $7500Together we will rid organisational planning of excel :)
M.
1 vote
- Don't see your idea?