Jira Forms meets Flower BPM

Jira Forms meets Flower BPM

never lose a byte of crucial data again and keep everything in one form

Jira Forms meets Flower BPM

Never lose a byte of crucial data again and keep everything in one form. Here we show you how to create forms in Jira and how they can be combined with Flower BPM in the following three steps.

Create a Jira Form

Forms and form fields are always associated with a Jira issue type. This issue type then later becomes our Flower process instance. If a bigger number of forms are required, it is advisable to create a dedicated Jira forms project in which each issue type represents a separate form.

Jira Form Project holding all Flower Forms

The form fields defined on the issue type are then visible and editable on all Jira issue screens and Flower activities.

Jira Service Management Forms

The form fields that have just been created can then also be recompiled in a form that can be used as an issue create screen (and is only visible at create time). This is what is hidden behind the "Forms" tab in Jira Service Management:

Jira Form Builder

  • The Jira form builder described here, only refers to team-managed projects in Jira.
  • The additional Forms tab is only available in Jira Service Management and is not in Jira Software.
  • The form builder in company-managed projects works in a similar way (opens in a new tab).
  • There are still numerous apps on the Atlassian Marketplace (opens in a new tab) that only deal with the topic of forms.
  • No mandatory fields can be used, as it is not clear at the time the process instance is created which values are to be assigned to the corresponding fields. However, if you start the Flower process directly from a Jira Service Management form, mandatory fields are allowed. see below.

Link form and Flower BPM

Flower BPM uses the same data and forms as your Jira tickets. We just need to tell Flower which of the forms created above belongs to which BPMN process model. Since a Jira ticket is used for each process instance (a run of a process model), we want to be able to access our form data on this ticket. So let's link the BPMN process model to the same issue type that contains our form:

How to Link Flower to a Jira Form


As a different issue type can be selected for each activity in Flower BPM, but we want to set the issue type for the higher-level process instance, no other element must be selected in the modeler to get the right property settings.

Launch a Flower process instance directly form a Jira Service Management create-form

If you want to start a Flower process instance directly from a Jira Service Management form, you must link the form to the BPMN model. This means that every time a ticket linked to the form is created, it is converted into the Flower process instance.

Mandatory fields

In this way, mandatory fields can be used on the form, because it is ensured that the mandatory fields are filled after the form has been sent. The link between the flower process model and the Jira issue type can be made in the flower settings:

Flower BPM Issue Type Mapping


Be careful with this setting as it will turn any future ticket with this issue type into a Flower process instance. In particular, this issue type can then no longer be used for flower models or activities.

Access form data from every activity

All activities in a flower process share the same context, namely the process instance. This means every activity in a flower process has access to the same context form and documents via the Forms tab:

Flower Form Context in a Jira Issue screen

Learn more