How can I create an Automation Rule in Jira to show placeholder text for bugs/sub-bugs?

[Pat.Zandona]

How can I achieve inputting placeholder-like text in the Description field that appears before the ticket is created? This is specific to when issue types "Create Bug" or "Create Sub-Bug" form is displayed.

I have seen ScriptRunner needing to be installed as an option, but my org would not approve the high monthly cost of implementing this. So, I'm hoping setting up an automation rule can work?

I want to simply have this appear:

HIGH LEVEL SUMMARY:
STEPS TAKEN:
EXPECTED RESULT:
ACTUAL RESULT:

I'm open to other suggestions as well.

[Mikael Sandberg · Accepted solution]

Hi @Pat.Zandona,

Welcome to Atlassian Community!

The short answer is that you cannot do this with automations. Automations trigger after a work item has been created, you cannot trigger an automation before the item is created. You would need an app from the Marketplace in order to do this, like Scriptrunner or Live Fields.

[Pat.Zandona]

OK so let me ask another question then.
Could I have more custom fields appear in place of the description box that is broken down as:

Scenario + Steps Taken (this could be the description field - but can I change the title?):
Expected Result:
Actual Result:

Even the two fields 'Expected Result' and 'Actual Result' could even be one box.

So, in summary, could I have 2 description boxes like below without installing ScriptRunner and using the tools available to me, but titled as follows:

Box 1 - Scenario and Steps Taken

Box 2 - Expected vs Actual Results

[Mikael Sandberg]

Yes, that is possible. And if you want those custom fields to be rich text like the description you can do that by going to the field configuration that the project is using (Project settings > Issues > Fields) and click edit. Locate the new field and then click on Rederers and select Wiki Style Renderer.

[Mikael Sandberg]

Note that the renderer change applies to all projects that are using that field configuration, so is you do not other projects to be affected then you would have to create a new field configuration and associate it with the project.