Whether you're running into a problem during set-up or while importing issues into Panobi, find and click on your problem in the table below to learn how to resolve it.
💡 Don't forget to check Jira's status page to make sure the issue isn't due to a service interruption.
Issue | Description |
After you've authenticated and are just beginning to set up your Jira integration, you see unexpected field mappings in your settings. | |
When configuring your field mappings, you're not seeing all of the expected field options in a dropdown. | |
When importing from Jira, you aren't seeing an expected issue in the dropdown list of selections to import. | |
When importing from Jira, you're able to create the project but expected content or fields aren't there. | |
Jira information imports successfully but some formatting details get lost along the way. |
There are already field mappings in place that you didn't expect
If you're embarking on configuring your Jira integration, but you see unexpected field mappings in your settings — never fear! There's a reason for this, and you have the power to change anything you need to change.
If anyone else in your Panobi workspace was the first to authenticate and configure the Jira integration, Panobi will apply their field mappings to your integration settings. This is simply to save you the trouble of setting up each mapping.
Pre-filled mappings not quite right? Feel free to re-map the fields by making different selections from the dropdowns, or remove the mapping altogether by clicking the X to the right of the row. You can also add more mappings of your own choosing. Any changes you make to configuration settings will only affect your own settings.
You're not seeing a corresponding Panobi field for mapping one of your Jira fields
If you're configuring field mapping in your Settings and you don't see an expected Panobi field in the dropdown for one of your mappings, there might be a good reason for that:
Incompatible data types
It's not possible to map any Jira field to any Panobi field, because the data types need to be compatible. Date fields in Jira are mappable to start and end date in Panobi. Jira fields with numeric data are mappable to custom fields in Panobi that require some form of numeric data.
The exception to this rule is that anything in Jira can be mapped to a Panobi text field, like Description. The Description field is a handy catch-all because multiple Jira fields can all be mapped to it simultaneously.
You're not able to find the Jira issue you'd like to import
Issue gone missing in the dropdown of issues to import? Here's what might be going on:
Try typing the name of the issue to filter the list, rather than scrolling, if your issues list is extremely long.
It's possible your filtering settings are preventing the Jira issue from showing up. Open your Panobi Integration Settings, select Jira, and then check your filtering settings. Make sure the correct project and issue type are included.
Your Jira data isn't importing to Panobi as expected
If you're trying to import from Jira, but your newly-created Panobi project doesn't contain the content you're expecting, it could be for the following reasons:
Invalid format
Open your Panobi Integration Settings and select Jira. Check the configuration of your Jira-Panobi field mappings for any errors or misalignments between the types of fields, like text, numerical, etc.
Field mapping was removed
As above, in Settings, check your field mappings to see if any are missing or not fully mapped. If the mapping has disappeared altogether, this may be due to the removal of a custom field in Panobi. If the mapping row still exists in your mappings list but there's no longer a corresponding Jira field selected, check your Jira account to see if any content has been deleted or any fields renamed. You may need to re-establish the field in Jira, or remove the mapping altogether in Panobi.
Field is empty in Jira ticket
Check the ticket in Jira to see if perhaps the relevant field wasn't filled out.
Confusion over which field has been mapped
Open your Panobi Integration Settings, select Jira, and then check Field mapping to ensure you're looking for the information in the correct field. If the Jira field has been mapped to Description in Panobi, you may need to check the very end of the Description field for the content you're seeking.
Import error
If you've checked all of the above possibilities and still haven't solved the problem, there may have been an error during the importing process. We recommend trying again.
Your Jira formatting won't carry over
If you're importing from Jira, and your newly-created project is lacking some of the Jira formatting, that may be expected! Some formatting is possible to translate between the two platforms, but some is not.
Formatting and content that does carry over:
Bolding, strikethrough, italics, headers, bulleted lists, numbered lists, line separators, images, tables.
Formatting and content that does not carry over:
Font color (imports as black text), link unfurl objects (won't import), expand / collapse sections (import as normal text, fully expanded). Mentions, info panels, and status objects will all import as text.
Still having trouble?
Please reach out to our support team, and we'd be happy to help you figure out what's going on.