Automation rule: Summary field won't update with my value

[Herve Wiederkehr]

Hello,

Automation rule:

I am trying to auto populate the summary field when an new issue is created with the word "Project" but it remains empty when triggering the action.

Many thanks for your held

Kind Regards

Herve

[Herve Wiederkehr · Accepted solution]

Hello,

Here is the screenshot after editing then executing (nothing happens) but no trace in the log

[Bill Sheboy]

Hi @Herve Wiederkehr 

What problem are you trying to solve by doing this?  Knowing that may help the community to offer suggestions.  Thanks!

From what you have described thus fare, what do you want to accomplish: 

1. have a default value of the word "Project" when an issue is created
2. add the word "Project" to the beginning of an existing issue summary

#1 cannot be done with an automation rule.  Rules are triggered after an event has occurred, such as Issue Created.  If you ant a default value, you will need to use another method.

#2 can be done by changing your field edit to be the following, adding the existing summary after the word.

Project {{issue.summary}}

Kind regards,
Bill

[Herve Wiederkehr]

Hello,

What I am trying to do is exactly triggering an even:

Put the word "Project" in the Field "Summary"

When an issue is created (Clicking a button).

So I don't see why it won't be possible

Kind Regards

Hervé

[Bill Sheboy]

Hi!

To clarify what I described, automation rules execute when something happens (i.e. an event), such as issue create.  And so the rule does not run until after the issue is created.  When you click the "create" button to add a new issue, it does not exist until the issue is saved; that is when a rule can run.

If you want to add/modify a field after the issue is created, that can be done with an automation rule.

When you want instead a template for a field, some possible options include:

• change the default for a field, such as with a team-managed project's features
• purchase a marketplace addon which supports templates for issues
• create you issues in some external application and then call the REST API to create the issue within Jira

[Trudy Claspill]

@Herve Wiederkehr 

Can you also share the Audit Log for an execution of the rule?

1. Click on Audit Log above the rule components.

2. Find an execution that says "Success" in the Status column.

3. Click on "Show more" to the right of that.

4. Provide a screen image of all the messages revealed.

[Trudy Claspill]

Hello @Herve Wiederkehr 

The absence of an entry in the Audit Log for the rule means it was not even triggered.

It appears that the rule is turned on, as it say "Enabled" next to the rule name.

In the Rule Details, what is specified for Scope? This should list the project(s) against which the rule will run. The rule is triggered by creation of an issue in the specified project(s). Has an issue been created in the specified project?

[Herve Wiederkehr]

Hello,

Thank you for your answer.

The scope for this automation is the project "Project Follow Up HW" (See screenshot attached).

As the even isn't fired as was wondering if it could be related to my browser config (Chrome) related to javascript or even my antivirus?

Kind Regards

Hervé

[Trudy Claspill]

Hello @Herve Wiederkehr 

It is unlikely this is related to your browser config, javascript, or your antivirus.

@Bill Sheboy provided an explanation about how the Issue Created trigger works. You have to create the issue and click the Save button in order for this rule to be triggered and execute. The rule will be triggered only after you initially save the new issue.

[Sam Nadarajan]

Hello @Herve Wiederkehr and welcome to the Community!

A screenshot of your rule will help the community debug the issue!

In the meantime, here's what I'd look for:

• Is your rule limited to a project that's different from the project you expect to see the change in?
• Are there automation rules that you have created that are modifying the issue after your summary automation rule has executed?
• Are there conditions within your automation rule that limit the summary modification so that the issue you are expecting it on doesn't meet the conditions
• Is your automation rule enabled?

[Ravi Sagar _Sparxsys_]

Share you rule

[Herve Wiederkehr]

Hello,

Thank you for your prompt reply.

Please find the screenshot of the role hereafter.

Kind Regards

Hervé

[Herve Wiederkehr]