Skip to content

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.

374 results found

  1. Deleting of items should also be possible with a short cut key combination - not only removing the items from the structure

    Preferably without requiring an acknowledgement. The aim would be to mimic the speed of mind mapping tools for capturing information in meetings. One of the issues is if one wants to delete a item it should be as fast as creating one

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Strikethrough on closed or resolved issue

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

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Create shortcut key for setting tasks on Resolved

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

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  6 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 15 16 17 19 Next →
  • Don't see your idea?

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base