Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is it possible to force attachment on issue creation?

Is there a way to make attachment required on issue creation? 

2 answers

1 accepted

0 votes
Answer accepted
Rilwan Ahmed Community Leader Mar 02, 2022

Hi @Hadas Hamerovv ,

You can also do it using JIRA Suite Utilities - Field Required Validator. Its free plugin for server editions and paid for Data centre. 
After Installing the plugin, Open the required workflow, click edit, switch to diagram mode. For the transition "Create", add validator "Field Required Validator" and select "attachments" field. 

FYI, in Cloud jira, there is system Field Required Validator.

0 votes

Out of box no, but there is a ScriptRunner solution from Mark Markov here:


I'm not sure whether there are certain plugins that can implement a regular validator on Create without any groovy scripts - I wouldn't rule it out since it can be done, but at least I haven't come across one. So if you have ScriptRunner then the above suggestion might do the trick for you, if not, then I'll leave the floor for others.

I believe this code is only for Server and will not work on cloud.

However, yes, I forgot from the option of adding a validator to the creation. That solves the problem.

Then I'll tag it as cloud - the 'Jira Core Server' had me thinking otherwise.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events