I've used the following syntax ... none successfully:
@{{issue.customfield_XXXX.replace("\\@,thatGuy")}}@{{issue.customfield_XXXX.replace("\@,thatGuy")}}@{{issue.customfield_XXXX.replace("@,thatGuy")}}
Hi @Katie Kusjanovic
For a question like this, context is important for the community to help. Please post the following:
Until we see those...
What problem are you trying to solve with the replacements? That is, "why do this?"
That at @ character can be replaced without escaping for a text field like this:
@{{issue.description.replace("@, Bill")}}
However, if you are actually trying to replace a user mention in a field, those are stored to use markup with the account ID value. For example:
[~accountId:557057:1d4fd7f4-bbac-4466-82ee-aaabbbccc]
Kind regards,Bill
i have a field (issue.customfield_11010) that contains an email address - katie@nope.nope and i want to change it to be katie[@]nope.nope
the use case here is just simple content manipulation .. nothing fancy like the user mention example you posted.
the audit log seems to be pretty hunky-dory ... no issues with the rule firing weirdly / not firing
Hi, @Katie Kusjanovic
I checked smart value modification, that you're using, and it's working
@{{issue.customfield_XXXX.replace("@,thatGuy")}}
In order to replace @ with [@] just use construction
@{{issue.customfield_XXXX.replace("@,[@]")}}
I made a basic rule, to check it:
Looking at the log you show, your rule uses the Edit Work Item action. When you write the "after value", is that from the field?
If so, the edit only updates the value stored in the Cloud, not what the rule has in memory. Please add a Re-fetch Work Item Data action after the edit action, and before the comment and write to the log. This will reload the data from the Cloud.
It looks like you're new here. Sign in or register to get started.