I encountered an interesting situation while creating a Rovo Agent with an automation Trigger. Automation rules are usually triggered by an action that grants access to the issue(s) the rule is designed to process. Meaning that by the time the automation rule is triggered and running, it already knows about the current issue or issues if JQL is used.
If the automation rule is triggered by a date (which allows you to run a JQL query to load the issues if you had it ahead of time) or by some other action that is triggered by an issue, you would have the issue(s) loaded. You can use everyday automation actions to perform updates and other tasks on the issues.
In this case, the automation rule is triggered, which then invokes a Rovo Agent. The agent generates a JSON file containing issue keys and other values that need to be updated in the issues.
Here's the dilemma: The automation rule is triggered without knowing what issue(s) are involved, so it cannot load the issues in preparation for the automation actions.
I can loop through the JSON file (using the For Each: Smart Value component) and now have one set from the JSON file with the issue key and fields to update.
However, I don't see any action that allows the issue key to load the issue, so that the regular automation actions can update it.
I hope this is not the result of too little caffeine or sleep, or both, but how can you get there from here?
Thanks in advance for your shared wisdom. It is and always will be appreciated.
