Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Can attachment filename be read on a Jira Cloud transition screen before allowing the transition?

Can attachment filename be read on a Jira Cloud transition screen before allowing the transition?

Ujwala Vallala
July 21, 2026
Is this achievable in Jira Cloud?

Requirement:

  • If Is It An Existing Contact? = Yes
  • Read the uploaded attachment filename
  • If the filename contains a specific text (for example, "contact" ), allow the transition
  • Otherwise, if uploaded attachment has other name,block the transition and display an error message



I tried using a ScriptRunner "Validate details using a Jira Expression" validator, but the validator fails with "Failed to load condition".

My questions:

  1. In Jira Cloud, is it possible to access the filename of an attachment uploaded on the transition screen from:
    • ScriptRunner Jira Expression validators?
    • ScriptRunner Behaviors?
    • Automation
  2. Can a workflow transition be blocked based on the filename of the attachment being uploaded during that same transition?
  3. If not, is the only option a custom Forge workflow validator/app?

Has anyone successfully implemented attachment filename validation during a transition in Jira Cloud?

1 answer

1 accepted

2 votes
Answer accepted
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 21, 2026

Hi @Ujwala Vallala

For your specific scenario, where the attachment is uploaded during the same transition, I don't believe this is currently possible in Jira Cloud.

Workflow validators, including ScriptRunner Jira Expression validators, cannot reliably inspect the filename of an attachment that is being uploaded as part of the current transition, because the attachment is only available after the transition has been processed.

Similarly, Jira Automation isn't suitable for this requirement, as it runs after the transition completes, so it can react to the attachment but cannot prevent the transition.

If the attachment were already on the issue before the transition, then validating its filename would be a different scenario and could be handled by a validator. However, for attachments uploaded during the transition itself, a custom solution (such as a Forge workflow validator) is likely the only way to enforce this requirement before the transition is allowed.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events