Define mandatory fields at ticket creation but not be mandatory for customer/external in issue creat

[Lena Wiethaus]

Agents forget to fill in data

To avoid this I would like to define mandatory fields for one specific project

Acutally we do this with validators in the transition, but this is the step after creation

The mandatory fields should have no affect on creating an issue as customer/external or by creating a ticket with e-mail import

Any ideas how to solve this?

[Maciej Dudziak _Forgappify_]

Hi @Lena Wiethaus

One potential solution is to use a Jira expression-based validator. If you already have an app that provides this functionality, you can configure it to check if the current user has any roles in the project. If they do not, you could assume they are a customer or external user. The expression would look like this:

user.getProjectRoles(issue.project).length == 0 || issue.customfield_12345 != null

You can read it as follows:

1. If user has no project roles allow transition/issue creation

2. OR If not (has a project role), then check if custom field is not empty/null 

I am from Forgappify, and we developed Jira Expression Validator, which is part of the Workflow Building Blocks for Jira app, in case you are looking for such validator. In our expression editor, when you start typing the name of your field, you will get a suggestion for the ID.

Please note that all 3rd party validators are only available for company-managed projects.

I hope it will help.

Cheers