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.
18 results found
-
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".
22 votes -
Quick Grouping and Sorting
Currently we can only use quick filters. The most used feature in our customer projects (datacenter) is the quick group feature.
This feature should be available on structure cloud as well, because it makes the use of structures so much more flexible and enhances the usability.
Currently our users create a lot of new structures just because of this missing feature. Obviously this leads to maintenance issues, because all other configurations need to applied across multiple structures...Same goes for Quick Sorting, but the grouping option is more important.
9 votesHi Martin,
With the latest update, we've added quick grouping capabilities. Sorting by a column is already available for our users. Please, take a look and let us know if it solves your use case.
Quick groups:
https://wiki.almworks.com/documentation/structure/9.0/cloud/quick-groups-187662723.html
Sorting by columns:
https://wiki.almworks.com/documentation/structure/9.0/cloud/sorting-by-columns-157319184.html
-
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? -
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… -
"Effectors" feature for Structure Cloud
Hello, our organization is using Structure apps for our projects management. We just discovered, that in Jira DC/Server the Structure app has a feature called "effectors" https://www.youtube.com/watch?v=oE1dSklL9D8 . Could you add this feature to the Jira Cloud Structure app? If there is any chance to raise the priority of this feature in your roadmap - it would be great!
This is one of the most important features for us.6 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.
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?
-
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
-
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?
-
Colorize field depending on the value
Make it possible to colorize a field depending on the value, similar to Wiki Markup for Structure for Server/Data Center.
I want to use Structure as a dashboard to monitor project status or individual issues. Color indicators quickly highlight the status. Especially a simple green, yellow, and red colorization of the text or the panel can help a lot.
3 votes -
work logged (in maydays)
Now the field 'tempo work logged' calculates the time logged in: xW + xD + xH etc. Can you also make time summed as 'x Mandays' or 'x Hours' as calculating in weeks is not easy to calculate a budget. From project management perspective its better to have a start and finish date a.k.a lead time AND the time (hours or days) spent in mandays to very the budget.
3 votesHi Tom,
Thank you for your request.
Could you please clarify, how you make calculations on the work-logged data? Do you export structures to Excel first?
-
Tempo Hours in Structure: Budget (planning) - Actuals (logged) - ETC (remaining)
As a Project manager, it's handy if the hours are visible in Mandays or Hours to check the financials. 3 columns if (not yet already available to see the Tempo Hours in Structure cloud: Budget (planning) - Actuals (logged) - ETC (remaining). And this is for each separate issue type and rolled-up based on hierarchy or grouping. And visible or reported not in weeks but accumulate in mandays and/or hours. Tom
3 votesHi Tom,
Thank you for your request.
I see that you require your columns to be in a specific format.
But could you please clarify, do you have the Budget (planning) column already or do you want it to be implemented? If you already have the Budget column, is it just a custom field in Jira?
Thank you,
Konstantin
-
Allow entering list values on separate table rows
It would be nice to have options of single and multi-select list fields optionally displayed in different rows.
2 votesHi Dimitrios,
Thank you for the request. Could you please clarify a little what do you mean by select fields displayed in rows?
Is it about Jira fields? Do you want them to be in rows, but not columns? How would you like to use it and why?
Thank you,
Konstantin
-
Filtering a selected item should not cause its children to also be filtered
Filtering a selected item should not cause its children to also be filtered. I tried filtering a selected item that had children and was expecting everything but the item and its children to be removed. However, applying the filter removed all child items, which essentially renders the filtering feature not very useful.
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 -
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 -
Progress by TimeTracking original/remaining split
Use colour to show time remaining vs original estimate as in standard JIRA progress fields when using time for estimates
1 voteThank you for the request.
Could you please clarify it a little bit and share your use case? Do you want this progress bar to be split on estimated, remaining and logged separately as in standard Jira On-Premise? Or what would you like to see in this column actually? How are you going to use it?
-
Allow Drag and Drop re-ordering Structure Cloud
In Structure cloud, I cannot drag and drop items to re-order them. When is this on the product roadmap for release/?
1 voteHi Domenic,
Thanks for reaching out. There are already a couple of ways to drag and drop issues on Cloud:
- If you have a manual hierarchy (a hierarchy that is built without generators): https://wiki.almworks.com/documentation/structure/latest/cloud/building-a-structure-manually-130881237.html
- If you use a sort-by-rank generator, you can also use drag-and-drop to change Jira ranks: https://wiki.almworks.com/documentation/structure/latest/cloud/sort-generators-130882739.html
Our Data Center version supports manual adjustments, did you by any chance mean this type of drag-and-drop? https://wiki.almworks.com/documentation/structure/latest/data-center-and-server/manual-adjustments-57934755.html
-
Manual adjustments to automated structures in cloud
We want a structure where automation is used to fetch issues, but where we manually sort issues into a hierarchy of folders.
It can be done using metadata for issues, but that has two drawbacks:
1. It can be quite tedious to update metadata to get the issue into the right folder
2. If someone "else" updates the metadata the issue will move immediately. We what to do the moving manually in status meetings/during grooming.1 voteHi Lars,
Thank you for your request.
Could you please share a little bit more details so we could learn more about your scenario? Why do you need automation to fetch issues, and adding them manually and moving between folders won't work for you?
- Don't see your idea?