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. Use the standard Atlassian User Interface objects

    I would suggest you to resort exclusively to the AUI objects for your interface instead of your custom ones that clearly gives the impression that you are exiting the Jira world to step into another one.
    I think you user would deserve a smoother user experience, with the same kind of buttons, icons, tables to which they are already used to. I'm especially talking about the transformation/filters features that should be improved in that direction to my mind. Thanks for you great achievement!

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  3. Structure of Structures - no data just an index with link to the relevant structure

    I would like to create a Structure of Structures for structure navigation, whereby specific child elements allow you open the referenced structure. I have many structures that contain the same data, just displayed differently for different user groups.

    The use case is in essence:
    Parent - Folder (a name listing a group of similar or related structures)
    Child - New Structure Link - simply a mechanism to either open or navigate to the referenced structure - includes description.

    Implementation:
    Is it possible to add a new Structure element into the "Add" Dropdown called "New Structure Link". (i.e. New Issue, New…

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add ability to synchronize at the Project category level

    A structure is set up across multiple JIRA projects and when I add a new project, I have to redo the synchronizer. If I could select a Project Category instead of individual projects, then I would only need to add the new project to the project category.

    4 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  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Structure  ·  Flag idea as inappropriate…  ·  Admin →
  6. Automatically clear multi-selection after a move/paste operation is completed.

    The structure plug-in allows users to select multiple, dis-contiguous issues using the multi-select mode, whereby the user clicks on the little radio button next to every issue they want to select. The selection can then be operated on as a whole, for example, to reposition the issues in the structure.

    This feature works great, however, I find it annoying because the selection 'sticks', even after I've completed the operation I wanted to perform. Then, when I move onto select other issues, the previous ones, which are still selected, unintentionally come along for the ride.

    Let me provide a use-case. Assume…

    4 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  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add a custom field on child issues to show the structures root element

    I would like to see the root element in the structure in the custom fields of the children so I can use this when exporting data from jira

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 4 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 Cloud  ·  Flag idea as inappropriate…  ·  Admin →
  9. Would like a way to get Structure formula calculations into "normal" Jira custom fields

    Structure formulas are extremely useful. Now our users would like ways of using them in other places within Jira. This may be tough in some ways because they are specific to the structure they are part of, but even something simple like the ability to choose an menu option or call some API to commit formulas into an underlying custom field could be quite useful.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Keep carriage returns during Excel export or be able to save off the Printable Page.

    We added 2 custom fields for testing steps. The carriage returns show up in Printable Page nicely. But we can just print that. The Excel export doesn't keep them and so the steps are jumbled in each cell instead of a clean representation.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support entering data into mandatory fields on SubIssue creation

    when you are creating a sub issue you might hit a wall when the creation of the issue have some mandatory fields which needs to be filled out.first.
    it should be possible to enter data during sub issue creation.
    it is already shown which fields that need to field out.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow quick transformations from Gadget

    Hello,

    I am in love with structure. Thank you so much for making it!

    Would it be possible to put the Quick Transformations in the Dashboard Gadget in Jira?

    Thank you!

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  13. Color quick transformation buttons to allow faster identification and categories

    Currently, when you add a quick transformation the buttons are all white/clear. When you have a large number, it can be hard to find the transformation your looking for.

    With colors, you could create visual categories (i.e. groupings, component filters, label filters, etc) and the user can navigate to them much faster.

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  14. Group by Link Type

    Group by Link Type.

    We have many link types used to represent different things.

    E.g.
    - A "Story" ticket may [LinkType: Satisfy] many "Acceptance Criteria" tickets
    - A "Bug" ticket may [LinkType: Block] a "Story Ticket"
    - An "Epic" may [LinkType: Solve] a "High Level Requirement" ticket

    Where tickets have multiple types of link coming from them, would be nice to have that as an explicit folder / grouping in the tree.

    E.g.
    Story X
    > Blocked By

       Bug Y
    
    Bug Z

    > Solves

       Acceptance Criteria A
    
    Acceptance Criteria B

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  3 comments  ·  Structure Cloud  ·  Flag idea as inappropriate…  ·  Admin →
  15. Use Monaco editor for editing formulas

    The Formula column is a killer feature, but it can get tricky when the formula expression grows larger than the size of the editing area, and has a few levels of nested expressions.

    Beyond just the ability to enlarge the editor, it would be fantastic to have a more advanced editor to assist here, and the obvious candidate is the https://microsoft.github.io/monaco-editor/

    My suggestion for iterations for this would be:
    - Just replacing the actual editor and make sure it's still working when editing and not (so no functional changes)
    - Adding config and definitions needed for highlighting brackets and auto…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Structure  ·  Flag idea as inappropriate…  ·  Admin →
  16. Automatically create issues to represent structures

    Allow structures to have attachments, comments, workflow, etc by creating an issue for each existing structure. This could be automated by the Structure plugin.

    Let the administrator configure a special project / issue type for those issues.

    4 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  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. [Structure+Testy] Make it possible to have a type of parent child relation inside an issue

    Use Case 1:
    As a tester I would like to use a unique test case and run it several times and after every run I would like to add my test data/environment to it. (E.g. Result and what format, browser, platform, DB that was used during test run...)

    Use Case 2:
    As a Test Manager I would like to be able to create a dashboard report or filter based on specific data and the outcome of the result with that test data/environment.

    Current solution with testy today (https://marketplace.atlassian.com/plugins/com.almworks.testy)
    has some good features but you still lack the method…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base