| Redirect |
|---|
| delay | 3 |
|---|
| filename | |
|---|
| location | https://docs.meta-inf.hu/jeti-cloud/faq/email-this-issue-for-jira-cloud-how-to-configure-the-email-this-issue-addon-user-in-jira-cloud |
|---|
|
| Note |
|---|
|
are in the process of migrating our product documentation and soon we will not Please navigate to our new documentation site and update your bookmarks accordingly. If you're looking for the former content of this page, click here. |
Each Jira Cloud addon has its own user account created in the Jira Cloud systems where the addon is enabled. The Email This Issue addon user is called "Email This Issue" with username "addon_com.metainf.jira.plugin.emailissue".
The addon user must be properly configured to benefit from all features and expoit all potentials of Email This Issue for Jira Cloud. Find below the use cases that require special attention.
Send Ad-hoc Emails
In order to send issues in ad-hoc emails manually, the addon user must have at least read access to the issue.
- Add Browse Projects and Add Comments permissions to the addon user, hints:
- make sure the addon user is member of the project role "atlassian-addons-project-access"
- and grant Browser Projects, Add Comments for this project role in the permission scheme
- Add the addon user to all Issue Security levels either directly or via the addon project role (see above)
Send Emails to Individual Users and Groups
...
