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.
64 results found
-
Reverse the order of the Epic column string
I'm very pleased to see the addition of the Epic column. However, it presently is displayed with [Key]-[Epic Name].
It would be more useful to see it displayed as [Epic Name]-[Key], or at least the option to select between the two.
1 vote -
Have different permissions for the editing of values in columns and rearranging structure through drag and drop
Instead of having one Edit permission, divide it into 2 different ones. By doing this, users that can edit values in columns cannot rearrange issues in the structure by mistake with the drag and drop feature.
- Permissions to edit values in columns
- Permissions to rearrange items in structure under group by automation (Change Epic,Rank,etc)
1 vote -
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… -
Change status sort order by their position on the statuses page
Hi,
currently statuses in cloud version are sorted by their:
- Status category
- Project (global statuses are shown above)
- Status ID (field id?)
and as a Jira admin I'm unable to change the order.
In server/DC version this feature is much more usable and I'm able to change the order which has huge impact on how we use Structure in planning.
Cloud sort order documentation: https://wiki.almworks.com/display/strcloud/Sort+Order
Server/DC sort order documentation: https://wiki.almworks.com/display/structure/Sort+Order
1 vote -
Add ability to edit name and rank of Version/Release
Add ability to edit name and rank of a Version/Release from within structure. Right now that's not possible and it's very inconvenient to navigate to the project in scope to make this edit.
1 voteThank 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. -
Add "Configure Structure" to Tools in the Structures pull-down in Structure Cloud
I'd paste a screenshot here if I could. At the bottom of the pull-down under the Structure name, it says "Tools: Create Structure, Manage Structures. Manage Structures just takes you to a screen where you have the choice of configuring the structure, or opening the structure you just left (this is useless), or delete the structure. Why not put "Configure Structure" on the pull-down with Tools, Create, Structure, Manage Structures, and make the Manage Structures button take you to Manage All Structures? You should also put a filter box on the Manage Structures page so you could zero in on…
1 voteThank you for the request, we have plans to improve this functionality in the future.
-
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 -
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.
7 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? -
When Grouping by Labels add ability to limit the labels in scope
Group by Labels is a useful feature, but has limited efficacy when there are too many labels.
Being able to limit grouping to a specific list of labels, would result in only those groups being displayed.
1 voteThank you for the request!
-
Can "Remove Inserter/Extender Duplicates" be added to Structure Cloud?
I use this filter automation all the time in Structure on Server, sad to see it's not there on Cloud.
1 vote -
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 B9 votes -
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?
-
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
8 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?
-
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 -
Why the limited functionality of Structure Cloud?
Why the limited functionality? No Gadget for Dashboard? No column sort? No bulk change?
7 votes -
Show ellipses menu for issues
Show the [...] menu for an issue to allow standard features such as assign, workflow transistions etc as is done elsewhere in JIRA.
1 vote -
4 votes
Thank you for the request! The feature is already in our backlog.
-
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
-
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.
4 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?
- Don't see your idea?