Rovo, Agents, Automations, oh my: having a default description

[David Gerrard]

I've been excited at the prospect of using all the new AI features added to JIRA.

I'm the PM for teams across two different spaces.  I want to set default values for all 4 ticket types, but only impacting my spaces, not my colleagues.

We have 4 template tickets:  one for Stories, one for Tasks, one for Bugs, one for Epics.

Each time I create a new ticket, I find either an existing ticket that has cloned one of them, or clone it myself, to get the description right.

I thought, "maybe Rovo could handle this!"  No, can just give me the text to copy & paste in.

"Maybe an Agent could handle this!"  No, can't create tickets, even with the "Create Tickets" permission active.

"Maybe Automation could handle this!"  Only if I create the ticket first, and then re-open it.

This feels like such a simple task, but I'm blocked at every turn:  any recommendations for how I can implement this?

[Staffan Redelius · Accepted solution]

Hi @David Gerrard 

Do you want to create a type of template or static text in the description field and that should be different based on the issuetype?

You can use an automation to add a description template but as you have experienced it can only update the description after the ticket has been created (since it is triggerd by the "create work item")

The closest i got is to get the information updated immediately when the issue is created, Then it is possible to fill in the additional information. 

If this is what you want you can try this.

Create a rule that looks like this:

 

Trigger: The first step can be configured to only be triggerd by a specific project or user. 

Condition: In this example it is only for the issuetype Story but you can create a branch with a IF/Else statements to handle different issuetypes.

Action: In the Edit Work Item Fields you put your template description

{{issue.description}}

*Background*
.......

*Preparations/Preconditions*
...........

*Valdidation steps*
............

*Risks*
............

*Impact*
............

*Roll-back plan*
............

*Affected stakeholders and communication plan*
............

You could also try the Readiness checker" agent in Rovo to see if that can get you closer to the solution (ór create your own agent). You could also ask Rovo to clone a specific ticket including subtasks. 

Maybe not exactly what you want but at least it could give you some ideas to explore

/Staffan

[David Gerrard]

That's quite good, thank you Staffan.  I'll try that approach.

I was so surprised, going through all of these big new features, for something I felt would be so simple, to get stuck at every turn.  I would love to know some examples of, how any Product Managers are successfully using Rovo Agents.

[Dorota Popowska - Vilisoft]

Hi @David Gerrard, 

I’ve tried similar scenarios myself and, unfortunately, didn’t get a satisfactory result either.

In cases like this, it’s often more effective to use a dedicated app such as Clone Expert for Jira. It works directly with regular Jira issues, so you don’t need any special template structures. Any existing issue (Epic, Story, Task, Bug, etc.) can serve as a reusable template.

Clone Expert can duplicate it together with its content, subtasks and hierarchy. Before cloning, you can review and adjust everything in a preview table to ensure the final issue (or issue set) is created exactly as you want.

If you’d like, I’m happy to walk you through your specific use case and suggest a concrete setup that would work for your teams. Book my time here.

[Morgan Watts]

Hello, 

I believe automation should still be handle this. You could have a trigger of "create work-item" add conditions that when it's a specific type, maybe made by a specific person, then use an action to edit fields with default text.

[Nikola Perisic]

Hello @David Gerrard 

Why not having 4 separate custom fields that will have predefined default values? What this part means: "I want to set default values for all 4 ticket types, but only impacting my spaces, not my colleagues."?