Formating a rovo agent.

[Biedner, Simeon [ BAHAG.COM ]]

Hi,

I have a certain template for my JIRA tickets. I want to use this template:

{panel}
h2. User Story
*As a user*
*I want to*
*in order to*
{panel}

{panel}
h2. Background
Why we are doing this User Story?
{panel}

{panel}
h2. Acceptance Criteria
Recommendation: A testable, short description about what the user wants to do in this story
*
{panel}

{panel}
h2. Constraints
What is outside this user story or not negotiable (e.g. due to law)
{panel}

{panel}
h2. Additional Notes
 E.g. things came up in the refinement
{panel}

{panel}
h2. Open Points
{panel}

{panel}
h2. API
* Does the data come from API?
* Does the data come from CMS?
{panel}

But Rovo is simply ignoring it even I add it to the Agent by my own. 
Any tipps?

[Walter Buggenhout]

Hi @Biedner, Simeon [ BAHAG.COM ] and welcome to the Community!

Context is everything for questions like these. I understand you are trying to build a Rovo agent to add a certain format to new work items being created?

It might help us help you if you could share the full details of your agent and where/how you are trying to make it work.

Depending on your scenario, I may not recommend using Rovo for this either - while it is being included in your plan, you will be invoiced over time if you run agents more than the allowed number of credits you have with your plan. If all you want to do is making sure your description follows a certain template, you might create your work items with an automation rule instead and use Rovo for more advanced / valuable use cases.