On JIRA 7.0.5 and Service Desk, when I try to create a automation rule to alert user about upcoming SLA breach, I can only add a user. Is there a way to alert the assignee of the issue not a particular user?
The Alert I believe simple @mentions someone in a comment. You could simply add a private comment instead to notify the assignee of the upcoming event.
Under the 'THEN' section, "@ Alert user" it has to be a specific user name. I am trying to alert the Assignee so that it can be applied to all the issues.
You cannot. There is no function to do so.
As a workaround, you can simply Add Comment (Internal) and ensure your notification scheme sends Issue Commented events to the Assignee.
Thanks for your response. I am using Escalation Service to add a comment and I am trying to use
IssueInputParameters setComment(String comment, String groupId)
to add an Internal comment. Do you know which group should I use for groupId? We are using Service Desk. Thanks for your help.
Hmm, interesting. I think we're running into a current limitation –
https://thepluginpeople.atlassian.net/wiki/display/JEMH/What+makes+JSD+Comments+Public+or+Private
https://jira.atlassian.com/browse/JSD-2347
https://jira.atlassian.com/browse/JSD-1505
does not work if a service desk user creates an issue. Jira pretends that he's a customer, so only public comments would work. In this case, all users would receive an email.
Hello,
Just an accidental find while messing around that actually works.
Step 1: Find the internal username
Go to any workflow and edit it. Go to create transition and add a Post Function.
At the Post Function page, pick Update Issue Field.
Choose Issue Field Assignee and pick the third option (start typing...)
Start typing the desired user. Find him/her and click.
What is written in the field after the click is some kind of internal username.
If there is an easier way to find out this username, please, let me know.
Step 2: Add the internal username to the comment exactly as [~internal-username]
Step 3: Click preview...
-----
It also works with the wildcard [~assignee]
Unfortunately, using [~assignee] does not dynamically tag the assignee of the issue where-in this automation is triggered. It simply navigates to a general user profile.
Yes, you are right. I have noticed it about two months ago that this is not working any more.
It looks like you're new here. Sign in or register to get started.
