Workflow Action Examples (In-app)
Browse in-app workflow action scripts that create subtasks, transition parents, send Slack notifications, link follow-up work, assign role members, clear fields, add comments, and copy field values.
The following examples are available in-app via Example scripts when you're configuring Workflow actions. You can copy these scripts, adapt the logic to your own workflows, and attach the workflow actions to the relevant transitions in your workflow.
Create a subtask when a work item is transitioned
Automatically create a subtask (for example, Analysis) when a non‑subtask work item moves through a workflow transition.
Why it's useful: Ensures that standard follow‑up steps are always captured at specific stages (such as analysis, QA, or deployment tasks), reducing the chance that important work is forgotten and helping you enforce a consistent process across teams.
Transition the parent when all subtasks are resolved
Automatically transition a parent work item (for example, using the Resolve Work Item transition) once all of its subtasks are resolved.
Why it's useful: Keeps parent items in sync with the actual state of their subtasks, removing the need for manual status updates. This improves reporting accuracy (for example, epic or feature completion) and makes boards and dashboards reflect real progress.
Send a Slack notification
Send a Slack notification via an incoming webhook whenever this workflow action runs, including the work item key, new status, summary, triggering user, and a link back to Jira.
Why it's useful: Keeps teams informed about important workflow transitions (such as moving to Ready for QA or Blocked) directly in Slack, so they can react quickly without constantly checking Jira. This is especially helpful for distributed teams or time-sensitive work.
Create and link follow-up work items
Create a follow-up work item (for example, a new task in the same space with a prefixed summary) and link it to the original work item when this workflow action runs.
Why it's useful: Captures the next piece of work (such as follow-up bugs, maintenance tasks, or rollout activities) at the moment a workflow step is completed, while preserving traceability between the original and follow-up items for auditing and reporting.
Assign to role members
Set the assignee of a work item to a user from a specified role (for example, assign to the last user in the Developers role for the current space) when this workflow action runs.
Why it's useful: Automates handoffs between roles at key workflow steps, such as from Triage to Developers, or from Testing to Release Managers, so work items move smoothly to the right person or team without manual reassignment.
Clear fields
Clear one or more fields, named in the settings at the top of the script, when this workflow action runs. List fields such as labels and components are emptied, and every other field is unset.
Why it's useful: Removes values that shouldn't carry over to the next stage, such as an approver or a due date when work is sent back for rework, so nobody is misled later by a value that no longer applies.
Add a comment
Add a comment when this workflow action runs, naming who made the transition and when. You set the wording, the date format, and the time zone in the settings at the top of the script, and you can post the comment internally on a service project so customers can't see it.
Why it's useful: Leaves a record on the work item itself, so anyone reading it later can see who moved it and when without opening the history. Useful for approvals and handovers that need to be visible to the whole team.
Copy a field value
Copy one field into another on the same work item when this workflow action runs. You name the source and target fields in the settings at the top of the script, and they should be the same type.
Why it's useful: Keeps a second field in step with the first without anyone retyping it, such as capturing who the reporter was at the point of a transition so later changes don't overwrite the record.