If your team tracks work in Jira Cloud, you can connect it to NexerIQ so the two work together — customer issues show up where you need them, and (optionally) the time your team logs in Jira flows into NexerIQ work journals. This guide is the starting point: it covers connecting the two systems and setting up the customer field. Don't worry if you've never set up an integration before; we walk you through every step.

Before you start

• A Jira Cloud account with permission to manage your Jira site.
• Your Jira site address — it looks like https://yourcompany.atlassian.net.
• The email address of the Atlassian account NexerIQ will use to connect.
• An API token for that account (we'll create one in the next step).

Step 1 — Create your Atlassian API token

An API token is like a password that lets NexerIQ talk to Jira on your behalf. It belongs to your Atlassian account, not to one specific Jira site, so you create it once in your Atlassian profile.

1. Go to https://id.atlassian.com/manage-profile/security/api-tokens and sign in with the Atlassian account you want NexerIQ to use.
2. Click Create API token, give it a name you'll recognise later (for example, "NexerIQ"), and confirm.
3. Copy the token straight away and keep it somewhere safe — Atlassian only shows it once. If you lose it, just create a new one.

In NexerIQ, the API Token field has a Create token button that opens this same Atlassian page in a new tab, so you don't have to hunt for it.

Step 2 — Connect NexerIQ to Jira

1. In NexerIQ, open Settings and go to the Jira Integration page.
2. Tick Enable Jira Integration.
3. Fill in the Base URL (your Jira site address, such as https://yourcompany.atlassian.net), the Admin Email (the Atlassian account email), and paste your API Token.
4. Click Save.
5. Click Test Connection to confirm NexerIQ can reach Jira. A success message tells you it's connected; if something's wrong, it shows the exact reason so you can fix it.

Your API token is stored securely and shown only as dots after saving — you won't need to type it again unless you want to replace it. If Test Connection ever reports that the saved token couldn't be read, just paste a fresh API token and click Save again to restore the connection.

Step 3 — Set up the customer field

So NexerIQ can tell which Jira issue belongs to which customer, it uses a dedicated field in Jira.

1. In the Customer Field section, enter a Customer Field Name (for example, "NexerIQ Customer").
2. Click Auto-Inject Field into Jira. NexerIQ creates that field in your Jira site, switches on the indexing that lets it search by customer, and remembers the field for you — no manual Jira configuration needed.

Limiting to specific projects

By default NexerIQ looks across all your Jira projects. If you'd rather it only consider certain ones, use Limit to Project Keys under Project Scope and add the project keys you want (for example, SUP or OPS). Leave it empty to include every project.

Where to go next

With the connection and customer field in place, you can:

• Surface a customer's Jira issues inside NexerIQ and in their portal — see Jira issues in NexerIQ: the admin view and the customer portal.
• Turn the time your team logs in Jira into employee work journals — see Jira worklog time in NexerIQ: turn logged work into work journals.

Tip

Save before you test. The Test Connection and Auto-Inject buttons use the details you've entered — if you see "Jira is not configured", make sure you've filled in the Base URL, Admin Email, and API Token and clicked Save first. And remember the API token is tied to the Atlassian account, so the email you enter must be the same account that created the token.