2 fields but it's mandatory to have at least one filled in

Question

Hi,

I have these two fields Parent Link and Epic Link for an issue type and I would like to do that at least, one of those two, needs to be filled in. Let's say:

* Issue #1 has Parent Link, so Epic Link is empty
* I want to set Epic Link with a value and set Parent Link to empty
* One of these two must always have a value

I don't want to do the validation on a transition because the users are allowed to change these fields any time. A couple of questions

* Is this possible without an Automation rule? I wanna avoid this approach because it would be triggered after the change is done, so people may overlook it.
* Can it be done with no extra plug-ins/add-ons?

Thank you!

JCameron_8s6jjj · Answer

Replying to my own question - thought of this when I flipped back to the workflow. Since it's an "either or", you can do something like have two different possible transitions between the two states, each with a conditional that checks for one of the two conditions. That way if either is set a transition is allowed.

JCameron_8s6jjj · Answer

I'm curious if you ever found a solution to this within the workflow settings. I was just looking to do the exact same thing for epics. To move them to "Done", it must either have a parent link or a fix version. But the validators and conditionals are all basically "AND" operators.

Right now to avoid "yet another plug-in" (especially ScriptRunner, which is so prohibitively expensive), I'm checking things in an automation that bounce it back so that we can set the conditionals how we want using JQL.

Sergio Montávez · Answer

Hi @Daniel Ebers

I probably misled you by waying "no extra plug-ins or add-ons". Workflows and Jira Automation are welcome. I usually manage mandatory fields in each Issue type field configuration of a Project, but I know it can't be done like that if you want an "or mandatory" involving more than 1 field.

I'm striving for a reactive idea in Automation: given a timeframe of 2 minutes, if both fields are empty, take the value of the last non-empty field and set it back. Then notify the user to solve the issue.

It's not the best approach, but I think it can do the work.