JIRA for Rocket Aldon

Everyone loves JIRA (well, almost everyone). And what’s not to love? Many consider Atlassian’s JIRA the go-to tool for managing projects for many reasons. It’s highly customizable, it’s not restricted to a single platform, and it can be hosted on-prem or in the cloud.  Its capability to include requirement and change management processes adapted to an organization’s unique needs is also a plus.

Management loves the visibility provided from the graphical dashboards and reporting that includes the status and financial costs associated with their projects.

Development teams especially appreciate the agile project management framework suited for scrum, Kanban, or a mix of any methodology — all from a single tool. And, because it is so popular, many plug-ins and add-ons for other popular ALM/DevOps/Operations tools are available.  

This brings me to the best part for anyone using Rocket’s Aldon Lifecycle Manager products. 

Did you ever wish that a ticket or task created for a code change could automatically be created from JIRA for use in Rocket Aldon Lifecycle Manager (LM) for the IBM i and/or Lifecycle Manager Enterprise? Or that a simple status change could move changes through your lifecycle and deploy changes to test and production servers? Or that you had one place to provide information when those pesky auditors are interrupting your day?

Now you can! Rocket has launched a Rocket Aldon LM Add-on for JIRA.

When JIRA projects are integrated with one or more Lifecycle Manager products, updates in JIRA can navigate your development lifecycle stages through verification and delivery. Transition points are configured in the JIRA project to trigger movement of code changes through your unique process, while still providing all the automation and builds of those changes LM(i) and LM(e) manage for you today. This ensures the right changes go to the right places at the right time.

As an example:

• Changing a status from “In Progress” to “In QA” would promote it to a test stage. 
• A change from “In QA” to “Complete” might promote/deploy it to production servers.

All the current functions defined in Lifecycle Manager remain. For example, with LM(i) managed objects, you can add dependencies, create objects in the correct order, manage the overhead for file and table changes, and more.

The LM Add-on for JIRA also provides a sample workflow template for teams to customize to suit their own processes.

If you are a customer and want to give it a try, you can download the Rocket Aldon LM Add-on for JIRA from the https://my.rocketsoftware.com/RocketCommunity#/ under the Aldon Ops Portal. Please let us know what you think! We know the Rocket Community has the best ideas on how we can help make your experience better with our products.

If you are not a customer but want to see a demo, request one today!

By Anita LeMay, Senior Sales Engineer at Rocket Software