Businesses achieving agile transformations on a small scale often fail to replicate their success at an enterprise level due to a lack of alignment across disparate systems and cross-functional teams. Adopting an automated integration solution increases collaboration, reduces development time, and ensures quicker time to market.
Integrating best-of-breed tools like Rally and Jira using OpsHub Integration Manager (OIM) provides full visibility to product management, development, and quality assurance teams into each other’s work. This seamless integration enables faster product delivery and delivers cohesive value to customers.
The product team in Rally starts by creating user stories, which synchronize as stories in Jira. They assign each story a name, description, status (e.g., “active”), and priority, saving them accordingly. Additional user stories can also be created and prioritized differently based on requirements. All user stories created in Rally automatically synchronize to Jira along with their details, such as name, description, Remote Entity ID, and Remote Entity Link. Statuses and priorities set in Rally are mirrored in Jira.
The development team begins work on a user story in Jira by changing its status to “in progress,” adding comments and attachments, and saving their updates. These changes are bidirectionally synchronized with the corresponding Rally user story. For example, a status change to “in progress,” added attachments, and comments in Jira reflect accurately in Rally, along with the Remote Link and Remote ID for the Jira entity.
Similarly, updates made in Rally, such as modifications to a user story’s description or status, are synchronized back to Jira. The development team can also link a defect to a user story, create bugs with appropriate summaries and descriptions, set priorities, and specify link types. These defects synchronize to Rally, maintaining the linkage to the relevant user stories.
The product team in Rally can further enhance defect details by adding attachments, comments, and modifying statuses, such as setting it to “submitted.” Any updates to the defect in Rally, including priority changes or additional information, synchronize seamlessly to Jira. Entity IDs and links for the defect are visible in both tools, ensuring transparency and alignment between the teams.
This bidirectional synchronization ensures that updates made in Jira and Rally are consistently reflected, maintaining collaboration and reducing inefficiencies across the product development lifecycle.