nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Question regarding Jira/Salesforce connector - Jira Issue component for Lightning Page

KrisjanisPunculis

We have question how Link to Jira instance is generated in Jira Issue component for Lightning Page.

Currently we have Jira/Salesforce connector installed and exposed the Jira Issue component to display in Lightning Page the main information. This component has clickable URL towards the Jira instace. However this URL differs between Production and Test Salesforce (and Jira) instances.

https://<production instance>/rest/api/3/issue/4732323

https://<test instance>/rest/api/3/issue/bulkfetch/908695

For test instance bulkfetch is added and Jira always returns "You found dead link"

Is there a way how we can control this link from Salesforce (or Jira side)?

Accepted answers

All comments

AaronPavez_Appfire

Hi @KrisjanisPunculis

A couple of things first, to better understand your use case:

1. The connector already has a Lightning component and a Visualforce component to show you the associated work items. With links you can click to get to them.

Why are you exposing something else and using the wrong URLs?

These APIs are Jira internal APIs. Nothing to do with the connector.

If you need a clickable link so you can open the associated work item, you need this URL,for example:

https://yourorghere.atlassian.net/browse/JIRA-1

The other one is the REST API to check the work item details.

Regards - Aaron

KrisjanisPunculis

Hello Aaron,

We are using the Jira Issues component that comes with the package. We haven't found the place were we can control the format of the URL (so this could be our oversight) - as in Lightning App Builder we can 1) place the component 2) control the visibility of component itself.

AaronPavez_Appfire

Can you send us a screenshot of the component and how it looks?

> We haven't found the place were we can control the format of the URL

Sadly, you can't. You cannot change anything in the Lightning component.

Regards - Aaron

KrisjanisPunculis

AaronPavez_Appfire

Thanks for the screenshot.

The link to JIRA-396 should be youratlassiansite.atlassian.net/browse/JIRA-396.

If it's something else, then it might be how you are creating the associations.

Are you doing it manually, or is it a trigger?

If this happens on all associations on all records, please open a support ticket with us here so we can take a deeper look:

https://appfire.atlassian.net/servicedesk/customer/portal/11

Regards - Aaron

Javier Pozuelo -Exalate-

Hi @KrisjanisPunculis I’m the Community Manager at Exalate.

As Aaron mentioned, the URLs you’re seeing (like /rest/api/3/issue/bulkfetch) are internal Jira API endpoints, which aren’t meant to be directly accessed via a clickable link. That’s why they result in a dead page.

If your goal is to provide a clickable link to the Jira issue from Salesforce, the recommended format would be something like:

https://yourdomain.atlassian.net/browse/ISSUE-KEY

This URL leads directly to the issue view in Jira and works reliably across environments.

If you’re using the Jira Issue Lightning component provided by your connector, it should already handle this linking logic for you. If it’s not behaving consistently between environments, I’d suggest checking:

Whether the Jira base URL is configured correctly in both test and production
If the component settings are identical across environments
Whether there are version differences in the connector between your test and production instances

If you eventually need more flexibility around how Jira and Salesforce are connected—like customizing exactly which fields show up, controlling URL structures, or syncing related data (e.g., comments, attachments, statuses)—there are other tools available on the Marketplace you might consider, such as:

Each option has different strengths depending on how tailored your setup needs to be.

Hope this helps!

KrisjanisPunculis

To return to this - the issue was with the wrong package for wrong setup and thus the issue arose. By using correct package (for Cloud or Server) the issue is reseloved

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud