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. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support dependency offsets

    As a project planner I need to be able to define a dependency with an offset.
    Example: Task 5 can start 3 days after Task 4 starts. I would define that as a Start-to-start dependency from Task 5 on Task 4 with a +3 day offset.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  3 comments  ·  Gantt  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Send to top/send to bottom

    I miss the "Send to Top" and "Send to Bottom" functionality that is in the context menu on Agile boards. I learned how to cut/paste to move tickets but that is a lot of clicks and scrolling for a common (for me) action.
    I saw a comment from Igor in another suggestion to open a new panel with the same structure, and drag the ticket to the top/bottom of the new panel. I tried to do this and I got this error "Cannot move issues inside JQL query result."
    I'm still feeling my way around structure so maybe I'm doing…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Structure  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Provide the option to "Extend with Linked Issues" with all Link Types

    Would it be possible to provide an option to "Extend with Linked Issues" with all Link Types instead of having to create an extender for every Link Type? Hopefully that makes sense...

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Structure  ·  Flag idea as inappropriate…  ·  Admin →
  9. Have a Back to Structure button in Issues

    When you open the Issue to view/edit the full details, a link back to the full structure would be nice

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Show more results to allow me to use the browsers scroll function.

    The view port of the structure plugin is rather small. I can only see a max of 12 rows on my screen (1360x768). I need to export to excell to see more stories in my epic. It would be nice if more results are displayed on the screen. And to be able to use the browser's scroll bar to scroll, that's why it's there. Or did I miss a config option?

    4 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 →
  13. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. [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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Flag idea as inappropriate…  ·  Admin →
  18. Creating structures from agile boards with Epics and Epic-less tickets

    When creating a structure from an Agile board it would be nice to be able to add as well Epic as stories not assigned to an Epic.

    Creating a structure with Epics and adding an JQL-Inserter for the Epic-less Stories is not sufficient. I am not able to move Stories into an Epic later on the structure board this way. ("Cannot remove issues from JQL query result. ")

    3 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 →
  19. Sync task to add Tasks to Folders

    Folders is a great new feature in 3.0 (long awaited) but the sync tasks do not allow tasks to be added to folders which is an obvious feature for auto adding tasks to structure and also a huge use of ordering and sorting tasks in structure.

    3 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. Extend Sub-Task Synchronizer with JQL filter

    The Sub-Tasks Synchronizer only allows to select the Issue-Type to be selected. It would be helpful to have a JQL field to filter out more and also to have a JQL field when a Sub-Task should be removed from the Structure.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Structure for JIRA: Ideas

Feedback and Knowledge Base