Welcome to the Atlassian Community!
No, there's no way to do this. You can't put issues into a quantum state where they are done and not done at the same time.
What I would do here is admit that you're not remotely doing Scrum (albeit you might still be quite Agile) and split the process because you've effectively got two teams doing the work, rather than a single cross-functional one that Scrum wants, even if your organisational structure defines the people as belonging to one team.
When you have two or more teams, the most effective thing to do is have each team use a different board. This way, each team can be very scrum-like and you don't need to mess with zero estimates or split ones.
Imagine a simple workflow with the hope that an issue can just go straight through it (going back in the flow and having lots more status, or boards with more than three columns are a diversion here, it's the status and column mapping principles that matter)
New -> In dev -> Dev done -> In test -> Finished
Your test team should have a board that lists columns:
- To-do: Dev-done
- In-progress: In-test
- Done: Finished
Your dev team is a little more complex, they need
- To-do: New
- In-progress: In-dev
- Done: Dev-done, In-test, and Finished
The basic idea here is that "one team's 'done' is another team's 'to do'". This method is not truly scrum, because it has many definitions of done and you don't have teams that can deliver something alone, but it does make your teams pretty close, and gives you all the reporting by team and story that you need.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.