Morning.
I have confirmed the following in 2 separate one-atlassian environments.
When using the work item planner agent, either in confluence, or in Jira, asking the agent to create the epics or issues (ie: from the page action items, or from an epic etc) always fails with errors like
“It seems there was an issue with creating the Jira epics directly from the action items on the "Brainstorming" page. However, I can guide you through creating them manually based on the breakdown I provided earlier.”
or
"It seems there was an issue creating the epics in Jira. Please ensure that you have the necessary permissions to create epics in your Jira instance."
I've read the agent instructions end to end multiple times, and it definitely seems like it should be able to create items in Jira in these situations.
What is going on? Is there anywhere to look for log files? Audit-log has nothing....
Thanks in advance!
NOTE - its not just work item planner. Another example is Issue Organizer Agent, which won't suggest parents/epics for things without a parent. It'll detect them fine but then says this when there are CLEARLY Epics/Parents that would be appropriate:
"Unfortunately, I couldn't find any suitable epics to suggest as parents for these tasks. If you have specific criteria for selecting a parent, please let me know, and I can assist further!"
Hi @Rob Little Rovo agents should be able to create Jira issues, including epics. Ensure the agent has the necessary permissions and that all required fields for issue creation are specified. If you still can't complete the action consider submitting a support ticket. https://support.atlassian.com/ Be sure to include:
The name of the agent
The Jira project key
Your permission level
The exact prompt used
A screenshot of the error message
This will help the Atlassian team investigate more efficiently. And here are the steps to check your Rovo agent’s configuration for Jira issue creation:
Go to Rovo Studio in Confluence or Jira.
Open the agent you're using (e.g., Work Item Planner).
Under Agent Settings, confirm that:
The “Create Jira issue” action is enabled.
The target Jira project is correctly set and accessible.
Any required fields for the issue type (e.g., Epic Name, Summary) are either pre-filled or prompted.
Test permissions by manually creating the same issue in Jira with your user account—Rovo inherits your permissions.
@Dr Valeri Colon _Connect Centric_ Thanks, its not a permission thing... i'm an org admin, project admin, these are fresh one-atlassian envs, and i can do everything mentioned just fine manually.
As per 'agent settings' for an agent, where do you see such an option???
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I loooove a good screenshot! Thanks for sending this @Rob Little Looks like you need to configure your agents. Click on "Duplicate Agent". Your goal is the specify the "Actions" and the "Knowledge" Here's the step by step: https://support.atlassian.com/rovo/docs/create-and-edit-agents/
I have a free community led class on Rovo with @Ali BenCafu in 20 minutes. If you can join us, We'll show you how to do it live.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wow, ok so this is very similar to the dev agent beta 'template' paradigm, where you MUST duplicate the template and configure it.
I presumed that the OOTB work item planner, with the highlighted instructions in my screenshot, could *do* the things it says it can do, and that the actions list on the side was just some example actions.
But, i've tested what you said, and you are correct - i duplicated Work Item Planner, and gave it some actions (including create work item) and then it could parse my page of goals/ideas in confluence and generate a bunch of content.
OK. I'm stoked you taught me this. I'm shocked thats how these OOTB looking agents, dont actually do what the instructions say, OOTB!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am stoked that I was able to show you @Rob Little thanks for joining us! I love a good community forum to class cross-over. We're all learning and sharing together.
I need another term besides "out of the box", I agree it can be misleading. The majority of the agents can be used without having to adjust instructions or identify specific pages or spaces. But in general all agents work better if you add your details. And a few will give inconsistent responses unless you adjust instructions or identify specific pages or spaces -- especially when actions are involved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So that explains Agents acting wonky for me @Dr Valeri Colon _Connect Centric_ but what about generic Rovo Chat, similar issues performing actions but explicitly documented here https://www.atlassian.com/software/rovo/use-cases/reassign-jira-issues-to-new-assignee
What permission or action is missing and how do i have this work? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rob Little you broke Rovo! hahaha just kidding. From everything you sent -- Rovo chat should be able to complete the action.
Smash that thumbs down button. It might be a bug, and consider submitting a ticket with the one-atlassian team via the same support portal that you used to create the environment. The one-atlassian accounts have specific settings that may be interfering.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.