Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
/
Using an inactive user with user creation enabled
Updated Feb 10, 2023

    Using an inactive user with user creation enabled

    • 1 Summary
    • 2 Email sender is the inactive user
      • 2.1 When Non-Jira users is setup
      • 2.2 Treat Unprivileged users as non-Jira is enabled
    • 3 Email participant is a inactive user
      • 3.1 Treat inactive participants as non-Jira

    Summary

    New users will not be created when JEMH finds a inactive user that has the same email address as the sender or participant. This is so that JEMH does not create multiple users with the same email address as this could cause potential issues within Jira. Inactive users can also impact how issues are created and how some features function within JEMH. Below is a couple of features and scenarios that inactive Users will impact.

    Email sender is the inactive user

    When Non-Jira users is setup

    When non-Jira users is enabled within the Profile it will result in the default reporter being used and the inactive user being treated as a non-Jira user. The sender email address will be added to the Custom Fields that are set for Non-Jira users.

    For more information about non-Jira users see: Supporting JIRA and email only users for email issue creationPreview

    Treat Unprivileged users as non-Jira is enabled

    When Treat Unprivileged users as non-Jira is enabled in Profile > Security and the sender relates to a inactive user it will result in the issue being created with the Default Reporter and a message being displayed within the report stating that the user is denied creation privilege.

    For more information about Treat unprivileged users as non-Jira see: Add JIRA users without project permission as non-JIRA usersPreview

    Email participant is a inactive user

    When a inactive user is added as participant, JEMH will not add the user to Jira User fields and will result in the following messages.

    Treat inactive participants as non-Jira

    If Treat Unprivileged users as non-Jira is enabled in Profile > Security it will result in the inactive user being added to issue as a non-Jira user and being added to the Custom Field that is configured for email only users. This will result in the message seen below:

    For more information about Treat unprivileged users as non-Jira see: Add JIRA users without project permission as non-JIRA usersPreview

    The Plugin People
    Teams
    , (opens new window)
    Knowledge Base
    • How-to articles
      How-to articles
       This trigger is hidden
    Results will update as you type.
    • How to change the event type of a notified event
    • Diagnose no inbound mail handled
    • JSD (Jira Service Desk) - Who is notified when?
    • HTML extraction method to Wiki mark up
    • Setting System Fields using Script Field Processor
    • Test case editor fails to load
    • MessageRemovedException in log files during email processing
    • Characters appearing as question marks
    • UI not visible after upgrading to version 3+
    • Default Project Mapping and unwanted inheritance causing inbound mail to be forwarded
    • JEMH is disabled on startup in Manage Apps
    • Configure JSD Customers for use with JEMH
    • Custom Field values are cached causing recipients to not receive notifications (JIRA 7.3.0 - 7.3.4 , JEMH 2.1.0 - 2.1.11)
    • Restrict commenting to one project
    • Foreign key constraint violation during Audit Event history purge
    • Request participants not sent JEMH notification
    • Handling out of disk space
    • Profile import timeout error
    • Zendesk integration
    • Outlook sending formatting
    • Attachment links added as comments, Jira Service Management/Desk
    • Incoming Auditing Actions Error Popup
    • Updating JEMH's issue event listener to listen for IssueEventBundle's (JEMH-6994)
    • Template Set Responsibility Devolution (JEMH-5403)
    • Support non-ascii characters in email addresses (JEMH-6431)
    • Custom Fields don't get added during creation phase causing creation notifications to not fire for User/Group field types. (JEMH-306)
    • Cant stop reporter being added as a watcher (JEMH-790)
    • Handle re-index failure during watcher setup (JEMH-7180)
    • Inline User Macros sometimes don't render (velocity 2.0 needed) (JEMH-5536)
    • "Stuck" emails in queues after post condition test (JEMH-5366)
    • Dealing with 'Undisclosed Recipients' (JEMH Server/DC)
    • Missing Methods in TemplateIssue Class since Jira 8.19.0
    • Why do FolderClosedException occur
    • Customer Permissions for Request Participants
    • User Anonymization Fails - SQL Server 2019
    • Maintaining JEMH Attachment Property Set values
    • Display Issue Notifications in Right To Left Languages
    • Jira Server/DC - when mail polling stops, fixing without a Jira restart
    • A3 BAD User is authenticated but not connected error message when using JIRA with Office365
    • JEMH not enabling on upgrade to Jira 8.13.x and 8.20.x LTS releases made after 23-MAY-2022
    • Using an inactive user with user creation enabled
    • Missing Created/Timestamp Columns Causing Problems
    • -1 Values for the "Comment count limit" and "Comment char length limit" in the Default Project-Mapping
      Calendars
    You‘re viewing this with anonymous access, so some content might be blocked.
    {"serverDuration": 9, "requestCorrelationId": "1a104a3cdd31453ebefd8734366e02e4"}