Jira Cloud Automation: trigger when push the "create new issue button"

Mikael Kalla
Contributor
September 23, 2020

Hi,

In Jira automation I can use the trigger "Issue Created" to run my automation.

But that trigger is after you save your new created issue.

I am looking for a trigger/function which runs when I press the "create new issue button"

The function could be to populate fields with text (that I don't want to have as default in fields "manager")

It looks like no automation can run prior the is issue is created (saved)

So even if I add the "field value change" event, I can't have that working unless the issue is created/saved.

1 answer

1 accepted

1 vote
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 24, 2020

Hi Mikael,

You are correct, the Jira Cloud version does not have the ability to auto-populate fields prior to the issue being created. 

Is there a reason that having automation add the value after the creation of the issue is not acceptable?

Mikael Kalla
Contributor
September 24, 2020

I see several automated functions that would be good to have when you hit the Create button to launch a new issue.

One is that automation pre-fill some fields for the user directly at launch,
so user then just can add rest of the info.

Another is,  writing something in Summary field, automatically,updates Description field.

And all this before the issue is saved  for the first time

If I trigger on the today "issue Created" event (which I use for lots of other automation)
If I have to save the issue, then the new created issue goes into the boards, Then user has to look for the issue and open it again = too complicated

Like # people like this
Mikael Kalla
Contributor
September 24, 2020

In my specific case, I want to set some default text into the description field for a certain project.
But since the common Description field is used in all of our different Jira projects, I can't set my text as "default text" fot that field, due it's not applicable for the other projects.
So my idea was to use automation, but it doesn't look to be possible if the issue first must be created "Issue created" event

Like Ben_Sumnicht likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 25, 2020

Based on your example above, no that cannot be done in Jira Cloud, outside of having default values in the fields. You can only update the fields after the issue is created. 

Petr Plenkov March 11, 2022

I just have been searching for a similar requirement. We would like description field to be populated with Summary by default. Such a strange thing that is not possible to do in automation. Where can I report it to have it added to a backlog? We definitely need an event "Before creation", or what is better - Field/Property change should be triggered also when creating a ticket

Like John Funk likes this
Ben_Sumnicht April 15, 2022

Hi Petr, this looks like a link for the Automation for Jira in Server/Data Center. Scriptrunner can be used for this action in Jira Server using the behaviours, however that feature is inaccessible in Jira Cloud.

We are working on a cloud migration and it looks like this trigger is not available in cloud, preventing the editing of text in a description field (or other field) before the issue is created. We created this issue to track this request in Jira Cloud Automation. 

[JRACLOUD-78886] Jira Cloud Automation doesn't support pre issue creation triggers - Create and track feature requests for Atlassian products.

Petr Plenkov April 16, 2022

Hi Ben, thank you for your reply. Actually we do need this in Server. Currently we are using Automation for Jira, which is active in our project. There we can create rules without actual scripting. I meant that feature =)

Ben_Sumnicht May 11, 2022

Hi Petr,

The original question here appears to be requesting the ability to gain this functionality in the cloud. The ticket you linked is related to Server. My comment refers to this being possible in server with ScriptRunner Behaviours. Jira cloud doesn't have the ability to auto populate the description field for example, with Jira automation, so I opened a ticket and posted it here in my comment above.

Søren Kerrn
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 5, 2024

This thread is a couple of years old but the same wish and request is still there.

Has an implementation been made available for the cloud version at this point?

Like # people like this
Tomasz Maryniak
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 21, 2024

Same here, I want to add automation that would pre-fill some of the mandatory fields based on the user that is creating issue but I am not able to do that. And using automation after field is created is not an option 

Georgi Ovcharov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 26, 2024

I would ask for the same - prefilled Description field on hitting "Create" button.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 26, 2024

UPDATE: For those just now finding this thread or have posted already, here is an update for a workaround.

This could be solved simply enough by putting in a Default value. HOWEVER, default values are at the field level so ALL issues using the Description field would have that same default value. Obviously, that is not the desired goal. 

So, a little bit of work is needed. And this is just one suggestion - others may have other ideas on how to approach it. 

Create a custom field of Paragraph type (multi-line text). Call it whatever you like that is descriptive of the field - just as "Story format" or "Story description". 

Then place the new field on the Create screen for that project and remove the Description field from the Create screen. 

Now do the opposite for the Edit screen - add the Description field and remove your new field. 

After that, edit the new custom field to put your default text/format in the Default value for the field. 

Next, create an Automation rule with an Issue Created trigger. Use whatever Conditions you might need for this particular use case, such as Issue Type = Story. 

Then add an action for Edit issue. Select the Description field. (it might be showing already).

Click the 3 dots to the right of the Description field after it is added. Select Copy.

Leave the value for Current Issue in the top box, but select your new field to copy from in the bottom box. 

Turn on your rule/Update. 

What this will do is show your new custom field on the Create screen with the default value/format showing. Once the user creates the issue, will will copy the information from the custom field to the Description field. You will use the Description field from that point on for that issue and can edit the value as needed without affecting other issues. 

I hope that helps!

Evaldas September 11, 2024

@John Funk Well, it's actually a good idea... for the "Description" (or other) field that is not mandatory... and can "played" this way

in my case, I need to add some {{smartvalue}} to the "Summary" field when creating ticket.. not default text, but like creator name and due date...

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 11, 2024

Hi @Evaldas  - You should open a new question for your particular case. But basically you would create an automation rule that updates the Summary field with the information you want. 

Evaldas September 12, 2024

Sorry, I won't start a new topic, as indeed I've already went that way with an Automation that replaces the {{summary}} on creation... but it's not very "nice" - as Automation starts only after saving the issue, so I have to provide a {{summary}} when creating (either a default text, as ex. "this text will be overwritten") or let user enter smth (that will be immediately changed/overwritten)... and after issue creation you have to refresh the page to see the outcome (of Automation)... and you see Automation in History.. and notification is sent...

therefore, not critical, but it's not "nice"...

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 12, 2024

True - but that's pretty much the only way. If you were using JSM, you could hide that field in the form on create and then show it after creation with the values wanted. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events