Forums

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

Issue with requiered field

Javier_Garay
Contributor
August 28, 2018

Hello everyone,

I have a field called Problem Type associated to one of my screens which is called "Create a Problem". I also have other screens to create other type of issues like Requests and Incidents. My problem is that when I try to create a Request or an Incident, Jira ask me to fill the field "Problem Type" which is not associated to the Create Request or Create Incident screens, so I don't undestand why Jira ask me to fill it.

Does anyone have an idea of why this occurs or what should I do to avoid this issue?

Thanks

2 answers

2 accepted

2 votes
Answer accepted
AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 28, 2018

Hi there, Javier.

I had this tested on my end and verified that the issue is reproducible when the Required field is associated to a single field configuration that is being used by multiple projects. For example, we can see that I created the required Problem Type custom field and assign it specifically for the HIP project Create Issue screen only:

Screen Shot 2018-08-29 at 09.31.39.png

However, I was presented with the following error when I tried to create a new issue in the Project M screen below:

Screen Shot 2018-08-29 at 09.33.02.png

I reviewed the Field Configuration  again and noticed that it is due to the fact that the default field configuration is being used by all my projects here:

Screen Shot 2018-08-29 at 09.30.43.png

To overcome this, I went ahead and created the following to cater for this project only:

  • Field Configuration
  • Field Configuration Scheme

Screen Shot 2018-08-29 at 09.41.22.png

 

Screen Shot 2018-08-29 at 09.41.28.png

As you can see, it is different from the default field configuration and I assign them specifically to the HipChat (HIP) project. Under the field configuration, I made the Problem Type field required and verified that I don't encounter the same problem again.

Can you please go through the same steps and let me know if you are still facing the same problem? I will be happy to provide you with detailed steps by steps in needed.

Javier_Garay
Contributor
October 29, 2018

Hi Ahmad!!

It's been a while since your answer! :) I just wanna thank you for your response.

I resolved this using separated configuration fields for each of my issue types. Yes, I was using the same field configuration for all my issue types, so if there was a mandatory field, all the issues types that uses that field configuration were going to ask it for.

Thanks for all

Javier

AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 29, 2018

Hello, Javier.

You are most welcome. Any time!

1 vote
Answer accepted
Alexey Matveev
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 Leaders.
August 28, 2018

Hello,

Check your field configuration scheme for this project. I guess, the Problem Type field is set as required there. If it is set as required, Jira wants it to be filled upon issue creation. It does not matter, if this field is present in the create screen or not.

Javier_Garay
Contributor
October 29, 2018

Hi Alexey

Yes... It was the field configuration. As I said to Ahmad, I was using the same field configuration scheme for all of my issues.

Thanks!

Suggest an answer

Log in or Sign up to answer