Raley can automatically assign a custom purchase order number provided that is is stored in a specific Jira custom field as specified in Raley PO - Jira config menu.
The value would be retrieved and assigned to the current purchase order no matter what's its status.
Most typical scenario is to set up a Jira automation script to generate custom PO# when the Jira issue is transitioned to Approved status. Automation for Jira would assign the custom PO# to the specific custom field of given issue.
Once the issue is updated, Jira will trigger issue_updated webhook and Raley will react on it. It will check if the specific custom field was assigned and if so - assign the value from custom field to PO# and generate a PDF file.
For security reasons we advice that you keep the Jira custom field with PO# either hidden or read-only on the form, so that the Jira users would not be able to modify it manually.
It is supposed to be assigned only by Jira automation or a similar tool. A user in Finance role can always update PO# manually on purchase order form if this is required. See Custom purchase order number section in Approving purchase orders article for more information.
