Skip to main content

Request Tracking for Popular Tools Like Jira, Bugzilla and GitHub

By 06/29/2017February 15th, 2022Continuous Delivery

Implement Change Request Tracking from Jira, Bugzilla and GitHub to Your Deployment.

DeployHub allows popular change request tracking tools to be linked to Components and Application objects. This allows DeployHub to track which defects are being worked on and where they are in the Software Development Life Cycle.

Because DeployHub supports different change request tracking tools (Jira, GitHub and Bugzilla) and allows individual components to be connected to these tools, each development team can use their own preferred Bug Tracking tool. You could have a Database Team using Bugzilla for change request tracking whilst the Application Development Team uses Jira. DeployHub consolidates all this bug data to show you the current state of an application, including all the bugs, their current state, and whether the bug is “open” or “closed”. Each bug is color-coded to give an instant view of the defect state.

DeployHub presents both a list of defects associated with the component or application but also a “burn down” chart which shows the bug fix activity over time. Providing this level of detail creates a level of collaboration across teams. As bugs are added or closed, the burn-down chart changes at that time. This gives an instant view of how quickly defects are being added and/or closed to the object giving you instant visibility of progress in bringing the application to a release state.

The Application view shows the defects associated with the application as well as all the defects associated with the constituent components. The Release view takes this a stage further and performs the change request tracking associated with all the applications in the Release. The burn down chart for a Release shows instantly how close the Release is to being ready for production.

Further Reading: