Automation sends old URL

[Dd]

Hi,

I have a manual automation that when executed updates some fields and then sends a message to a slack channel using ({{toUrl}}) to display the URL of the work item with hyperlink.

I changed the project name from say XXX to YYY but the automation still sends the old URL (i.e. XXX).

Any idea how to fix that?

Thanks

Dd 

[Dd]

Known issue: 

1. Jira Automation Rules Incorrectly Reference Old URL After Domain Change

[Bill Sheboy]

Hi @Dd 

For a question like this, context is important.  Please post the following to help the community offer better suggestions:

• an image of your complete rule in a single, continuous image
• images of any relevant trigger, actions, conditions, and branches
• an image of the audit log details showing the rule execution

Until we see those...

If the rule is updating the work item fields in a way that impacts your URL, did you include a Re-fetch Work Item Data action to reload the data from the cloud before building the URL?

Kind regards,
Bill

[Dd]

Hi @Bill Sheboy ,

Nothing that I update there would impact the URL.

Here's the flow:

 

Audit log:

[Bill Sheboy]

Just to confirm, are you using Jira Cloud or Server / Data Center?

I notice your Slack message uses the plural {{issues}} smart value, but that is only supported with Server / Data Center for bulk-handling.

Your rule appears to only access one work item, so please change to the singular {{issue}} one.

Some other things I note in that message:

• Please use the {{url}} smart value, not {{toUrl}}: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.url--
• The smart value for properties has a typo: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.properties--

Finally, the rule uses Edit Work Item fields, and then may be using those fields in the Slack message action.  If so, please add the Re-fetch Work Item Data action immediately after the edit and before the message; that will reload the data before the rule proceeds.

[Dd]

Ouch! Many things to fix.

I'll update and see how it goes.

Thanks

BTW - cloud

[Dd]

Still getting the old url.

[Bill Sheboy]

Would you please post images of your updated, complete rule and the audit log details showing the execution?  Thanks!

[Dd]

Sure

Rule:

Audit Log:

[Bill Sheboy]

That is curious!  I recall some related, recent defects for project name and key changes in the public backlog with team-managed projects. 

At this point, I recommend asking your Jira Site Admin to submit a ticket to Atlassian Support to take a look.  You appear to be on a paid license and so the admin can do that here: 

https://support.atlassian.com/contact/#/

When you hear back from them, please post what you learn to benefit the community.  Thanks!

[Dd]

This happens to be a known issue.

This is a known issue: after changing your Jira Cloud site URL, automation rules that use the {{issue.url}} smart value may still reference the old URL in Slack notifications and other automation actions. Even though your site is updated and redirects work, the smart value does not always reflect the new domain as expected 1.

Workaround:
You can manually construct the correct URL in your automation rule using your new domain. For example, instead of using {{issue.url}}, use:

https://<your-new-domain>.atlassian.net/browse/{{issue.key}}

Replace <your-new-domain> with your updated site name. This will ensure that the links in your Slack messages point to the correct, current URL 1.

Atlassian's development team is aware of this issue. You can check out the bug report and add yourself as a watcher to get notified of any updates:

https://jira.atlassian.com/browse/auto-1809

[Dd]

Thanks @Bill Sheboy 

[Bill Sheboy]

Thanks!  I was searching for that open defect and did not find it with my criteria.