For our software development team, we have multiple steps in the process carried out by different people. A bug fix may be developed by one person, tested by another, and deployed by a third. We have the workflow defined in Jira. However, when John finishes development he can remove himself as an assignee to keep the task open, but his work won't be tracked when we review productivity at the end of the sprint.
Welcome to the Atlassian Community!
That is not how sprints work. The point of a sprint is that the team selects some issues to deal with, and then delivers results.
It does not matter that several people might work on it, nor that which team member does any work on it.
You should be tracking team productivity, not individuals. "task open" means that the team has not finished. "task closed" means the team has.
Hello @Sean Haskins and welcome to the Community! This scenario is a typical use case for including sub-tasks in your Bugs/Stories. Have a look here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get the most out of Jira
Explore the interface and basic Jira terms, then discover how to effectively manage your work.
Learning Path
Atlassian tools and practices for developers
Focus on your development work by using Jira software features and functions efficiently.
Atlassian Certified Associate
Jira Software Essentials certification
Demonstrate proficiency in utilizing essential Jira features and working efficiently with Agile frameworks like Kanban and Scrum.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.