I created a global automation rule that syncs the comments between two tickets in two different Jira Service Management projects.
Unfortunately if I limit this rule Jira Service Management Projects I lose the option to choose the visibility of the comment.
I would expect it to be gone, only because the projects are the same type and the type of the original comment will just be taken over. But this does not happen.
No matter if the comment is to the customer or internal the Automation for Jira user will copy it as an internal comment.
Changing the executing user to my own or another administrator does not help.
What do I miss here?
If I understood everything right there is an issue in "previous" issue tracker with Codebarrel (Atlassian aquired Corebarrel some time ago) which deals with this annoying effect:
Assuming this is the case what you are seeing here the suggestion either would be to wait for a fix or to try the workaround listed over there (add an if-else with two matching comment actions).
Hope this helps a bit.
Regards,
Daniel
My guess is It might also be a license issue - the automation user may not have an agent seat, and thus can only create internal comments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
as I wrote, I already tried it out with my user, which has all the rights he needs in JSM and is of course fully licensed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My apologies - you had written that you had created the global rule and applied it to those projects, but it wasn't clear to me that you also had an agent license for JSM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I normally do is first check the type of comment using {{comment.internal}}, it will return true for internal comment and in those cases I don't use the add public comment checkbox. I use if else block for either adding internal or external comments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I'm not really understanding what you are suggesting. How should I - even if I successfully checked - define a comment to be public, if the option to do so goes missing as soon as I narrow the range of the rule down to Service Projects?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.