Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-24937

When a user is deleted in AD or Crowd, JIRA could keep the user in JIRA as an inactive user

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      This issue supercedes CWD-2515. I have had a chat with Olli Nevalainen and we agreed that this is a good improvement request for the behavior of JIRA when a user is deleted from the AD side or from Crowd.

      Currently, the user would disappear from the JIRA user browser and will show up in gray color in the issues when he is the assignee of reporter. However, this may cause problems later on. I have witnessed one problem of it when retrieving SOAP remote issues which their assignee/reporter does not exist in JIRA due to him/her being deleted from LDAP/Crowd side. There may be more hidden problems about it.

      Deleting a user who matches any of this criteria was never possible from the UI:

      1. Assignee of any issue
      2. Reporter of any issue
      3. Lead of any project

      Thus, I have raised this improvement request to keep the user in JIRA even after being deleted from the external user management system, but as an inactive user (he/she will not be able to log-in anyway).

      Regards,
      Ali

        1. D3904554-8F1C-8F48-9B44-FF092AD4E845(2)
          7 kB
        2. D3904554-8F1C-8F48-9B44-FF092AD4E845(2)
          7 kB
        3. D3904554-8F1C-8F48-9B44-FF092AD4E845(2)
          7 kB
        4. D3904554-8F1C-8F48-9B44-FF092AD4E845(2)
          7 kB
        5. D3904554-8F1C-8F48-9B44-FF092AD4E845(2)
          7 kB
        6. D3904554-8F1C-8F48-9B44-FF092AD4E845(2)
          7 kB
        7. JRA-24937.patch
          1 kB

            [JRACLOUD-24937] When a user is deleted in AD or Crowd, JIRA could keep the user in JIRA as an inactive user

            Tulsi made changes -
            Assignee Original: Tulsi [ a82fc827eb8d ]
            Tulsi made changes -
            Assignee Original: Mark Lassau [ mlassau ] New: Tulsi [ a82fc827eb8d ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3155699 ] New: JAC Suggestion Workflow 3 [ 3656786 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2328939 ] New: JAC Suggestion Workflow [ 3155699 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2098893 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2328939 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2061764 ] New: JIRA Bug Workflow w Kanban v6 [ 2098893 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 1865829 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2061764 ]
            jonah (Inactive) made changes -
            Description Original: This issue supercedes CWD-2515. I have had a chat with Olli Nevalainen and we agreed that this is a good improvement request for the behavior of JIRA when a user is deleted from the AD side or from Crowd.

            Currently, the user would disappear from the JIRA user browser and will show up in gray color in the issues when he is the assignee of reporter. However, this may cause problems later on. I have witnessed one problem of it when retrieving SOAP remote issues which their assignee/reporter does not exist in JIRA due to him/her being deleted from LDAP/Crowd side. There may be more hidden problems about it.

            Deleting a user who matches any of this criteria was never possible from the UI:
            # Assignee of any issue
            # Reporter of any issue
            # Lead of any project

            Thus, I have raised this improvement request to keep the user in JIRA even after being deleted from the external user management system, but as an inactive user (he/she will not be able to log-in anyway).

            Regards,
            Ali             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-24937].
              {panel}

            This issue supercedes CWD-2515. I have had a chat with Olli Nevalainen and we agreed that this is a good improvement request for the behavior of JIRA when a user is deleted from the AD side or from Crowd.

            Currently, the user would disappear from the JIRA user browser and will show up in gray color in the issues when he is the assignee of reporter. However, this may cause problems later on. I have witnessed one problem of it when retrieving SOAP remote issues which their assignee/reporter does not exist in JIRA due to him/her being deleted from LDAP/Crowd side. There may be more hidden problems about it.

            Deleting a user who matches any of this criteria was never possible from the UI:
            # Assignee of any issue
            # Reporter of any issue
            # Lead of any project

            Thus, I have raised this improvement request to keep the user in JIRA even after being deleted from the external user management system, but as an inactive user (he/she will not be able to log-in anyway).

            Regards,
            Ali
            jonah (Inactive) made changes -
            Link New: This issue is related to JRASERVER-24937 [ JRASERVER-24937 ]
            vkharisma made changes -
            Project Import New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ]

              Unassigned Unassigned
              ajawad Ali Mohamed Jawad [Atlassian]
              Votes:
              68 Vote for this issue
              Watchers:
              72 Start watching this issue

                Created:
                Updated:
                Resolved: