--- title: "Status Workflow Plugin for Orangescrum Self-Hosted" description: "Design task statuses, allowed transitions, transition permissions, and validation rules in Orangescrum self-hosted. 26 workflow templates included." canonical: https://www.orangescrum.com/self-hosted/plugins/status-workflow --- # Status Workflow Plugin for Orangescrum Self-Hosted > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). 1. [Home](/) 2. › 3. [Self-Hosted](/self-hosted) 4. › 5. [Plugins](/self-hosted/plugins) 6. › 7. Status Workflow # Status Workflow by [Orangescrum](/) · Productivity Self-HostedVerifiedProcess Control A workflow designer for task statuses. Draw the statuses and the arrows between them, and only those moves are permitted. Attach permissions so a move belongs to named roles or people, attach rules so a move needs a comment, a filled field, or a merged pull request, and attach a screen so the person making the move is asked for what the next stage needs. Enforcement runs on the server, so the task form and the Kanban board are held to the same rules. Installs Available Active deployments Support Vendor Supported Priority response Trust Self-Hosted Your infra, your data $499/year Per company • Add-on to any Self-Hosted plan [Buy & See All Plans](/self-hosted/pricing#addons)[Talk to Sales](/contact-sales) - Visual designer for statuses and allowed transitions - Per transition permissions by role or named user - Rules for required fields, comment, minimum age, and role - Git rules: linked branch, commit, open or merged pull request - Transition screens that ask for what the next stage needs - Post functions: auto assign, set a field, send a notification - 26 ready made workflow templates across 11 categories - A workflow per project, or a different one per milestone Pairs with [Self-Hosted Core ($1,500/yr) or Business ($2,250/yr)](/self-hosted/pricing) [Overview](#overview)[Features](#features)[About](#about)[Install](#install)[FAQ](#faq) ## Screenshots Workflow designer with statuses and allowed transitions Transition detail with permissions, rules, and a screen Template gallery across 11 categories ## Key Features ### Visual Workflow Designer Lay the statuses out on a canvas, draw the arrows between them, and save the positions. The diagram is the workflow itself, not a picture of one kept somewhere else. ### Custom Statuses Add, rename, reorder, and remove the statuses a workflow uses, and give each one a colour so the board reads at a glance. ### Allowed Transitions Only A move with no arrow behind it is refused with a reason. A workflow with no transitions defined stays permissive, so installing the add-on does not freeze work in progress. ### Transition Permissions Attach roles or named users to a transition. Anyone without it sees the move refused, on the task form and on the board alike. ### No Owner Bypass Workflow rules are process, not access control, so owners and administrators follow the workflow they defined. A permission on the transition is the way to grant an exception. ### Validation Rules A move can require named fields to be filled, a comment on the transition, a minimum age in the current status, or a specific role. ### Git Backed Rules A move can require the task to have a linked branch, a commit, an open pull request, or a merged one. The state is read live from the provider through the Git Sync add-on. ### Transition Screens Ask for the fields the next stage needs at the moment of the move, instead of hoping somebody fills them in afterwards. ### Post Functions After a move succeeds, auto assign the task, set a field, or send a notification, without anybody having to remember. ### Conditions on Offer Conditions decide whether a transition is offered at all, based on whether an assignee is set, a field value, or how long the task has sat in its current status. ### 26 Workflow Templates Start from a ready made workflow: software development, bug triage, code review, pull request, support ticket, recruitment, sales pipeline, invoice approval, ITIL incident and change, and more. ### Clone and Adapt Clone any workflow, including a template, and edit the copy. Names are checked as you type so you do not end up with two workflows sharing one name. ### Honest Status Pickers The status dropdown asks the server which moves this person may make on this task, so it only ever offers moves that will actually succeed. ### Milestone Level Workflows A milestone can carry its own workflow, which takes precedence over the project's. A task moved into that milestone is remapped to the first status of the milestone workflow. ### Enforced on Every Path The rules run in the save pipeline and in the Kanban drag handler, so a card dragged across the board is checked exactly like a status changed on the form. ### WIP Aware With the WIP Limits add-on installed, a hard limit on the target column is checked as part of the same transition and the move is refused with the count and the limit. ## About this plugin ### Why Status Workflow for Orangescrum? A status list is not a process. Without rules, anything can go anywhere, a task jumps from open to done with no evidence, and nobody can say afterwards whether the steps were followed. This add-on turns the status list into a defined workflow: which moves exist, who may make them, and what has to be true first. ### Draw it, then it is real The designer is a canvas. Statuses are nodes, transitions are arrows, and positions are saved so the diagram stays readable. Once a workflow has transitions, only those moves are allowed. A workflow with none defined stays permissive, which means you can install the add-on and adopt it project by project instead of all at once. ### Who may move it, and what has to be true Each transition carries permissions by role or by named user. Each transition can also carry rules: required fields, a comment on the move, a minimum age in the current status, a role restriction, or a Git condition such as a linked branch, a commit, an open pull request, or a merged one. Conditions can hide a transition entirely until it makes sense to offer it. ### Ask at the moment, and act afterwards A transition screen collects the fields the next stage needs while the person is making the move, rather than leaving a gap somebody chases later. Post functions run once the move succeeds: assign the task, set a field, or send a notification. The work of keeping a process consistent moves from people to the workflow. ### Rules that hold on every path Enforcement sits in the save pipeline and in the Kanban drag handler, so a card dragged across a board is checked exactly like a status changed on the task form. Owners and administrators are not exempt, because a workflow is process compliance rather than access control. If somebody genuinely needs an override, grant it as a permission on the transition where it belongs. ### Start from a template Twenty six templates ship with the add-on across eleven categories including software, Git and code review, generic Kanban, marketing, HR, sales, support, operations and approvals, finance, product and design, and ITIL. Clone one, rename the statuses, adjust the arrows, and you have a workflow that fits without starting from an empty canvas. There is a wider feature overview at /custom-status-workflow. ### What's included - Visual designer for statuses and transitions with saved node positions - Add, edit, reorder, colour, and delete custom statuses per workflow - Allowed transition list per workflow, with from any and to any support - Permissive fallback when a workflow has no transitions defined yet - Transition permissions by role and by named user, with a user search - Condition rules: assignee set, field value check, minimum time in status - Validator rules: required fields, comment required, minimum age in days, role restriction - Git validator rules: link required, branch present, commit present, pull request open, pull request merged - Post functions: auto assign, set a field, send a notification - Transition screens with a configurable field list - Server side enforcement in the save pipeline and in the Kanban drag handler - Allowed status endpoint so pickers only offer moves that will succeed - No owner or administrator bypass, by design - 26 workflow templates across 11 categories - Template preview, clone into your company, and duplicate an existing workflow - Duplicate workflow name checking - Project level workflow assignment with milestone level override - Automatic status remap when a task moves into a milestone with its own workflow - Optional WIP limit enforcement through the WIP Limits add-on - Multi-tenant company-scoped data isolation ### Compatibility Requires the Orangescrum Self-Hosted edition running PHP 8.2+, CakePHP 4.6+, and PostgreSQL 16. The plugin folder is StatusFlow and it is gated by the STATUS\_FLOW\_ENABLED flag in config/constants.php. The diagram editor is a Vue application bundled with the plugin and built with npm. Git backed rules read live provider state through the Git Sync add-on and are skipped when it is not installed. WIP enforcement is delegated to the WIP Limits add-on when that is loaded. Multi-tenant aware, so every transition, permission, rule, and screen is company-scoped. ## Installation A self-hosted install takes a few minutes. Buy the add-on, drop the plugin into your `plugins/` directory, run the migrations, and you're live. 1. 1 ### Buy the add-on Purchase the Status Workflow add-on from /self-hosted/pricing at $499/year per company, payable annually. 2. 2 ### Drop the plugin into your install Copy the StatusFlow/ folder into plugins/ on your self-hosted Orangescrum server. 3. 3 ### Enable the feature flag and register the plugin Add \`define('STATUS\_FLOW\_ENABLED', true);\` to config/constants.php and register \`StatusFlow\` in src/Application.php with \`routes => true, bootstrap => true\`. 4. 4 ### Run the database migrations Run \`bin/cake migrations migrate --plugin StatusFlow\` to create the transition, transition rule, transition permission, and transition screen tables. 5. 5 ### Build the workflow designer Run \`npm install\` then \`npm run build\` in plugins/StatusFlow/vue-app so the diagram editor assets are compiled. 6. 6 ### Create your first workflow Open Workflow Settings, clone one of the 26 templates or start from scratch, then draw the statuses and the arrows between them. 7. 7 ### Add permissions, rules, and screens For each transition decide which roles or people may make it, which rules have to pass first, and whether a screen should collect fields at the moment of the move. 8. 8 ### Assign the workflow and test a move Assign the workflow to a project, or to a milestone if that stage needs its own. Then try a move from the task form and by dragging a card on the Kanban board. ## Frequently Asked Questions ### What happens to our existing projects the day we install this? ▾ Nothing changes until you define transitions. A workflow with no transitions configured stays permissive and every move is allowed exactly as before. That lets you design and adopt workflows project by project rather than freezing work while you plan. ### Can administrators skip the workflow? ▾ No, and that is deliberate. Workflow rules are process compliance rather than access control, so owners and administrators follow the workflow they defined. If a role genuinely needs a shortcut, grant it explicitly as a permission on the transition that needs it. ### Is there multi-level approval routing in this add-on? ▾ No. A transition carries permissions and rules, so it can require a particular role and a comment before a move, but it does not build sequential or parallel approver chains with sign-off records. Multi-level approval chains live in the Document Management and Risk Management add-ons. ### Do the Git rules work on their own? ▾ Only partly. Whether a task has a linked repository record can be answered from stored data, but branch, commit, and pull request state are read live from the provider through the Git Sync add-on. Without Git Sync connected there is nothing to read, so those rules should not be relied on. ### Does dragging a card on the Kanban board follow the rules? ▾ Yes. The Kanban drag handler calls the same transition check as the task form, so an unpermitted move, a failed rule, or a hard WIP limit refuses the drag with the same message a form save would have shown. ### Can different parts of a project use different workflows? ▾ Yes. A workflow is assigned to a project, and a milestone can carry its own workflow which takes precedence. When a task is linked to such a milestone and its current status does not belong to that workflow, it is remapped to that workflow's first status. ### Do we have to design a workflow from scratch? ▾ No. Twenty six templates ship with the add-on across software, Git and code review, generic Kanban, marketing, HR, sales, support, operations and approvals, finance, product and design, and ITIL. Preview one, clone it into your company, and edit the copy.