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!


Emailed Request Configuration on Project with Issue Collector that has Required Fields

Kevin McCarthy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Sep 28, 2023


I am in the process of setting up a Jira project that we want to have both emailed requests, and also issues created via an issue collector functional, these will be the main way tickets are created for this project. Several of the fields in the issue collector must be required, and the only way I have found to do this is by marking the fields as "required" at the field configuration level for the project. However this also adds them to our request type for emailed service requests, even though they are not fields for our emailed request issue type. This prevents the emailed service request, request type from being in a valid configuration for the email channel.

I was wondering what the best way to work around or solve this issue might be. I had hoped that creating a dedicated issue type specifically for emailed requests would solve the problem but this does not appear to be the case.

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events