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.
384 results found
-
Why the limited functionality of Structure Cloud?
Why the limited functionality? No Gadget for Dashboard? No column sort? No bulk change?
7 votes -
Available resources
Limiting number of resources that can be allocated for a day to specified number.
Use case: I have two people working on a project and they can't do more that two cards at the same time.
3 votes -
Ability to Stop Structure from Updating So You Can Change the Automation
When trying to get the automation correct for a complex structure, you can spend a lot of time just waiting for things to load so you can update the automation. Would be great if there is a way to click on the spinning weel to stop the automation.
1 voteThank you for the request!
-
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 -
Use Monaco editor for editing formulas
The Formula column is a killer feature, but it can get tricky when the formula expression grows larger than the size of the editing area, and has a few levels of nested expressions.
Beyond just the ability to enlarge the editor, it would be fantastic to have a more advanced editor to assist here, and the obvious candidate is the https://microsoft.github.io/monaco-editor/
My suggestion for iterations for this would be:
- Just replacing the actual editor and make sure it's still working when editing and not (so no functional changes)
- Adding config and definitions needed for highlighting brackets and auto…4 votesThank you for request!
-
Have option to show multiple tasks on one row in Gantt
Currently we are using a different app for this but would prefer to use Structure.
9 votesHi Peter,
Thank you for the suggestion, we’re evaluating this idea and figuring out how to do it the way it will work for most use cases. Can you please describe your use case in more detail?
Thank you!
Regards, Alexey
-
4 votes
Thank you for the request! The feature is already in our backlog.
-
Show Which Columns Have Been Edited Before You Revert
As a product manager editing a structure view that is being used by other people on my team, I want an indicator to show me which columns will be removed if I revert changes to the view, so that I can experiment with changes to a view and feel confident that I know which columns will be discarded when I revert changes.
This would be especially helpful for formula columns, as it can be time consuming to create them, and I want to feel confident I'm not going to lose work if I revert changes. It will also help me…
1 voteThanks, please check the comments
-
Allow multiple simultaneous updates
The edit capability in the table view is very helpful but even more helpful would be ability to update multiple fields and/or multiple issues. Is copy a row or column or table from Excel into structure table.
6 votesthanks! please check the comment
-
Have option to customize or hide what buttons are shown
Trying to get users to update information who are less familiar with Jira. Want to customize what options/buttons users see so it's less overwhelming.
5 votesthanks! please check the comment
-
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?
-
1 vote
Thank you for the suggestions! Please check my comments.
Julia.
-
Removal of manual location of individual issues
When an issue is shifted manually around in a generated hierarchy, it retrieves the "hand" symbol and the position seems to be memorized in an (invisible, structure internal) attribute. Sometimes this memorized position gets in conflict with updates generator rules etc. and I want to withdraw the manual relocation. But not for all relocated issues (which is possible) but only for individual ones.
1 votethank you!
-
be able to export to .xlsx (xlsx-Format, MS Excel 2016 and higher)
Our users like to export their structures to .xlsx to use the full functionality of modern Excel.
3 votes -
"Remove Inserter/Extender Duplicates" generator should also work for non-hierarchical duplicates
When using the "Remove Inserter/Extender Duplicates" generator also non-hierarchical duplicates, based on different used linkage types like "child-of" and "resolved by" should be removed.
6 votesThank you! Check the comment, please
-
user defined rank attribute
Create an attribute "Rank" to allow a user to manually order stories.
Use case: I want to prioritise stories for a given release. e.g. I have 20 stories and want to rank them 1-20.
Benefits:
- the ranking is more transparent to a larger audience than the ability to move stories on screen
- if another user changes the order I can see what was changed5 votes -
Allow for shared filters similar to how views are managed
Similar to how views can be shared across different Structures, it would be great if Quick Transformations could be the same. Right now, we have 15+ separate, but related Structures. All should have consistent views and transformations. Managing views is very simple, but if you change a filter on one Structure, you must replicate that change X more times.
5 votesThanks for your suggestion!
-
Add Project Category
Structure recently added the ability to use "Status Category" as a column. As Categories can be pretty powerful tools, I would like to suggest bringing "Project Category" in as a column as well.
In addition to columns, the bigger need I have at the moment is to be able to "Group by" Project Category in the Automation options. I also noticed that Status Category is missing here as well, so I think it would be great to bring the existing work to the Automation section as well.
4 votesThanks! Please check the comment
-
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?
- Don't see your idea?