Change Custom Field Requirement of Linked Issues after an Issue Transitions. Post Function Question.

[perdue_brandon_vast-inc_com]

Hello All - 

I have been having lots of trouble regarding a post function I am trying to implement. I have searched far and wide throughout the Atlassian Community and still can't figure out how to solve this problem. I'll begin with some context of my project - 

I have two Issue Types on two different workflows. They are Potential Candidate and Open Position. When I create a Potential Candidate, I have created a post function which automatically links that Potential Candidate to an Open Position, based on what I select from the Query Custom Field that I have made. This works well. The idea is that I create an Open Position, and then have multiple Potential Candidates linked to that Open Position. Again, Potential Candidates and Open Position are on separate workflows, but they're linked. 

Let's say I have five Potential Candidates linked to one Open Position. Sooner or later one Potential Candidate will reach the end of its workflow, causing the Open Position to reach the end of its workflow (transitions to Done). I created this automatic transition rule via JIRA Automation (great add-on). That works well. 

Here's my problem. The one Potential Candidate has filled the Open Position. Now I have 4 more Potential Candidates left in the workflow. What I want to happen is to be automatically required to change the Query Custom Field on each remaining Potential Candidates. The Query Custom Field that I created automatically links Potential Candidates to the Open Position that I choose. The idea is that I now have to reassign these four candidates to other Open Positions, by updating their Query Custom Fields.

Is there any way to be required to update the remaining Potential Candidate Issue Type’s custom field after an Open Position has transitioned to Done on its workflow? Any help/insight would be much appreciated. Thanks in advance.

[Eric Almquist]

Are you using the Script Runner plugin or is this all native to the standard JIRA workflow postfunctions?

If you have ScriptRunner this may be doable, but I can't think of a solution without it.