Add a trigger or API to dynamically pre-fill fields when the "Issue Creation Form" opens

Question

Currently, automation only supports triggers after an issue is created (i.e. on "Work item created"). There’s no way to dynamically pre-fill fields (like Description) when the issue creation form opens i.e. when you click the "+ Create" button.

So I would like to request a new trigger or API event that fires when the issue creation form is opened.

This would allow users to:

* Dynamically pre-fill fields such as Description, Summary, or Labels based on project, issue type, or user role.

* Provide contextual templates or guidance text to improve issue quality and consistency.

* Reduce repetitive manual input and ensure standardized issue reporting across teams.

The only workarounds that I know of are browser scripts or marketplace apps (such as ScriptRunner, Issue Templates) which are either unsupported or require additional licensing and maintenance.

Let me know if I am missing something, otherwise I hope the dev team would take this into consideration.

Cheers!

Monika Ambrozowicz_Seibert_ · Answer

Hi @Andreas Gandrup you're right that native Jira automation doesn't support a "form opened" trigger. Automation rules are reactive (they fire after an issue exists), so there's no built-in way to pre-fill fields before the user submits the creation form.

I know you mentioned you'd rather avoid marketplace apps. However, it seems that you don't have native alternatives, and apps not only fill the gaps in Jira but also often come with personalized support. If you would consider one, I'd like to suggest Templating.app. Full disclosure: I am affiliated with the team that built it, but I've been using different templates from Templating.app a lot.

The Description Templates feature uses a Behavior Builder that fires when a user opens the issue creation form. Based on conditions you define (project, issue type, or other field values), it can automatically pre-populate the Description, and you can guide users to fill in structured information like steps to reproduce, acceptance criteria, or any other context your team needs. It's not limited to the description either - summaries and other fields can be pre-filled or set as required based on those same conditions.

Issue Templates, on the hand, allow you to create (or clone) full issue hierarchies (epics, stories, subtasks) and save them as templates, saving a lot of manual work and reducing errors.In addition, issue templates work with Jira automation, allowing unlimited triggers and conditions.

On top of that, one app comes with an entire package of templates: for work items (issue templates), descriptions, boards, spaces (project templates), and subtasks.

Finally, Templating.app is constantly maintained and its customers supported. If you have any questions, I'd be happy to answer them of give you a demo.

Olha Yevdokymova_SaaSJet · Answer

Hi @Andreas Gandrup

Jira Automation cannot currently react when someone opens the native + Create dialog, so it cannot dynamically inject values into that screen before the work item is created.

Another approach you might consider is Smart Forms for Jira, developed by my team. It would not modify Jira’s native creation dialog, but it can provide a separate, guided work item creation form with dynamic templates and prefilled values.

For example, you could add a field such as Request type or Template with options like:

* Bug report

* Feature request

* Security review

* Marketing request

Then configure the form so that each selection reveals a different prefilled Description field or set of fields.

Smart Forms supports multiple conditional rule groups for individual elements, so you can create several possible paths within the same form. Depending on the selected project, work type, team, or request category, the form can show the relevant fields while hiding the others.

You can also use:

* Default responses to provide ready-made Description, Summary, or guidance text

* Pre-fill form options from Jira fields to keep values such as Priority, Components, Labels, or custom select fields aligned with Jira

* Hidden elements with default responses to automatically add values such as request source, team, category, or standard labels

* Create new work item to generate the final Jira ticket after submission with Form-to-work-item mapping to populate the corresponding Jira system and custom fields

A possible flow would be:

Open Smart Form → select template → relevant prefilled fields appear → adjust details → submit → Jira work item created

This allows you to keep many creation templates inside one form rather than maintaining a separate form for every scenario. Users only see the fields relevant to their selection, while predefined text and metadata are already populated.

The form link can then be added to the project sidebar, Confluence, or another internal workspace so the team uses it as the standard creation entry point.

Andreas Gandrup · Answer

Heya @Martin Runge!

Thank you for your response. Sounds like I have to look more into the native way of templating. Perhaps I need admin rights and that's the reason I have not stumbled upon it yet?

And good to know. I just followed the feedback-link that appeared when I tried to create the automation flow, and it led me to here.
Looking at the Atlassian's public issue tracker, it seems like I cannot post anything in the "Automation for Cloud" project. Where else should I put a suggestion like this? Or how do I request access?

Have a nice day!