Request type field validation

[Philip Colmer]

I have a form that allows various aspects of an employee to be changed, e.g. their department, manager, job title and so on. Since it is an "all in one" form where any combination of items can be changed in a single ticket, none of the fields are required.

It has been brought to my notice, though, that if someone is changing department, the likelihood is that their manager is also going to change, so I want to see what I can do to try and ensure that if the new department field has a value then the new manager field has a value as well before the ticket is created.

Does anyone have any suggestions on how to achieve this? Add-ons are a permissible solution :)

Thanks.

Philip

[Susan Hauth _Jira Queen_]

Hi Phillip,

We use the User properties to define the Employee's office and manager.   We use post functions to grab the reporter's properties.  The Office property goes into the field Office.  The Manager field is often used to populate the Approver field.

Hope that helps

Susan

[Philip Colmer]

Thank you for sharing this, Susan.

The challenge I'm trying to solve is changing a field from optional to required if another field on the same request gains a value. I suspect it is a limitation of JSD that nobody has solved but there are so many add-ons out there I have got my fingers crossed :)

[Susan Hauth _Jira Queen_]

Hi,

Take a look at Extension for Jira Service Desk.  They support dynamic forms.

Susan

[Philip Colmer]

Thanks, Susan. We do have that installed and I've read the documentation but it doesn't seem to do what I want. I've raised a ticket with Deviniti and they've concurred.

The manager field needs to always be visible, so that the manager can be changed regardless of the department being changed. There are some limitations of Deviniti's dynamic forms which means that trying to meet my needs with that approach would get very messy and it isn't entirely clear if it is actually solvable.

Reading their proposed approach made me realise that I really do just want a pre-create validator so that I can check the values in the fields *before* the issue gets created and raise a message to the user/block the issue creation if there is something wrong with the data.