nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Isolating Scrum Boards for Tasks

Liz_jj7s7o

We have each of our Managed Service clients set up in Jira as Projects, so we can track tasks etc.

We are planning a large migration for an existing client and I would like to use the Scrum Boards to track progress of just the migration tasks set up in the client Project (not the other support tasks).

My question is, can you isolate Scrum Boards to a particular task and all it's connected sub tasks? or does it have to be a new project?

Accepted answers

unknown

Hi Elizabeth,

You can create a separate board only for that. This new board can be in the same project as the other boards.

First, you need to set up a filter for the board, that will only show the issues that are related to the migration task. You can either add a label to all these issues, like Migration and then configure the filter to look only for issues with this label, or simply specify all the issue keys in the board filter.

All comments

unknown

Hi Elizabeth,

You can create a separate board only for that. This new board can be in the same project as the other boards.

Liz_jj7s7o

Thank you. I'm struggling with setting up the JQL filters. Being a non-coder ;/ any helpful links for learning Jira JQL?

Liz_jj7s7o

The query I am trying to filter for is...

Project > Parent Task reference > including related subtasks to that task

unknown

Hi,

This and this should help you.

For the situation that you presented, I provided 2 scenarios. Either:

1. add a text field named "label" to all the issues in the project, and add the label Migration to all the issues that are related to your large migration. Then, your JQL should look like:

Project = <project key> AND label ~ "Migration"

2. Note all the issue keys for issues related to the large migration and then do a JQL like:

Project = <project key> AND issuekey in ("AB-1", "AB-2", "AB-3")

(assuming project key = "AB").

Personally, I find the first option much easier.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud