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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,462,024
Community Members
 
Community Events
176
Community Groups

Validator not working correctly

So we are in the process of migrating to Jira, but I can't figure out how to make a field required within the ticket. What I would like to do is when a user resolves a ticket they must input a resolution (which is a multi-text field) I have made a validator for the required field which is resolution but it's not working when I transition to resolve. I just have to select the reason for resolving the ticket and nothing else. The resolution field remains blank. Has anyone had any issues with this?

 

The first picture shows the field (resolution) that I would like to make required. The second picture shows what is prompted when resolving an issue and after hitting resolve the resolution field remains blank with no errors.

 

Capture.PNGCapture2.PNG

1 answer

1 accepted

1 vote
Answer accepted
Jack Brickey Community Leader Jul 07, 2021

So my first advice here is do not create a custom field called “resolution“. You should not duplicate names on any fields particularly those that are default system fields. This might be the fundamental cause of you not seeing your multi text “resolution field“. If you select resolution you’re likely selecting the default system field. Can you rename your custom field to something other than resolution and re-attempt?

You are a lifesaver Jack! That was the exact issue. I changed the wording to workaround and it finally works. Now I have to figure out what to rename it lol

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events