I work on a team that has all code and builds in an on premise Azure Devops and all issues reported in an on premise Jira installation.
There seem to be a million ways available to integrate those two, so I am I am looking for advice on what would be the recommended path for that so we could see info on commits and builds in jira cases and also the availability to create branches from Jira cases.
Bidirectional sync between jira cases and devops workitems is not a must but might be nice to have as well.
@melurinn hello. If you're open to exploring external help on the integration, take a look at ZigiOps. It's a no-code integration solution. You can customize it to fit various use cases. It can connect Jira and Azure bi-directionally, allowing the easy transfer (issues, work items, cases) and syncing of data between the two. Feel free to explore it and if you think it might be beneficial for any similar future projects, you can book a demo to see it in action.
Regards, Diana (ZigiWave)
There are two approaches through which Commits and Builds information from ADO can be synchronized to a Jira issue:
An enterprise-class integration solution can support both of these approaches.
It is more robust to integrate work items from Jira to ADO as that will allow you to apply rules on commits and builds. To achieve end-to-end traceability between Project Planning, development, and deployment, bidirectional synchronization between ADO work items and Jira issues is the recommended approach.
To create branches from Jira cases, you can look for something like Scriptrunner Atlassian add-on and call create branch API from the script.
OpsHub, an Atlassian partner, can help you integrate ADO commits and builds to Jira issues. Refer to Jira Integration with Azure DevOps documentation for more details.
Feel free to reach out to OpsHub’s Integration Experts for an initial free consultation on your integration planning.
You should check out TFS4JIRA - Azure DevOps integration!
You can view your project or issue-associated Azure DevOps check-in/git commit logs directly in your on-premise Jira instance. Actions are categorized by distinct event tags for quick and simple reference.
All changes are initiated and documented in Jira, which includes all of the necessary information, discussion, and testing verification.
The TFS check-in add-on for Jira allows anyone to see both request and solution under one unified view in Jira.
We'd love to talk with you and show you how TFS4JIRA can work with your environment. You can book a demo with our support team.
Let me know if you have any additional questions I can help with!