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.
382 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…
107 votesat least partial solution shipped with Structure 4.2, see comments
-
Limit parent-child relationship to specific types of issues
Let JIRA admin specify what issue types could contain what other issue types. For example, a Test Suite may contain Test Cases, which can contain other Test Cases, but not Feature Requests.
86 votes -
Propagate field values down the hierarchy
Let the user specify, for example, that all sub-issues of the issue X should have the same Security Level and Project and Priority.
65 votes -
Artifical task as from BigGant
Hi, I thing something as Artifical Tasks from BigGang should be handy. We can´t planning far for future. In many times we need plan work which we did´t have fragmented to tasks. There is only highlevel overview that Member1 will have work on Project1 on week35 - week37 than on Project2 on week38-39 and etc. We need tasks which is not under project and created as Jira task, but only as shadow task significant than Person will be on Project. Folders can only group tasks but doesn´t have start date and end date.
33 votesHi!
Indeed that would be a good addition! We’ll definitely do something like this!
Thanks for your feedback!
-
Allow scheduling effectors
Having effectors that can take a formula and set the value to a field is great. What we are missing is the ability to schedule the effectors, so that they run every hour/day/week, which will enable us to have these "calculated" fields up-to-date without manual intervention
27 votesThanks! please check the comment.
-
offer a way to save your column widths with a view and with the perspective view.
Our users will customize their view, setting the column widths in a way that allows them to best see the data in the view. While Structure does a great job of preserving this, in their session, there is no way to save the column widths, either in a saved view or in the "perspective view", from the Share button. Our users would like to share these adjusted column widths with other members of their team.
27 votesThank you! please check the comment
-
Support a User Story Map View
User Story Mapping is becoming a very popular way to organize your product backlog: http://www.slideshare.net/nashjain/user-story-mapping
It basically uses a 3 level structure but displays tickets in a vertical layout, as illustrated here:
There are only a few tools that support this online, and only one that is part of JIRA. The market is ripe for a tool that is robust, simple, and flexible. Since Structure already organizes tickets hiearchically, all that would be required would be to create a new view of a Structure, with a possible limit of 3-4 levels. (The Story Map structure only supports 3, but I…
25 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 -
Link a structure to a JIRA board, not just a project
The description of of Structure on the Project page (https://wiki.almworks.com/display/structure/Structure+on+the+Project+Page) is really misleading because this image is of viewing a JIRA board, not a project. With JIRA boards I can use JQL to divide a projects (or multiple projects) issues across many boards, but I do not have a way to link that board to a specific structure that also filters for the same set of issues.
Having a default structure for a project is fine, but I would also like to be able to correlate a structure to a board. This would help teams that for example…
22 votes -
Moving items in the structure will update ANY task link / parent
Our organization would like to have a possibility to move any task in structure and update issue links accordingly.
F.e. Move the subtask from one issue to another in structure - this should change the parent link for the subtask.Move task without epic link inside the Epic - update Epic link.
Move Epic task to another random task - a popup should appear with question "choose link type".
22 votes -
Enable you to specify a parent issue when doing "+ Add to Structure"
Currently in the Issue Page you can only add the issue at the end of the structure.
Parent issue input could be equal to the way we Link issues in JIRA.
19 votes -
Allow user to make a new copy of multiple items from one structure in another structure with new keys.
We have several structures in place now, each with several epics (epic = enhancement for us). We need both an enhancement template and a test plan template, each having several tasks in their hierarchy, in a separate structure. For each new enhancement, we would copy the template into our structure, then edit it to be workable. So we either need the ability to copy a structure template into another structure, clone multiple issues from one structure to another, or make templates out of portions of a structure's hierarchy that we can then clone to another structure.
19 votes -
Provide the option to "Extend with Linked Issues" with all Link Types
Would it be possible to provide an option to "Extend with Linked Issues" with all Link Types instead of having to create an extender for every Link Type? Hopefully that makes sense...
16 votesCollecting requirements – please see the comment.
-
Subscription to a structure view
Jira has a "issue filter subscription" feature, which runs a filter at a certain time of the day and email the user with the results. Structure could have a similar subscription feature tied to a particular structure's view, where a snapshot of that view would be taken at a certain time of the email and the results would be exported to excel and emailed to the user.
My company currently use structure to keep track of our day-to-day progress by manually exporting structures to excel at the same time each day. Automating the exporting would allow us to automate the…
15 votescollecting requirements (see comments)
-
Possibility to change the start and the end dates of the entire project
Our organization would like to have a possibility to change the start and the end dates of the entire project. In this way, we could have a big picture view of all our projects in the timeline.
13 votes -
Create sub-issue should work similar to Link New Issue Operation (LNIO)Valiantys
I typically want to create issues of another issuetype, and probably in another project.
Just cloning is too trivial, and it requires to much work to change issuetype, and project.Alternative (even better): automatically detect sub-issues for certain link-types
13 votesplanned after 1.0
-
Bulk Clone Part of the Structure
This is becoming a necessity as we move forward with Structure. In order for all users to easily make copies of sets of issues from a repository-type structure at different points in their structure, we need bulk clone. The current copy/clone process requires admin authority and too many steps to roll out to non-admins and expect the environment to stay clean.
13 votes -
improve "templates" functionality and provide simple interface to work with it
- That's will be useful to have a possibility to create structure by one click. Ex. It could be a quick button (as jira has "+ Create issue" at the right top conner). When I click on it, I can choose template name & click create. That's all.
- Sub-tickets in template structure should be predefined, so I don't want to specify each time what project it should be and what options to copy.
- In existing structure that's will be nice to have a possibility to create tickets\sub-tickets using templates for issue. Ex. I want to have a possibility to easy create…
13 votes -
Change the colors of the font or/and background of the Structure folders
It would be great to be able to customize the appearance of the Structure Folders in order to have a possibility of manual highlighting the "problematic" folders.
13 votes -
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
- Don't see your idea?