I suggest Structure should ...

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…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Jeremy shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

6 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Mikal H Henriksen commented  ·   ·  Flag as inappropriate

    I'd like this too. We have a large organization with several teams and projects. My use case is to get an overview of all issues in other projects that are linked to my project, mostly to easily visualize blocks, but usage of link types isn't always consistent so I don't want to limit it to one link type. So that means all link types and directions, and I was picturing it as a subfolder per link direction, kinda similar to what it looks like on the normal issue details page.

    I'm handling it right now with ScriptRunner and an extender per link type, but it's a chore.

  • Erlend Flaa commented  ·   ·  Flag as inappropriate

    Adding to this discussion. Yes, this could be handy... but only if I am able to see the link type (which is another pending feature request, I believe).

  • Jeremy commented  ·   ·  Flag as inappropriate

    My apologies for the response delay. Yes, I would like to see all linked issues regardless of the direction.

    I currently use Structure to list all my customers' feature requests. When a request is created I then get my dev team to link issues they are working on that relate to that original request. It is great because I can set an overall Status for the original request as well as view the statuses of all linked issues in a single dashboard. Very handy. Thanks!

  • AdminIgor Sereda (Admin, ALM Works) commented  ·   ·  Flag as inappropriate

    Hi Jeremy, thank you for the explanation!

    Please note that each link has a direction. For example, "Blocks" link type would have directions "A blocks B" and "B is blocked by A". Would it be correct to say that when you configure such an extender (that would include multiple link types), then you'd want to see all linked issues regardless of the direction?

    Also, could you expand a little on what is the use case -- how do you use such structure?

    Thank you!
    Igor

  • Jeremy commented  ·   ·  Flag as inappropriate

    Thanks for your reply, Igor. I believe the problem resides in the fact that we currently have ~20 different Link Types (ex. "Blocked", "Dependency", "Duplicate", "Parent", "Related", etc). Don't ask me why there are so many but that seems to be the case now and I doubt I can narrow down the list without impacting other teams who possible use some of those Link Types. A similar example of multiple Link Types can be seen here on Atlassian web site:

    https://confluence.atlassian.com/adminjiraserver071/files/802593137/825787649/1/1448938809126/issue_linking.png

    If you use that image as reference, for all my Structure dashboards, I need to currently create a separate Extender for each Link Type (i.e. Blocked, Bonfire Testing, Cloners, etc). This is a bit tedious and prone to error if someone in the future adds a new Link Type and I have not created a new Extender to display those links.

    Regarding direction, I'd rather not have the user have to configure anything for each link type. I'd like a single Extender with Linked Issues cover all Link Types.

    My apologies for any lack of understanding on my part. I have only begun using Structure recently but find it very powerful!

  • AdminIgor Sereda (Admin, ALM Works) commented  ·   ·  Flag as inappropriate

    Hi Jeremy, thanks for the suggestion --

    It does make sense, but brings a couple questions. Will this extender require the user to configure a direction for each of the link type? Can you expand a bit more about the use case?

    Thanks!
    Igor

Feedback and Knowledge Base