Best practices in JIRA for managing both design and development

[Mike Kondrashin]

We are using Jira Cloud for our product. The complete product workflow involves many stages, but primarily:

1. Design and Specification

2. Development 

Each stage itself includes number of steps - in progress, in qa, in review, approved, etc.

This way, the designer would take item from the backlog, work on it through all the stages and once it's done - it will become a part of developer backlog. 

What is the best way to incorporate this in Jira? Please don't suggest using one board for everything, it will be huge! :D 

[Cristina]

Mike, did you ever solve this issue? I have the same question :) 

[Luis Felipe Inurritegui]

@mike, @Cristina - did any of you get to solve this requierement? I'm desperately looking for options and even considering a different tool.

[Rifat Anik]

@Mike Kondrashin @Luis Felipe Inurritegui @Cristina looking forward to solving this requirement for quite a while. Were you guys able to solve it? If not, how are you guys progressing the tasks? 

[Avigail Manheim]

It sounds like you want to create multiple boards for data in the same project. This can easily be done. First, create the new boards, naming each board appropriately (Design and Spec; Development; etc). Under board settings, change the names of the columns to match the steps you want to appear for that stage, and map the matching statuses to the columns. All statuses that you don't want to see on the board leave on the right as 'unmapped'. Optionally, you can edit the board filter to only include the desired statuses so that nothing is unmapped.

Note that this answer assumes that you've already created a workflow that has all of the steps (known in Jira as "statuses"). If not, step 0 is to create the workflow.