Configure Gmail IMAP Mail Servers with Multi-factor Authentication in Jira

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.


Jira Work Management and Jira Software can receive emails from licensed users to create issues or add comments and attachments automatically. This can be achieved by using the POP/IMAP Mail servers configured within the 'Incoming Mail' settings of Jira.

Most of the organizations currently include multifactor authentication to add an extra layer of security to the user account. But Jira only accepts username and password to authenticate to the IMAP mail server. Thus, rendering the accounts with the multifactor authentication enabled, throw errors while configuring. This can be prevented by using Gmail App-specific Passcode instead of the account password during the IMAP Mail server configuration.


JIRA only accepts the basic authentication method to communicate with the mail server. Leaving no way to produce the second passcode to the IMAP Mail server.


Enable App-specific Passcode

  1. Log in to the Gmail IMAP account

  2. Click on the user avatar in the right-hand top corner

  3. Select Google account.

  4. In the new tab that opens, select  Security > Signing into Google

  5. Select App Password

  6. In the new screen created, authenticate yourself

  7. In the next screen select app: Mail and Select Device: Custom
  8. Copy the 16 Digit app passcode and keep it handy for the future use.

Configure the IMAP mail server in Jira

  1. Select  the Jira icon ( or )  >  Jira settings > System > Incoming Mail
  2. Add POP / IMAP Mail server
  3. Fill in the required details:
    • Service Provider: GMAIL apps Mail / GMAIL IMAP
    • Username: Email address of the IMAP mail server
    • Password: Provide the 16 Digit app passcode obtained from the previous step.

Sign in using App Passwords

Last modified on Apr 26, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.