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. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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  ·  Flag idea as inappropriate…  ·  Admin →
  3. Testy: ability to creatae multiple test sessions/cycles without cloning tests and/or test results

    USE CASE:
    1. Visualize Progress Bar functionality test coverage on diff browsers (following example @ https://marketplace.atlassian.com/plugins/com.almworks.testy)
    2. Re-use the same test plan structure for multiple builds

    OPTIONS FOR BUILD 2:

    Option 1;
    Use columns for each browser (next build requires cloning to track test execution)
    Problem 1: Requires cloning of entire structure for next build
    Problem 2: Cloning just test results will not work as new results will overwrite test results from build 1

    Option 2:
    Use columns for each test run (no need to clone the tree and browser makes put in the hierarchy)
    Problem 1: after a…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Let user to zoom in and focus on just one hierarchy level

    One of the features that makes Workflowy so great, is the possibility to zoom-in to one hierarchy level only. I think this could work for Structure as well.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  5. have the ability to control the visible amount of a custom field

    I currently use a custom field for scope statements and wkly highlight reports. As far as I know, Structure only allows me to see a small excerpt of this field. I would like to be able to control the amount I can see (maybe in number of characters / lines). That way I can view issues listed in a Structure and see at least 2 or 3 paragraphs of the report/statement at once.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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  ·  Flag idea as inappropriate…  ·  Admin →
  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  ·  Flag idea as inappropriate…  ·  Admin →
  8. Auto-Convert Perspective-Link into Structure-Gadget on Confluence-Pages

    In this way one is able to create whatever view of the Structure in the structure itself and share this on Confluence pages without dealing with the UI of the gadget (which needs some improvements).

    1 vote
    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 →
  9. Integration on Jira Agile

    It's very useful the integration with Jira Agile (on Jira 6 and next releases), so I can see near the tab Epic and Version (in the backlog view) also the other structure that I can build.
    Actually, I have to manage two different views: Structure view and Backlog view. It's better to integrate this two views.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  10. Structure lite

    Have you ever thought about a lite version of structure with reduced functionality? e.g. only supporting parent / subtask or epic / story relations or homogenous link hierarchies for example.

    1 vote
    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 →
  11. Not override the functionality of the JIRA Create button

    I think the decision to override JIRA's big, blue Create button in the top navigation is a mistake. And it's causing some headaches on our end. We have non-technical users who are using the Structure (with edit permissions) who aren't aware that creating a new issue will add it to the Structure they're viewing. They simply want to create an issue, not necessarily add it to their structure. We could remove the button easily, but then we'd have to have our users jump to another JIRA screen to create an issue. That's design breakage! My opinion is, leave the ubiquitous…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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  ·  Flag idea as inappropriate…  ·  Admin →
  13. Be able to Receive a notification when an item is manually added to a structure folder and/or it's sub-folders

    Be able to Receive a notification when an item is manually added to a structure folder and/or it's sub-folders. That way when someone adds an item or removes one to an existing structure folder, anyone subscribed to notifications for that folder would get an email notification. to implement, just add a button to the button bar when the folder is selected and when you click the button, you get a popup with an option to subscribe to notifications like you do with issues in JIRA.

    Obviously, this would only be available for folders WITHOUT automation.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  14. 1 vote
    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 →
  15. Folders within epics and Epic extension automation

    I need to track business Epics, but these are usually large and I like to break them down into smaller-sub-epics to deliver and track (via multiple releases). Jira doesn't support Epics with Epics (unbelievable really) and I need to work at ira as well as structure level so I create folders in structure under the main epic to perform this partitioning. Each Jira story is still linked to the main epic so I can use Epic reporting in main Jira, but it does mean that I can now track sub-epics at the folder level in structure too. Unfortunately this means…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  16. Filter the issues that aren't picked up by the generators

    To force a rebuild of the structure based on generator rules only.
    The filter would help to identify the issues manually added into the structure.
    Then we can decide which issues (all or selected) to remove from the structure if not relevant.

    Problem: We cannot remove all the issues from the structure. There's a warning when removing at least one issue that is picked up by the generators, and when we acknoledge all the issues come back.

    1 vote
    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 →
  17. Limit the issuetypes for automators so you can use multiple link automators per structure

    With Synchronizers it is possible to limit the issuetypes. Therefore it is possible to have multiple link synchronizers for different issuetypes.

    Example:
    one could defined a parent/child link between epics and features and use a is blocked link between features and bugs. with automators this scenario can not be implemented at the moment.

    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  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. be able to copy directory path

    This feature can help a user orientate an issue in a structure, or share the path with another user easily.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  19. Would really like to be able to color fields, columns or rows in structure chart (without having to pay for expensive plugin)

    I create some rather large Structure charts with multiple levels of nesting. Want to be able to highlight aspects of the chart (Rows, Cells, Columns) with color. This helps with focus (these items are critical), organization and overall visual appeal.

    1 vote
    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 →
  20. Folder metadata

    It would be useful to have folder metadata. There are many uses for this but at a high level you could definitely folder types (strategic vs. operational), provide folder owners etc.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base