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
-
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.
-
5 votes
-
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.
-
Automatically clear multi-selection after a move/paste operation is completed.
The structure plug-in allows users to select multiple, dis-contiguous issues using the multi-select mode, whereby the user clicks on the little radio button next to every issue they want to select. The selection can then be operated on as a whole, for example, to reposition the issues in the structure.
This feature works great, however, I find it annoying because the selection 'sticks', even after I've completed the operation I wanted to perform. Then, when I move onto select other issues, the previous ones, which are still selected, unintentionally come along for the ride.
Let me provide a use-case. Assume…
4 votes -
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.
-
Would like a way to get Structure formula calculations into "normal" Jira custom fields
Structure formulas are extremely useful. Now our users would like ways of using them in other places within Jira. This may be tough in some ways because they are specific to the structure they are part of, but even something simple like the ability to choose an menu option or call some API to commit formulas into an underlying custom field could be quite useful.
4 votescollecting requirements, see comments
-
Add ability to synchronize at the Project category level
A structure is set up across multiple JIRA projects and when I add a new project, I have to redo the synchronizer. If I could select a Project Category instead of individual projects, then I would only need to add the new project to the project category.
4 votes -
[Structure+Testy] Make it possible to have a type of parent child relation inside an issue
Use Case 1:
As a tester I would like to use a unique test case and run it several times and after every run I would like to add my test data/environment to it. (E.g. Result and what format, browser, platform, DB that was used during test run...)Use Case 2:
As a Test Manager I would like to be able to create a dashboard report or filter based on specific data and the outcome of the result with that test data/environment.Current solution with testy today (https://marketplace.atlassian.com/plugins/com.almworks.testy)
has some good features but you still lack the method…4 votesCollecting requirements – please see the comment.
-
Have a Back to Structure button in Issues
When you open the Issue to view/edit the full details, a link back to the full structure would be nice
4 votes -
Show more results to allow me to use the browsers scroll function.
The view port of the structure plugin is rather small. I can only see a max of 12 rows on my screen (1360x768). I need to export to excell to see more stories in my epic. It would be nice if more results are displayed on the screen. And to be able to use the browser's scroll bar to scroll, that's why it's there. Or did I miss a config option?
4 votesinvestigating – please see comment
-
Use the standard Atlassian User Interface objects
I would suggest you to resort exclusively to the AUI objects for your interface instead of your custom ones that clearly gives the impression that you are exiting the Jira world to step into another one.
I think you user would deserve a smoother user experience, with the same kind of buttons, icons, tables to which they are already used to. I'm especially talking about the transformation/filters features that should be improved in that direction to my mind. Thanks for you great achievement!4 votesplease see the comment
-
Structure of Structures - no data just an index with link to the relevant structure
I would like to create a Structure of Structures for structure navigation, whereby specific child elements allow you open the referenced structure. I have many structures that contain the same data, just displayed differently for different user groups.
The use case is in essence:
Parent - Folder (a name listing a group of similar or related structures)
Child - New Structure Link - simply a mechanism to either open or navigate to the referenced structure - includes description.Implementation:
Is it possible to add a new Structure element into the "Add" Dropdown called "New Structure Link". (i.e. New Issue, New…4 votesThank you!
Check the comment, please -
Support entering data into mandatory fields on SubIssue creation
when you are creating a sub issue you might hit a wall when the creation of the issue have some mandatory fields which needs to be filled out.first.
it should be possible to enter data during sub issue creation.
it is already shown which fields that need to field out.4 votescollecting requirements
-
support project roles in JIRA
Structure currently only supports permission groups but not project roles. If a project is set to support project roles then there could be surprises if some users are part of the right role but do not belong to the groups that Structure has been permitted to.
4 votes -
Enable group by Elements Connect (formerly nFeed) fields
Enable nfeed field for the Group by function
plugin link: https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed
4 votesThank you for the request! Added to backlog
-
When due date is set, automatically calculate remaining estimate and turn on time tracking
If an issue has a Due Date, calculate automatically days to complete and set that value as a Remaining Estimate, and turn on Time Tracking automatically.
При установке срока задачи сделать возможность автоматического учета рабочего времени
Если в задаче установлен срок то автоматически высчитывать сколько времени в днях она займет и выставлять в поле планируемое время это значение и автоматически включать учет времени.
4 voteswaiting for reply
-
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?
-
Log changes
Sometimes someone deletes stuff from the structure and we do not know how the structure looked before (no version management exists).
In this case, as a workaround we would like to have a log to see what has changd.
4 votesThank you, please check the comment
-
Link issues in a hierarchy as you move issues around in the Structure view
Currently, when you clone a subtask and move it to another parent issue, it actually remains (for all intents and purposes of JIRA data) as part of the original parents issue.
This is a problem, because in Greenhopper on the planning board (where you move User Stories to actual date defined releases), they have to reflect the same structure as you created in Structure.
4 votesWaiting for response
-
When displaying subtasks in Structure, include parent jira # as part of summary (like Jira filters)
When displaying subtask in Structure, include parent jira # as part of summary (like Jira filters).
4 voteswaiting for clarification
- Don't see your idea?