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.

I suggest Structure should ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Visualize hierarchichal structure in Issue Navigator and GreenHopper planning board

    Structure looks promising. To make it truly usable for my needs, I would need to visualize the hierarchical structure in the Issue Navigator, GreenHopper planning board, and Filter Results dashboard gadget.

    112 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  17 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    78 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  20 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    68 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    31 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

    63 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  12 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    27 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Gantt  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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…

    22 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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…

    21 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Integrate structure in JiraClient

    I'd love to see structure represented in jira client...

    20 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add last comment as a column

    Comment can be used to know the current status along with status of jira. Therefore, it will be great if last comment can be displayed.

    19 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

    17 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Improve the administration (Synchronization Settings) for structures with many syncronizers

    We have structures with many syncronizations and have had some problems maintaining them:

    1. Fast way of resyncronize ALL syncronization rules for the structure
    - In some cases the syncronizations needs to be "Resync"ed.
    We have found that for example when a filter syncronizer refer via a 'filter' it doesn't take effect when we change the refered filter. After a forced Resync it works.
    Example
    JQL query: (project = DEVENVC2JIRA or label = Jira) and filter = "DEVENVC2 - Next month" and status = Assigned
    In this case, when we change the "next month", we need to resync. To do…

    15 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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…

    15 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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.

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Open structure issues in Issue Navigator

    Similar to functionality in Greenhopper and other plugins, add a button to structure to allow opening the list of issues visible in the structure in the Issue Navigator.

    I use the Agile Cards plugin. It's possible to print cards from the Issue Navigator. I would like to be able to print cards for a portion of the hierarchy in a Structure but I have no way to get from the structure to that functionality. One possibility is to allow opening the issues currently visible in the Structure in the Issue Navigator.

    It seems like this would be useful for other…

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Use different fonts for the levels in the hierarchy to make them more distinct

    It would be great for easier differentiation to make the font larger for higher level issues in the hierarchy. E.g.

    Level 0 - H1 Bold
    Level 1 - H2 ...
    Level 3 - H3
    etc

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  11 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Need additional mark for Closed issues

    Structure shows check mark when issue is resolved, but I want another mark if issue is closed!

    11 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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.

    11 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Strikethrough on closed or resolved issue

    A closed or resolved issue should have have a "strikethrough" on the summary.

    10 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 9 10
  • Don't see your idea?

Structure for JIRA: Ideas

Feedback and Knowledge Base