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.

  1. Present a warning or confirmation dialog box prior to removing a generator from a structure

    There is no undo for accidental deletion of generators or folders.
    If you accidentally delete a root folder - you can lose everything!

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure Cloud  ·  Flag idea as inappropriate…  ·  Admin →
  2. Calculate context-aware Progress

    When displaying structures in a specific context (for example, after selecting a specific Version from the Project view), the Progress roll-up should be done in the context of that version.

    For example, assume I have an Epic containing multiple stories which will be completed across several releases. If I view the structure in the context of the upcoming release, it would be nice if the Progress calculation were based solely on those stories targeted for the upcoming release.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Connnect more than one JIRA instance

    When working with external partners they often use their own JIRA instance. You can connect them via the JIRA application link feature with your own JIRA instance and are able to set links between issues in the two JIRA instances this way.

    It would be great to be able to display linked issues from the remote JIRA in your own structures.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Show progress of selected issue/task in Confluence

    In our company we use very closely JIRA and Confluence. Structure allows us to properly organize issues based on our demands and workflows and it works perfectly for people who are assigning tasks or implementing them. But we use Confluence for executive summary of progress on specific builds where would be very helpful if we can display progress bar of a specific issue (counted from all issues below of selected issue in the hierarchy). This way we would be able to create great overviews like e.g. "Bug fixing of Feature1", "Implementing Feature2", ... with progress bars behind without a need…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. import from excel

    First set of columns each represent a structure level.
    Following structure, top row includes field names for data entry (e.g. Story Points, Type=Epic, Story...

    (not sure if this will come through or not, but something like this:

    |Level1 |Level2|Level3 |Level4 ... |Type |Story Points|
    |Jurassic Park| | | ... |Epic |
    |Jurassic Park|T-Rex| | ... |New Feature|
    |Jurassic Park|T-Rex|Goat Release| ... |Story |
    |Jurassic Park|T-Rex|Goat Release| As a goat I can be raised up so the T-Rex can eat me|Story| 8 |
    |Jurassic Park|T-Rex|Goat Release| As a goat I can NOT escape so that I will live|Story| 2 |

    Note…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Use tokens in the summary to capture recurring fields and indendation levels

    By specifying some fields e.g, priority and assignee as well as the indendation level of the issue while entering the summary text of the issue will speed up the data capturing with structure. Please consider having a look at www.checkvist.com for effective keyboard support for increased speed and useability.

    Eg use the @ to specify the person eg @john
    use the # sign to specify the priority
    Eg #0 - blocker

    1 critical

    Tab indentation in the summary for instance indentation level 1 specified by 1> indendation level of 2 specified by >2

    >1

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. add custom fields to structure-folders

    Budgets are often not added as issues. Structure could add value by allowing some limited amount of named custom fields on structure-folders (like notes, but some more). They would bind to a structure and could be accessed from formula columns.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Structure  ·  Flag idea as inappropriate…  ·  Admin →
  8. Navigate to next/previous issue in structure

    We want to have the feature to go to the next issue in the stucture.

    The scenario is:
    1. You have a structure open
    2. You open up the first issue in a full screen mode
    3. You go to the next issue in the structure. Without jumping back to the structure.

    In the same way as you can jump to the next/previous issue after you have performed a filter/search in plain JIRA.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. I suggest the structure gadget displays the full name of the structure in the dashboards

    Currently it truncates the names so it is difficult to tell which structure is displayed.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. introduce the same TP column as in the non-cloud versions

    The TP column provide icons with summarizing information. I miss this in the cloud version

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  1 comment  ·  Structure Cloud  ·  Flag idea as inappropriate…  ·  Admin →
  11. ...have separators, or sticky issues, that stay on top.

    My idea is that I want specific issues to not be affected by the sorting. Not affected, so that they can stay on top (or bottom).

    Another cool way to do this may be a separator or separators, that can be added similar to the way folders are added. Except these separators allow their content to stay where the user assigns it to.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Show some type of visual indicator when the progress rollup contains interpolated data

    I love the ability of the structure plug-in to roll-up numerical fields of children into their parents (thank you!). As I understand it, if some of the children do not have values, the roll-up algorithm estimates values for those children based on the values set in their peers (i.e the value of the unset children is the average value from all of their peers). Essentially, the structure plug-in is making estimates for the children even if users haven't entered any information.

    When that happens, it would be nice if the plug-in offers some kind of indicator on the rolled up…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Don't Dismiss Automation Dialog When Pressing Escape Key

    If you are adding a filter or some other automation that requires writing a query, the autocomplete often obscures the text of the query you are trying to write because the window is very small. If you press Escape to dismiss autocomplete to see what you are writing, the window closes, and you lose your work.

    In other entries, like the issue search screen, pressing the Escape key dismisses autocomplete, so it is more likely you will lose your work because you have the muscle memory of pressing escape to dismiss autocomplete.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Structure  ·  Flag idea as inappropriate…  ·  Admin →
  14. It would be nice if you could change the colour for different types of links

    Would it be possible to somehow recognize different types of links in the structure? e.g. add an icon for issues which are linked by "is blocked by" or change the colour of the blocking ticket.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure Cloud  ·  Flag idea as inappropriate…  ·  Admin →
  15. Hide empty folders

    In structure folders created based on custom fields will show "no value"-folder in case issues haven't set the related custom field. It would be nice to get an option to define whether to show such "no value" folders or to show such issues without a folder under their parent.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Localization

    Do you have prepared structure for translating structure. SWe need a German version.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Print Structure Cleanly

    Right now, I have two choices, export to Excel or print from the structure board.

    In our situation, the description and acceptance criteria have bullets, numbers and other items allowed in JIRA's rich editor.

    When exporting to Excel, this renders as HTML tags which Office does not accept and render correctly.

    When using the print functionality, JIRA Issues cross over page breaks (which we could fix if we could have it render in Excel)

    The reason this is a concern for us is that or customers want to be able to review the technical architecture. ePrinting is our only real…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Limit Structure Depth for "Master" Structures

    With all the work being done to create sub-structures or copy portions of structures, the master or enterprise view typically does not need all the detailed subtasks, those will even make that view less usable. It would make that view more useful to have a default depth to open the tree, so if I have
    Issue-1 - Project

    Issue-11 - Milestone
    
    Issue-111 - task 1
    Issue-112 - Task 2

    Issue-2 - Project 2

    Issue-21 - Milestone
    

    etc.

    I can have structures for the projects with all the details, and the structure for multiple projects defaulting to open to a depth…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Create a method to prevent parental and causal links to sub-tasks unless those sub-tasks have sub-issues

    if you have issues with sub-task type issues there's no way to pull those sub-tasks and any child or resulted in linked issues into a structure without structure creating child and resulted in links for all sub-task tasks of those parent issues. It appears that any configuration of the links synchronizers will results in the sub-tasks getting child and resulted in links to the parent issue. If this is true, I propose the following feature request.
    In the Links Synchronizer, create a sub filtering feature that uses the logic of: "don't create parental or causal links for sub-task type issues…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base