I have an issue with custom fields where the default value is set.
In fact I have 2 fields where a default value is set for a special request type. When a customer opens another request type which does not include those fields these are nevertheless shown in the request detail screen (in the backend) for all other request.
Since I did not assign the fields to other request I do not expect that those fields will show up on other request types (as it is quite disturbing) since these fields do not have anything to do where they pop up.
Is there a config which I missed ?
Thanks in advance.
I want to have the custom field only appearing where it belongs to. I try to give a more detailed example of my problem.
custom field: primary mail -> default value "@example.com"
custom field is added to request type: "user creation"
when a request of type "intranet problems" (does not include "primary mail" field) comes in and I check the detailed view I can see description etc. but also "primary field" : "@example.com"
This should not be shown in the request as this type does not have the field attached. Either there is a bug or I missed some configuration.
You say the request type doens't have the field attached. If you're thinking it doesn't appear on the create or edit screens that doesn't matter. It sounds like when you created the field you made it either global, for the issue type (inadvertantly perhaps), or for the project. It doesn't matter if appears on any of the screens, if it is defined for the issue type, project, or global it will appear in the details page when there is a value, default or set, for it. Go to the custom field and verify how it is defined.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG