Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-36973

Setting Personal WIP or WIP limits per user

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 12
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Hello JIRA team,

      I would like to propose an enhancement for JIRA that will IMO benefit all agile/lean teams out there.

      =========
      Narrative
      =========

      AS a team member

      I WANT jira to stop me from going above my defined WIP limit

      SO that I can stop starting and start finalizing

      ================================================
      Scenarios (examples 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

      ==========================================================
      Implementation proposal (applicable to any kind of scenarios including the above)
      ==========================================================

      Note how the two WHEN can be expressed as a JQL filter, an operator and a result 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 a candidate issue to 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 candidate issue and if a filter condition is matched then the count will increase for that filter. The rules will trigger and only if the user can accept the ticket the operation will be successful.

      In fact the target user should not even be 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"

      Thanks!

      • Nestor

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              206fe5f45714 Nestor Urquiza
              Votes:
              441 Vote for this issue
              Watchers:
              167 Start watching this issue

              Dates

                Created:
                Updated: