Swimlanes via linked issue "is child of"

Phillip Nalesny March 14, 2024

Dear Atlassian Community,

I'm seeking assistance with structuring user stories on my Active Sprint Board using swimlanes, which are determined by the features above them. The features above are structured on the ART level with the abbreviation "VDAS", while the user stories are structured on the team level with the abbreviation "PUAT". The connection between these two issue types is established through a Is-Child-Of relationship.

I'm wondering how the SQL query should look like to group all user stories (PUAT-XXX) according to the linked (link type = "is child of") feature (VDAS-XXX) above them.

Any help or guidance on constructing the SQL query would be greatly appreciated!

Thank you in advance.

Best regards,

Phil

1 answer

1 accepted

3 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 14, 2024

Hello @Phillip Nalesny 

Welcome to the Atlassian community.

You would not be able to write a single query that would dynamically create a swimlane per feature VDAS-###.

You would have to write a query explicitly for each VDAS feature issue and assign each query to a swimlane by setting the Swimlanes option to Queries.

If new VDAS feature issues were created, you would have to add a new query swi.lane for each one.

Is that a solution you are willing to implement and maintain?

Phillip Nalesny March 14, 2024

Hello @Trudy Claspill thank you very much for your quick answer. Yes that is a solution I'd be willing to implement and maintain.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 14, 2024

The query that you would use then would be

Issue in linkedIssues("<insert VDAS issue key here>", "is child of") and project=PUAT and issue type=Story

You can find details of the linkedIssues function here:

https://support.atlassian.com/jira-software-cloud/docs/jql-functions/

Like Phillip Nalesny likes this
Phillip Nalesny March 14, 2024

Awesome! Somehow the whole thing did not work for me but I reduced it to: Issue in linkedIssues("VDAS-990") and now it works! Thank you very much! :)

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 14, 2024

I had added "and project=PUAT and issuetype=Story" because you mentioned that the issues you were wanting to collect would be Stories from the PUAT project.

I do see that my original response had a typo, in that it says "issue type" rather than "issuetype" (without a space).

Suggest an answer

Log in or Sign up to answer