Skip to main content

​
Overview

The Jira integration connects your Jira Cloud site to G360 and syncs delivery data for reporting and analytics. Setup takes about 15 minutes and has four steps:
  1. API token: create an Atlassian API token for the account G360 signs in as.
  2. Connection: add the Jira site and credentials in G360.
  3. Data scopes: choose the Jira boards to sync.
  4. Project: create a Work Management project that schedules the sync.
After the first sync, the Jira delivery dashboard fills with data.

​
Prerequisites

Before you start, make sure you have:
  • G360 admin access, so you can open Integration and Projects and add connections.
  • A Jira Cloud site, for example https://your-company.atlassian.net.
  • A Jira user account for G360 to sign in as. Use a dedicated service account, for example g360-sync@your-company.com, rather than a personal one. The sync then keeps working when people change roles or leave.

​
Required Jira permissions

G360 sees only what this account can see. The account needs these permissions:
Before you start, sign in to Jira as the service account and open each board you plan to sync. If the account can’t open a board, G360 can’t sync it either.

​
Step 1: Create an Atlassian API token

G360 signs in to Jira with the account’s email address and an API token. Create a classic API token, using the plain Create API token option. A classic token acts with the permissions of the account that created it, which is what G360 expects.
Don’t use Create API token with scopes. Scoped tokens fail with 403 Forbidden.
1

Sign in as the service account

Sign in to Atlassian as the service account, not as yourself. The token belongs to whoever is signed in, and G360 sees exactly what that account can see.
2

Open the API tokens page

Go to id.atlassian.com/manage-profile/security/api-tokens.Alternatively, in Jira, click your avatar → Manage account → Security tab → Create and manage API tokens.
3

Create the token

Click Create API token, then fill in the dialog:
  • Name: a name that says what the token is for, for example G360 integration.
  • Expires on: an expiry date. Atlassian allows 1 to 365 days. Choose the longest your security policy allows, and set a calendar reminder to rotate the token before that date.
Click Create.
4

Copy the token

Click Copy. Paste the token into a password manager, or straight into G360 in Step 2.Your token is a long string like this:
Atlassian shows the token only once. If you lose it, revoke it and create a new one.
When the token expires, syncs start failing with a 401 Unauthorized error. Create a new token as described above. Then edit the Jira connection in G360 and paste the new token into API Token.

​
Step 2: Add the Jira connection in G360

1

Open the Jira integration

In G360, open Integration from the left menu. In the Work Management section, click Jira.
2

Add a new connection

Add a new connection. The Manage Connections: Jira form opens.
3

Enter connection details

4

Test the connection

Click Test Connection. A success message means G360 reached Jira with these credentials. If the test fails, see Troubleshooting.
5

Save the connection

Click Save Connection. The new connection appears in the Jira connections list.

​
Common Endpoint URL mistakes

A trailing slash is optional. G360 adds it for you.

​
Step 3: Add data scopes

A data scope is a Jira board. G360 syncs only the issues on the boards you add. Adding a board brings in the issues that the board’s filter shows, plus their sprints and releases.
Pick boards, not projects. If a project has no board, create one in Jira first (project → Board → Create board), or ask your Jira admin which board your team uses.

​
Add the boards

1

Open the connection

Open the Jira connection you created in Step 2.
2

Add a data scope

In the Data Scopes table, click Add Data Scope.
3

Select boards

Search for boards by name, for example Payments, or browse the full list. Select every board you want to report on, for example:
4

Save

Save your selection. The boards appear in the Data Scopes table.
To stop syncing a board, use Delete Data Scope. G360 keeps data it already synced.

​
Create and associate a scope config

A scope config tells G360 how to read your Jira fields. For example, it sets which custom field holds story points and how your issue types map to G360’s work types. Without a scope config, the board still syncs. However, story-point metrics stay empty, and the dashboard shows a Scope Configuration Required warning.
1

Create a scope config

On the connection, create a scope config and fill in the fields below. Leave a field blank if you don’t use it.
2

Associate the scope config

In the Data Scopes table, select the boards and click Associate Scope Config. One scope config can serve many boards.

​
Find a custom field ID

To find the ID of a custom field, such as story points:
  1. In Jira, go to Settings (gear icon) → Issues → Custom fields.
  2. Search for the field, for example Story Points or Story point estimate.
  3. Click ⋯ → Edit details (or View field information). The URL ends in id=10016, so the field ID is customfield_10016.
Team-managed (next-gen) projects often use Story point estimate, while company-managed projects use Story Points. These are different fields with different IDs. If your boards mix both, create two scope configs.

​
Step 4: Sync the data and view metrics

​
Create a Work Management project

Syncs run on a schedule that belongs to a G360 project. For more on projects, see Projects.
1

Add a project

Open Projects from the left menu and click Add Project.
2

Enter project details

Enter a Project Name, for example Acme Delivery, and select the type Work Management Project.
3

Add the Jira data source

Under Data Sources, click Add Data Source and select the Jira connection from Step 2. Its boards come with it.
4

Set the sync behavior

Under Sync Behavior, set:The page shows the next three runs so you can check the schedule.
5

Create the project

Click Create Project. The first sync starts immediately, then runs on the schedule.
The first sync takes from a few minutes for a single small board to an hour or more for several large boards with years of history. Later syncs are incremental and much faster.

​
Check the sync status

  • Projects list: each project shows its Last Sync time and status (Succeeded or Failed). The KPI cards at the top count succeeded and failed projects.
  • Sync now: to sync immediately instead of waiting for the schedule, open the project (View) and click Run Sync Now. The button shows Syncing… while the sync runs.

​
What G360 collects

G360 also classifies each issue into a work category, such as new feature, defect, or maintenance. This classification drives the effort allocation views.

​
View the metrics

Open Jira from the left menu, under Work Management. Use the Team, Sprint, and Release filters at the top to narrow every tab. For metric definitions, see Jira metrics. If the dashboard shows Jira Connection Required, no Jira connection with a synced board is linked yet. Go back to Step 2 through Step 4.

​
Troubleshooting

Likely cause: wrong email, a wrong or expired token, or a token created by a different account.Fix: check that Username (Email) is the account that created the token. Create a new classic token (Step 1) and paste it again.
Likely cause: the account has no Jira product access, or the token is a scoped token.Fix: give the account Jira access. Use a classic token, not Create API token with scopes.
Likely cause: the Endpoint URL points to a page, not the site root.Fix: use only https://<site>.atlassian.net. See Common Endpoint URL mistakes.
Likely cause: a network or proxy issue.Fix: check that G360 can reach *.atlassian.net. Fill in Proxy if your network needs one.
Likely cause: the account can’t see the board or its filter, or the project has no board.Fix: share the board’s filter with the account, or create a board for the project.
Likely cause: the board’s filter excludes them, they’re outside the Time Range, or the account can’t browse that project.Fix: check the board filter in Jira, widen the project’s Time Range, and grant Browse Projects.
Likely cause: no scope config, or the wrong Story Point Field.Fix: set the correct field ID (Create and associate a scope config), associate the config with the board, then run a sync.
Likely cause: the board is Kanban, or there are no sprints in the time range.Fix: use a Scrum board for sprint metrics.
Likely cause: issues don’t use Fix versions.Fix: set fix versions on issues in Jira.
Likely cause: Jira rate limiting.Fix: turn on Custom Rate Limit, for example 3000 per hour, or schedule syncs outside working hours.
Likely cause: the API token expired.Fix: create a new token (Step 1) and update the connection.
Likely cause: the account can’t read groups.Fix: grant Browse users and groups.

​
Best practices

  • Use a dedicated service account for the token, and give it read access only to the projects you report on.
  • Rotate the token before it expires, and update the connection the same day.
  • Sync only the boards you report on. Fewer boards means faster syncs and less load on Jira.
  • Set up a scope config before the first sync, so story points and type mappings are right from day one.
  • Schedule daily syncs outside working hours, so G360 doesn’t compete with your team for Jira’s rate limit.