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.
98 results found
-
Include "Epic Link" in Categories that are copied when adding issues
The ability to add issues directly in structure is great. Especially when using the "Copy from" categories option to have a new ticket inherit a lot of values from another ticket. It would be REALLY useful to have "epic link" among the list of included fields that are copied. I've used the "required fields" workaround for other fields, but unfortunately "epic link" cannot be made required.
6 votes -
Conditional Highlighting Transformation
Highlight attributes or rows in a structure board (bold, italic, font, color, background color) based on conditions. Visual queues which bring the eye to topics on a board which need special attention. Perhaps an extension of the Transformations capability (Filter Sort, Group, Extend and now Highlight) Highlight transformation accepts several of the same options as Filter transformation (JQL Query, S-JQL Query, Sprint, Text Query) and now an additional options. Highlight scope (attribute, row, row and children rows) and Highlight Type (Font, Bold, Italic, Color, background color)
1 vote -
Integrate with zephyr for Jira
Integrate with zephyr for Jira to be able to get the test execution and the linked defect related information into structures. Currently structures is able to show the Zephyr test case , but not the test execution status and the linked defects
3 votes -
Show keyboard shortcuts more prominently
The keyboard shortcuts looks great, however discoverability could be better. Even technically minded individuals in the majority do not go searching for keyboard shortcuts.
Adoption of Structure may be more natural and frictionless if users were shown a permanent reference to keyboard shortcuts.
3 votes -
Ability to save and "Perspectives" or combined set of Structure, View, Enabled Quickfilters that you can save and share
Users get overwhelmed with the number of options that they have to change the way they visualize the data in the structure.
Currently we can share a perspective which is similar functionality to what is being requested. However we cannot keep a library of perspectives in the system the same way we have the Views. This would help provide users with a library of options based on what they intend to do (i.e. risk management, project prioritization, reporting, etc.)
3 votes -
Set different views for folders
Different folders in Structure may have different needs for columns/views, so it would be great to be able to define a view to use for each folder.
3 votes -
Add fixversion as non-issue hierarchy element
For Release Planning, I group by fixVersion in my hierarchy. But Gantt shows the start-end dates as of rolling up the dates below the grouped items. And there are no "sync" with jira version's dates.
I propose the ability to include a non-issue elementes, synced with Jira's fixVersions, for synced scheduling at version/release level. Or something similar.
Thanks!
1 vote -
Named perspectives
This one is so obvious - I'm surprised I didn't find it already.
Provide a feature to save a Named Perspective that is permanent (until deleted) and can be modified.This would 1000% improve the usefulness of perspective views for us. As it works now, there are two major issues with perspective links:
1) When not used for awhile, the perspective gets deleted and users are confused when they load the link
2) There is no way to update the perspective. For example, if we want to add, remove, or change the fields shown, there is no way to update…1 votePlease check the comment!
-
have more videos linked to the "Get Started" page to explain more examples of how this is used.
more training videos
1 voteThanks! check the comments, please
-
Allow html (Jeditor) renderer for column type field
If we add new column form issue field which use Jeditor renderer(html), than in Structure table we see html tags and not the same view like at issue view page
3 votesthanks!
-
Risk Management in Structure
For our company would be useful a risk management addition, a same feature as Big Picture has with the Risk matrix.
4 votesThank you for the suggestion! check the comment, please.
-
Granular control over Automation grouping, particularly with Labels
Currently, grouping within Automation is kind of an "all or nothing" approach. For example, we use labels to identify which "product" our epics are for, but we also use the Labels field to track other information. For our main Structure, what we want to do is have the Automation grouping only look at the 6 labels we currently use for "product" tracking and ignore all of the others, but I cannot seem to find a way to do this without manually creating my own folders and setting up the Automation for each one; the drawback to this is we can't…
5 votesThank you!
Check the comment, please.Julia.
-
1 vote
Thank you for the request, please check the comment!
-
Expand Editing from Gadget
Please add the ability to edit more fields especially custom fields from the Gadget (https://wiki.almworks.com/display/structure/Editing+from+Gadget). The ability to edit custom numeric fields via jira dashboards/confluence pages would be awesome!
5 votesThanks! check the comment, please.
-
Don't Dismiss Automation Dialog When Pressing Escape Key
If you are adding a filter or some other automation that requires writing a query, the autocomplete often obscures the text of the query you are trying to write because the window is very small. If you press Escape to dismiss autocomplete to see what you are writing, the window closes, and you lose your work.
In other entries, like the issue search screen, pressing the Escape key dismisses autocomplete, so it is more likely you will lose your work because you have the muscle memory of pressing escape to dismiss autocomplete.
2 votesThank you! Please check the comment
-
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!
-
Line Break when composing text with CONCAT function
When using the CONCAT function, I would like to use the special character "line break" in the text I'm composing.
How can it be done?1 voteThanks, check the comment please
-
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
-
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!
-
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!
- Don't see your idea?