A bug issue is assigned to a developer. Later in the work flow, the issue is transition to In Test and reassigned to a Tester. This makes things very confusing. Is that the right way? Perhaps, after a bug issue is created, a requirement issue should be created to describe the fix to the bug and a subtask should be created under the requirement? What is the way that make the most sense? The bug issue shouldn't be passed between two people. By doing that we are using visibility Any articles that I can read about this?
The flow makes sense - an issue moves from person to person as the new person becomes the appropriate one to take over. It's not always the case, of course, but if Alice is the current assignee and Bob is the best person to do it, there's no reason to create another issue for Bob to take a look, just let him take over from Alice.
It doesn't reduce visibility or increase complexity in any way. Many people may well look at and work on the same bug.
It is worth keeping an eye on the reporter (person who raised it), and some processes benefit from having an "owner" which would change a lot less (Chuck owns the bug, but Alice, Bob and Chuck can all be the assignee when it's their responsibility to do something with it). An owner is easy to set up - just add a custom field for it.
There's nothing wrong with that. The assignee is dealing with the bug, that's what having an assignee is for.
If you need to report on types of work, you could simply look at the time it was assigned to each user and derive the type from that, or you could look at the work-logs, or if you really do want to split it up, create a sub-task for testing (and maybe development, and other stuff)
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot