Skip to content

Rally Software Integration with GitHub and Zendesk

Rally Software Integration

The integration of Rally Software with GitHub and Zendesk provides the project management team complete traceability for any ticket (incident, problem, or defect) raised by a customer.

Rally Software – Zendesk & GitHub Integration Overview

In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between the cross-functional teams play a great role. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements.

Best-of-breed systems such as Rally Software, Zendesk, and GitHub bring rich functionalities to the ecosystem. When GitHub is integrated with Rally Software and Zendesk, all stakeholders have real-time visibility into the commits made by the development team. It is also easier to enforce authentic commits against each work item and access the changes/edits made to the commit files from Rally Software itself.

How Rally Software – Zendesk – GitHub integration is beneficial for an enterprise

  • Track commit volume, track commit trends and edits/changes to commit files in real time
  • Enforce authentic commits to make sure each commit is happening against a scheduled and open workitem
  • Eliminate manual effort to close Rally Software & Zendesk workitems by automating the state transition on GitHub commit

With Rally Software + GitHub + Zendesk integration, enterprises can:

Rally Software Zendesk GitHub Integration

How OpsHub Integration Manager integrates Rally Software – GitHub – Zendesk

OpsHub Integration Manager integrates Rally Software with GitHub andZendesk – each system with the other bidirectionally. It ensures that all data isavailable to each user, in that user’s preferred system, with full context, in real-time.All the details related to a commit made against a work-item in Rally Software canbe tracked from Rally Software itself. For example, for each commit thatdevelopment team makes in GitHub, GitHub synchronizes a ‘commit entity’ linked tothe specific requirement id back to Rally Software. Each ‘commit entity’ includesinformation such as ‘who did the commit?’, ‘when was the commit done?’, and‘which part of the code was committed?’.

The support team, using Zendesk, is also up-to-date with the status of a ticket (incident, problem, or defect) raised by a customer.

Popularly synchronized entities

Rally Software Zendesk GitHub Entities Mapping

Use Case: Rally Software integration with GitHub and Zendesk

Problem statement: Lack of commit traceability means development and support teams must manually update their systems after successful commit against a workitem.

Solution: If Rally Software, GitHub, and Zendesk are integrated using OpsHub Integration Manager, the build results will be automatically synchronized to all the integrated systems.

  1. A support team member logs an incident in Zendesk.
  2. The development team traces it as a ‘defect’ in Rally Software.
  3. The development team works on the ‘defect’ in Rally Software and commits the changes against the ‘defect’ in GitHub.
  4. OpsHub Integration Manager synchronizes the commit information to Rally Software as a ‘change set’ in the associated defect.
  5. The change also reflects in Zendesk.
Rally Software Integration with Zendesk GitHub

Benefits of integration for Rally Software, GitHub, and Zendesk

Rally Software & GitHub users

  • Traceability for business requirements throughout the ALM tool chain
  • Direct visibility into customer issues and their priorities
  • No dependency on manual communication

Zendesk

  • Access and real-time updates to the development status within Zendesk
  • Easy to categorize and transfer customer tickets to Rally Software
  • No dependency on manual communication