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

How to make comment field mandatory when changing a status


We have a requirement when we want user to provide a comment before closing/cancelling a ticket. For each issue we have two options - Add internal note/Reply to customer. We want to make Reply to customer field mandatory.


Is this possible in next gen JSM project?

1 answer

0 votes

Hello @Shruti Sharma,

Thank you for reaching out to Atlassian Community!

In next-gen service projects, it’s not possible to add a validator on a transition to make a field required. One of the reasons is that it’s not possible to configure screens, so since no screen shows when closing a ticket, it’s not possible to add required fields.

On the workflow, it’s possible to add rules to transitions, but the “Update request field”, “Remind people to update empty fields” and “Check a request’s field” don’t have the option to select “Comment”.

With this said, it would be necessary to use a classic project in order to add a validator to the transition to make sure agents adds a comment before closing a ticket.

If the purpose of the comment is just to inform the customer that the ticket was canceled, for example, a canned response, you can use automation to add a comment. 

If the comment that the agent would add is unique depending on each case, then the way to “force” this would be using a validator on the workflow that is available only on classic projects.

Kind regards,

Suggest an answer

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

Announcing Mindville Insight is now part of Jira Service Management!

Hello Community! We’re excited to announce that Mindville Insight’s asset and configuration management capabilities will now be integrated into Jira Service Management Premium and Enterprise plan...

755 views 12 15
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