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

Toggle between fallback to Default Reporter or preventing issue creation for emails from users with no create issue permission

    XMLWordPrintable

Details

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

    Description

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

      Problem Definition

      When the mail handler picks up an email whose sender is from a JIRA user account, that does not have Create Issue permissions in said project, it will throw an error and no issue is created:

      WARN [Test] atlassian-scheduler-quartz1.clustered_Worker-2 ServiceRunner    Test Test[10000]: Reporter (test) does not have permission to create an issue. Message rejected.

      This error obviously makes sense because the user does not have permissions to create issues. But we should allow the option to fall back to using the Default Reporter configured in the mail handler, so theres still an option of creating issues here.
      Technically, the user doesn't have permission to create issues directly in JIRA, but at least have the option of doing it through mail.

      Suggested Solution

      A Toggle functionality in the mail handler to choose between:

      1. Ignore default reporter and prevent issue creation if email is from a user with no Create Issue permission.
      2. Allow issue to use default reporter and be created in JIRA.

      Workaround

      "Trick" jira into thinking these users are anonymous users, (so it will fall back to Default Reporter), e.g. by changing their email addresses in JIRA to a different email. This of course has implications e.g. no notifications can then reach these users.

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-30521 Use the Default Reporter configured in the mail handler when creating an issue from email, if the email sender already existed in JIRA and do not have the permission to create issues

          • Closed

          Suggestion - JRASERVER-62399 Allow mail to be created as JIRA issues under Default Reporter when sender granted Confluence application access only

          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-33116 Mail handler incorrectly matches inactive or deleted users email address when creating an issue

          • Low - Low priority issues
          • Closed

          Suggestion - JRACLOUD-46212 Toggle between fallback to Default Reporter or preventing issue creation for emails from users with no create issue permission

          • Closed

          Suggestion - JRASERVER-60805 Change Default Reporter field description to include how it works

          • Closed

          Activity

            People

              Unassigned Unassigned
              dleng Daniel Leng (Inactive)
              Votes:
              26 Vote for this issue
              Watchers:
              23 Start watching this issue

              Dates

                Created:
                Updated: