Setup Flower

Configure Flower for Jira Automation

Setup & Configuration

To seamlessly integrate BPMN workflows into Jira, Flower does not store process data separately.
Instead, it relies on Jira issues to manage and track all BPMN elements.

Before you can start using Flower, some basic configurations are required:

• Define where BPMN models, process instances, and tasks should be stored in Jira.
• Set up issue type mapping to allow Jira issues to trigger BPMN processes automatically.

These settings ensure that your BPMN models are fully integrated into Jira workflows and can be executed smoothly.

Step 1: Define Default Values for Jira Integration

Since Flower stores all process-related data as Jira issues, Jira must know which project and issue types to use for different BPMN elements.
The following object types need to be mapped:

• BPMN Models → The graphical representation of a process, stored as a Jira issue that contains all versions.
• Process Instances → Created when a BPMN model is executed, tracked as Jira issues.
• Tasks → Each BPMN activity (rectangle) is a Jira task, created when the process reaches that step.

To configure these defaults:

1. Open Flower Settings in Jira.
2. Set the default project and issue type for BPMN models, process instances, and tasks.
3. Save the settings.

By default, all tasks inherit their project and issue type from the global settings.
However, you can override these settings at the activity level within your BPMN model (see Process Instances).

Step 2: Configure Jira Issue Type Mapping

In many cases, you don’t want to start BPMN workflows manually. Instead, processes should be triggered automatically when certain Jira issues are created.

To achieve this, Flower allows you to map BPMN processes to specific Jira issue types.
Once mapped, every time a Jira issue of that type is created, Flower automatically starts a process instance.

How to configure Issue Type Mapping:

1. Go to Flower Settings → Issue Type Mapping.
2. Select a Jira issue type that should trigger a BPMN process.
3. Save the mapping.

This configuration ensures that Jira users can start BPMN processes without accessing the Flower App—just by creating an issue in Jira.
For details on how to launch and manage process instances, see Starting a Process.

Step 3: Using Flower with Jira Service Management (JSM)

Flower can, be used with Jira Service Management. No special configuration is required. However, we recommend creating a separate Jira project (not JSM) with an issue type “Flower BPMN Model” to store BPMN models. Link this issue type as “Issue Type Model” as described above. This ensures that Flower can be used with Jira Service Management, Jira Core, and Jira Software without any restrictions.

If a JSM request type is mapped to a BPMN Flower Process, every new customer request (submitted via the JSM portal or Jira) automatically becomes a Process Instance. The request can still be handled as usual in JSM, while Flower manages all linked process tasks within the same ticket.

This setup allows seamless integration between JSM and BPMN-based process automation, without changing existing JSM workflows.

Summary

• Flower integrates BPMN models, process instances, and tasks as Jira issues.
• Default values define where BPMN elements are stored in Jira.
• Issue Type Mapping enables Jira issues to automatically trigger BPMN workflows.
• JSM Optional: Flower can be used with Jira Service Management (JSM) by linking a JSM request type to a BPMN Flower Process, allowing JSM requests to act as process instances while still being handled in JSM.

Once these settings are in place, you’re ready to run automated workflows with Flower in Jira.