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 you to wrap text in a column in the structure view.
I would like to be able to see 6 columns and have the option to see ALL the text wrapped not just the starting text. I'd like to retain the option to just see the starting text too though. I have used the full screen real estate but I can still only see the start of the wording.
Current work around is to only have 1 or 2 columns showing at once and add in the others as necessary later.
e.g. View currently shows:
Summary Description Labels Components Assignee
Client Doc Data in clie Docum Disclosure Sarah Sm
I'd like…
108 votesat least partial solution shipped with Structure 4.2, see comments
-
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 -
Show sum of time columns
I would like the bottom line of the structure widget to also show the sum of remaining estimates for all (shown) issues in the structure.
For example, I have a structure with issues for our next release. I would like to enter a filter like "fixVersion=<currentSprint>" to see issues assigned to the current sprint, how they are spread across overall plan, and also see the remaining estimates for the sprint.
The bottom already say something like "Showing 25 issues (100 issues are not shown)", so there's quite enough space to say "Showing 25 issues (10 weeks remaining) | 100 issues…
25 votes -
Integration on Jira Agile
It's very useful the integration with Jira Agile (on Jira 6 and next releases), so I can see near the tab Epic and Version (in the backlog view) also the other structure that I can build.
Actually, I have to manage two different views: Structure view and Backlog view. It's better to integrate this two views.1 voteplease see comments
-
Auto-Convert Perspective-Link into Structure-Gadget on Confluence-Pages
In this way one is able to create whatever view of the Structure in the structure itself and share this on Confluence pages without dealing with the UI of the gadget (which needs some improvements).
1 vote -
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
-
custom row heights and the ability to export to ms word/view in web layout mode
custom row heights and the ability to export to ms word/view in web layout mode
0 votesCollecting requirements – please see comment
-
Allow an attachments column with attachments preview, similar to the Images column
The structure view should allow the user to display "attachments" as a column, where attachments are listed similarly to the "Images" column. Clicking on an attachment thumbnail would popup a preview of the attachment.
At the very least it should allow the user to download the file without opening the ticket itself.
12 votes -
Allow Better Transitions
By example, we use stories and have them implement features. Our final state for stories is "Closed" and when all stories are closed we want to have the feature change it's state to "Ready for Production" however there doesn't seem to be a way to do that.
To that end, it would be nice if we could say that for state X we could specify what transitions could go there given that its sub-items state may be different.
Example:
Feature Workflow has "In Progress" --- {Ready To Deploy} --->>> "Ready for Production"
Story Workflow has "Verify" --- {Ready To Deploy}…1 vote -
Custom structure template based on 1 or more JIRA fields
The plugin allows users to create arbitrary structure and also structure based on JIRA links. It would be nice if there is a way to create structure based on JIRA fields like Reporter, Assignee, version, status. So user can drill down the issues by reporter, By Assignee, By version or any such combination and order.
1 votePlanned in Structure 3
-
have the ability to control the visible amount of a custom field
I currently use a custom field for scope statements and wkly highlight reports. As far as I know, Structure only allows me to see a small excerpt of this field. I would like to be able to control the amount I can see (maybe in number of characters / lines). That way I can view issues listed in a Structure and see at least 2 or 3 paragraphs of the report/statement at once.
1 votecollecting requirements
-
Let user to zoom in and focus on just one hierarchy level
One of the features that makes Workflowy so great, is the possibility to zoom-in to one hierarchy level only. I think this could work for Structure as well.
1 votecollecting requriements – please see comments
-
Localization
Do you have prepared structure for translating structure. SWe need a German version.
8 votesawaiting reply
-
allow us to synchronize links between sibling and cousin issues
Right now the link synchronizer works only between parent and sub-issues. However, this is often not enough. For example, we would like to automatically link "development" and "system testing", which are usually sibling issues under a single "Change Reqest ### for system XYZ" issue.
A use case for "cousin" links is similar: "integration testing" should depend on all "system testing" issues within the same "Change Request ###" parent/grandparent issue.
Right now we work around this by using template structures, but this is fiddly and error prone, since issues like "integration testing" should be edited manually after N "change request for…
3 votesPlease see the comment
-
Testy: ability to creatae multiple test sessions/cycles without cloning tests and/or test results
USE CASE:
1. Visualize Progress Bar functionality test coverage on diff browsers (following example @ https://marketplace.atlassian.com/plugins/com.almworks.testy)
2. Re-use the same test plan structure for multiple buildsOPTIONS FOR BUILD 2:
Option 1;
Use columns for each browser (next build requires cloning to track test execution)
Problem 1: Requires cloning of entire structure for next build
Problem 2: Cloning just test results will not work as new results will overwrite test results from build 1Option 2:
Use columns for each test run (no need to clone the tree and browser makes put in the hierarchy)
Problem 1: after a…1 votecollecting requirements
-
Allow users of the Tempo Plugin to see a per-user summation of time usage
We always have multiple coders on our projects, and almost always have multiple coders contributing to each piece of functionality within a project. We use the Tempo Plugin for JIRA to keep all that straight.
Structure's time summations are really helpful and beneficial. But for our multi-coder environment, we have to look at that summation in Structure, then look at every subtask and split out exactly who contributed how much to the Structure main task, because different coders are at different billing rates. This is not workable except on very small projects.
What would be ideal is if we could…
7 votesshould be possible with Structure 3.0
-
Indent Structure based on JIRA Issue Type as is done with Summary field based on Issue Type
epic TP icon
story TP icon
story task TP icon1 voteNeeds clarification – please see comments.
-
Add view setting to specify level of expansion
When creating or editing views, allow specifying the degree of expansion. My use case is that I want to show all issues in the top three levels by default. Furthermore, I want the expansion setting to apply to the Confluence gadget.
Alternatively, a perspective can be used to achieve the same result, but there is currently no way to use a perspective for the Confluence gagget. If the perspective could be used in the gadget, then I would recommend combining with http://structure.uservoice.com/forums/43181-structure-plugin-for-jira-ideas/suggestions/1773075-add-controls-to-expand-contract-one-level-at-a-t to allow an unlimited customization of gadget presentations.
3 votesLikely planned for 3.0
-
Keep backlog always up-to-date with notifications
I think it would be nice to have possibility to notify Scrum Master and Product Owner that some of UserStories are holding in a backlog for quite a long period of time (could be specified in extra settings), for example 3 moths.
It should help to keep backlog always with actual UserStories.3 votescollecting requirements
-
Reorganize the ManageStructure page
- allow us to specify a short name for each synchronizer
- move the items which appear once per structure, i.e., Name, Owner, Access, Popularity, Operations, out of the table to a header, so that the information in the Sync With column could be expanded: this would allow more room so that the Sychronizer Short Name could be displayed, and the type of synchronizer would not line-wrap. Thanks !
1 vote
- Don't see your idea?