Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

"Affects Version/s" field is required error

I am facing an issue w.r.t Affects Version/s

{"errorMessages":[""Affects Version/s" field is required and the project "xxx" does not have any versions."],"errors":{}}

meta data is as below

"versions":{"required":true,"schema":{"type":"array","items":"version","system":"versions"},"name":"Affects Version/s","hasDefaultValue":false,"operations":["set","add","remove"],"allowedValues":[]}

I am trying to create a issue via Jira python api

I am confused if the field is not there and why it is throwing error??correct me if am wrong

Could anyone help me to solve this issue??


1 answer

1 accepted

0 votes
Answer accepted

Hello @Sridhar Mohan 

Welcome to the community.

If you try to create the same type of issue in the same project through the UI are you required to enter a value for the Affects Version/s field?

Generally the fields that are required for a given issue type in a given project are determined in the Field Configuration/Scheme for that project. If you are getting this error then likely that field has been set as Required in the Field Configuration for that issue type in that project. Alternately a field can be set to be required during a workflow transition (in a Company Managed project) using a Validator to check if the field has been filled in. In either case, if you try to create the same type of issue in that project through the UI it should also be requiring you to fill in the field.

If a field is required when you try the operation through the UI, then you will have to provide the same data if you are trying the accomplish the operation through the API.

@Trudy Claspill I got your point that required field is necessary,But here in my project the Affects Version/s has no selectable value and is permanently set to "None".

Also not sure why api throws error " the project "xxx" does not have any versions



Go to the Releases page for the project and see if there are any entries there in any states (Unreleased, Released, Archived). The message is complaining that there are no version defined.

Does the UI allow you to save the issue when the field is set to None?

Getting the same error in UI too and could not save it.

Then an administrator of the project needs to go to the Releases page for that project and create a version, and then select that version as part of your issue creation.

Or your JIRA Administrator needs to change the project so that the Affects Version/s field is not required, at least when an issue is being created.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

270 views 13 14
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you