# Jira

## Introduction <a href="#h_01hr43g9x1hnvnrxbzqa3qsdjq" id="h_01hr43g9x1hnvnrxbzqa3qsdjq"></a>

You can automatically create tickets in Jira as a part of the following cases:

* Access Request has been approved
* Access Review has been denied

This functionality allows you to automatically create tickets to provision/de-provision resources based on the corresponding access request/review. Let us explore the steps to configure this on your tenant:

## Configure Jira Email Notification System: <a href="#h_01hr43gkmbr25jr2m35kt363bz" id="h_01hr43gkmbr25jr2m35kt363bz"></a>

### To configure in Jira <a href="#h_01hr43g4x52k5d6xfdhpz3zzk9" id="h_01hr43g4x52k5d6xfdhpz3zzk9"></a>

1. Go to *Jira* > *Settings* > *System* > *Mail* > *Incoming Mails*.<br>

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FJ7b3BmbuJM7AaDJnaR45%2Fimage.png?alt=media&#x26;token=797e3ea5-3905-4d44-bbd7-ff6ca6decf1f" alt="" width="375"><figcaption></figcaption></figure>

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FgrY2sbnWXzuUhZJZz8dr%2Fimage.png?alt=media&#x26;token=b0e4b9de-81ea-4bf6-8a33-1b51d73f6a89" alt=""><figcaption></figcaption></figure>
2. Go to **Mail Handlers**.
3. Click on **Add a incoming mail handler** to create a new mail handler with the following configurations:

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FZBDMIpEejZtswp4UUSKS%2Fimage.png?alt=media&#x26;token=0d82bb75-fbaa-4fbb-8bb4-90953d21fa92" alt=""><figcaption></figcaption></figure>

   1. Provide a name such as “*Email Notifications*” or something relevant to your use.
   2. Set your incoming mail server to the **Default Cloud Mail Server** available.
   3. Set the mail handler type to - **Create a new issue or add a comment to an existing issue**.
   4. Let your folder name be left blank blank (set to default) to let it scan the inbox. If your emails are directed to some other folder within your mail, you will be required to configure that in this field. Go to the **next page** after this.<br>

      <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FNJAgHnxn8fnTMHgHgfuf%2Fimage.png?alt=media&#x26;token=9ef1de07-fcc5-4701-be87-9fc167751383" alt="" width="375"><figcaption></figcaption></figure>
   5. Set a **Jira Service Management** project for your issues to be created. All issues created for this purpose will be redirected to this project.
   6. Set the type of issue you would like to have created for your purpose. (We consider provisioning/de-provisioning resources to be a task and hence we have set our issue type as a **Task**).
   7. Assign a **Default Reporter** for all the issues being created.
   8. You can assign a forward email for troubleshooting purposes.
   9. Save your configurations.<br>

      <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FLORZjO9CL2aQ9acU09IK%2Fimage.png?alt=media&#x26;token=88b54b27-b7ee-4031-a68b-271c37a0017d" alt="" width="375"><figcaption></figcaption></figure>

To understand more about mail handlers and mail servers inside Jira, refer to this document - <https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/>.

### To configure within your tenant <a href="#h_01hr43v8yte2q8z6gxgwnm345q" id="h_01hr43v8yte2q8z6gxgwnm345q"></a>

1. Go to Configure > Integrations on your BalkanID tenant.
2. Click on either *Add Integration* or *Edit Integration* for a particular integration<br>

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fxh88KcnjnevO79gJlxd9%2Fimage.png?alt=media&#x26;token=37ae79d5-899e-4fcf-822c-41aa25820241" alt=""><figcaption></figcaption></figure>

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2F4RLzFDzyv86Y36nRogci%2Fimage.png?alt=media&#x26;token=afdb2cd0-7de8-4f06-9d7b-2fa0a78b9d62" alt="" width="375"><figcaption></figcaption></figure>
3. Go to the *Optional Configuration* section.&#x20;
4. In **Fulfillment options,** choose **ticket creation**. It will open up a section below to select the ticketing system - Jira in this case. A text box will also appear to set the *Email Address*. <br>

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2F7zlBSBaC3FrEtm0TW7aZ%2Fimage.png?alt=media&#x26;token=14982814-38b8-40fe-bf04-1ad14f3bdc38" alt="" width="563"><figcaption></figcaption></figure>
5. Add the email corresponding to your jira default cloud mail server. ([jira@\<organization-name>.atlassian.net](mailto:jira@%3Corganization-name%3E.atlassian.ne)) You can find your jira default cloud mail server in jira as shown in the below image. Then hit *Save Changes* on the side panel. <br>

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2F3WCJqkQI4aoWs59P8PAn%2Fimage.png?alt=media&#x26;token=8f7dbdc2-9f81-4714-8967-ea9faae1e49a" alt=""><figcaption></figcaption></figure>
6. This is all the configuration you need to do on the tenant. Click on Save.

You can test your setup by denying access reviews on your tenant. After the campaign has been marked as **complete**, an email will be sent out and a ticket will be created in Jira within the project you configured for denied access reviews. It will resemble the one shown in the image given below:<br>

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FRhLWRItRfC5K2R4Mkc3z%2Fimage.png?alt=media&#x26;token=bd0e7973-943b-4f14-87ba-0d8870e053c6" alt=""><figcaption></figcaption></figure>

## Troubleshooting <a href="#h_01hr44ee9r6etkagqn611nmq27" id="h_01hr44ee9r6etkagqn611nmq27"></a>

In case things do not work, add an email as the forward email in the corresponding mail handler. All of jira’s debugging trails while trying to read the templated email will be forwarded to the email set in the forward email field.

<br>