Description Template on Jira Projects?

[Fahim Ahmed]

Is there an easy way of creating a set template for a specific issue type (i.e. Epic) within a Jira project? 

i.e. Whenever an Epic is created for Jira Project X, it has a template within the description like: 

Stakeholders - 

Deliverables - 

Cost Code - 

[Harrison Ponce · Accepted solution]

Hi @Fahim Ahmed , great question! Templates have always been tricky for text fields in Jira without the use of marketplace apps.

Once of the ways you could accomplish this is with automation. You can set the trigger to issue created and add use IF statements for issue fields condition as issue type equals epic. Then you can use the edit issue action to edit the description field to whatever you want.

The automation formatting for text fields is a little weak but it could definitely get the job done.

Hope this helps!

[Fahim Ahmed]

Thanks Harrison - will give that a go. 

[Fahim Ahmed]

I tried this and it was easy to follow - thanks! My first automation. 

However one issue I encountered. 

When creating the issue from the 'Create' option the templated fields don't appear - see image 1. 

Once created, if I click on the issue however, the template prompts do appear - see image 2. 

Have I missed something  for it not to appear on the initial 'Create Issue' screen? 

Image 3 is the automation rule as per your guidance. Thanks again,

[Nar Kumar C. - Narva Software · Accepted solution]

Hi Fahim,

Automation is already mentioned. That is one way to do it.

There are few other ways, specially if you are using team managed projects.

Check out our last article on this topic 👉 Ultimate Guide to Issue Templates in Jira

[Lukas Nicolai_Seibert]

Hi @Fahim Ahmed  ☺️, if you're open to using a third-party app, Templating.app is a great alternative featuring an easy-to-use UI with no scripting required.

• You can easily apply Jira description templates for all issue types like epic. 

You can find us at the Atlassian Marketplace ➡️ https://marketplace.atlassian.com/apps/1224664 

This is how this can look like for your epic use case: