Why connect bob with Jira?

bob-Jira integration is used to plan, track and manage projects with your bob HR data connected and synced to Jira. For example, when an employee is created, create a Jira ticket with a customized mapping of bob fields to Jira ticket fields. 

How Does It Work?

Based on your configuration, bob can create a ticket based on a number of events that take place in bob. Possible bob events to trigger sync include:

  • Employee joined
  • Employee created
  • Employee left
  • Workflow triggered 

Setting up Jira with bob

bob uses the Jira API. We recommend you create a dedicated Jira user account for bob, but if you prefer, you can also use an existing Jira user account.

To configure a Jira integration, please send us the following information:

  • Jira subdomain
  • Jira API token 
  • Jira project key
  • Jira issue type
  • Jira user email
  • Your desired field mapping

Don't know how to create a Jira API token? Follow this link for additional information.

Need more information about Jira issue types? See this link to find out.

Don't know how to determine your company's Jira subdomain? Follow these steps:

  1. Access Jira in your browser. Your URL should be something similar to: https://your_domain.atlassian.net/secure/BrowseProjects.jspa
  2. The Jira subdomain is your_domain.

Not sure how to determine your company's Jira project key? Just follow these steps:

  1. In Jira, go to Project Settings > Details
  2. The value in the Key field is your project key.

Required Permissions

The API token required by bob will have the same permissions as the Jira account that generated it. The permissions required by bob are those of a standard user account with access to Jira Software (placed in the jira-software-users group in the latest Jira cloud deployments) and, if using Jira Service Desk, access to Jira Service Desk (placed in the jira-service-desk-users group in the latest Jira cloud deployments).

If using a custom permission setup, make sure the user has the following:

  • Access to site
  • Access to Jira Software
  • Browse users and groups global permission
  • Browse projects project-level permission
  • Create issues project-level permission

If using Jira Service Desk, make sure that in addition to the permissions above, the user also has the following:

  • Access to Jira Service Desk
  • Permission to access the service desk
  • Permission to view the service desk
  • Permission to create requests in the specified service desk

For more information about how to grant the Browse users and groups permission, see the The Jira find users API returns empty results troubleshooting item.

See How to grant project-level permissions.

Jira API Usage

bob uses the following APIs to implement the Jira integration:

Need more information about user field mapping?

You define how bob employee fields are mapped to Jira ticket fields. See below (make sure the field names in bob and Jira match so the information maps correctly):

Troubleshooting

The Jira find users API returns empty results

This behavior can occur if the account used to generate the API token has been configured with access to Jira Software but is missing the Browse users and groups global permission.

To add Browse users and groups global permission, navigate to Jira Settings → System → Global permissions

In the bottom of the screen, select the Browse users and groups permission, then select the group containing the bob account and click Add.

Both Jira find users & create metadata APIs return empty results

This behavior can occur if the account used to generate the API token is missing site access. To grant the user site access, navigate to Jira User Management → Users and enable the Has access on site option.

That's it!

Need more help? If you're unsure about anything please send us a message through the chat icon below.

Did this answer your question?