in jira service managment cloud premium does assets field can have more than one context in the same project?
Hi @Fadi Messaoudi
No you can't have multiple context to the same space based on an Asset type field.
So this is why you are not able to use the setup you described in your post.
Hello @Fadi Messaoudi
@Marc -Devoteam- is right here.
This is not specific to the Assets field itself, but to how Jira field contexts work. For one custom field, you cannot assign the same project to multiple different contexts, so in the same project you cannot have that one Assets field behave through several separate contexts.
If you need different behavior in the same project, the usual options are either create separate Assets fields for the different use cases, or keep one Assets field and handle the filtering inside that context with Filter scope (AQL) or Filter work scope (AQL), depending on what you are trying to narrow down.
Atlassian documents both of those on the Assets object field configuration.
Create an Assets object custom field | Assets | Atlassian Support
Thanks , and if you have an idea there is any other workarround to make this field mandatory in some requests and not in others
Thanks! Do you have any idea how to make this field mandatory in both the agent and customer views for some requests, but optional for others?
@Fadi Messaoudi
Make it required on the request form for the request types that need it and for agents, enforce it with a workflow validator on the relevant transition.
@Arkadiusz Wroblewski
but when i enforce it with the workflow validator it will be required for all the issue type (for example : incident) , but for me in the same issue type i want it to be required for both agent and customer in some requests and no for others in the same issue type.
Create a separate Field Configuration for each Work Type (associated to the Request Type) and make it Required for that Work Type Field Configuration.
It looks like you're new here. Sign in or register to get started.
