The file is in Jira. Finding it is the work.
A release is ready for review. The specification is attached to a story, the approval is on another work item, and the screenshots sit across several bugs. Someone asks for the complete set of files. Before the review can begin, someone has to remember where everything lives.
That is the gap we wanted to address when we expanded Attachment Tags for Jira into view26 Attachment Manager for Jira. Labels remain part of the experience. The revamped app brings together attachment search, bulk actions, folders, sharing, storage reporting, and REST APIs.
At VIEW26, we built this around a practical question: how can teams work with files across Jira while keeping the connection to the work that produced them?
Start with the file, then follow its context
When you know the work item, finding its attachments is straightforward. The harder search starts with a partial filename, an uploader, or the memory that someone added a PDF last week.
Attachment Manager brings indexed attachments into a single view. Search by filename, then narrow the results by project, label, file type, uploader, upload date, or size. Open the source work item when you need the discussion, status, or decisions behind the file.
For example, a project lead preparing a handover could filter to the relevant project and the specification label. A support lead looking for a recent diagnostic file could use the uploader and upload date. The search can begin with the details people actually remember.
Give files a shared vocabulary
A filename describes a file in the language of the person who uploaded it. A label gives the team a consistent way to find it later.
Labels such as specification, approval, and screenshot make useful starting points. Select several attachments and apply the same label in one action. If the label you need does not exist, create it in context and choose a color.
Administrators manage a shared label catalogue. Renaming or recoloring a label updates it everywhere, helping teams maintain a common vocabulary as their work changes.
Agree what each label means. An approval label can help someone locate approval evidence; the work item and the document still provide the context needed to interpret it.
Bring the working set together with folders
Labels describe files. Folders collect the files needed for a particular piece of work.
Consider a release handover spanning engineering, service operations, and a customer rollout. Its specifications, screenshots, and supporting documents may belong to different work items and projects. A folder can bring those attachments together without moving or copying the underlying files in Jira.
Select the files, add them to a folder, and open that folder when it is time to label or download the collection. The original work items retain their attachments and context.
Folders can be shared with people or groups. Jira permissions still determine who can see each file. Sharing a folder does not grant access to an attachment that a colleague cannot otherwise view. This is worth checking with the intended audience when preparing a shared collection.
Act on the files you have found
Finding ten relevant files should lead directly to the next task. Selecting one or more attachments opens a selection bar with actions to download, delete, add labels, or add the selection to a folder.
This connects discovery to everyday work:
- Prepare a handover: find the supporting files, collect them in a folder, and download the selection.
- Organize a review: apply a common label to the selected specifications or screenshots.
- Review cleanup candidates: narrow the results by size, type, or upload date, inspect the source work items, and delete only the attachments your team has confirmed are no longer needed.
The useful change is continuity: search, select, and act in the same workflow.
Make attachment growth visible
Files accumulate one upload at a time. Understanding that accumulation requires a broader view.
The Overview shows attachment volume, storage by project and file type, upload trends, and the largest files. These views help teams decide where to investigate: which projects account for the most storage, which file types dominate, or where upload activity has changed.
A large file may be essential. An old file may still document an important decision. Use the reporting to identify what deserves review, then use the source work item to understand why it is there.
Connect search and labels to your own tools
Some attachment workflows extend beyond the app interface. The REST API lets integrations and automations search attachments and read or change labels.
For teams building their own processes, that creates a way to incorporate attachment discovery and classification into existing tools. Start with a specific requirement, such as finding files that match a naming convention or updating labels as part of a defined review process, and check the API documentation for the supported operations.
Keep files connected to the work
The move from Attachment Tags to Attachment Manager reflects a broader job: helping teams find the files they need, organize them around a shared task, and take action with the relevant Jira context close by.
Explore view26 Attachment Manager for Jira on the Atlassian Marketplace.
Where does your team lose the most time with Jira attachments: finding the right file, assembling a collection for others, or deciding what to keep?
