Set up the scope and the owner field
Requirements
- Jira Service Management with Assets (Standard, Premium or Enterprise).
- A Jira administrator to install and configure the app. Owners only need access to Jira.
Where to find the app
After installing, open Settings → Apps → Vouchline for Assets. The page has five tabs: Overview, Setup, Campaigns, Leavers and Evidence. The Overview tab shows a “Get started” checklist until the first campaign is running.
1. What to review
- Assets schema — the schema that holds the assets owners should confirm, for example laptops and phones.
- Narrow down with AQL (optional) — for example
objectType = Laptops. Leave it empty to review the whole schema. The page counts the matching assets as you go. - Access check — the page shows whether the app can read the schema. The scan sees exactly what this check sees.
2. Who owns each asset
Choose the object type that holds the owner field and the field itself. Two layouts are supported:
- A user field on the asset, for example “Owner (user field)”.
- A reference to a person record whose user field points at the account, shown as “Owner → User (owner is a person record)”. Atlassian's IT Employee Assets template uses this layout.
Used by (optional) is the person who uses the asset day to day. It is used only to find assets held by people who have left (rule AS3).
If the AQL is empty and the schema holds other object types (consumables, software), the page warns that the whole schema will be scanned: objects without an owner field would all count as “without an owner”. One click on Use objectType = … narrows the scope to the type you chose.
Click Save scope. Then run the first scan from the Overview tab.
3. Schedule
- Scan every night keeps the findings up to date, especially assets held by people who have left.
- Scheduled campaign — off, every quarter or every year, from a date you choose; owners get the number of days you set. A scheduled campaign is built from that night's scan, and only from a complete one.