You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Jira and Jira Align Integration works by Jira Align sending outbound rest API calls from Jira Align to Jira to sync issues, boards, sprints, and fix versions between the applications. A couple of Jira rest API calls can be utilized to help configure the connector and to troubleshoot common sync errors.
This call is the health check the Jira and Jira Align integration utilizes to validate API connectivity between Jira and Jira Align. This API calls does not require authentication to receive a response from Jira and for this reason Jira Align does not send an authentication header with this API call. Under Jira Align Admin > Jira Settings > Jira Connectors there is a “Test Now” button that utilizes this API call to validate connectivity between Jira and Jira Align. If you utilize an API Gateway or Reverse Proxy to connect Jira and Jira Align that requires credentials on inbound calls it will lead to this call failing as it does not send credentials.
This call will return information on the referenced Jira issue such as present fields and their values, the resolution date, and current issue status. This call is useful for determining if a field is present on a Jira issue’s screen, pulling the resolution date field name and current value, checking the status ID of an issue’s current status, and validating the type of an issue. This call is helpful when an update did not sync from Jira to Jira Align or there is a sync error from Jira Align to Jira. An example would be finding the current status of a Jira issue to verify its ID and the corresponding Jira to Jira Align status mapping configurations.
This call will return information on the referenced Jira project such as its name, type, issue types, and Fix Versions. This call is extremely useful for pulling all the Fix Versions from a Jira Project and verifying their start and release date. When executing this API call from the API service account you can also verify that the API service account has permission access to view a particular Jira Project and access its Fix Versions.
This call will return information including the name, start date, end date, state, goal, and origin board ID on the sprints currently associated to a Jira Board. This API call can assist with identifying sprints that were created in Jira than shared to the integrated Board, sprints have since been deleted in Jira, and issues with data syncing between Jira and Jira Align. The “?StartAt=50” query parameter will be necessary to investigate all sprints when there are more than 50 sprints on a Jira Board as Jira will only return 50 sprints at a time. This value can be shifted up or down as needed based on the number of sprints on an integrated board.