Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Attachment validator not working as expected

jessica_huebner
Contributor
August 18, 2025

In my workflow, I have a condition that checks the value of a field. If the value is equal to a certain option, an attachment is required, else no attachment is required. The workflow is not working as expected. Here's the issue:

Condition/Validator

Condition: User Notification Required? = Yes - All Staff

Validator: Attachment "field" required

 

Expected Results

Attachment is attached. User can transition to the status without issue.

 

Actual Results

Error message still thrown, despite the attachment existing on the issue.

 

How can I alter my workflow to get this to give me the expected results? NOTE: I must rely on native Jira features. I have no interest in using 3rd party apps/add-ins like script runner. If this is not possible with native Jira functionality, that's ok, just need to know.

Thanks in advance for your help!Attachment error.pngAttachment.pngCondition.pngValidator.png

1 answer

1 accepted

0 votes
Answer accepted
Aaron Pavez _ServiceRocket_
Community Champion
August 18, 2025

Hi @jessica_huebner 

Can you add the attachment to that screen? The validator is looking for the attachment in that screen, not the one you've already have in the work item.

You can add the Attachment field to that screen.

Regards

jessica_huebner
Contributor
August 18, 2025

Hey @Aaron Pavez _ServiceRocket_ thank you, this did work.

Is this the only way this validator will work? My worry is my users may attach before they get to this screen. The end result I feel is confusing. Attachment already exists, yet it asks for it again. When I do this, the work item now has 2 of the same attachments.

This also seems to be a bit of a variance in system behavior - my other validators can be filled in beforehand without issue, The attachment on the other hand, seems like a user must submit during the transition (not before like they can with other fields). Do you know why this is?

Thanks so much for your help!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events