Automation or logic on population of default description template for idea

[Jon Linczak]

The ask here is that could there be some automation that we can write that the default description template for an idea type change based on the filling out of a specific field for that idea?  For example, if I have a field called Capability that's a single-select, I can create an automation to adjust the default template for the description based on the Capability chosen.  Fraught with potential issues (short of creating two different spaces), but it's something we're seeing a lot that we have no better ways to control and we're not willing to setup multiple spaces or multiple idea types (XXXX Epic vs YYYY Epic) in order to satisfy that situation.

[Enric Font]

Dear @Jon Linczak 

Yes, but with an important limitation: in Jira / Jira Product Discovery, native automation can update the Description after the idea is created or after the field changes; it does not dynamically swap the pre-create default description template in the create form based on another field value. Atlassian’s docs support default description templates for ideas, but those are selected/configured at the template level rather than conditionally changed by another field at creation time.

So for your example:

• have a field such as Capability on the idea,

• trigger automation on Idea created or Field value changed,

• add conditions for each Capability value,

• then edit the Description with the corresponding template text. Atlassian’s automation docs and KBs describe editing Description through automation, including advanced field editing when needed.