New product feature process
Take each feature from idea to release the same way.
1 epic, 3 work items · On request
See the template setEach run creates an epic for one video and three work items under it, one per stage. The writer, the editor and the person who publishes each get their own work item, so a video never stalls because no one knew it was their turn.
Add checklists to each work item for the small steps that get forgotten: captions, a thumbnail, the link in the description. The checklist arrives with every new video.
$videoTitleEpicThe line under each item is a suggested scope. Write your own in each work item's description.
Variables fill in what changes from run to run. They work in text fields, such as the summary and description. A user variable fills in a person field, such as Assignee.
| Variable | What it fills in | Example |
|---|---|---|
$videoTitle | The epic's summary; a text variable you add | How to apply a template set |
$nextWeek | A date a week from the run, in a description | The target publish date |
$videoTitle is a custom variable the app asks for. $nextWeek is built in.
Use one way, or more than one. Each way creates the same structure.
Apply it from the app when the work starts.
The app asks for any variables, so each run carries its own details.
Weekly, if you publish every week.
Save the variable values with the schedule, and a new video epic arrives each week.
Call the app's API from a rule.
Use this when an event in Jira, such as a field change, should start the work.
Marketing and content teams that publish video on a regular rhythm, such as product walkthroughs or a weekly show.
It suits small teams where one person does several stages and needs to see what is next.
For a one-off production with an agency, the agency’s own process will matter more than a template.
If your videos are planned in a content calendar tool, link each epic to its calendar entry rather than keeping two schedules.
Yes. Rename the work items to match your stages, such as book the guest, record and publish. The structure stays the same.
Yes. Set the same Assignee on each work item, or add a user variable so the app asks who owns the video.
Attach drafts and final files to the work item for that stage, or link to where they are stored.
Other template sets that teams use alongside this one.
Building Jira apps since 2017.