Optimise handover of design to development

[Tejasv Garg]

Hey, I have recently started using Jira, and I noticed that our team uses only one board for development and design. It's a small team so it's somehow working, I want to optimize it by having separate boards for design and development. How do I ensure that issues shifted to Done on the design board get cloned to TO-DO on the development board and that it's assigned to me? I want to automate it. Kindly provide detailed step instructions to do that. 

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Take a step back, there's something you should know before you try to do this.

Boards are not containers of issues, they are a view of a selection.  (Projects contain issues).  Issues do not "move from one board to another".  When they appear to, it is because the boards have different selection criteria.

Imagine you've got two teams - Dev and Design, and you want them to have their own boards (not a bad idea - boards are actually supposed to represent and manage a team's work)

At the moment, you've got one board that just says "Project = XYZ", so everyone sees all the issues in project XYZ.  I would create two others:

• Dev board: "Project = XYZ and Assignee in (Alice, Bob, You)" - Alice and Bob are your developers.
• Design board: "Project = XYZ and Assignee in (Charlie, Dave, You)" - Charlie and Dave are your designers.
• And the team as a whole still has the original board to work from.  As they are views of data, changes made from any board will show in the others (although you will have to refresh to see them)

Of course, you can run this off whatever criteria you want to assign your teams (a team-select field, labels, separate projects, etc)

I think you should run this off "status" though.

Imagine a workflow of:

To-do -> in-design -> ready-for-dev -> in-dev -> done

Create both boards with just "Project = XYZ", and use the column mappings to define the process.

• The dev board is easy:
  • To-do: ready-for-dev
  • In-progress: in-dev
  • Done: done
  • Leave the other status unmapped
• The design board has a slight twist:
  • To-do: to-do
  • In-progress: in-design
  • Done: ready-for-dev, in-dev, done

The design board is seeing all the post-design status as done - if you don't include them, they will reappear in the backlog!

[Jeroen Poismans]

Hi and welcome!

Why the choice of creating an new issue?

Instead of creating a new issue why not transfer, progress the issue from design to development using your workflow. That way all info, history ... concerning the realisation stays on 1 issue. You would also not have to worry about cloning and automation since you can just create a new board covering different statuses in the flow of the issue.

Hope this helps?

Jeroen