Once a ticket is created under "requested" it will automatically assign to specific users in the project based on workload.
For this to be correctly balanced -- Jira should check the entire board excluding what has been "completed" or "approved" since these are both considered finished -- thus they shouldn't be accounted for.
Statuses that should be considered to balance workload correctly: Requested, More Details Needed, In Progress, Edits Needed, Ready For Review
The other caveat: depending on where the issue is in the workload -- it could be assigned to the creator (for review as an example). is this also able to take that into consideration?
I.e although the designer is the original assignee, it will be reassigned to the issue creator for the "ready for review" status. -- i don't want this rule to read this as X person doesn't have this ticket anymore, but rather X person still has this ticket although it's reassigned at this current moment.
I have included a screenshot of the rule as it currently stands but I don't think it is correct?
The balanced workload method will look at the tickets that are included in your selection (JQL), check who are the current assignee on those tickets and assign the ticket to the person who has the least assigned work in the selection at the time the rule runs. It is not capable of what may happen in the future, it will just consider the current workload across the team at that specific moment in time.
Based on what you describe, you could use the following JQL to narrow done to the statuses you say you want to be considered:
Project in ("Project A", "Project B") AND status in (Requested,
"More Details Needed", "In Progress", "Edits Needed", "Ready for Review")
I would add the project in part to make sure you are not including projects that your team is not working on.
Hope this helps!
Thanks so much Walter!! This was helpful and I've added it in! Appreciate your help.
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.