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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How can I make urgency and impact optional on the fields?


I followed the steps on how to automate priority, after implementing the automation. The urgency and impact field became needed to be input before you can send a request.


However it is a problem when the request comes from email, it will says Configured request type has too many visible required fields.


How can i make it optional?


Please see attached image below for what I am saying:

visible fields.PNG


Thanks in advance

1 answer

0 votes

Hi @ThinkConveyancing IT 

I would advise you to change the email request type. Follow these instructions to do that

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events