nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

{{issue.url.customer}} not working

Marius Fischer

expected behaviour:
{{issue.url.customer}} returns portal request link
{{issue.url}} returns project request link

behaviour in my project:

{{issue.url.customer}} returns no link at all, no matter the HTML framing
{{issue.url}} returns project request link

it works as expected in other projects, so it must be some configuration error preventing the portal access? But i can access the created tickets in the portal (via the link from the backend or in the My Requests Section).

Accepted answers

Trudy P Claspill

Hello @Marius Fischer

In what context are you using those smart values? Is that in an Automation Rule?

If so, please share the full rule and show the details of the steps where you are using the value.

Does the issue where you are executing the rule and getting no value for {{issue.url.customer}} have a value in the Request Type field?

In the Rule Details, what is the setting for Rule Actor?

All comments

Jack Brickey

hmmm, something does appear to be amiss. I just looked at an old rule that I had and it does not appear to be working as previous. Here are the results below

last week here was the result...

I wonder if this is a side effect of the automation issues earlier this week.

Trudy P Claspill

Hello @Marius Fischer

In what context are you using those smart values? Is that in an Automation Rule?

If so, please share the full rule and show the details of the steps where you are using the value.

Does the issue where you are executing the rule and getting no value for {{issue.url.customer}} have a value in the Request Type field?

In the Rule Details, what is the setting for Rule Actor?

Jack Brickey

@Marius Fischer , So I spoke too soon. I just ran several more tests and it appears to be working. I haven't yet figured out why it's not working on the one issue I tested it on but I'm sure it's something I'm just overlooking. Would you mind sharing a screenshot of your automation rule?

Marius Fischer

@Jack Brickey

at the moment it's a mess because i'm testing different options:

Jack Brickey

can you try the following simple form...

{{issue.issue key}}
<a
href="{{issue.URL.customer}}"> "click the Link"
</a>

For test purposes you may wish to change your trigger to manual in that way you don't have to keep creating a bunch of issues. Just execute the manual trigger from any existing test issue

By the way, your post is under Jira software but hopefully this is referring to your Jira Service management app.

Trudy P Claspill

Based on my experimentation, if the issue has no value in the Request Type field then the smart value {{issue.url.customer}} will return no value within the context of an Automation rule.

Marius Fischer

Thank you, this was the solution to my issue!

Since the ticket was created and then the Request Type edited both by Automation, JSM could not create the link at the time of the Automation. I adjusted it to trigger from the Customer Request Type being set instead of the issue created. Now the url is properly created from {{issue.url.customer}}

R. Dormanns

FYI: if you set the Request Type in an Automation rule and would like to access the URL in the same rule, a "Re-fetch issue data" suffices.

I just had the same problem and found out the re-fetch works.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management