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
-
Localization
Do you have prepared structure for translating structure. SWe need a German version.
2 votesawaiting reply
-
Navigate to next/previous issue in structure
We want to have the feature to go to the next issue in the stucture.
The scenario is:
1. You have a structure open
2. You open up the first issue in a full screen mode
3. You go to the next issue in the structure. Without jumping back to the structure.In the same way as you can jump to the next/previous issue after you have performed a filter/search in plain JIRA.
2 votes -
Create a method to prevent parental and causal links to sub-tasks unless those sub-tasks have sub-issues
if you have issues with sub-task type issues there's no way to pull those sub-tasks and any child or resulted in linked issues into a structure without structure creating child and resulted in links for all sub-task tasks of those parent issues. It appears that any configuration of the links synchronizers will results in the sub-tasks getting child and resulted in links to the parent issue. If this is true, I propose the following feature request.
In the Links Synchronizer, create a sub filtering feature that uses the logic of: "don't create parental or causal links for sub-task type issues…2 voteswaiting for clarification
-
import from excel
First set of columns each represent a structure level.
Following structure, top row includes field names for data entry (e.g. Story Points, Type=Epic, Story...(not sure if this will come through or not, but something like this:
|Level1 |Level2|Level3 |Level4 ... |Type |Story Points|
|Jurassic Park| | | ... |Epic |
|Jurassic Park|T-Rex| | ... |New Feature|
|Jurassic Park|T-Rex|Goat Release| ... |Story |
|Jurassic Park|T-Rex|Goat Release| As a goat I can be raised up so the T-Rex can eat me|Story| 8 |
|Jurassic Park|T-Rex|Goat Release| As a goat I can NOT escape so that I will live|Story| 2 |Note…
2 votesNeeds more details – please see comments.
-
Connnect more than one JIRA instance
When working with external partners they often use their own JIRA instance. You can connect them via the JIRA application link feature with your own JIRA instance and are able to set links between issues in the two JIRA instances this way.
It would be great to be able to display linked issues from the remote JIRA in your own structures.
2 votesCollecting requirements – please see comments.
-
...have separators, or sticky issues, that stay on top.
My idea is that I want specific issues to not be affected by the sorting. Not affected, so that they can stay on top (or bottom).
Another cool way to do this may be a separator or separators, that can be added similar to the way folders are added. Except these separators allow their content to stay where the user assigns it to.
2 votesConsidering the feature — please see the comments.
-
Hide empty folders
In structure folders created based on custom fields will show "no value"-folder in case issues haven't set the related custom field. It would be nice to get an option to define whether to show such "no value" folders or to show such issues without a folder under their parent.
2 votesPlease see the comments for a workaround.
-
Allow entering list values on separate table rows
It would be nice to have options of single and multi-select list fields optionally displayed in different rows.
2 votesHi Dimitrios,
Thank you for the request. Could you please clarify a little what do you mean by select fields displayed in rows?
Is it about Jira fields? Do you want them to be in rows, but not columns? How would you like to use it and why?
Thank you,
Konstantin
-
1 vote
-
Deleting of items should also be possible with a short cut key combination - not only removing the items from the structure
Preferably without requiring an acknowledgement. The aim would be to mimic the speed of mind mapping tools for capturing information in meetings. One of the issues is if one wants to delete a item it should be as fast as creating one
1 vote -
let users do Move up / Move down voting
We've been working with a structure for product planning. We rank candidate improvements top to bottom. I'd like to have a casual "vote up / vote down" button for each row. To use I'd reset the votes and then ask viewers to vote away. We'd all sit and watch the voting tally increment as the structure updated. After a few minutes we'd stop and then prioritize and reset the votes.
I'd like to be able to see who voted and when they vote prompt them for why.
1 votewaiting for requirements clarification
-
Search Result Panel: option to display other structures with their hierarhies
It would be great if Structure has an option to display other structures in search result panel, not just list of available issues in JIRA by search criteria.
For example, user may select from the list of available structures to display in search result and add issue with all its hierarchy tree to his structure.
Permissions apply, of course.A few point that I thought of:
1) User must have "view" permissions to view and select the structure from the list and add issues to his structure.
2) Permissions should apply on the issue / project level. User should not…1 vote -
Export to Excel is good. With a view to importing to Project need additional fields such as due date.option to configure fields to export?
An ability to specify the fields to be exported such as due date etc etc.
1 vote -
Not show tasks and subtasks when using the GreenHopper's Rank and Epic/Theme fields Syncronize w/ auto-add subtask deselected
when selecting the Greenhopper syncronize w/ the epic/theme field selected and the auto-add subtask option deselected, structure is still bringing in tasks and it's subtasks. We were expecting only to see Themes, Epics and Stories in our structure. In addition, when we have Rank syncronize selected as well, it doesn't always line up with Greenhopper.
1 votesupport request in progress
-
Add editing roles for users
Lock specified users for editing just specified (or their) issues.
Give ability for specified user create issue subtasks, change estimates, etc. but lock title editing, assignee1 votecollecting requirements
-
add user stories w/out subtasks automatically to the product backlog by using the greenhopper epic synchronization
There is a separate setting to auto include the sub-task, by I am sure I didn't tick the box (I tried it 3 times).
It looks like the synchronization is always adding the sub-task regardless if you want them or not. This has worked before but recently I get the sub-task in the product backlog as well. We recently upgraded from 5.7.2 to 5.8.6 so maybe something in 5.8 broke this.1 vote -
Combine structures
Structures Seouls be able to be added up
1 vote -
Combine multiple filters for synchronization
Say I have two members in a structure, Epic1 and Epic2. I created two filters, Epic1 Resolved Bugs, and Epic2 Resolved Bugs, and created synchonized filters accordingly. Now I see all the Epic1 resolved bugs under Epic1, and Epic2 resolvedbugs under Epic2, as expected. Now I just want to see resolved bugs fixed at a certain version. I'll have to edit each filter to accomplish this. It'd be nice if I can AND a "Fixed by VersionX" filter to ALL the filters, and then just change this filter everytime.
1 votewaiting for response
-
Have a right click contextual menu instead of the gear and hover that sticks to the far right forcing me to scroll every single time I edit
Right now everytime you edit a structure item (eg change status or Link to another issue) when the screen redraws the focus is forced to the bottom right. This then requires the user to have to scroll first before they can take any further action on a structure item. I find I have to do 10 - 15 unnecessary mouse transaction to edit a test case, block it and then link it to the blocking item
1 votewaiting for reply
-
In a multi project
In a multi project scenario can we have a scattered epic(collection of stories implemented by different projs) to be tracked as part single structure this will allow big programs to be tracked for their distributed progress in individual queues and collective status at one place for decision making.
1 votewaiting for reply
- Don't see your idea?