For one of our projects, we have the following behavior in place:
1. a sub-task is assigned to person A and it's not-started
2. the scrum master, person B, check status, and notices some sub-tasks were not updated and performs the changes by himself. When he moves the sub-tasks from not-started to in progress, the task gets assigned to the person who performs the change instead of leaving it to the person who was initially assigned to it (person A).
Is this the expected behavior? Can we change it so the assignee value remains the same irrespective of who moves it across the status?
Yes, you can change this. Your workflow must have been designed with this in mind, as it is an option that can be chosen.
In your workflow, likely on the Start Progress Transition, someone has applied the following post-function:
Removing this will not assign the issue when someone triggers the Start Progress transition.
When it was Greenhopper, there was a setting to do that, but I thought it was global, not tied to a project. You should check that. I don't have agile installed now.
I think it used to be an option, but I am not sure it is in Agile any more. It certainly isn't a board option. Perhaps if you use the simplified workflow? Not sure.
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events