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.
173 results found
-
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!
-
Color settings for baseline bars
Now baseline bar can be only gray. If you print Gantt chart on paper it is not easy to see baseline bars.
Can you add color settings (maybe like for slices) for choosing color for baseline bars?3 votesHi Alexander! Thank you for the request, so am I getting you right that your idea is to be able to select the baseline color while exporting Gantt chart? Would making it more contrast by default help you?
-
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.
-
Feedback on Learning About Structures
I'm a product manager and have a technical background, but pretty much had to figure out how structures work using trial and error. I gave up the first few times I tried to build one because I just didn't get what was going on.
It wasn't until I had a need to look at data across teams in a specific way, that without a structure, would have resulted in a ton of duplicated effort in Excel, that I forced myself to figure out how they work. At that point, I also discovered the formula columns and found that documentation to…
7 votesThank for the request!
-
Autocomplete Frequently Obscures the Text I'm Trying to Edit
When doing things like adding a filter to an automation, the autocomplete frequently appears on top of the text I'm trying to edit, which prevents you from seeing what you are typing.
1 voteThanks! please check the comment
-
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.
-
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 -
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
-
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?3 votesThanks, 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
-
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!
-
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
-
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
-
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?
-
"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
- Don't see your idea?