AttachPulse for Jira
Named attachment fields for Jira Cloud: slots such as "Signed contract", "Invoice PDF" or "Site photos", with rules, a workflow validator and JQL. By PuzariCloud. Runs on Atlassian.
What it does
- Adds a custom field type, Attachment slot (AttachPulse). Create as many slot fields as you need.
- On the issue, users open the field and tick files that are already attached to the issue. Images show thumbnails.
- Each field context has rules: allowed file types, maximum size per file, minimum and maximum number of files, and a hint for users. Jira enforces them when the field is saved.
- The issue view shows the slot's files as file cards with download, plus image thumbnails.
- The workflow validator Attachment slot has files (AttachPulse) blocks a transition until a slot holds at least N files of the types you choose.
- Slots are searchable with JQL.
Set up a slot
- Go to Settings > Work items > Fields and choose Create new field.
- Pick Attachment slot (AttachPulse), give it a name (for example Signed contract) and add it to the screens of your projects.
- Open the field's Contexts and default value page and choose Edit custom field config (the AttachPulse rules). Set allowed types (for example
pdf), maximum size, minimum and maximum files, and an optional hint. Tick Single file slot for a one-file field. Save.
Fill a slot
- Attach the file to the issue the normal way: the paperclip Attach button, or drag and drop.
- Click the slot field. AttachPulse lists the issue's attachments, newest first. Files that break the rules are greyed out with the reason (wrong type, too large, limit reached).
- Tick the files that belong in the slot and press Save. Press Refresh if you attached a file after opening the field.
On the create screen, the slot explains that files are picked after the issue exists, because a new issue has no attachments yet. The slot also works on transition screens.
Block a transition until files are in
- Edit the workflow, select the transition (for example Approve) and add the validator Attachment slot has files (AttachPulse).
- Choose the slot, the minimum number of files and, optionally, the file types that count (for example only PDFs). You can write your own error message.
- Save the workflow. The transition now fails with your message until the slot holds enough matching files that are still attached to the issue.
The validator works in company-managed and team-managed projects.
Search with JQL
| Query | Finds |
"Signed contract" is EMPTY | Issues whose slot has no files |
"Signed contract" is not EMPTY | Issues whose slot is filled |
"Site photos.Count" >= 3 | Slots holding at least 3 files |
"Invoice PDF.FileType" = pdf | Slots holding at least one PDF |
"Signed contract.FileName" ~ acme | Slots with a file whose name contains the word "acme" |
"Signed contract" ~ "msa" | Text search across the whole slot value |
The search list and CSV exports show the slot as a comma-separated list of file names.
Good to know
- Files stay normal Jira attachments. A slot points at attachments of the same issue. The files still show in the issue's Attachments section, and Jira's attachment permissions apply.
- Deleted attachments drop out. If someone deletes an attachment, it leaves the slot the next time the issue is opened. The validator only counts files that are still attached.
- Minimum files applies once a slot has files. To require a slot, make the field required or use the validator.
- Up to 50 files per slot.
- Uploading directly into a slot is not in version 1. Attach the file to the issue first, then pick it. Direct upload is planned for a later version.
- The rich editor and file cards appear on the issue view and on transition screens. Boards, the list view, bulk edit and email show the file names.
- Jira Service Management portal screens and Jira mobile show the file names only.
Moving from Kepler Attachment Fields
Kepler "Attachment Fields | Simple & Multiple" is built on Atlassian Connect, which no longer gets new features and will lose support. AttachPulse is built on Forge and runs on Atlassian. To move:
- Install AttachPulse and create one slot field for each Kepler attachment field, with the same name and rules.
- Add the new fields to the same screens and contexts.
- Files attached through Kepler are ordinary issue attachments, so they are still on the issues. Open an issue and pick them in the new slot. AttachPulse cannot read Kepler's stored field values, so this step is manual. For many issues, ask us about a scripted move through the REST API.
- Replace Kepler workflow conditions or validators with Attachment slot has files, then remove the Kepler fields.
Security and data
AttachPulse runs on Atlassian Forge and makes no calls outside Atlassian. The slot value (attachment IDs, file names, sizes and types) is stored by Jira in the custom field, like any other field value. The app has no database of its own and stores no personal data. See the privacy policy.
Support
Email support@puzaricloud.in. We reply within two business days.
Coming from Kepler Attachment Fields? See how it compares.
How to add an attachment custom field in Jira