Skip to main content

Common problems with Jira

When you add the integration​

What you seeWhat to do
jira.example.com refused the credentials (401). Check the token, and that it has not expired.Create a new token (Data Center, Cloud) and paste it as is. For Jira Cloud, check the E-mail: it must be the one of the account that owns the token.
jira.example.com accepted the token but refuses access (403). Give the token the rights described in the « ? » of the field.The token's account cannot use Jira. Log in to Jira with this account: it must see your projects.
This address is a Jira Cloud one (.atlassian.net). Use the Jira Cloud integration for it.Your Jira is a Jira Cloud: use the Jira Cloud card.
This address is not a Jira Cloud one (they end in .atlassian.net). For your company's own Jira, use the Jira Data Center integration.Your Jira is your company's own: use the Jira Data Center card.
No server answers to the name jira.example.com. Check its spelling against the address you open in your browser. If it is right, Astrolabe cannot see this server: tell your company's Astrolabe administrator.Copy the address from your browser into the URL field, without path.

In My Account, or when you connect your account in a card​

What you seeWhat to do
example.atlassian.net refused your token (401). Check it, and that it has not expired.Create a new token of your own and paste it as is: see Add your Jira issues to your dashboard.

On a component or your dashboard​

What you seeWhat to do
No Jira tab on a componentAdd the jira/project-key annotation, and turn on Enable Jira in Administration › Plugins: see Show the Jira tab.
The tab says The project SHOP does not exist, or the token account cannot see it. Check the jira/project-key annotation of the component.The key written in jira/project-key is not a Jira project, or the account of the token cannot open it. Compare the annotation with the key of the project in Jira, then check that the token's account can open the project.
The tab says No open issue in SHOP. while the project has open issuesCompare the annotation with the prefix of the project's issues, then check that the token's account can open the project in Jira.
A card says Your Jira account is not connected.Click Connect my Jira account in the card: see Connect your Jira account.
The jira source is missing from Add a cardJira is not connected yet: ask your Astrolabe administrator.
Nothing here yet and No open Jira issue is assigned to you. on My Open IssuesYour Jira account has no open issue assigned to it. Nothing to fix: the card fills as soon as there is one.
Nothing here yet and No Jira issue is waiting for your approval. on To ReviewNothing to fix: the card fills as soon as an issue waits for your approval.
Nothing here yet and Your JQL query returns no issue. Check the query. on JQL QueryOpen the card menu, click Edit, and correct the query in the jql field.
Showing the first 1000 issues: Jira holds more. Narrow the query to see the rest. above the table of a Jira cardThe query matches more than 1000 issues. Narrow it in the jql field: add a condition, for example AND statusCategory != Done.
A JQL Query card says Jira answered with an error it did not explain. Check the host and the API address in Administration › Company connections › Jira. If they are right, Jira itself is in trouble: try again later.Check the query first: on My Dashboards, open the more menu of the card, Edit, and read the jql field. Try the same query in Jira's own issue search: it must run there.

Not verified on an instance yet: the message about a project that does not exist, no Jira is connected to the test instance.

When the tab says a module is missing​

What you seeWhat to do
Astrolabe does not offer this Jira feature on this instance. and A module is missing from this Astrolabe installation. Tell your Astrolabe administrator.The integration may be connected and the plugin on, but this installation of Astrolabe lacks the module that serves Jira. Tell your Astrolabe administrator. Nothing to change on the component.

Not verified on an instance yet: this message needs an installation that lacks the module.

Still stuck?

Write to support@forgeit.fr with the name of the component and the message you see.