Jira Forms meets Flower BPM
Jira Forms meets Flower BPM
Never lose track of important data again.
Flower BPM integrates seamlessly with Jira Forms, ensuring structured data collection and automation in your workflows.
This guide walks you through how to create forms in Jira and connect them with BPMN processes in Flower.
Step 1: Create a Jira Form
Jira Forms are always linked to a Jira issue type. Since every Flower process instance is a Jira issue, your form fields will automatically be available in Flower.
For better organization, consider creating a dedicated Jira Forms project, where each issue type represents a separate form.
Jira Service Management Forms
Jira Service Management (JSM) offers a form builder that lets users fill out structured data fields when creating an issue.
These forms are configured under the “Forms” tab in JSM.
- The Jira form builder is only available in team-managed projects.
- The “Forms” tab exists only in Jira Service Management (JSM), not in Jira Software.
- Company-managed projects have a similar form setup .
- Additional marketplace apps offer even more form customization options. See Atlassian Marketplace .
- Mandatory fields cannot always be enforced because values might be unknown at process start. However, mandatory fields can be required when starting a process from a JSM form. See below.
Step 2: Link a Form to Flower BPM
Flower BPM does not create separate forms—it uses existing Jira issue forms.
To connect a form to a BPMN process:
- Open the Flower Modeler.
- Select the Jira issue type that contains your form.
- Save the mapping.
This ensures that every process instance has access to the same structured form data.
Since every activity in Flower BPM can have a different issue type, ensure that the process instance itself (not individual tasks) is linked to the form.
Step 3: Automatically Start a Process from a Jira Form
If you want a process instance to start automatically when a form is submitted,
you need to link the Jira issue type to a Flower BPMN model.
- Open Flower Settings → Issue Type Mapping.
- Select the issue type that contains your form.
- Save the mapping.
Now, whenever an issue of that type is created, Flower automatically starts a process instance.
Mandatory Fields
Since the form is submitted before the process starts, mandatory fields can be enforced.
This ensures all required data is captured before the process execution begins.
Be careful with this setting!
Any new Jira issue of this type will become a Flower process instance.
This issue type can no longer be used for modeling or BPMN tasks.
Step 4: Access Form Data in BPMN Activities
Every activity in a Flower process shares the same context, meaning that:
- All tasks inherit the form data from the process instance.
- Users can access form fields via the Forms tab in Jira.
This ensures that all required data is available at every step of the process.