Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Group by Story on next gen board doesn't work with linked issues

I have a next gen Scrum board that I'm trying to configure to group by Story. From the looks of it, grouping by Story doesn't work if the story doesn't have any sub tasks. However, my stories are made up of linked issues. The reason for this is that we have several issues that span multiple stories (components need updating in common components, etc).

So, my story has 8 linked issues, all with a 'requires' operator. I've moved the story into this Sprint, however when I look at the Board, there is no way for me to group by story and see the linked issues underneath it. 

 

Is what I'm trying to achieve possible?

 

1 answer

1 accepted

0 votes
Answer accepted

Hello Stuart,

Welcome to Atlassian Community!

I understand that you would like to group linked issues underneath other stories in Next-gen boards. Is it correct?

I can confirm that the "Group by Stories" in Next-gen boards are created to be applicable only for sub-tasks and, Unfortunately, JIRA Next-gen doesn't have a "group by function" for linked issues. As we think it would be a useful feature in next-gen projects, we created the following feature request to get it implemented:

As a Jira Software user, I want to be able to configure swimlanes on next-gen boards 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

For now, you can choose one of the two options below to achieve your need:

1 - Change the linked stories to sub-tasks of the main story and use the "group by Stories" functionality

2  - Migrate your issues to a classic project, navigate to the board > Board settings > Swimlanes > Select the swimlanes to be based on a query and configure the following one:

issueLinkType in ("requires")

This will group your issues underneath the issue they are linked to.

Let me know if this information helps.

Thanks for the reply Petter!

You are welcome, Stuart.

Please, don't hesitate to contact us again in case you have any other questions. Have a nice day!

I just tried this, and I get this message back:

 

There is no issue link type with either an inward or outward description 'requires'.

 

Is there a way to "unaccept" an answer, as this CLEARLY does not work.

Hello @Marcelo Lopez

Please, note that the "requires" link type is a custom link type created by @Stuart_Fuller, as he mentioned in the description of the question, so the instructions provided to his scenario.

To apply the same instructions to your site, you would need to create a custom link type named "required" or use another link, as "Blocked by", "Related to", etc.

My apologies if I missed something in his note.

I do not see where he stated outright that he had created a "custom" link type....

 

The "Related to" still doesn't derive the grouping between A STORY and it's specifically associated TASK.

 

 This:   issuetypelink in ("relates to")

puts ALL Stories and ALL TASKS that have "relates to" set into the same lane.

i.e.

---------------------------

Story A

Story B

Task 1 related to Story A

Task 2 related to Story B

--------------------------

Everything else

--------------------------

 

When what should be possible is:

----------------------------

Story A

Task 1 related to Story A

----------------------------

Story B

Task 2 related to Story B

--------------------------

Everything else

--------------------------

@Petter Gonçalves Your solution puts all items that have the specifies relationship in one lane, and all items that do not have any such relationship into the second lane.

The goal is to GROUP items that relate to a specific item into a separate swim lane. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Software

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

4,664 views 22 33
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you