I am looking for the ability to set a WIP limit per user, as my team has anywhere from 3-7 team members. I want to limit each person, not just the column. For example, if I want to set a WIP of 3 per person, I would set it to 21 if I have 7 people on the team, but if I only have 3, that could ultimately have 7 tasks. Is there any way to set it on a per user basis?
I would like the input on the below for a potential feature request.
AS a team member
I WANT jira to stop me from going above my defined WIP limit
SO that I can stop staring and start finalizing
Scenarios (in this case based on classes of services aka CoS)
GIVEN an attempt to assign an issue to a user
WHEN the issue is expedite and there is one current expedite issue assigned
THEN do not accept the assignment
WHEN the issue is non expedite (fixed delivery date, standard or intangible) and there are two current non expedite issues assigned
THEN do not accept the assignment
Note how the two WHEN can be expressed as JQL filter an operator and a count. Let us call them Personal WIP rules:
filter, operator, count
PWIP rule1: CoS = "expedite", <=, 1
PWIP rule2: Cos in ("fixed delivery date", "standard", "intangible"), <=, 2
These rules should be assigned to user roles.
Suppose some user (the originator) attempts to assign an issue to a another user or self (the target). The system will count the current tickets assigned based on the filter rules for the target user, will apply the filter rules for the current issue and if a filter condition is matched then the count will increase for that filter. The rule will evaluate and only if the user can accept the ticket the operation will be successful.
In fact the target user should not be even presented as a candidate to resolve the ticket. At a minimum, as stated above, the validation of the submission should fail. The result should be an error like "Could not perform this action. Personal WIP limit reached"
I'm sorry but the boards to not differenciate between swimlanes. The min and max for a column is for the entire column reguardless of how you divide it. Setting your max to 21 would allow 7 people to have 3 issues or 1 person to have 21 issues.
The only way you can control this that I am aware of is making individual Kanban boards for each employee and setting the WIP on each board.
If you want to see all work across the team you could use a Scrum board for the combined work of the team but that will only allow you to control the WIP for the team and not for each member.
I use a combination of both boards to acheive what you need. As the project manager and Scrum Master I run the Scrum board, make sprints, and deligate work in two week chunks across multiple projects. This allows me to control the WIP for all the teams. I then made indivdual Kanban boards for each team member that they can use to see only their work. This also allows me to control the WIP for each person. The boards are linked by a filter and assignee.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...challenges organisation’s experience in their efforts to adopt and scale agile. Many people associate agility with complete flexibility. And that’s not necessarily true, as demonstrated by this finding....
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs