Jira administrators can open Jira settings → Apps → Attachment Manager. The settings page contains Labels, Projects, REST API and About.
Choose tracked projects
-
Open Projects and use Search projects to locate a project.
-
Enable tracking for the projects you want Attachment Manager to index.
-
Check the row’s indexing status and Last indexed value. Attachment count and Storage help confirm the indexed coverage.
Only tracked projects appear in Attachments, Folders and Overview. Tracking a project does not grant anyone Jira access; the caller’s work-item visibility still applies. After changing tracking, allow indexing to complete before checking results.
Refresh summary data
Projects includes Rebuild rollups to recompute aggregate counts and storage. Use it when summary figures need refreshing, then check the status and timestamps. It is a summary maintenance action; it does not upload or recreate Jira attachments.
Configure the storage comparison
Open About, choose the appropriate Jira plan under Site storage allowance, and save. The app uses this allowance to calculate Overview’s storage comparison because Jira does not expose the quota directly. An unconfirmed value is shown as assumed.
Enable REST API integrations
The REST API tab explains site enablement, the required OAuth scopes and integration setup. The API must also be enabled in Atlassian Administration for the exact app installation. Follow the linked guide for the full workflow and request examples.
Overview and storage reporting
Troubleshoot missing or stale data
|
Symptom |
Check |
|---|---|
|
Project missing from the app |
Is tracking enabled, and does the user have Jira access? |
|
New attachment missing |
Has the project finished indexing, and has the new upload had time to be processed? |
|
Labels appear but counts lag |
Read the usage “as of” timestamp; totals update in the background. |
|
Storage percentage looks wrong |
Confirm the plan allowance in About. |
|
API endpoint returns 404 |
Check the environment/base URL, tracked project, indexing and consenting user’s visibility. |