Skip to Content
Flower 3.3.2 is released 🎉
DocsResourcesChangelog
Image

Changelog

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog , and this project adheres to Semantic Versioning .

Known Issues

[3.3.2] - 2025-10-23

🚀 Features

  • FEAT: Lane actions – open Jira issues filtered by lane via the external-link icon.

🐞 Fixes

  • FIX: Help modal restyled to Atlassian look; resolved icon import and removed an unwanted link icon.
  • FIX: Attachments – prevented upload crash; Add button now opens the process instance in Jira; always show a file icon when no thumbnail is available.
  • FIX: FlowerForm hardened to handle unknown/custom field data types gracefully.

♻️ Refactor

  • REFACTOR: Migrated client to React 18 root API and adjusted dependencies.

[3.3.1] - 2025-10-13

🚀 Features

  • FEAT: Replace browser prompt with a unified Create/Import Model modal. Added Advanced options to specify Jira Project and Issue Type with defaults preselected from Settings.
  • FEAT: Advanced section UX: hidden by default for plain creation, automatically open for import; added subheadings “Jira settings” and “Import model”; moved import UI into Advanced and styled with an Atlassian-like file chooser button.
  • FEAT: Added an information box in Advanced: guidance about mandatory fields and a link to Flower settings.
  • FEAT: New modal state createModelAdvanced to open the same modal with Advanced options expanded (used by the header Import action).

🐞 Fixes

  • FIX: Creating a new model again includes default BPMN XML and SVG (behavior from createPlainModel merged into createModel).
  • FIX: Preselect the correct default Issue Type for Models using settings.issueTypeModel (fallback to settings.issueType).
  • FIX: Settings link in the modal now navigates correctly using router-based navigation in Atlassian Connect context.

♻️ Refactor

  • REFACTOR: Unified creation API – removed createPlainModel; createModel now injects default BPMN when none is provided.
  • REFACTOR: Simplified import API – importModel now uses object-shaped signature: importModel({ summary, project, issueType, file, model }, httpAuth); updated all internal usages.

[3.2.10] - 2025-06-26

  • Added support for Personal Access Tokens (PAT) – Flower now supports three authentication methods for Jira DC:
    • Basic Authentication using username and password
    • Personal Access Token (PAT) using Bearer token
    • TrustedRequest (default system-level execution)

[3.2.9] - 2025-06-11

  • Fix: Iframe path resolution – Improved handling of Jira DC installations with varying context paths.

[3.2.8] - 2025-05-15

  • Fix: Reopen issues in Jira Data Center: Issue transitions did not work as expected when trying to reopen issues. Root cause: Jira DC uses a different REST endpoint format for transitions than Jira Cloud.

[3.2.7] - 2025-04-25

  • Settings extended for DC compatibility: Base path and user credentials can now be configured for Flower REST calls.

[3.2.6] - 2025-04-22

  • BasePath for Jira REST API – Ensure base path is reachable from Jira host

[3.2.5] - 2025-04-04

  • Expression Handler – Ensure all fields are available during expression evaluation
  • Expression Handler – Add experimental validation of expressions at runtime

[3.2.3] - 2025-03-25

  • Issue Type Mapping: Throws a client-side exception when the user does not have project browsing permissions
  • Model Validation: Fails validation if a node is empty

[3.2.2] - 2025-02-13

  • Lane assignment minor bug fixes
  • Create plain model should only contain a start event
  • Create plain model should contain svg data
  • DC resize resize parent after clicking on a Flower gadgets in Issue view

[3.2.1] - 2025-01-30

  • Minor fixes

[3.2.0] - 2025-01-24

  • FEAT: Dark Mode implement dark mode feature
  • FEAT: Atlassian design system update new Atlassian icon system

[3.1.1] - 2025-01-13

  • FIX: DMN Fonts: Fonts have the wrong http header in DC
  • FIX: Mandatory Fields Error: Add better describing error message

[3.1.0] - 2025-01-12

  • FIX: Task Count at Starting PI is limited to 50: rest service restriction => https://bauer-it.atlassian.net/browse/SUPPORT-395 
  • FEAT: Error Handling: All errors are now logged as comments on the associated process instance.
  • FEAT: Circling Timer Events: https://bauer-it.atlassian.net/jira/servicedesk/projects/SUPPORT/queues/custom/42/SUPPORT-388 
  • FEAT: Data Residency Page:
  • FEAT: Admin Button to performe Timeout Event:
  • FEAT: Decision Handling: Introduced a default transition in case decision expressions fail to resolve, avoiding errors in decision processing (WebComputing).
  • FIX: Process Management: Added functionality to terminate processes and automatically set the process instance to resolved.
  • FIX: Session Timeout:
  • FIX: Repository Page at card tile: tag click does not work
  • FIX: Terminate End Event Close open Issues without propagating process
  • FIX: OnBoarding: First Screen has circling card
  • FIX: The BPMN diagram does not show up for unpublished models at Jira issues
  • FIX: AP.jira.openIssueDialog does not work as expected see bug report 

[3.0.0] - 2024-12-21

  • FEAT: Major Release: Unified the Cloud and Data Center versions to the same feature level.
  • FEAT: Flower BPMN Automation Engine: Introduced support for the Flower BPMN automation engine in Data Center.
  • FEAT: BPMN Time Out Events: Implemented BPMN timeout event handling for Data Center.
  • FEAT: Decision Nodes at BPMN Gateways: Added support for decision-making at BPMN gateways based on Jira field values in Data Center.
  • FEAT: Engine Exceptions as Comments: Exceptions from the BPMN engine are now logged as comments on the Jira issue of the process instance.
  • FEAT: Issue Type Mapping: Extended issue type mapping functionality to Data Center.
  • FEAT: BPMN Diagram Alignment: Improved alignment of BPMN diagrams in the Jira issue web panel for a cleaner presentation.
  • DEPS: Dependency updates
  • FEAT: Clear Distinction Between Process Types: Introduced a separation between “executable” processes, which can be automated by the process engine, and “legacy” processes, which are manually managed.
  • FEAT: Support for Jira 10.x: Updated compatibility to Jira version 10.x, with special focus on supporting the Long Term Support Release 10.3.
  • FEAT: Message events: Webhook to Jira Automation (e.g. send Email)
  • FEAT: Wishing everyone a Merry Christmas! 🎄

[2.5.3] - 2024-09-25

  • FIX: Dependency updates and minor bug fixes
  • FEAT: Open Swim-lane Filter when click on the lane

[2.5.2] - 2024-06-15

  • FIX: Auto assignment for new issues in a Lane does not work

[2.5.1] - 2024-02-16

  • FIX: Remove double link at GeneralPage
  • FIX: Remove issueGlance from connect-config
  • FEAT: Open Swim-lane Filter when click on the lane
  • FEAT: Auto-create next issues also in agile mode
  • FEAT: Create comment to pi if a decision cannot be made
  • FIX: Unselect Issue Type does not work properly in BPMN editor
  • FIX: Auto starting a PI from issue type mapping creates the PI but not the first activity
  • FIX: Activities should be subtasks of the pi (does not work)

[2.5.0] - 2024-01-05

  • FEAT: disable version control in setting
  • FEAT: add reporting page
  • FEAT: move process instance list to Jira filter
  • FEAT: extend Flower REST API: createProcessInstance and create certain (or all) activities
  • FEAT: add BPMNView page to better visualize large models
  • FEAT: split build to improve loading performance
  • FEAT: launch successor task automatically even in agile mode
  • FIX: switch to strict mode and back was not working
  • DEPS: dependency updates
  • TEST: extend unit tests to rest api

[2.4.0] - 2023-11-30

  • FIX: unpublished models cannot be started
  • FEAT: DMN Decisions on Select Fields
  • FEAT: remove the Description Text (replace it with something like {Flower Auto Text} see user manual)
  • FEAT: Flower REST API

[2.3.4] - 2023-10-20

  • FIX: AMS Ticket 
  • FIX: Naming of Jira tasks is too large: remove PI name
  • FEAT: application scope added: ACCESS_EMAIL_ADDRESSES
  • FIX: move bpmn.io logo into view box
  • FEAT: customer onboarding messaging optimized

[2.3.3] - 2023-10-06

  • DEPS: dependency updates (09627dc) 
  • FEAT: entity Property flowerLane added
  • FEAT: processOwners added to Flower settings(9592826)
  • FIX: model export broken (SUPPORT-192) 
  • FIX: order model list by created DESC (4ae4d8b) 
  • FIX: minor bugfixes

[2.3.2] - 2023-08-26

  • FEAT: map jira issue type with Flower process model (c5f5c26) 
  • FIX: BPMNView cannot display collapsed subprocesses due to overlay issues

[2.3.1] - 2023-07-08

[2.3.0] - 2023-06-08 DMN

  • FEAT: DMN modeler integrated (2af39d9) 
  • FEAT: DMN evaluation implemented
  • FEAT: export dmn model
  • FEAT: link bpmn gateway with dmn decision table
  • FEAT: decision Control for Issues based on DMN decisions

[2.2.1] - 2023-05-1

[2.2.0] - 2023-04-06

  • FEAT: create client record based for each install
  • FEAT: PI View in portal - rework margins
  • FEAT: start unpublished models
  • FEAT: test with company/team managed projects
  • FEAT: better highlite current node
  • FEAT: create hirachyal issues like Epic-Story based on sub-processes in bpmn

[2.1.2] - 2023-03-19

  • FEAT: expanded Sub-Processes
  • FEAT: issue Hierarchies
  • add Parent Field to Activities in Modeler
  • make Sub Activities (from collapsed Subprocesses) launchable
  • process Instance View as Tree Table
  • make Initiative ticket root level
  • FIX: createIssueView format errors
  • FEAT: set Hierarchy Initiative
  • FIX: createIssueView Filter only not started nodes
  • FEAT: modeler remove parent select box

[2.1.1] - 2023-02-17

  • FEAT: exporting an unsaved model produces an error message.
  • FEAT: apply Jira issue hierarchy when creating a Flower entity to persist structures like Epic -> Story and Task -> Sub-task
  • FEAT: create new Model function uses wrong template

[2.1.0] - 2023-02-06

  • FEAT: added mandatory field validation when creating an epic
  • FEAT: added Model Version Navigator to navigate through previous versions
  • FEAT: made Jira process/type editable when launching a process instance
  • FEAT: implemented WorkflowCondition to allow transition only if all linked issues are resolved
  • FEAT: implemented WorkflowValidator to allow transition only if all linked issues are resolved
  • FIX: BPMNWrapper now only works with one lane-pool. Models with multiple pools have no bpmn control in the start workflow screen
  • FIX: ProcessInstanceView page now refreshes after a popup has closed
  • FIX: Optimized Build das not work with bpmn-js
  • DEPS: library updates
  • FEAT: added functionality to createJiraTask:
  • Jira field description is now set to bpmn element documentation
  • Added Blocked By link when creating a new task
  • Added previous nodes field to flower properties
  • Added next nodes field to flower properties
  • FEAT: BPMN Templates updated
  • FEAT: User manual updated

[2.0.2] - 2022-11-09

  • Activate license support
  • Set mandatory fields when creating Jira issue (DC only)
  • After the Settings modal, properties are not updated on repository page
  • Help Modal update links
  • Disable Reporting Button in Repository
  • Settings Page: repository link: history object not there because no routing
  • Redirect /flower/page => /page
  • Set Project/IssueType in Edit Mode Page Properties Panel
  • Migrate unpublished models
  • Make existing instances visible (existing tasks should be visible at the pi)
  • Disable start-workflow-button while starting PI to avoid creating multiple pis
  • IssueView: make current activity visible
  • Make the Flower icon red Cloud

[2.0.1] - 2022-11-03

  • RepositoryPage: bpmn pictures are not rendered correctly in cards
  • RepositoryPage DC: onboarding no scrolling available
  • ReactGA4
  • Remove Axios from client libs
  • PanelLeft DC: page padding-bottom is by far too large
  • PanelLeft Cloud: the model has no status
  • CreateProcessInstance produces undefined in summary
  • StartWorkflowModal “Click to enter the value” instead of instance summary
  • adjust token-simulator look and feel/CSS

[2.0.0] - 2022-11-01

  • Flower Data Center version added
  • Remove Redis
  • Remove middleware
  • Remove form-io and forms at all
  • Remove the unsupported nodes button
  • Rework http Error handling to be in sync with dc
  • Token Simulation added to EditModelPage
  • Save bpmn at instance (Flower)
  • Clean up issue properties. merge all in one
  • Show issue status in bpmn-view
  • Add flower templates as a label in the repository list (remove template button)
  • Update bpmn-js-properties-panel
  • Repository
  • Remove label filter for dc
  • Rework templates
  • Create a plain model as a template
  • Check Onboarding
  • CheckSettingsModal
  • ProcessInstancePage
  • Remove edit header
  • Hide non-task-activities
  • Beautify table rows for started tasks
  • Edit summary
  • BPMNView fitUpperLeft
  • Deal with issue-create errors (permissions) (eventuelly save errors at pi)
  • Show priority in table view
  • Make table toggable
  • Fix create all button
  • Rework Onboarding
  • ProcessListPage
  • Rework onboarding
  • ProcessInstanceListPage
  • Check Onboarding
  • PI-Status Column
  • Make Summary editable and make labels savable at the EditModelPage Properties Panel- IssueView web-panel integration  Settings page- Rework Onboarding

[1.2.1] - 2022-07-01

  • HTTP and Jira Mock have been changed to work with the Jira AP api
  • MQ Engine to be running without Redis. switch on/off in flower/conf
  • Decision Handler moved to MQ in one method
  • This changelog added
  • Added Flower-core/spec/mock test spec for mock
  • nNw localhost:3000/demo/ endpoint to run with mock backend
  • Added Puppeteer tests added
  • Added test event added to test HTTP functions in graalvm
  • Added Flower core build script to create a graalvm runtime

[1.2.0] - 2022-01-22

  • Added Test Coverage with Jest
  • Changed Build with parcel.io
  • Removed web pack

[1.1.6] - 2021-12-06

  • Diagram ausrichtung in der jira issue ansicht adjusten
  • Formular verschwindet manchmal
  • Add process instance name to the Flower task summary
  • Add the model name to the process instance summary
  • At the repositories tab select box, some values cannot be selected
  • Add the Jira task status to the BPMN diagram

[1.1.5] 2021-11-20

  • Tested user interface in chrome
  • Indicate at the Jira ticket at which Flower type we are (model, instance, or task)
  • Hardening the user interface

[1.1.0] - 2019-12-01 - 2022-01-22

  • We had many Flower releases which are not documented in this file## [1.0.0] - 2019-12-01
  • Initial Flower release
Last updated on
Data ResidencyFlower Help