Coming from Asana: how to adapt our workflow

[Luis Novo]

Hi Folks, 

We currently run all our software development and processes in Asana, but now we are migrating to Jira and we are having trouble mapping our current workflow to what's possible in Jira. 

Let me explain the workflow in a simple example:

- We have an Asana project called Bugs

- We have 2 other projects for the backlogs of 2 different teams

In Asana, it's possible to have a task exist in more than one board. So the process we apply today is: 

- Anyone at the company can report a bug to the Bugs project

- That project has a bug verification workflow (Inbox, Verify, Fix, Confirm)

- So the bugs will go through this workflow until they are fixed

- When bugs enter the "Fix" lane, we also add another project (the backlog of the team that will fix the issue)

- This way, the bug exists in 2 boards. It exists in the Bugs board so we can track it centrally, but it also exists now in the team backlog. They are not duplicate tasks. It's the same task that lives in 2 projects. 

I know this is not possible in Jira. But I also figure that the community must have work-arounds for this. 

So can you share how you'd do it?

[Fabian Lim · Accepted solution]

Hi @Luis Novo

Welcome to jira.

I would recommend you create two new tasks for each board and then you can link them to the original bug ticket. The task would represent the work required by the team.

Now, you could use automation thought jira  automation or workflow post functions to move the central ticket to done status if both linked tasks are completed.

I hope this helps.