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

Sprints: Deactivated user should be removed from Sprints

    XMLWordPrintable

Details

    • Severity 2 - Major
    • X-Men - WT3
    • No

    Description

      Issue Summary

      Sprints: Deactivated user should be removed from Sprints

      Steps to Reproduce

      1. Login
      2. Go to the Administration>People.
      3. Deactivate any user that is assigned to Sprints in different States: Not Started, Planning, In Development, Completed. User should have some allocations. User should affect Existing financial reporting.
      4. Check if the User still appears in the Sprints and if he is still affecting financial reporting.

      Expected Results

      Deactivated users should be removed from any future team sprints with the state "Not Started" or "In Planning". (future sprints should be determine based on start date is future from today's date). If the sprint start date is today's date or already past, but the sprint is still in "not started" or "in planning", then keep them on the sprint. 

      If a user is deactivated, for any sprints already in "In Progress" or "Completed", keep them on the sprint member list, with a yellow icon next to them with hover-over "This user has been deactivated."

      If a user is deactivated and removed from the team list and any "not started" or "in planning" sprints, then reactivated, we will not auto-populate them back to the team or sprint list.  

       

      Actual Results

      Deactivated user is removed from team member list but not from any of the team sprints. 

      Workaround

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

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rpetrunyak@atlassian.com Roman Petrunyak (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync