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
-
Would like a way to get Structure formula calculations into "normal" Jira custom fields
Structure formulas are extremely useful. Now our users would like ways of using them in other places within Jira. This may be tough in some ways because they are specific to the structure they are part of, but even something simple like the ability to choose an menu option or call some API to commit formulas into an underlying custom field could be quite useful.
4 votescollecting requirements, 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
-
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
-
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
-
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
-
...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.
-
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
-
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
-
1 vote
Collecting requirements — please see comments.
-
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.
-
support grouping of issues by link type
e.g. all 'Blocked By' issues added via Extend automator grouped together under parent.
This makes the Jira relationship between Structure parent/child issues clearer.
3 votes -
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
-
Creating structures from agile boards with Epics and Epic-less tickets
When creating a structure from an Agile board it would be nice to be able to add as well Epic as stories not assigned to an Epic.
Creating a structure with Epics and adding an JQL-Inserter for the Epic-less Stories is not sufficient. I am not able to move Stories into an Epic later on the structure board this way. ("Cannot remove issues from JQL query result. ")
3 votesplease see the comment for an alternative setup
-
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 -
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
-
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 -
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
- Don't see your idea?