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. Link issues in a hierarchy as you move issues around in the Structure view

    Currently, when you clone a subtask and move it to another parent issue, it actually remains (for all intents and purposes of JIRA data) as part of the original parents issue.

    This is a problem, because in Greenhopper on the planning board (where you move User Stories to actual date defined releases), they have to reflect the same structure as you created in Structure.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Display a collated view of multiple structures

    As a release manager, I want to see multiple structures represented in one view so I can easily collate the work multiple teams are doing. Our planning and management of structures is distributed, but I need to be able to see them all for enterprise planning purposes. Additionally, I want to be able to filter the one "master" view so I can see only those items related to specific criteria (e.g. release or project or component).

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 →
  4. Header/Footer for Print & PDFs

    Add ability to edit header and/or footer for print outs. Include fields for Date/Time Printed, Structure Name, Etc.

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. 5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. When displaying subtasks in Structure, include parent jira # as part of summary (like Jira filters)

    When displaying subtask in Structure, include parent jira # as part of summary (like Jira filters).

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. expose a structure's "order" so JQL queries and filters can be created to list issues in that order.

    The order's created would be very handy to be able to query in JQL - something like: project = MARSCOLONY AND assignee = "cosmonaut" ORDER BY "taskorder1-structure" ASC

    This would allow exposing structures in Confluence and other places in a useful way.

    Not sure what to do about different levels, but initially just ignore issues that aren't at the top level?

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

    Allow users to set due date based on due date of parent and estimated time. Plus when due date of parent is changed propagate change to all child issues accordingly

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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 →
  11. 8 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 →
  12. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Create shortcut key for setting tasks on Resolved

    A shortcut to set a task on resolved would be appreciated.

    6 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 →
  14. Allow CSV Output of Information from Structure Board

    It would be nice to have the ability to dump the structure board to a csv. Thinking that it would be something quick and dirty, with ' - ' noting structure, like this:
    "Name", "Est Hours", "Progress"
    "Mars Colony", "10h", "80%"
    " - Terraform", "6h", "50%"
    " - - Make Oxygen", "2h", "100%"
    " - Create Colony", "4h", "0"

    Once this was CSV, it could be manipulated in other programs. Right now, I don't see a way to get the Hierarchy or estimate roll-up data out of the system for project managers to use.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 →
  16. 7 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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 →
  18. 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 →
1 2 6 7 8 10 Next →
  • Don't see your idea?

Structure for JIRA: Ideas

Feedback and Knowledge Base