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.

118 results found

  1. Ability to connect to more that one Confluence instance (Structure.Pages)

    Current (unless I'm doing something wrong) we can only link one Confluence instance when setting up Structure Pages integration.

    It would be nice to have the ability to link more than one. This should come though with the proper UI to select the server when adding a page or searching.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  2 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)
  2. Allow to see the structure in the issue type 'Test'

    When viewing an issue of type “Test”, created by Zephyr and assigned to a Structure, we are not able to see the corresponding Structure section as expected. If we change the type of the issue to anything else (Bug, Story, Epic, etc.) then the Structure section becomes visible. It seems that either Structure or Zephyr is not playing well together. This is critical to our organization as we try to integrate structured testing into our organization.

    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)
  3. Reinstate search on the issue page

    In Structure 3, search and filtering functionality was removed from the issue page. But sometimes we need that to rearrange structure without leaving a specific issue.

    More feedback:

    But with the loss of the toolbar we can no longer filter or search the structure from the issue view.

    We frequently need to unpin, search then re-org the structure, and we like to do it from the issue view. At my work we are considering rolling back to 2.x to get the search/filter feature back on the issue view.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  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)
  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

    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. Name in issue viewer

    When beeing displayed in the issue viewer and the default structure name should be "None" to avoid confusion as another structure name makes it seem to belong to one.

    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  ·  3 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)
  6. Allow an attachments column with attachments preview, similar to the Images column

    The structure view should allow the user to display "attachments" as a column, where attachments are listed similarly to the "Images" column. Clicking on an attachment thumbnail would popup a preview of the attachment.

    At the very least it should allow the user to download the file without opening the ticket itself.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  12 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)
  7. Allow Better Transitions

    By example, we use stories and have them implement features. Our final state for stories is "Closed" and when all stories are closed we want to have the feature change it's state to "Ready for Production" however there doesn't seem to be a way to do that.

    To that end, it would be nice if we could say that for state X we could specify what transitions could go there given that its sub-items state may be different.

    Example:
    Feature Workflow has "In Progress" --- {Ready To Deploy} --->>> "Ready for Production"
    Story Workflow has "Verify" --- {Ready To Deploy}…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  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)
  8. Custom structure template based on 1 or more JIRA fields

    The plugin allows users to create arbitrary structure and also structure based on JIRA links. It would be nice if there is a way to create structure based on JIRA fields like Reporter, Assignee, version, status. So user can drill down the issues by reporter, By Assignee, By version or any such combination and order.

    1 vote
    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)
  9. Allow users of the Tempo Plugin to see a per-user summation of time usage

    We always have multiple coders on our projects, and almost always have multiple coders contributing to each piece of functionality within a project. We use the Tempo Plugin for JIRA to keep all that straight.

    Structure's time summations are really helpful and beneficial. But for our multi-coder environment, we have to look at that summation in Structure, then look at every subtask and split out exactly who contributed how much to the Structure main task, because different coders are at different billing rates. This is not workable except on very small projects.

    What would be ideal is if we could…

    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)
  10. Reorganize the ManageStructure page

    • allow us to specify a short name for each synchronizer
    • move the items which appear once per structure, i.e., Name, Owner, Access, Popularity, Operations, out of the table to a header, so that the information in the Sync With column could be expanded: this would allow more room so that the Sychronizer Short Name could be displayed, and the type of synchronizer would not line-wrap. Thanks !
    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  2 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)
  11. Allow "Active Sprint" option for the Work Logged field

    Currently, the options are current and prior day, week, month, year. Can we have current and prior sprint?

    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  ·  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)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  3 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)
  13. Add link to documentation and resources from toolbar drop down menu

    I'm the admin and know of and installed structure, however, my JIRA users don't know what it is or how to use it. To help educate all please include links to helpful resources in your toolbar drop down such as documentation, etc.

    Thank you

    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  ·  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)
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  2 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)
  15. 3 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)
  16. Support wildcard in structure() S-JQL function

    I would like a way to use a 'wildcard' in the structure() S-JQL function so that it searches all matching structures. Specifically, I am trying to solve the following problem: find all leaf nodes in any structure.

    Here's a potential use-case: I want to have a task backlog implemented in Structure. I also want to be able to organize my tasks in a hierarchical manner, also using Structure. In my task backlog, I only want to track the 'leaf' tasks which appear in my hierarchical structure.

    I know I can do this now using the structure() function, but I must…

    0 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)
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  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)
  18. Support hierarchy of projects

    Can I display a hierarchy of projects? I have a project x that is a sub project of a, b, c. Is this possible?

    8 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  ·  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. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  2 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)
  20. Limit parent-child relationship to specific types of issues

    Let JIRA admin specify what issue types could contain what other issue types. For example, a Test Suite may contain Test Cases, which can contain other Test Cases, but not Feature Requests.

    86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  20 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)
  • Don't see your idea?

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base