I am trying to put below default fields in the Request but actually default field is affecting all other Request's. Can someone help me out to find out how i can make Default field only for that particular Request.
The above field hidden somewhere in other Request Type even though i have not select them from backend and is showing when Jira ticket is creating.
Can you please provide us a screenshot displaying the page you used to configure the field on your request type? I would like to better understand what do you mean by adding a default field.
When you add a field to a request type using the conventional method (see screenshot below), it is placed only for that specific request type and not for others:
Can you confirm if you are not seeing the same Request Type across different Request Type Groups?
If you are not, I can clearly confirm that the field was manually added to the other request type too, unless you used a different method than the one above to add your fields.
We will be waiting for your feedback.
Hi Petterson, @Petter Gonçalves
I have also a question about those fields under request types.
My goal is to change email request type from "bug"(issue type Bug) to "technical support"(issue type Support).
Under Project settings> Email requests> Cloud email address> Request type:
The gray types (cannot be selectable) need visible Summary and Descriptions to let it be selectable, and others are optional.
But I cannot change the settings to meet its needs. There are always some default fields in the type which cannot be removed, do I need higher access to do it? I'm now the admin of the project, but not the admin of the whole Jira product.
Need your advice, thanks a lot!
Just to confirm that we are on the same page:
A request type is suitable for the email channel when both the Summary and Description fields are visible, and all the other visible fields, if any, are optional. If you want to use this request type, you need to change its setting to match the criteria.
That been said, you are saying there are some fields that you are not been able to remove in some request types. Is that correct?
Can you provide me which fields are reproducing this problem? Are them custom fields or system fields?
For now, I would check if the fields are flagged as required under project settings > Fields. If they are, turn off this option to allow the creation of the issue without add any value to the fields.
Hi Atlassian Community! This is Teresa from the Atlassian team. My colleague Paul Buffington @Buff and I are excited to share a brand new ITSM resource we’ve created – "The Complete Guide to At...
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