Monthly access review
Check who has access to what, every month, with one subtask per system.
1 work item, 6 subtasks · Monthly
See the template setEach run creates one work item for the week, dated with the day it runs, and three subtasks for the agenda. The person who runs the meeting owns the review, and each agenda step goes to whoever does it.
Because the review creates itself, the habit survives busy weeks. Last week’s review is one search away, so decisions don’t get made twice.
$todayTaskThe 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 |
|---|---|---|
$today | The date of the run, in the summary | Weekly review, plus the run date |
$host | Assignee of the review; a user variable you add | Marco Ruiz |
$today is built in. On a scheduled run, the app uses the $host value you saved with the schedule.
Use one way, or more than one. Each way creates the same structure.
Weekly, Friday, 09:00 in your time zone.
The calendar view shows the next runs, so you can check the schedule before the first one.
Apply it from the app when the work starts.
The app asks for any variables, so each run carries its own details.
Call the app's API from a rule.
Use this when an event in Jira, such as a field change, should start the work.
Team leads and project managers who run a weekly check-in and want it to happen even in busy weeks.
It suits teams where decisions get lost between meetings, or where people who miss the meeting never hear the outcome.
If your team already reviews work in a daily standup, a weekly review may repeat it. Use it for the wider look ahead.
For a meeting with no actions, a calendar invite is enough. Use the set when the review produces work.
Yes. Pick any day and time for the weekly schedule, or use a custom CRON schedule, in your time zone.
Close that week’s review without doing it, and keep the schedule running. The history shows the week was skipped on purpose.
Yes. Copy the idea into a second template set with a monthly schedule and a longer agenda.
Other template sets that teams use alongside this one.
Building Jira apps since 2017.