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.

360 results found

  1. Allow multiple simultaneous updates

    The edit capability in the table view is very helpful but even more helpful would be ability to update multiple fields and/or multiple issues. Is copy a row or column or table from Excel into structure table.

    6 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  ·  Structure  ·  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. Earn Value Management Formulas

    Formulas for project tracking: Earn Value, Cost Performance Index, Schedule Performance Index, Estimate at completion, etc using cost from Tempo

    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)
  3. 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.

    6 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  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add progress aggregation based on the number of sub-items

    Parent issue progress % seems incorrect based on underlying children progress % values, assuming equal weighting per child.

    Example screenshot: imgur.com/a/43lgW

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  4 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)
  5. Flag items in the structure

    Hello,
    I would like to be able to flag items in my structure tree view in the same way as I can on my JIRA Kanban board and JIRA Kanban backlog. The original Atlassian feature is described in https://support.atlassian.com/jira-software-cloud/docs/flag-an-issue/

    Jens

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  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. 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)
  7. "Remove Inserter/Extender Duplicates" generator should also work for non-hierarchical duplicates

    When using the "Remove Inserter/Extender Duplicates" generator also non-hierarchical duplicates, based on different used linkage types like "child-of" and "resolved by" should be removed.

    6 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  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Progress by status category

    Currently progress by status is supported(among other statuses).

    To simplify configuration in complicated jira setups it would be nice if one could filter by status category. Instead or in combination.

    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)
  9. start date

    As a team lead, I want the Gantt view to show all unresolved issues as starting in the future irrespective of the view's "start date", so I can quickly visualise dependencies between teams that will impact their next sprint

    5 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  ·  Gantt  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    accepted  ·  Alexey Pegov responded

    Hi Robert, thank you for the request! This feature is called a Backlog and planned to be available in one of upcoming releases!

  10. Allow for shared filters similar to how views are managed

    Similar to how views can be shared across different Structures, it would be great if Quick Transformations could be the same. Right now, we have 15+ separate, but related Structures. All should have consistent views and transformations. Managing views is very simple, but if you change a filter on one Structure, you must replicate that change X more times.

    5 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  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Ability to hide the time line in the gantt chart view

    It is a widely adopted practice to not share specific dates in long term planning and it would therefore be helpful if I could hide the dates/timeline in the gantt view.

    The only option today is to zoom out but that is not practical as the feature-bars will become to small and the timeline is still visible but in years.

    I want to be able to show how feature A is scheduled before Feature B and that it is dependent upon Feature C being completed without having to show when the features will be worked upon.

    Simply hiding, or making…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Gantt  ·  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. Expand Editing from Gadget

    Please add the ability to edit more fields especially custom fields from the Gadget (https://wiki.almworks.com/display/structure/Editing+from+Gadget). The ability to edit custom numeric fields via jira dashboards/confluence pages would be awesome!

    5 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  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. show more bars for one issue in a row (use more than 2 datepicker fields)

    In our issues we use more datepicker fields, e.g. Start Phase 1, End Phase 1, Starte Phase 2, End Phase 2 and so on.

    I want to show that bars within structure gantt, so not only one bar for one issue but several bars next to each other for one issue to show that time periods.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Gantt  ·  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. Granular control over Automation grouping, particularly with Labels

    Currently, grouping within Automation is kind of an "all or nothing" approach. For example, we use labels to identify which "product" our epics are for, but we also use the Labels field to track other information. For our main Structure, what we want to do is have the Automation grouping only look at the 6 labels we currently use for "product" tracking and ignore all of the others, but I cannot seem to find a way to do this without manually creating my own folders and setting up the Automation for each one; the drawback to this is we can't…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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)
  16. Have option to customize or hide what buttons are shown

    Trying to get users to update information who are less familiar with Jira. Want to customize what options/buttons users see so it's less overwhelming.

    5 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  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. user defined rank attribute

    Create an attribute "Rank" to allow a user to manually order stories.

    Use case: I want to prioritise stories for a given release. e.g. I have 20 stories and want to rank them 1-20.

    Benefits:
    - the ranking is more transparent to a larger audience than the ability to move stories on screen
    - if another user changes the order I can see what was changed

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. removing a column sort is not easy. Make it simple.

    Structure is sorted by Rank (through automation). I often click on Assignee column to sort by it. The only way to remove the sort is to click Transformation, Click the sort and click the remove. This is way too many steps to just remove a sort. One idea is to have each column have 3 states when clicked. Sort Ascending, Sort descending, Remove sort.

    5 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  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Report or filter on accumulated fields

    FIelds like 'progress', 'estimate' or 'logged' are calculated (accumulated) over the sub-structure under the issue. I would like to be able to report those values in reports (e.g. accumulated estimate) or use them in JQL queries (e.g. accumulated_estimate > 2w)

    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)
  20. 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.

    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)
  • Don't see your idea?

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base