The first step to troubleshooting this problem is to ensure that the project in Ketryx has been synced with Jira.
Note: After an initial Jira sync has been completed, changes to advanced settings can cause future syncs to fail. It is recommended to check the System Logs ("target project" -> History -> System Logs) for any sync failures. This log can be export and provide clues into what is causing the sync error.
If the sync is done and there is still an issue, confirm that the name of the item type in Jira is the same as what Ketryx reads. For example, if you renamed your anomaly item type to “Anomaly 1,” Ketryx will not treat this as an anomaly. If the name of the item is different from Ketryx defaults, perform issue mapping. Once this is complete, sync with Jira again and see if the states have updated. If there are still issues, you can add status mapping for that particular item type in advanced settings. Ensure that the Jira status name maps to one of the Ketryx item states. An example of this is:
{
"statusMapping": {
"Anomaly 1": {
"Open": "OPEN",
"Closed": "CLOSED",
"Reopened": "REOPENED"
}
}
}Now, perform a sync with Jira and that statuses should be mapped into Ketryx as intended.
Comments
0 comments
Article is closed for comments.