Audit Metadata
Available in both the Jira and Confluence versions of the app.
Overview
Script Master records who created and who last changed each item you configure, together with the timestamps. On instances where several administrators or consultants work in the same app, this answers the usual question — who touched this fragment last week, and when? — without an external audit trail.
Audit metadata is tracked for:
Four values are stored per item:
| Field | Meaning |
|---|---|
| Created by | The user who first saved the item |
| Created at | When the item was first saved |
| Updated by | The user who saved the most recent change |
| Updated at | When that change was saved |
Stamping happens on the Forge backend at save time, using the identity of the calling user. It cannot be set, spoofed, or edited from the browser, and there is no way to save an item without being recorded as its last editor.
Where audit data appears
On the module dashboard
Each module's dashboard can show the audit columns. Updated by and Updated at are shown by default; Created by and Created at are hidden by default and can be switched on.
To change which columns are shown, use the Choose columns button above the table and toggle the columns you want. Reset to defaults restores the original set.
Your column choices are stored in your own browser, per dashboard — they are personal preferences, not an instance-wide setting, so changing them does not affect other administrators.
Updated at and Created at are sortable, which is the quickest way to find recently changed items.
In the editor
When you open an existing fragment, gadget, macro, scheduled job, or web trigger, the editor shows an Updated by (user), (date and time) line, so you can see the last editor before making changes.
Items created before this feature
Audit metadata was introduced in a later app release and is stamped only when an item is saved. Items created earlier show an em dash (—) in the audit columns until someone saves them again.
Saving an older item stamps Updated by/at but leaves Created by/at empty — the original creation is not reconstructed, because the information was never recorded.
What is stored
Only the Atlassian account ID and the timestamp are stored with the item. Display names and avatars are resolved on the fly from your Atlassian instance when a dashboard or editor is rendered, so nothing about the user is duplicated in app storage. If a user is deactivated or removed, their account ID may render without a name.
See Data Storage & Security for the full picture of what the app stores.