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.
-
Moving items in the structure will update ANY task link / parent
Our organization would like to have a possibility to move any task in structure and update issue links accordingly.
F.e. Move the subtask from one issue to another in structure - this should change the parent link for the subtask.Move task without epic link inside the Epic - update Epic link.
Move Epic task to another random task - a popup should appear with question "choose link type".
18 votes -
Export to Google Sheets
Make it possible to directly export a structure into Google Sheets. It will save one step converting an Excel file into Google Sheets.
10 votes -
Add color in rows of Structure
Currently Structure doesnt have capability to add color in cloud version good to have if I am building multiple hierarchy one
8 votes -
Why the limited functionality of Structure Cloud?
Why the limited functionality? No Gadget for Dashboard? No column sort? No bulk change?
7 votes -
As a user I would like to be able to view issues in a side pane instead of having to load a new page
As a user, I would like to be able to view issues in a side pane instead of having to load a new page, so I save time in looking at the details of each issue
7 votesThank you for the suggestion!
We cannot reuse Jira’s issue view, so we will have to implement our own, and implementing it will be a challenge. Most of the Jira fields can already be viewed inside Structure and changed by inline editing.
Could you please describe what you would like to view or edit in the side panel?
-
Group by Link Type
Group by Link Type.
We have many link types used to represent different things.
E.g.
- A "Story" ticket may [LinkType: Satisfy] many "Acceptance Criteria" tickets
- A "Bug" ticket may [LinkType: Block] a "Story Ticket"
- An "Epic" may [LinkType: Solve] a "High Level Requirement" ticketWhere tickets have multiple types of link coming from them, would be nice to have that as an explicit folder / grouping in the tree.
E.g.
Story XBlocked By
Bug Y
Bug Z
Solves
Acceptance Criteria A
Acceptance Criteria B6 votes -
Deeper hierarchy in issue types
Our organization would like to have a possibility to create another tasks layer above Epics (like in Jira's advanced roadmaps). For example, I create a new issue type "Initiative" in Jira and then I can group in structure gantt all tasks in this hierarchy:
Initiative>Epics>Stories, Tasks>Subtasks.6 votesActually, that’s something Structure can already help you with!
Structure allows creating hierarchies using existing relationships between issues in Jira. If there is a link between two issues, Structure can visualize the relationships in the parent-child form, putting one issue above the other.
You just need to use standard Jira link functionality which is available in any Jira version by default – the ‘blocks’, ‘implements’, etc type of a link. You can configure them at Settings | issues | Issue linking and create links between issues using the Link option on any Issue Page.
And once links exist between Initiative and Epics, then you can build your structure with the desired hierarchy the following way:
1. Create a structure.
2. Click Automation | + | Insert and type a JQL query to match all Initiatives that you want to add.
3. Then click + | Extend | Linked Items and… -
Group by Due Date
I need to be able to group by Due Date, so that we can see the progress of all items assigned to a particular date. It seems like this may have been solved in server but not in cloud.
6 votes -
Progress by status category
Currently progress by status is supported(among other statuses).
To simplify configuration in complicated jira setups it would be nice if one could filter by status category. Instead or in combination.
5 votesThank you for the suggestion.
Could you please share your use case and some details about your setup? What do you want to achieve with this functionality?
-
4 votes
Thank you for the request! The feature is already in our backlog.
-
Support S-JQL in JIRA Cloud
S-JQL is supported in non-Cloud versions of Structure. It would be really helpful if it could be made available to the Cloud version as well.
4 votesThank you for your suggestion!
Unfortunately, Jira Cloud does not support custom JQL functions for now. So it’s not possible to migrate S-JQL as is.
We may try to find a workaround for some specific use-cases. So could you please describe what you want to do with S-JQL? -
Need new "workload" view
I would like to have the same functionality as InstaGantt has. The workload functionality is simple but genius.
On the Structure side, the workload view is very limited and hard to use. you have manually filtered out the required people to view their workload. After page refresh the filter resets and you have to apply filters wor the specific people from the very beginning.
3 votes -
A possibility to have scenarios in gantt.
Our organization would like to have a possibility to perform changes in Gantt, check how those changes affect the resources, and decide to save them or not to save (and rollback to live view window).
3 votes -
Vertical marker line in a gantt chart
Our organization would like to have the possibility to create vertical markers in a Gantt chart. For example, I press on the timeline a popup appears, I write a description there and save it.
3 votes -
It would be nice if you could change the colour for different types of links
Would it be possible to somehow recognize different types of links in the structure? e.g. add an icon for issues which are linked by "is blocked by" or change the colour of the blocking ticket.
3 votesThank you for the suggestion.
Why would you need to recognize different link types in Structure? Do you have multiple Link Extenders on the same level? Could you please describe your structure a bit and what problem you are trying to solve?
-
Notes on folders or any other elements
Could be nice be able to write descriptions/notes on folders and maybe other elements like groups. It would be a way to have a private environment for product owners to discuss about OKRs or any other thing on the panel
3 votesThank you for the idea!
-
Upgrade the Structure Cloud Manage Structures page
There's a lot of whitespace and not a lot of function.
* You could use more than 3 columns to show more information, e.g., the description and the permissions.
* You could support more actions:
** Copy an existing structure - then you could copy and tweak instead of starting from scratch every time
** Support right-click on Open to open in a new tab3 votesThank you for the request!
The improvements you have suggested are reasonable, and we have plans to update this functionality in the future. The ability to copy structures is already in our backlog. -
Have a structure folder be a Jira component
Would be great if this could work in 1 or both directions:
When creating a folder, I have the option of pulling a component from my component list (perhaps there could be an option to instantly pull in all existing issues in the component)
Ability to "nominate" a folder as a component (perhaps there could also be the option to add existing and newly added issues from the folder inside the structure to the Jira component)
3 votesThank you for the suggestion!
For now, folders are designed as our internal entities to structure a hierarchy. But you can use Grouper Automation by Component. https://wiki.almworks.com/display/strcloud/Field+Grouper
If Field Grouper doesn’t work for you, could you please share your use case? Why do you need to integrate folders and Jira components?
-
Open issues in Jira search view
It would be helpful if you could open a folder, sub-folder or a grouping, within your structure, in the Jira search view pre-populated with the issues in folder. This would allow you to easily share specific issues in your structure with relevant engineers so that they don't have to find the issues themselves within your structure.
Examples:
Create a sub-folder and insert issues using JQL. Open all the issues in that sub folder, in a Jira search view. From the Jira search, you can easily share with team members.3 votesThank you for the suggestion. As I understand, you want to share issues from the structure somehow, right?
There is the “Sharing a Perspective” feature in Structure for Jira On-Premise. It allows you to focus a specific folder or select some issues and share this view with others in the form of a permanent link.
Would this feature solve your problem if we migrate it to Structure Cloud? You can read more about it in our wiki https://wiki.almworks.com/display/structure/Sharing+a+Perspective
-
introduce the same TP column as in the non-cloud versions
The TP column provide icons with summarizing information. I miss this in the cloud version
2 votes
- Don't see your idea?