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
-
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!
-
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?
-
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
-
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.
-
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.
-
show more bars for one issue in a row (use more than 2 datepicker fields)
In our issues we use more datepicker fields, e.g. Start Phase 1, End Phase 1, Starte Phase 2, End Phase 2 and so on.
I want to show that bars within structure gantt, so not only one bar for one issue but several bars next to each other for one issue to show that time periods.
5 votes -
Integration with insight
The step forward for structure development - adding a posibility to work with insight objects inside formulas or in more UX attractive way. Such integration will provide unlimited power for structure to produce any type of dashboard / timeline / resource plan etc.
5 votes -
Propagate Due Date
Allow users to set due date based on due date of parent and estimated time. Plus when due date of parent is changed propagate change to all child issues accordingly
4 voteswaiting for clarification
-
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
-
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
-
Automatically create issues to represent structures
Allow structures to have attachments, comments, workflow, etc by creating an issue for each existing structure. This could be automated by the Structure plugin.
Let the administrator configure a special project / issue type for those issues.
4 votes -
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
-
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 -
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
-
Keep carriage returns during Excel export or be able to save off the Printable Page.
We added 2 custom fields for testing steps. The carriage returns show up in Printable Page nicely. But we can just print that. The Excel export doesn't keep them and so the steps are jumbled in each cell instead of a clean representation.
4 votes -
Add a custom field on child issues to show the structures root element
I would like to see the root element in the structure in the custom fields of the children so I can use this when exporting data from jira
4 votes -
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 -
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 -
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 -
[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.
- Don't see your idea?