Schedules are good for work that comes back on a date. Some work comes back on an event instead: a request is approved, a deal is won, a bug is confirmed. For that, you want the structure to appear when the work item moves to a status.
AppsDelivered Templates includes a workflow post function that applies a template set when a work item makes a transition.
Where it works
Post functions belong to Jira workflows. You can add this one to workflows in company-managed spaces. Team-managed spaces use a simpler workflow editor without post functions, so for those, use a schedule, apply the set by hand, or call the app’s API from Jira Automation.
Good places to use it
- HR requests. When “New hire” moves to Approved, apply the onboarding set.
- Change requests. When a change moves to Scheduled, apply the set with the change’s steps and checks.
- Customer projects. When an engagement moves to Signed, apply the kickoff set with the standard first-week work.
- Bugs. When a bug moves to Confirmed, apply the set with reproduce, fix and verify steps.
Set it up
- Open the workflow for the work type in Jira’s workflow editor.
- Pick the transition, such as Approve.
- Add a post function and choose the app’s apply template post function.
- Pick the template set and save. Publish the workflow.
Test it on a copy of the workflow first if the workflow is shared by many spaces.
Keep the trigger visible
A post function runs quietly, which is the point, but it can surprise people. Add one line to the transition’s description or your space’s how-to page: “Approving this request creates the onboarding epic.” People trust automation they can see.



