No, you can't have a workflow that have two statuses at the same time. It is against the principles of Jira, in my opinion.
You can use subtasks to seperate issues that you want to have different statuses.
Or you can create a custom field that will serve as an extra status.
But it is difficult to comment without knowing the main purpose of this.
Then, I think you need to use clone issue option. You can use components to differ your teams and when you clone the issue you can change the component of each issue to the related team. That would be the best option, I believe.
Well, they are still working on a single project. If reporting is what concerns you, you can use components to differ your reports. Also there is issue links, which indicates that your two issues (although two different teams are working on it) are related.
Also as I suggested above, using subtasks would be another solution. You can create one issue and distribute the issue to your teams on subtasks. You can design a workflow that when all the subtasks are closed, the main issue should be closed, etc. Which one to use, depends on what you are expecting from Jira. But you cannot have two statuses at once on an issue.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs