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 .

[3.6.1] - unreleased

Highlights

• NEW: Flower on Atlassian Forge (Jira Cloud). Flower now also runs as a Forge app, inside Atlassian’s infrastructure. It is an update of the same app with the same listing and license, offered in Manage apps. Your Flower settings are taken over automatically, and models, process instances and work items stay in Jira. See Moving to Atlassian Forge.
• CHANGE: Usage analytics. Flower records more usage events to find problems earlier, for example when a process is started, completed, or fails to start. The Forge app sends no names, e-mail addresses or work item titles. You can switch the analytics off in the Flower settings, tab Analytics.

Fixes

• CHANGE: REST API: the Flower REST API now calls Jira with the permissions of the API user (your e-mail and API token), no longer with the permissions of the app. The user needs the usual Jira permissions to read and create models and process instances. See Flower REST API.
• FIX: The BPMN viewer no longer fails with the error “Failed to execute ‘scale’ on ‘SVGMatrix’” when its container has no width yet or the diagram is empty.
• FIX: Process end: a process instance ends when no branch is running any more. Before, the first end event ended the whole process, even when another branch was still open. This matters if a parallel branch ends without a gateway that joins it. A terminate end event still ends the process at once.
• FIX: Timers: the timer job waits until all due timeouts are done before it reports that it has finished.
• FIX: A model without the isExecutable setting no longer stops with the error “No executable processes”.
• FIX: Jira Data Center: Flower no longer fails with the error “flag is not a function” in newer Jira releases (Jira 11). Messages that Jira cannot show are only logged.
• FIX: The issue panel, the model views and the start dialog no longer show an error when the work item does not exist or you are not allowed to see it.

[3.6.0] - 2026-11-04

This is a big update for Jira Cloud and Data Center. The process engine is renewed, timers work as documented, and Flower speaks your language.

Highlights

• NEW: Flower in 13 languages. Everyone sees Flower in the language of their own Jira profile: English, German, Spanish, French, Italian, Portuguese, Japanese, Chinese, Korean, Dutch, Polish, Russian and Turkish. The BPMN modeler is translated for German, Spanish, French, Italian, Portuguese, Japanese, Chinese, Polish and Russian. See Setup.
• NEW: Jira sub-tasks. Choose a sub-task work type for an activity (or a lane) and Flower creates the work item as a sub-task of the process instance. The modeler warns you in advance if Jira would not allow it, see User Tasks. If Jira refuses a sub-task anyway, the process goes on with the default work type and Flower writes a warning at the process instance.
• NEW: Message flows between pools. Models with several pools can send messages from one pool to the other, see Message Flows. The process instance ends when the last pool has ended.
• NEW: Timers work as documented. Repeating timers (R/P1D, R3/P1W), timers with a date, and timers in hours or minutes are supported and fire at the right time. Existing models keep working. See Due Dates and Timer Events.
• UPDATE: New process engine (bpmn-engine 26). Running process instances continue after the update. An OR join (inclusive gateway) now waits for all branches that were taken. Before, the process could end while work items of other branches were still open.

Improvements

• NEW: The Flower page uses the whole window and scrolls below the header, in Jira Cloud and Data Center.
• NEW: Spinners and busy buttons while a model is created, imported, saved, published or validated. Nothing is sent twice any more.
• NEW: Analytics tab in the Flower Settings: administrators can switch off the anonymous usage analytics. See Setup.
• NEW: Data Center writes its own log file flower.log next to the Jira log, see Setup.
• CHANGE: Restoring a version asks for confirmation and opens the editor with the restored model.
• CHANGE: A model whose path does not end in an end event now gets a warning, not an error, and can be published. Models with a boundary event without a definition get a warning, too.
• CHANGE: The product tour shows one card at a time and never cuts off its text. The buttons in the editor header stay in one row, and the links in the help dialog open.
• CHANGE: The buttons of the issue panel can be used with the keyboard and with screen readers.
• CHANGE: DMN decision tables are only modeled. The engine does not evaluate them any more (this only affected process instances created before the engine existed). Use conditions at gateways, see Migrate from DMN.

Fixes

• FIX: Jira Cloud: the daily timer job failed at 00:00 UTC and could stop the server. It runs correctly now, and a failing job is only logged.
• NEW: If Jira does not take a due date (the field “Due date” is not on the screen of the work type), the process instance gets a warning. Timeout events work anyway.
• FIX: Jira Data Center: Flower now follows the language and time zone of the Jira user. Before, Flower was always English on Data Center.
• FIX: Parallel branches that are resolved at the same moment (two people, or a bulk transition in Jira) no longer get lost: the process continues after the join. Flower now handles the changes of one process instance one after the other.
• FIX: Jira Data Center: umlauts and other special characters in the name of a work item no longer cause an error when Flower talks to Jira.
• FIX: A condition on a field without a value (for example an empty custom field) is simply false. Before, the process stopped with an error.
• FIX: A boundary event without an event definition no longer prevents the work item of its task from being created.
• FIX: The model export (zip) works for models with unsaved changes. Importing a file that is not valid XML shows a clear message.
• FIX: The panel of a sub-process shows the sub-process and a link to the calling process.
• FIX: The timer job runs at 00:00 UTC, the due date of a work item is the day in the local time zone, and flowerTimer is cleared after the timeout. Completing a task whose timer has interrupted it no longer hangs.
• FIX: The decision table editor no longer shows errors when you open it, and the expression editors work reliably.
• FIX: Requests that Jira answers with “too many requests” (429) are repeated automatically after the time Jira asks for.

Before you update

• The saved state of processes with parallel or inclusive gateways is 10 to 30% larger.
• Jira Data Center: the Flower log moves to its own file flower.log (see above).

[3.5.0] - 2026-11-01

Sub-processes

• FEAT: Sub-process automation. A call activity runs another process model. Map a work type to a model in the Jira Work Type Mapping and give the call activity this space and work type. Flower turns the work item of the call activity into a sub-process instance. The calling process waits at this step and continues as soon as the sub-process is resolved. Works in Jira Cloud and Jira Data Center. The embedded sub-process stays a graphical element. See the new documentation page Sub-Processes.
  • The sub-process starts with the model version that is published when the call activity is reached.
  • Gateway expressions in the sub-process can read the calling process instance as par, next to pi and cur.
  • A terminate end event ends the running sub-processes with all their work items, also nested ones. A terminate end event inside the sub-process ends only this sub-process.
  • The model report counts a sub-process at its call activity.
  • If the sub-process cannot be started, Flower writes an error comment at the calling process instance.
• FEAT: Descriptions. The work item of a call activity is described as Flower Subprocess with the parent process and the parent process instance, in a purple panel. Work items inside a sub-process name their parent process instance. New description placeholder {{flower.parent}}: the key of the parent process instance in a sub-process, empty otherwise.
• CHANGE: The summary of the work item of a call activity becomes Sub-Process Instance of <model> (<node>).
• FEAT: Warning when a call activity is not mapped. If the space and work type of a call activity are not part of the Jira Work Type Mapping, Flower writes a warning at the process instance: the work item is an ordinary task and no sub-process starts.
• FEAT: Modeler. The Jira section of a call activity offers the spaces and work types of the Jira Work Type Mapping, with a link that opens the Jira Work Type Mapping tab of the Flower Settings (the tab was called Work Type Mapping).
• FEAT: Validation.
  • Error: a call activity without its own space and work type (they are not inherited from the lane or the model), or with a combination that is not in the Jira Work Type Mapping.
  • Error: a model that calls itself, directly or through other models. Warning: a called model cannot be loaded.
  • Warning: a task whose space and work type are part of the Jira Work Type Mapping (its work item would start a process).
  • Mandatory fields are not allowed for the work type of a call activity.
• CHANGE - check before updating: call activities in existing models are executed now. Until 3.4 Flower ignored a call activity. Now it creates a work item (with the space and work type of the activity, or the defaults of lane, model and settings if none is set) and the process waits there until this work item is resolved. If a work type is mapped to a model, the work item starts that model as a sub-process. Models that contain a call activity only as a drawing (or an imported one) have to be changed before the update takes effect: use an embedded sub-process for documentation, or give the call activity a space and work type. Models are checked when they are published, but a model that is already published keeps its call activities until you publish it again, and its running and new process instances wait at them. Also, “create all activities” in the process instance view now creates the work items of call activities.
• CHANGE: Jira Data Center: the JQL field flowerActivity is indexed like in Jira Cloud. Jira has to reindex.
• Limitations: a loop back into a call activity is not supported (Flower writes an error comment at the calling process instance and does not reopen the sub-process). A timer boundary event on a call activity sets the Jira due date, but the timeout is not processed yet. Existing tasks that were converted by the Jira Work Type Mapping are not migrated.

Fixes

• FIX: Flower sets the resolution when it resolves a work item. If your workflow does not set a resolution when Flower resolves a process instance (or closes tasks at a terminate end event), the work item had the status Done but no resolution. JQL (resolution is EMPTY), the timer job and the reports then counted it as open, and in Jira Cloud a calling process did not continue after its sub-process. Now Flower sets the resolution (Done, or Won’t Do when a process is terminated). For this the field Resolution must be on the transition screen or the edit screen of the work type, or set by the workflow. If it is on none of them, Flower still resolves the work item and writes a warning comment at the process instance that says what to configure. Applies to Jira Cloud and Jira Data Center.
• FIX: A sub-process continues its calling process exactly once. If continuing fails, Flower writes an error comment at the calling process instance.
• FIX: A work item that is converted into a process instance by the Jira Work Type Mapping is not converted again when Jira delivers the event twice. Before, the second run replaced the link to the calling process and started the process a second time.
• FIX: A sub-process runs on when its calling process instance cannot be loaded; par is empty then, and an error comment is written at the sub-process.
• FIX: Models with a message flow to a pool without a process (a “black box” pool, for example the customer) start again. Such a message flow is only documentation and is ignored. Message flows between pools that both have a process are still not supported. This also fixes the template Manual Automation.
• FIX: Jira Data Center: a task that is resolved by a workflow transition which fires the event Issue Resolved or Issue Closed (the transitions Resolve Issue and Close Issue of the classic default workflow) now continues the process; Issue Reopened is processed as well. The simplified and project management workflows were not affected. Jira Cloud is not affected.
• FIX: SOP numbering: tasks in different branches of a split no longer get the same index. Every branch gets its own level (1.3.1.1, 1.3.1.2, 1.3.2.1).
• FIX: A process instance that is created by the issue-created event now waits until the process engine has finished its first steps.
• FIX: The REST call that returns the BPMN of a model as JSON works again. Errors of the REST API are returned with a message.

[3.4.2] - 2026-10-19

• FIX: Gateway conditions that reference a field the process instance does not have (e.g. a misspelled or not yet available custom field) now write an error comment at the process instance. The process still continues on the default flow as before, but the cause is no longer silent. Fields that exist but are empty are not reported.
• FIX: An error while reporting a problem to the process instance could prevent the engine state from being saved
• FIX: Data Center: requests to and responses from Jira are now handled as UTF-8, special characters such as umlauts in comments, field values and issue data are no longer garbled

[3.4.1] - 2026-10-02

• FIX: Process instances and activities could start without processing the triggering Jira event correctly in Data Center, which could block the Jira workflow transition of the issue
• FIX: Gateway conditions that evaluate the resolution or status of the task that has just been completed now always use the current values
• FIX: Process instance could not be started when a Jira project contains versions (JSON serialization of project data failed)
• FIX: Throw Event web service calls: a full URL and a relative path are both accepted in Data Center, a configured Base URL is no longer prepended to a full URL
• FIX: Failed web service calls in Data Center now create an error comment at the process instance instead of being reported as successful
• FIX: Timer Boundary Events with Terminate End Events could block the process in Data Center
• FIX: Jira REST errors (e.g. 400, 404, 500) are now reported as errors in Data Center, consistent with Jira Cloud
• FIX: Work Type Mapping: newly added rows are no longer shown as “no permission” in Data Center when the Jira space differs from the default space
• FIX: Work Type Mapping: unresolved entries are labeled “no access” or “not available” and keep their stored values when other rows are added or removed
• FIX: Saving the Work Type Mapping can no longer clear the default Jira space and work types in the settings
• FIX: Jira space and work type defined on a lane are now applied to the activities of that lane
• FIX: Throw Event web service calls in Jira Cloud no longer follow redirects and do not report network details in issue comments
• FIX: Dropdown menus for Jira space and work type in the process instance activity table are no longer covered by the following section
• SECURITY: Throw Event web service calls in Jira Cloud are restricted to secure public targets
• BREAKING: Jira Cloud: Throw Event web service URLs must use HTTPS and must not contain credentials
• IMPROVEMENT: Faster processing of Flower events in Data Center (shared JavaScript engine)
• IMPROVEMENT: Flower events are processed in the background in Data Center, so Jira workflow transitions are no longer delayed
• IMPROVEMENT: HTTP requests in Data Center now have timeouts
• IMPROVEMENT: Improved diagnostics for event processing in the Jira log
• IMPROVEMENT: Existing models with a Jira space or work type on a lane now create the activities of that lane there instead of in the default space

[3.4.0] - 2026-05-01

• FEAT: Jira 11 and Java 21 compatibility
• BREAKING: Dropped support for Java 17 (Java 21 is now required)
• UPDATE: Upgraded embedded GraalVM / JavaScript engine for improved compatibility and stability
• UPDATE: Adjusted issue property handling to comply with stricter indexing validation in Jira 11.3
• FIX: Prevented issue creation failures caused by invalid or null property values
• IMPROVEMENT: Refactored HTTP layer to support Personal Access Token (PAT) authentication
• REMOVED: Deprecated TrustedHttp usage (no longer supported in recent Jira versions)
• IMPROVEMENT: Enhanced base URL detection for more reliable operation across environments
• IMPROVEMENT: Stabilized runtime initialization and reduced startup-related edge cases
• IMPROVEMENT: Reduced log noise and improved diagnostics

[3.3.7] - 2026-04-21

• FIX: Hardened authentication for Flower REST endpoints
• FEAT: Made Flower REST authentication reproducible in dev mode and added test coverage
• FEAT: Enabled trust proxy to ensure correct client IP detection (required for express-rate-limit behind reverse proxies)
• FIX: Resolved Data Center deployment error

[3.3.6] - 2026-04-18

• FIX: Data Center release adjustments
• FIX: DC Throw Events could call incorrect external URLs in certain cases
• FIX: Placeholder replacement in BPMN description fields did not resolve nested properties correctly
• FIX: Different editmeta structure in Data Center caused field filtering issues in the issue form tab
• FIX: Add Attachment button in Flower activity view now opens the process instance issue in Data Center
• FIX: Different editmeta service in Data Center caused incorrect mandatory field validation in the BPMN modeler
• FIX: Jira issue link type defined in the BPMN model is now applied when creating links between process instance and activity issues
• FIX: Dependency updates

[3.3.5] - 2026-04-02

• FIX: Link visualisation – model links are now displayed across all BPMN node types, not only tasks

[3.3.4] - 2026-03-25

• FEAT: Added shortcuts to improve model editor usability
• FEAT: Ability to restore a model from a previous version
• FIX: BPMN validation – ensure Jira project is valid for collaboration elements
• FIX: BPMN validation – prevent configurations with mandatory fields in work types
• FIX: Naming – updated terminology from issue types to work types
• FIX: Error handling – improved robustness of API error comments

[3.3.3] - 2025-11-05

• FEAT: Nested placeholder support for descriptions — template fields like {{instance.properties.*}} and {{node.lane.name}} are now supported for richer auto-generated descriptions.
• FIX: API deprecation of /rest/api/3/issue/createmeta
• FIX: API deprecation of /rest/api/3/project
• FIX: API deprecation of /rest/api/3/resolution
• FIX: Use /rest/api/3/ base path for all Cloud REST endpoints
• FIX: atlassian-connect-express migrated to @atlassian/atlassian-connect-express
• FIX: atlassian-jwt migrated to @atlassian/atlassian-jwt
• FIX: Null pointer in BPMN validator at node.transitions
• FIX: ExpressionHandler exception in some TimeoutEvent cases

[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

• FEAT: introduce strict mode (a61e6c6) 

[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

• FEAT: cacheable app iframe (9685f74) 

[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
• 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