In my release cycle, testing time is long enough, that developer is starting to fix bugs that were found during QA testing. It's possible to have a task in two status, like "open" for developer and "In testing" for QA tester in parallel? What is best approach to have a best time tracking this?
No, it's not. An issue has a single status, it's nonsense to suggest otherwise (unless it's an issue in a quantum state, but that's not going to be understood by most humans).
One easy approach is to let the issue go into "in testing" and then raise sub-tasks for "I found this problem" - especially as a test cycle may raise more than one problem with it. Not sure if this is the best for you, but it could be a good answer based on what you've said here.
Agreed, testing usually results in findings, which are ideally best represented in individual issues, which will have their own status assigned to the developer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.