Administration
APM+ settings are under Jira settings → Apps → APM+ settings (Jira administrators). Save applies the whole page.
Assets mapping
- Applications: the Assets object type that holds your applications, and the attributes for the fields APM+ keeps in step with Assets (Description, Tier, Status). With JSM's application template these are
a_description,a_tieranda_status; leave a field unmapped to keep it in APM+ only. - Business services: the Assets object type for services, and optionally its service ID attribute (to match tickets' Affected services) and tier attribute.
APM+ doesn't add attributes or object types to Assets.
Permissions
| Who | Can |
|---|---|
| Viewers | Everyone with Jira access, or only members of a viewer group if you set one. |
| Editors | Members of the editor group (default apm-plus-editors): create and change records, import, run reviews. |
| Jira administrators | Everything, including APM+ settings. |
Changes to an application's Assets fields are made as the person editing, so Assets permissions also apply.
Reviews
The service desk and request type for review requests, Create review request type, and the weekly reviews switch. See Stakeholder reviews.
Ticket counting
The Assets fields (for example "Application impacted") and the Affected services field that link tickets to applications, plus which issue types count as incidents and changes. APM+ suggests these on install.
Obsolescence alerts
The project and issue type for end-of-support alert tickets, and whether to add Business Owners as watchers.
Background jobs
| Job | Runs | Does |
|---|---|---|
| Assets sync | Daily, and Sync now | Brings in new applications and changes made in Assets; flags applications deleted there. |
| End-of-life catalogue | Daily | Refreshes the bundled support dates. |
| Obsolescence alerts | Daily | Raises alert tickets (when switched on). |
| Findings | Daily | Rebuilds rationalisation findings. |
| Reviews | Weekly | Raises review requests (when switched on); approvals are recorded as they happen. |
| AI suggestions | Weekly | Duplicates and capability mappings (when switched on). |
Compare with Assets
Compare now reads every application object in Assets and reports how many are in Assets, in APM+ and in both; which are only in Assets (the next sync brings them in); which are gone from Assets; and which were never linked. Links open the Applications list filtered to each group.
Lookups
Edit APM+'s reference lists: stakeholder roles, licence models, cost categories, risk types and ratings, and application tiers for assessments. Lifecycle statuses follow Assets.
Upgrading from an earlier version
APM+ versions before 4 kept their data in attributes they added to Assets. On those sites APM+ is read only until an admin runs the upgrade in APM+ settings:
- Run Sync now and let it finish.
- Start the upgrade. APM+ moves lifecycle onto your Assets statuses (Planned → Pending, Live and Sunset → Active, Retired → Archived), copies document links into APM+, and writes each application's description, tier and status to Assets' own attributes. Keep the page open; it shows progress.
- Optionally, Tidy up Assets removes the attributes APM+ created earlier (only ones APM+ created). This deletes their values from Assets and can't be undone; APM+ already holds the data.
Licensing, uninstalling and your data
- If the licence lapses, APM+ shows a message and its scheduled jobs pause; nothing is deleted.
- Export anything you want to keep before uninstalling: uninstalling removes APM+'s stored data (Atlassian deletes it in line with its Forge data policies). Your Assets objects stay in Assets.
- Data stays on Atlassian's platform. See Trust & Security and the Privacy Policy.