I have a team of 4 developers and 1 QA. My workflow in Jira is:
Backlog -> Analysis -> In Development -> QA Ready -> QA Complete -> Done
Every sprint (1 week) all issues get into QA Ready stage (QA member is not finishing to test all features in one iteration), also issues don't get burnt until they reach Done stage (deploy). So I am not measuring the effective team work per sprint.
Is it recommendable (for a story) to raise an issue for devs and another issue for QAs, so in a sprint I can only include the issues that will be "Done"?
For this, I will have to change my workflow to:
To do -> In progress -> done
So this way, analysis issues, development issues and QA issues will have a shorter lifetime but they will be burnt and measure per iteration.
I don't like this solution, because there will be 3 times more issues.
The thing is that burndown-chart is not showing what the team is working, even when I defined to set resolution when the issue gets to QA ready stage.