Problem with {{issue.key}} in automation message

[Piotr Piotrowski]

Hi,

I have a problem with {{issue.key}} in the message I want to send, or to be more precise, what is the result of using it. To illustrate where is the problem, I did a test with syntax like this:

1. Case with space between {{issue.key}} {{issue.summary}}
2. No space between {{issue.key}}:{{issue.summary}}

The result is like on this picture

"OTWARTE" is "OPEN" so it is the value of {{issue.status.name}}.

'New "space" test' it is the value of {{issue.summary}}

Where does this difference come from in what is displayed as {{issue.key}} in Case 1?

There is no such problem with other parameters and while using ${issue.key} in the Notification.

Kind regards,

Piotr Piotrowski

[Mark Segall · Accepted solution]

Hi @Piotr Piotrowski and welcome to the community!

When you have the space, the renderer gets smart and makes the key dynamically convert to key summary and status.  With no space, the renderer is unable to differentiate between the key and the following text and leaves it alone.

[Piotr Piotrowski]

Hi Mark,

thanks for your answer, and it's nice to be here :)

Is there any option to control render, e.g. if I don't want it to add status?

[Mark Segall]

There currently is no way to turn it off (Vote for the suggestion JRACLOUD-37224).

So, your best bet is to continue with your alternate approach.

[Piotr Piotrowski]

Thanks a lot.

[John Funk]

HI Piotr - Welcome to the Atlassian Community!

Where is the information displayed - in an email message? That's strange it would display differently. Can you share a screenshot of the rule? 

[Piotr Piotrowski]

To test this, you can use this simple rule:

1. Case with "space" between {{issue.key}} {{issue.summary}}
2. No "space" between {{issue.key}}:{{issue.summary}}

The result is displayed in the same way on the web as in the e-mail.

[Cloudites Owner]

Case 1 - match found, no colon.

Case 2 - no match found, with colon.

What are expecting for Case 2, the same match as in Case 1?