This video showcases a bidirectional integration between Jama and GitHub. Requirements created in Jama are automatically synchronized to GitHub, including all their details. Additionally, pull requests created and code committed in GitHub seamlessly update in Jama, preserving all linkages for end-to-end traceability.
A new requirement is created in Jama. Details such as the name, status, and description are added, along with rich text formatting elements like bold text, tables, and bullet points.” The name, status and other details are added to the requirement. The description is also added to the requirement.
OpsHub Integration Manager (OIM) supports the synchronization of rich text formatting, like bold, tables, bullets etc. OIM is running in the background fetching the requirement and its details to sync to GitHub.
in GitHub, a pull request is created and linked to the already synchronized issue from Jama. The pull request is successfully created and linked with the requirement from Jama, which is synchronized as an issue in GitHub. Afterward, a code commit is made in GitHub, and this commit is linked to the same issue that originated in Jama.
The pull request and the code committed in GitHub are bidirectionally synchronized to Jama, enabling end-to-end visibility between both systems. The link created between the issue, the pull request, and the code in GitHub is preserved during the bidirectional synchronization to Jama.
The page in Jama is refreshed to verify if the bidirectional synchronization from GitHub to Jama has been successful. In the comments section, the details of the pull request are visible, including the pull request ID, title, URL, and other information. Additionally, the details of the GitHub commit are also visible in Jama’s comments section, including the commit ID, committer, branch name, and URL.
GitHub, we can see the requirement from Jama has successfully synchronized as an issue. The title, description, status of the requirement from Jama are also visible in GitHub.