Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Two Boards for One Project with One Flow

Hello, I am setting up a project using JIRA Agile for my team. I am using Scrum methodology.


Our team is split into two groups. Those requesting the work, and those doing the work. I ideally like to have two boards for our team.

One board would be a Sprint board, We are using the default scrum workdlow. I want to integrate the following 

1.  create user story tasks in Jira for analysis phase, those task will not be part of Sprints, but is required to manage workload of other team who are requesting for the work and projects as well.


2. When the other team analysis phase is done then that user story will appeared in the backlog.


Any example workflows that have this setup would be much appreciated. Thanks!








1 answer

0 votes
Tarun Sapra Community Leader Dec 13, 2017

Hello @Amit Arora

This is a common requirement and not difficult to implement. 

Basically split your workflow among two boards based on JQL filters which are fetching issues for the boards.

In your workflow you can have status "ready for sprint" which can be the first status for the "sprint" board and before this there can be statuses like 

"In review" , "review done" etc and these statuses will form the "product owner" board (kanban board) and the moment the issue moves to final status status of PO board it will automatically appear in the scrum board backlog. 

The trick here is to have proper workflow statuses for both reviewing and then developing/testing and create board specific JQL filters which fetch issues meant for that board only. Rest everything will be taken care of by JIRA.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Agile

Join us LIVE: Atlassian & Experts Talk Research & Insights @ Scale

Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...

236 views 3 6
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