How to create multiple board under one project and have the same tickets assigned.

[Premnath Bakthavatchalam]

1) We have a Project setup with Backlogs. This is mainly for development and manual testing. Let's assume this as 'Board A'.

2) Now the team is in Sprint 3.

3) Automation Testing team is being introduced at this point to test whatever has been developed in Sprint 1 & 2 by the Dev team. Obviously, this will be Automation teams Sprint 1.

4) My question is, whether it is possible to have a separate board for Automation team as 'Board B' and have the same backlog tickets? Because, some tickets will be active in the current sprint, will that be of any problem?

5) Can anyone guide me how to proceed on this? I guess other work around would be to create a separate Project and have a board in it. But, if we can have it in the same board, it would be very helpful.

Thanks in advance.

Premnath

[Bill Sheboy]

Hi @Premnath Bakthavatchalam  -- Welcome to the Atlassian Community!

Let's pause to understand how your teams work before solving the JIRA boards question...

You note a team doing dev and manual testing, and a separate team doing automation testing.  Both teams appear to be using scrum.  Sometimes the dev/manual test team finishes the sprint's work before automation testing occurs.  Sometimes they happen in the same time interval.

One way to solve this would be to use smaller pieces of work that completely fit in a sprint, so dev, manual testing, and automation testing can start and finish in one sprint.  So, the teams would only use one JIRA board.  Further still, the teams might consider using a Kanban board to span the full workflow.

If it is more likely that dev/manual testing will complete and time will pass before automation testing occurs, consider these as two distinct pieces of work for two different sprints.  So there would be two boards to manage it.  Specifically, when a dev/manual test item completes (done) there is now a new work item for automation testing.  You could create the new item manually, or clone the done item, and then the automation team would use it.

To reduce confusion, consider using Components or Labels to specifically indicate on the JIRA issues which type of work is relevant: Dev/Manual Test vs Automation Test.

Best regards,

Bill