nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Do project specific email addresses within JIRA need to be accounts or aliases?

Marion Dunn

When setting up the email configuration for JIRA, I am using an email account for the default account, but cannot find any documentation as to whether project specific emails need to be accounts also, or whether they are aliases that have "send as" permissions for the default account. We are using JIRA full download and externally hosted Exchange for email.

Accepted answers

Rahul Aich [Nagra]

They can be aliases. We have lot of jira projects where in the default component assignee is the alias and that way a pool of developers assigned to that component can pick issues up and action.

Rahul

All comments

Rahul Aich [Nagra]

They can be aliases. We have lot of jira projects where in the default component assignee is the alias and that way a pool of developers assigned to that component can pick issues up and action.

Rahul

Marion Dunn

Thanks Rahul. Does the default account have to have "send as" permissions for this to work? Or does that come down to your mail server setup, rather than something specific in JIRA?

Rahul Aich [Nagra]

No, we have configured it at mail server level not jira level.

Rahul

Renjith Pillai

Usually the point of having project specific emalis is to enable load distribution for incoming mails to JIRA and also to enable creation of issues in the right projects. I didnt quite get what you meant by 'email aliasing'? All project specific accounts are created as Incoming mailboxes to enable automatic comment creation.

Marion Dunn

Thanks Renjith. By aliases, I mean that the email address does not have it's own account, rather that it's an address that gets sent to multiple users.