Link Jira issues to deployment requests in Blue Canvas for easy tracking. Bi-directional sync allows you to see Jira issues in Blue Canvas and vice versa.
Jira is a central hub for a massive number of software development teams. It’s the place of record for what work is done and, often, why.
Most of our customers use Jira as their system of record for their Salesforce application development. To make their lives easier, we’ve made it easy to link Jira tickets to deployments in Blue Canvas. Teams want to be able to tie changes to their source code and Salesforce configuration to Jira because that’s where work is tracked.
Blue Canvas supports three deployment types: a Fileset Deployment (deploying a collection of files), a Checklist Deployment (a list of manual steps that have been taken in configuration), and a Bulk Release (a collection of Fileset and Checklist Deployments). Blue Canvas users can now pin Jira tickets to each of these deployment types.
As a user is creating a Deployment, they will see a new field alongside the Title and Description fields called Jira Issues. When you start typing the name or ID of your Jira issue in that field, we’ll auto complete for you so you can attach the Jira issue to the Blue Canvas deployment.
The sync between Blue Canvas and Jira is bi-directional, so any Jira issues attached to Blue Canvas deployments will show up as links in Blue Canvas and as links on the associated Jira issue.
When changes are made in Jira, they will be automatically reflected in Blue Canvas in real time. For example, if you change the title of a Jira issue, it will automatically update the linked issue in Blue Canvas.
The Blue Canvas Jira integration captures basic details such as Issue Type (e.g., bug, story, task, etc.), Assignee (i.e. who owns it in Jira), Title, Status, and Jira ID (e.g. GC-2). The Blue Canvas Deployment status will also be updated and stored in Jira. When you need to attempt several deployments before your tests pass, each successive deployment will show up in the Jira with various statuses. You can even attach multiple Jira tickets and edit or add them to Deployments after the fact.
Our Jira integration is an expression of our larger philosophy of creating great developer and admin experiences for Salesforce that “just work”. Our goal is to remove complexity so that you can focus on building performant, useful applications.
The Jira integration is designed to be quick and seamless so that you can document as you work. No more jumping between Jira and Blue Canvas, no more using spreadsheets to keep track of changes.
Now your two most important systems for Release Management can communicate in real time with minimal overhead. This brings business requirements one step closer to the code and configuration changes required to satisfy them, which makes business users and developers happy.
Salesforce Developer Bo Laurent has published an ingenious fix for a perplexing Salesforce Developer Console bug.
A simple way to think of the cost benefit analysis when investing in Salesforce CI, DevOps and metadata backups.