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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Required Fields are not being enforced when moving to a new issuetype

We are using Behaviors to make several fields required on some issuetypes in one project. We you move a ticket from one issuetype to another these required fields are not enforced. For example, issuetype A does not have the some of custom fields that issuetype B has. Some of these additional custom fields are required on issuetype B. When the issue is moved from type A to type B, the wizard does not give the option to define these additional fields, regardless if they are required on issuetype B or not. How do I fix this?

2 answers

0 votes

This is because Behaviours are not making fields required as far as Jira is concerned.  They tell the browser to do it, not the server.

There's nothing you can do about this, the fields are not really mandatory.

oh, we used behaviors since we had trouble making a field required on one screen but not another within the same project. Users would get an error stating the field was required but it was not on the screen. We were trying to use the field configuration screen then to make a field required.  Any suggestions?

I'm afraid not.  The "move" function has nowhere to hook custom field checks into it - it only looks at the field configuration for the target issue type, and provides no insertion point for any code.

Hi Nic,

Will this be the same result if we move a ticket from say, project A to Project B?

And  thanks Nic! good to hear from you :)  

Suggest an answer

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

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

323 views 9 7
Read article

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