Automation dont view a field name

[Eric Roetenberg]

Hello,

Best wishes to everyone for 2025

I have a question I created an automation rule that does not put the project name in the field, the month it does display . What is going wrong here do I need to set something else.

Greetings Eric

[Bill Sheboy]

Hi @Eric Roetenberg 

To which project are you trying to refer in those Issue Create actions to set the summary field: the destination project where the issue is being added, or something else?

If it is to the destination project, what you show will not work.  The issue has not been created yet and so the smart value {{issue.project}} has no meaning yet.  And so the project names may need to be hardcoded into the summary.

If you mean another project, please provide more details for your scenario.

Kind regards,
Bill

[Fazila Ashraf]

@Eric Roetenberg  , What does format("MMMM") give?

I couldn't find this formatting option in https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ Pattern index.

Have you tried format("dd/MM/yyyy") ? 

[Eric Roetenberg]

January

[Tomislav Tobijas]

Hi @Eric Roetenberg ,

Happy new 2025! 🎉

When referencing to automation rules, it's usually easier to 'debug' issues and problems people are experiencing if there's an example and/or screenshots of automation rules together with appropriate components (maybe together with rule audit log).

Additionally, I think we would need info of which type of field you're looking at when trying to put project name value.

Cheers,
Tobi

[Tomislav Tobijas]

@Eric Roetenberg based on the screenshots you've provided, I'm afraid you'll have to 'hardcode' project key (at least I can't think of any smarter way) or name within issue summary.

As per official documentation:

The issue smart values are used to access information related to the rule’s active issue, which is the issue the rule is currently acting on

Which would mean that issue needs to exist in order to 'pull' that info from it. As, at this phase within the rule, you're still creating the issue (which means it isn't yet created), you won't be able to 'access that'.

{{issue.[property]}} is usually referring to cases where you have a specific issue defined within the trigger or within the rule branch.

👉 Potentially, you could create additional rule which would update issue summary once the issue is create (just use Issue created trigger).

[Eric Roetenberg]

Sounds very logical I am going to try an additional automation rule

[Fazila Ashraf]

Hi @Eric Roetenberg 

Happy 2025!

Can you share snippets of your automation?

[Marc - Devoteam]

Hi @Eric Roetenberg 

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of the actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. images showing the relevant data in an image that is part of the rule execution.

6. Explain where the issue is.

These questions are not for not willing to help, but to have community members learn on how automation works.

Not just to provide a full solution, which would not help to understand what the automation is doing, but to have members understand what a rule is doing, if in need of change or error.

[Eric Roetenberg]

it is a company-managed , see the upload images

[Marc - Devoteam]

Hi @Eric Roetenberg 

Try for project key, the following smart value {{project.key}}

[Eric Roetenberg]

no result

[Marc - Devoteam]

Hi @Eric Roetenberg 

Most likely is that the issue does not exist yet, so the smart value related to project key has no value yet.

You would then to add a re-fetch action after each creation and probably use if/els clause for each issue creation and then an edit action to edit the summary of the create issue

I do have another question, why the project key in the summary. The issue will get the project key as prefix of the created issue?

This based on the project the issue is created in.