Weekly review
Review open work with your team at the same time each week.
1 work item, 3 subtasks · Every Friday
See the template setEach run creates a Task for that month's review and six subtasks under it, one for each system your team checks. Every subtask is assigned to the reviewer, so each check has an owner from the first day.
Six systems is a starting point. Rename a subtask, add one for a tool you run, or remove one you don't use. Edit the template set, not the work items it created, so next month's run gets the change too.
$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 | Access review, plus the run date |
$reviewer | Assignee of each subtask; a user variable you add | Priya Nair |
$today is built in. You add $reviewer to the template set as a user variable, then use it as each subtask’s Assignee. When you apply the set by hand, the app asks who the reviewer is.
Use one way, or more than one. Each way creates the same structure.
Monthly, on the first day, at 09:00 in your time zone.
The app lists upcoming runs, so you can see the next review before the app creates it.
Apply it from the app before an audit.
The app asks who the reviewer is, so an extra review follows the same steps as the monthly one.
Call the app's API from a rule.
Use this when an event in Jira, such as a field change, should start the work.
IT and security leads who run access reviews, and Jira admins preparing for an audit.
It suits teams that already track their work in Jira and want every month’s review to have the same steps, the same owner and the same start date.
If your identity tool already records access reviews, link those records instead of copying them into Jira.
Keep one record of each review in one place. Two copies drift apart, and then someone has to decide which one is right.
Yes. Change the schedule to another monthly time, or write your own CRON schedule, in your time zone.
The person you saved as $reviewer with the schedule.
No. It gives your team the same review steps every month, with an owner and a record in Jira. Your auditor decides what counts as evidence.
Other template sets that teams use alongside this one.
Building Jira apps since 2017.