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.
-
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.
3 votes -
Ability to hide the time line in the gantt chart view
It is a widely adopted practice to not share specific dates in long term planning and it would therefore be helpful if I could hide the dates/timeline in the gantt view.
The only option today is to zoom out but that is not practical as the feature-bars will become to small and the timeline is still visible but in years.
I want to be able to show how feature A is scheduled before Feature B and that it is dependent upon Feature C being completed without having to show when the features will be worked upon.
Simply hiding, or making…
3 votesHi Andreas!
Thank you for the feedback! We’ll definitely evaluate your idea.
-
allow a status synchronizer to allow rollups based the first subitem entering the next stage
The status synchronizer allows as of today(2.0.0) only a rollup of the status to the parent when all children have reached this status (i.e. all children are "done" > parent is set to "done").
Imagine a workflow like: open > in progress > done.
For the status "in progress" it would be great to have a "roll-up once the first subitem enters a new state". So the parent reflects the new status once the first sub-item has been moved from "open" into "in progress".
3 voteswaiting for reply
-
Ability to hide the time line in the gantt chart view
It is a widely adopted practice to not share specific dates in long term planning and it would therefore be helpful if I could hide the dates/timeline in the gantt view.
The only option today is to zoom out but that is not practical as the feature-bars will become to small and the timeline is still visible but in years.
I want to be able to show how feature A is scheduled before Feature B and that it is dependent upon Feature C being completed without having to show when the features will be worked upon.
Simply hiding, or making…
3 votes -
support grouping of issues by link type
e.g. all 'Blocked By' issues added via Extend automator grouped together under parent.
This makes the Jira relationship between Structure parent/child issues clearer.
3 votessee comments for details
-
Use lightboxes when managing structure properties
Currently when editing a structure (Operations->Configure), you are throw into a new page for editing. When you are finished and go back, the structure list reloads and moves you to the top and I cannot find my place anymore. This is a problem when you are viewing a list of over a thousand structures.
A popup lightbox would make things much better and allow me to keep my place in the list of structures. This could apply to sync settings, and all other management operations.
3 votes -
Possibility to disable/filter the Structure notifications in the project & user Activity Streams
Currently only the Actitvity Stream "gadget" has the option to configure filters.
The standard (non-gadget) Jira Activity Stream on the Project Summary page & on the User profile page does not have this option. Hence these Activity Streams are heavily 'polluted" with Syncronizer updates and are becoming useless..3 votes -
Calculate context-aware Progress
When displaying structures in a specific context (for example, after selecting a specific Version from the Project view), the Progress roll-up should be done in the context of that version.
For example, assume I have an Epic containing multiple stories which will be completed across several releases. If I view the structure in the context of the upcoming release, it would be nice if the Progress calculation were based solely on those stories targeted for the upcoming release.
2 votes -
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.
-
Show progress of selected issue/task in Confluence
In our company we use very closely JIRA and Confluence. Structure allows us to properly organize issues based on our demands and workflows and it works perfectly for people who are assigning tasks or implementing them. But we use Confluence for executive summary of progress on specific builds where would be very helpful if we can display progress bar of a specific issue (counted from all issues below of selected issue in the hierarchy). This way we would be able to create great overviews like e.g. "Bug fixing of Feature1", "Implementing Feature2", ... with progress bars behind without a need…
2 votes -
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.
-
Use tokens in the summary to capture recurring fields and indendation levels
By specifying some fields e.g, priority and assignee as well as the indendation level of the issue while entering the summary text of the issue will speed up the data capturing with structure. Please consider having a look at www.checkvist.com for effective keyboard support for increased speed and useability.
Eg use the @ to specify the person eg @john
use the # sign to specify the priority
Eg #0 - blocker
#1 critical
Tab indentation in the summary for instance indentation level 1 specified by 1> indendation level of 2 specified by >2>1
2 votes -
add custom fields to structure-folders
Budgets are often not added as issues. Structure could add value by allowing some limited amount of named custom fields on structure-folders (like notes, but some more). They would bind to a structure and could be accessed from formula columns.
2 votesThanks! Check the comment, please
-
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 -
I suggest the structure gadget displays the full name of the structure in the dashboards
Currently it truncates the names so it is difficult to tell which structure is displayed.
2 votes -
...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.
-
Show some type of visual indicator when the progress rollup contains interpolated data
I love the ability of the structure plug-in to roll-up numerical fields of children into their parents (thank you!). As I understand it, if some of the children do not have values, the roll-up algorithm estimates values for those children based on the values set in their peers (i.e the value of the unset children is the average value from all of their peers). Essentially, the structure plug-in is making estimates for the children even if users haven't entered any information.
When that happens, it would be nice if the plug-in offers some kind of indicator on the rolled up…
2 votes -
Require the user to confirm a deletion of an issue before it is removed from the structure.
Require the user to confirm a deletion of an issue before it is removed from the structure. Right now there is a message that an issue has been deleted, but my users aren't noticing the message. Need to make them verify the deletion before it will occur.
2 votes -
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.
-
Localization
Do you have prepared structure for translating structure. SWe need a German version.
2 votesawaiting reply
- Don't see your idea?