HomeDocumentationAPI Reference
Getting StartedAPI ReferenceBug ReportingCrash ReportingAPMHelp Center

Jira Server

Jira Server

  1. Insert your username, password, and URL.

  1. Pick the project you want to forward to as well as the assignee. Fields can be mapped from Instabug to Jira fields. You can also choose which information is forwarded from your Instabug dashboard to Jira.

  1. At this point, we just need to test your integration so that we're sure everything is working smoothly.

  1. All done! Your integration is now set up and ready to go. From this final page, you can allow automatic forwarding (don't worry, though, these can be reconfigured at any time!)

  2. Start receiving issues on the spot on your Jira dashboard.

With this integration, bugs and feedback can be converted manually into issues on Jira with just a click.

Mapping Custom Fields

This section covers how to map Jira custom fields to fields from the Instabug dashboard.

  1. Create the custom field on Jira

  1. Choose a type for the field you've created in the previous step.

  1. Reconfigure your Jira integration.

  1. Map the Jira custom fields to the corresponding Instabug fields (make sure they have the same type).

  1. Test your integration.

  1. All done!

PAT Tokens

PAT stands for Personal Access Token. Use the PAT token, generated from Jira Server, to add a layer of authentication on Instabug ↔︎ Jira Server integration.

Using a PAT token is more secure than authenticating an integration with a username and password.

Setup steps

  1. Navigate to your Instabug dashboard.

  2. Navigate to your app’s Settings page.

  3. Navigate to the Integrations tab.

  4. Launch a new Jira Server integration wizard.

  5. Toggle from Basic Authentication to PAT Token

  6. Enter your PAT Token and Jira Site URL.

  1. Navigate to this link to create a PAT Token on Jira.
  2. Copy the created PAT Token to the PAT Token field on Instabug’s wizard.
  3. Continue setting up the integration normally.

Limitations

Token Expiry:

  • The token expiry date is controlled from the Jira side, not from Instabug.
  • If a token is created with a specific expiry date, it must be updated on Instabug’s dashboard before expiry, otherwise, there is a risk of not forwarding some data between Instabug and Jira during the period of non-validity of the PAT Token provided until it’s updated.

Editing Current Integrations

Currently, editing already existing integrations is not supported so a new one will need to be created.