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. Progress Bar changes color by ontime or overdue

    Allowing users a quick view of the status for more than completion percentage for [insert your object of choice] if they are overdue or nearing completion deadlines

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Be able to propagate up a risk value

    If a sub task had a custom field which indicated it's current risk or similar be able to propagate that up to the top level to show the worst of the risks or some other flag

    e.g. if a single subtask of a item is red risk, be able to show that red risk in all of it's parents in the structure. choose the worst value of all sub nodes to show at the parent level.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add last comment as a column

    Comment can be used to know the current status along with status of jira. Therefore, it will be great if last comment can be displayed.

    19 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. allow me to define a story point budget for a folder / issue

    I typically have rough estimates for bigger projects and I would like to be able to add them to the structure so that I can get an overview of what needs to be done. At the moment I can only do this by adding JIRA issues with estimates, but the problem is that at this stage I do not really want to create these issues yet (at least not for everything).

    The closes thing to what I want is to create epics and set the rough estimates on the epics. Later I can refine my estimates by creating storys. The…

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Connnect more than one JIRA instance

    When working with external partners they often use their own JIRA instance. You can connect them via the JIRA application link feature with your own JIRA instance and are able to set links between issues in the two JIRA instances this way.

    It would be great to be able to display linked issues from the remote JIRA in your own structures.

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. support grouping of issues by link type

    e.g. all 'Blocked By' issues added via Extend automator grouped together under parent.

    This makes the Jira relationship between Structure parent/child issues clearer.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Structure for JIRA: Ideas

Feedback and Knowledge Base