We’re Here to Help!!

Find A Solution, Learn Best Practices & Get Support 24x7

Integrating Flosum ALM with Jira Software


JIRA Software is an Agile project management tool. From Agile boards to reports, JIRA Software can help your team release higher quality software faster. You can plan, track, and manage all your agile software development projects from a single tool.

Flosum ALM is a complete Application Lifecycle Management solution for Salesforce that supports Agile. You can plan, coordinate, and deploy releases from your developer sandboxes all the way to your production organization. Flosum helps you develop your Salesforce applications, from requirements tracking to production deployment. Flosum is developed on the Salesforce platform specifically to meet the needs of Salesforce application development teams.

Integrating Flosum with Jira will provide an end-to-end solution for your Salesforce application development projects: from capturing requirements, assigning to developers, managing release processes, through tracking all changes for compliance oversight, these combined tools will drive velocity and value.

Use Case Examples
The most common case for Jira integration with Flosum is when Jira is being used as the repository for capturing and organizing Agile artifacts, such as business requirements, product backlogs, user stories, and for coordinating assignments of sprint tasks to developers, or tracking velocity and other sprint related information.

In this scenario Flosum is used to manage the development process as the developers implement their project requirements. Flosum helps manage the development along each step of the way, working with Jira to support Agile sprint cycles through easy-to-use development tools and processes.

To facilitate integration between Jira and Application Lifecycle Management products such as Flosum, several integration technologies are available. For instance, ServiceRocket provides these two Salesforce/Jira connectors:

which are very flexible and can be configured in a variety of ways. They do not require any coding. Integration can be achieved very quickly with very little configuration required.

Below we provide a few examples of how Jira and Flosum can be integrated using ServiceRocket Salesforce & Jira Cloud Connector. These same examples can be applied to ServiceRocket Salesforce & Jira Server Connector.

Integration with Flosum Branches:
During Sprint planning, developers are assigned tickets in Jira related to user stories based on business requirements. As developers make changes to the application in their developer sandboxes to satisfy these requirements, they will tag their component changes to indicate the corresponding Jira ticket (user story).


Once work on a Jira ticket begins, developers can automatically create a corresponding Flosum Branch, from within Jira, by selecting the Branch option from the drop-down menu:

which will automatically create the Branch in your Flosum org:

This integration between Flosum and Jira can be bi-directional. Updates made to the branch in Flosum can be pushed into Jira and vice-versa. Customers can configure the integration to align with their business requirements.

Customers can also choose to show complete details of the Jira ticket in the Flosum branch by creating new fields on the Branch object (in Flosum) and mapping additional fields from Jira Issues objects to the Flosum Branch.

This integration allows users to track which components have changed for every corresponding Jira ticket, along with many other Agile development changes and activities.

Extending the Commits object:
Above we showed it is possible to track, in Flosum, components modified for a specific Jira ticket. What happens when these components are committed to the Flosum Repository? We also need to track which components were committed for which Jira ticket.

To capture the component changes related to a Jira ticket, extend the Flosum Commits object to create new fields for this information which can then be populated from the Branch during the commit process.

Using this integrated solution, customers will have a complete history of which components were committed for which ticket.

Extending the Deployments object:
Deployments can also be tracked from the perspective of user stories rather than components deployed. A deployment can be created from a variety of sources such as Branches, Repository, Commits and Snapshots. Pushing the story information all the way to deployment enables users to track the deployment at the user story level rather than the component level. For example, the image below shows that the Hotfix patch takes care of three user stories.

Reporting at the User Story Level:
Managers can create reports and dashboards to track the visibility at the level of a User Story instead of the Component level. This dashboard shows the user stories which were deployed to production, the user stories which are in testing, and the user stories which are still being worked on by developers and admins.

How to integrate:
Please refer to the following documentation for more information on integrating Jira with Flosum:

Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful