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.
374 results found
-
All for better organization of Quick Transformations
Love the Quick Transformations, but usually have quite a few that are all listed on the toolbar such that it takes up space and can be difficult to find the one that I need at the time. Would love to be able to group them such that selecting the group provides a drop down style dialog in which I can select the desired filter.
Thanks for the great plugin!
1 voteThanks! please check the comment
-
Add "Configure Structure" to Tools in the Structures pull-down in Structure Cloud
I'd paste a screenshot here if I could. At the bottom of the pull-down under the Structure name, it says "Tools: Create Structure, Manage Structures. Manage Structures just takes you to a screen where you have the choice of configuring the structure, or opening the structure you just left (this is useless), or delete the structure. Why not put "Configure Structure" on the pull-down with Tools, Create, Structure, Manage Structures, and make the Manage Structures button take you to Manage All Structures? You should also put a filter box on the Manage Structures page so you could zero in on…
1 voteThank you for the request, we have plans to improve this functionality in the future.
-
Add ability to edit name and rank of Version/Release
Add ability to edit name and rank of a Version/Release from within structure. Right now that's not possible and it's very inconvenient to navigate to the project in scope to make this edit.
1 voteThank you for the idea!
-
Integrate Structure with the Easybi reporting tool
Integrate with EasyBI such that reports can draw on Structure information. This should include the organizational aids (eg Folder names and positioning of issues) but also the calculated values.
1 vote -
Filtering a selected item should not cause its children to also be filtered
Filtering a selected item should not cause its children to also be filtered. I tried filtering a selected item that had children and was expecting everything but the item and its children to be removed. However, applying the filter removed all child items, which essentially renders the filtering feature not very useful.
1 vote -
Make Structure Gadget on Jira Dashboards visible to not-logged-in viewers
Jira allows dashboards to be shared such that 'anyone on the web' can view the dashboard.
However, Structure gadgets on such a dashboard do not load for not-logged-in users.
Could the Structure Gadget be made visible, but limited, in that not-logged-in viewers cannot drill through into the issues, or Structure itself, without first logging in.1 vote -
Quick Filters should not show empty groups when items have been filtered
If I select the quick filter 'Assigned To Me' the results still show the group hierarchy for items that have been filtered out.
I discovered that if items are grouped by Release (i.e. Fix Version) anywhere then the empty Release group will still appear even though I don't have assigned items.
This is also means that if the Release group is sitting several levels deep then all parent groupings will still appear.
Update: I also discovered that this happens with Epics too.
1 voteHello Alex,
Thank you for the idea! Having this option unchecked by default for new Quick Filters would be a good improvement.
-
Have different permissions for the editing of values in columns and rearranging structure through drag and drop
Instead of having one Edit permission, divide it into 2 different ones. By doing this, users that can edit values in columns cannot rearrange issues in the structure by mistake with the drag and drop feature.
- Permissions to edit values in columns
- Permissions to rearrange items in structure under group by automation (Change Epic,Rank,etc)
1 vote -
Reverse the order of the Epic column string
I'm very pleased to see the addition of the Epic column. However, it presently is displayed with [Key]-[Epic Name].
It would be more useful to see it displayed as [Epic Name]-[Key], or at least the option to select between the two.
1 vote -
Add ability to not count child items
When the count of a group of items is summed I would like the child tasks (i.e. subtasks) to be excluded from the count.
1 voteThank you for the request! A column that could count only items on the next level (instead of all sub-items) would be a nice improvement.
-
Posibillity to shift more issues at once in the timeline
Our organization would like to have a feature which would let us to move few issues at once. F.e.:
Epic has issues inside. So if I move the Epic bar, all those issues inside epic would move the same. Like in Jira's Advanced Roadmaps1 voteThank you for your suggestion. This feature is frequently requested, and we hope to start working on it soon. If there’s something we can help you with, fell free to ask.
-
Maintain version history of the custom views
I use structure board on a daily basis and find it useful. I have multiple custom columns based on formulas. It would be great to have version history of the custom columns. If a formula column gets changed inadvertently and I want to revert back to the older version of the formula, right now, there is no option to do that.
1 vote -
support integration with qTest tool
Add support for qTest tool.
1 votethank you for your request!
-
Option to suspend Polling
When using Structure for Triage. I often make updates to Jira's as we do. I frequently have to wait for the polling to update the structure before I can continue with my meeting.
A potential solution, would be to have the option to disable polling (temporarily) as I make many edits, then do a refresh at a time of my choosing.
1 vote -
Be able to print issues attributes summed over time
As a user I would like to monitor the evolution over time of a numerical issue attribute value summed across issues and displayed it like ressource usage are displayed.
Example : attribute cost of a story to monitor cashflow over time.
1 vote -
Improve Sandbox feature capabilities
Latest version of sandbox with 3.0.1 is limited in its re-planning capabilities. Some changes require removing tasks and adding new tasks for change requests from Marketing. Need to add support for:
Changing links between tasks
Ability to add new tasks as a change requests and change linkage between resources
Ability to remove tasks as a trade off for a change request
Move tasks between groupings and relink with other tasks because of unexpected issuesIn all cases, most changes are to view how a change request or trade will effect a schedule before marketing and team commits to the changes.…
1 vote -
Allow multiple resource to work on one item
As a user I would like to have more than one resource to work on a task, especially when doing macro planning and integration task that require multiple team to work together in one item.
1 vote -
Reduce the margin/padding of every row to increase the level of entries visible in the screen
Gantt charts are a good tools to see the globality of the project at once.
Having a layout mode like: compact/confortable would be very interesting to maximized the visible content while looking at the dependencies in the gantt chart.1 vote -
Allow dependency linking to tasks not in the Gantt view
When trying to create a new dependency link for an item by clicking on the little dot beside the item in Gantt view it would be beneficial to be able to link to items which are not visible in the Gantt view. This is especially useful when using transforms which may filter items from the view but you still want to link to the hidden items.
1 vote -
Distinguish between multiple extensions by color or symbol
When using multiple extensions (for instance the link types "is blocked by" and "blocks") it would help a lot to have a way of showing why an issue in question is extended. Allowing each extender to have a background color on the items it adds, or a symbol next to the summary would be great.
Example:
An automated structure that inserts "type=epic and project=projectA"
Extension 1: Extend with Linked Issues, type: Blocker, "is blocked by"
Extension 2: Extend with Linked Issues, type: Blocker, "blocks"The extensions might be permanent or quick transformations. For each of them it would be nice…
1 vote
- Don't see your idea?