Validator breaks inline quick issue create

Question

I have a project with Epics and other subtasks type issues. In this project is a custom field that is a requirement for all issue types. For the non Epics, Epic Link is also a requirement. This is currently being enforced with a validator on creation, and in post functions to copy the field value from the Epic to the other issue types (using JWME). "If a value for field is not provided during the transition, show the following error: is a required field when creating Initiative issue types. " "The value(s) of field will be copied from the issue(s) linked to the current issue by the belongs to Epic link type (unless the field already has a value). Run as add-on user." If the Old Issue View is used, or if the user clicks the CREATE button at the top, then they can fill in this custom field and provide the Epic Link. If they are in New Issue View then the "+" inline quick create button in the Epic can be used. However, if the custom field validator is active, then I run up against JRACLOUD-72434. If i remove the validator to fix this then that allows people to create the issue without filling in the custom field. In JWME, there is also a version of its validator which allows to insert JQL but I'm not sure if this has the power to fix this problem. Can anyone help?

David Fischer · Answer

That's correct, post-functions run after validation. And Jira expressions, which are what apps use to build Validators, don't support testing whether the issue is being created through the "Quick create" feature. So your options are indeed essentially what you described.

Steven Rhodes · Answer

Thanks for your reply.

Well, i need the custom field to be filled in, as when people create the non-Epic type issues, they don't fill in this field. We also dont want them to create any issues that arent Epic without the Epic Link being provided. So for those times when they click the Create button and try and manually create an issue without these fields we'd like to take them from the Epic.

However, if we add a validator to enforce this, and use the New Issue View, then we dont get the screen and my feeling is that it doesnt reach the post function to copy the fields from the Epic before the validator complains of fields being empty.

So we can either have the validator to stop people from leaving the field empty when the screen does show, or we have to remove the validator to make sure the issue gets created when the screen doesnt show. Right?

David Fischer · Answer

Hi Steven,

I don't believe there is any solution to your problem, since you are using a Field Required Validator to enforce a value when creating an issue, and here you'd like to be able to create a new issue without enforcing a value. You can't have it both ways.

The real problem is that the inline quick create functionality of Jira doesn't show the Create screen for the issue type being created, which doesn't allow users to enter a value for required fields.

If you don't need the custom field to be filled in when creating a new issue, then you should simply remove the Validator. Otherwise, it means users cannot use the quick create button.