Keep the work and its owner together.
Assign unassigned work to the member who moves it to In progress. The rule checks the recorded event and current access before adding them.
Automations & templates · Repeatable work
Good habits.
Less chasing.
Keep the small follow-ups moving. Let reviewed rules handle familiar work changes, and give the next project a starting point your team has already thought through.
Picked it up?
Make it yours.
A project rule for work with no assignee.
WHEN
A member moves work to In progress.
ONLY IF
Nobody is assigned when the rule runs.
THEN
Add the member who made that move as an assignee.
Review the rule Enable this version
A small rule, a useful habit
When this happens,
take the next step.
Choose an event, narrow the work it applies to, and put the actions in order. Start with a project rule or manage a wider scope from workspace administration.
Give blocked work a way back.
When a bug becomes blocked, start watching it and schedule an in-app reminder for the rule owner. Choose the delay that fits the team's response.
Keep the right people in the picture.
Watch newly created work, add labels, or notify accessible teammates when a matching work change, milestone event or linked GitLab event arrives.
Illustrative workflows using supported triggers and actions. Rules run after future matching events are processed in the background.
See the effect before enabling it
Build the rule.
Review the change.
Guided editing lets you choose projects, stages, labels and people by name. Switch to JSON for advanced definitions and rules spanning several projects.
Both views share one definition. A preview checks current work; it does not execute actions or replay earlier events.
- 1
Preview, then save a draft.
Inspect matching work and proposed changes. Saving preserves the definition while you decide whether it is ready to run.
- 2
Enable the version you reviewed.
Review the saved rule and preview its current version before enabling. Editing an enabled definition returns it to draft for another review.
- 3
Follow what actually happened.
Open Runs for results and diagnostics for each target. Pause the rule when the process changes, or archive it when its job is done.
Templates · A considered starting point
Start from experience.
Make it your own.
A release checklist, a standard milestone, a familiar project setup. Store the structure once, preview it in its destination, and apply it to create new work your team can adapt.
Bring the guidance with itA project with its context.
Start a new project with labels, knowledge folders and pages, milestones and a work hierarchy. Choose its workflow and visibility when applying it.
A milestone with its work.
Reuse a milestone and its associated work in an existing project. Preview the resolved dates and workflow stages before creating the objects.
A checklist for the next task.
Carry reusable context, acceptance criteria and supported Required Context procedures into new work. Workspace Task templates can also target an eligible Team.
Reusable does not mean identical
The structure repeats.
The decisions stay yours.
Template previews show the objects, destination and actual dates before you apply them. Relative dates count calendar days, including weekends, so review where they land.
Applying creates new objects. Publish a new immutable template version when the process improves; work created from an earlier version keeps its existing content.
Choose people and access for the new work. Templates carry reusable structure and guidance; assignments, credentials, attachments and conversation history belong to the individual instance.
A few useful details
Before the first rule.
Who can manage rules and templates?
Administrators manage workspace rules and templates. Administrators and the project creator can manage them within that project. These features must be enabled for the installation; running a rule uses its owner's current permissions.
What actions can an automation take?
Move, complete or reopen work; add labels or assignees; change watchers; set a reminder; or send an in-app notification. The current definition format supports those workspace actions rather than arbitrary scripts, outbound webhooks or email bodies. Read the definition reference.
Do GitLab events work with rules?
Yes, linked merge-request and pipeline activity can trigger rules when the GitLab integration is configured. Conditions can narrow the relevant event state, and the rule still follows current work access. Explore integrations.
Will applying a template also trigger automations?
Template events are excluded by default. Include them explicitly when that is part of your process, then preview and review the updated rule. Automation-originated events also need explicit inclusion and have a limited chain depth.
How do plan limits and previews work?
Automation runs use the plan's monthly allowance. A rule preview shows a sample of at most 50 authorized targets and does not run actions. A template preview also needs to remain current before application. Compare the current allowances.
Do templates need JSON?
Template definitions are currently edited as JSON, with a starter definition for the selected type and a resolved preview before application. Automations offer both Guided and JSON editing. Follow the template walkthrough.
Less process to remember.
More work to move.
Keep the repeatable parts ready, and give your team space to decide what this particular piece of work needs.
Explore work managementCOME TAKE A LOOK
A little less busy.
A lot more together.
Curious? Leave your email. We’ll keep you posted on early access and what’s new.