Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-6712

Capacity: The "Team allocation" value includes the allocations of deactivated users and users with removed roles

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.132.0
    • 10.128.2
    • Capacity
    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      Capacity: The "Team allocation" value includes the allocations of deactivated users and users with removed roles

      This is reproducible on Data Center: yes

      Steps to Reproduce

      Preconditions:

      • Portfolio > Program > Team should be created and associated wit Release
      • Assign several users to the Team
      • Allocate roles and set allocations for these users
      • Configure the Portfolio estimation system to use Member/Team Weeks. # Open the "Capacity Plan" page for Program and Release from preconditions.
      1. Select the "Team allocations" option in the Members column for the Team.
      2. Wait for the backoffice "CapacitySourceCalculation" task to run.
      3. Open the Team slideout and deactivate users or remove roles from those with existing allocations.
      4. Wait for the backoffice "CapacitySourceCalculation" task to run
      5. Open the "Capacity Plan" page for Program and Release from preconditions again.
      6. Confirm that "Team allocations" reflects updates, excluding deactivated users or users without roles assigned.|

      Expected Results

      Deactivated users or users without roles assigned should be excluded from the "Team allocation" value.

      Actual Results

      Allocations for deactivated users and users with removed roles are still included in the "Team allocations" value.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            9430c2193c41 Bhanu Vanjaku
            37857daa0c44 Mangala Narayana
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: