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; } } }

When adding multiple boards in one project

Junichi Sasaki

I am a JIRA beginner.
Please allow us to ask rudimentary questions.

I would like to hear about a situation where a board is added separately from the existing scrum board in one JIRA project.

For example, suppose I was a designer and UI artist.
The main board of the project lists the stories of multiple teams in one sprint.

I would like to extract only UI related stories from them and see them.
In that case, Create a "UI board" and customize the filter there.

Is this correct usage?
If not, what is the correct way to add and use a board?

Accepted answers

John Funk

Hi Junichi - Welcome to the Atlassian Community!

Yes, that is correct usage as you have described. Then your filter for the UI Board would be based on the issue type or component or however you are identifying the UI work.

Michael Kuhl {Appfire}

Hi @Junichi Sasaki - Your approach is one of two ways to be able to view only UI related stories.

Here's an article on creating additional boards. In this case you will want to modify the filter to show only UI related stories. This option is simpler, but you risk being out of sync with other team members who use the other board if they make changes to how the other board works.

The other method is to add a quick filter to the existing board where the quick filter excludes non-UI related stories. This way you can ensure you are working with stories in the same way as the rest of the team but can constrain the set of stories you see when you want to.

All comments

John Funk

Hi Junichi - Welcome to the Atlassian Community!

Yes, that is correct usage as you have described. Then your filter for the UI Board would be based on the issue type or component or however you are identifying the UI work.

Michael Kuhl {Appfire}

Hi @Junichi Sasaki - Your approach is one of two ways to be able to view only UI related stories.

Junichi Sasaki

Hi John.

Thank you for your quick support.

Junichi Sasaki

Hi Michael.

Thank you for your answer.

I might have misunderstood.

For example, suppose you make a new UI board by copying the main board.
I can extract only UI-related stories, and I want to update the progress by talking with the UI team every morning about the subtasks set in the story.

As for the “risk of getting out of sync” you pointed out to me, it means that “even if you apply a filter on a newly created UI board, after change to subtask / Story to "done", The actual main board UI story is not updated."

This is correct?

In other words, changes made in the added board are not reflected on the main board ...? (I'm confused now..)

Michael Kuhl {Appfire}

Sorry for the confusion. If you make a copy of the board and only change the filter then the boards will be in sync as far as the story status is concerned.

What I meant by "out of sync" was if the other board decides to - for example - change the order or name of the columns then the story status will still be in sync between the boards, but they will look and work a bit differently. If the two teams don't need to work in each other's boards then this is not an issue.

Does that make it clear?

Welcome!

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

Quick Links

Find more posts tagged with

jira-software