I have a Agent which receives this example JSON filled out:
{ "priority": "<LEVEL>", "impacted_team": "<TEAM>", "sub_impacted_team": "<SUBTEAM>", "request_category": "<PRODUCT>", "sub_request_category": "<SUBPRODUCT>", "assignee": "<NAME>", "assignee_accountId": "<ID>", "issue_url": "<URL>" }
I want the Agent to edit the work item however after:
- Prompting the Agent to edit the work item
- Prompting the agent to edit the incoming JSON to fill out:
{
"update": {
"customfield_16165": [
{
"set": {
"value": "{{impactedTeam.value}}",
"child": {
"value": "{{subImpactedTeam.value}}"
}
}
}
],
"customfield_16164": [
{
"set": {
"value": "{{requestCategory.value}}",
"child": {
"value": "{{subRequestCategory.value}}"
}
}
}
],
"priority": [
{
"set": {
"name": "{{priority}}"
}
}
],
"assignee": [
{
"set": {
"id": "{{assigneeAccountId}}"
}
}
]
}
}- Prompting to edit the work item based on the filled out JSON above
- Lastly Giving the Agent actions of updating priority, assignee, and editing the work item
This agent should ultimately parse the incoming JSON and fill out the fields in the current work item.
In the Audit Log of `Edit work item fields` I keep getting a invalid JSON.
Additionally forcing the Agent to edit the fields does not do anything
@amit.deb Automation can’t apply the raw JSON you generate. Rovo Agents must output only the field values, not a Jira REST-style update object. The automation action builds the JSON for you. Have the agent return a simple object like: {priority:"High", impacted_team:"X", …}. Then map each value in Edit work item fields. If the agent outputs nested child objects or REST syntax, Automation rejects it as invalid JSON.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.