Assignee and State change
I have noticed a very annoying issue and I'm not sure of this is expected behavior (would be weird) or a bug.
When I move unresolved cards from a previous sprint to the current sprint it would sometimes change the assignee to myself and also sometimes set the state to New. I say ‘sometimes’ because I cannot determine a pattern and the Assignee and state change is not linked i.e. they don't always both change. This is very annoying because it makes sprint planning a nightmare for me.
Please sign in to leave a comment.
Hi Anton,
This is certainly not by-design behavior, but purely from our experience, a more likely culprit is a workflow rather than a product bug. Can you please check the workflows attached to the project to see if any of them might trigger the assignee and/or state change on a sprint move? Let us know if any help is needed with the review!
Hi Julia Bernikova
I have identified an action where the state defaults to New whenever a ticket is moved to the next sprint.
Example:
Ticket is put in On Hold state in the current sprint.
The ticket is not resolved in the current sprint and is move to the new sprint
The ticket state is reset to NEW
I've checked and there are not workflows that should trigger this.
Hi Anton,
We'd like to investigate this further - can you please submit a ticket us via https://youtrack-support.jetbrains.com/hc/en-us/requests/new?ticket_form_id=66282?