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

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

XMLWordPrintable

    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

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

            Emanuel Y added a comment -

            Any plans for Jira Cloud ?

            Emanuel Y added a comment - Any plans for Jira Cloud ?
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3061939 ] New: JAC Suggestion Workflow 3 [ 3692151 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Link New: This issue is related to CONFSERVER-58751 [ CONFSERVER-58751 ]
            Tomasz Kanafa made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 411715 ]
            Tomasz Kanafa made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 409891 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2600235 ] New: JAC Suggestion Workflow [ 3061939 ]
            Michael Perez made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-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             		New: {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-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
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2585864 ] New: Confluence Workflow - Public Facing v4 [ 2600235 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361879 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2585864 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2129507 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361879 ]

              mlassau Mark Lassau (Inactive)
              ajawad Ali Mohamed Jawad [Atlassian]
              Votes:
              68 Vote for this issue
              Watchers:
              83 Start watching this issue

                Created:
                Updated:
                Resolved: