Jira's workflow engine is one of its most powerful features and one of the most common reasons teams hire a Jira administrator. Starlex keeps the same ideas with far less ceremony.
The familiar building blocks
- Transitions between statuses, including global ones that work from any status.
- Conditions that decide who may use a transition: anyone, the assignee, the reporter or project admins, optionally only for some issue types.
- Validators that require an assignee, story points, a due date, an estimate, a description or a comment, or that check sub-tasks are done, nothing blocks the issue and its checklist is complete.
- Screens that ask for a comment or an assignee during the transition.
- Post functions that assign the issue to the mover or the reporter, unassign it, clear its flag or set today as its start date.
A canvas instead of a table
Starlex draws the workflow as boxes and arrows you can drag, connect and label. The layout is saved with the project, so everyone sees the same picture. No schemes, no shared configurations to untangle.
Advisory by default
New projects start with an advisory workflow: the board shows the intended path but does not block moves. When the team agrees on the rules, an admin switches enforcement on. It is the safest way to introduce process: people see the rules before the rules stop them.