I'd like to update the current issue from a workflow post function with JMWE in a way that doesn't send any notifications.
To achieve this, I tried unchecking "Send notifications" under the function:
However, with this, still, notifications are sent. E-mails can be handler by a filter, but having to click the bell notification in Jira in the top-right corner is really annoying.
I thought that we can get rid of this by running the post-function not as the add-on user, but the current user:
This breaks, however, if the current user is not an admin on the project:
How can we prevent JMWE updates from triggering notifications?
Thank you!
Most notifications simply cannot be avoided, this is a limitation of the Jira Cloud rest API that all apps must use. The only changes where the notification can be disabled are field changes done by the Set Issue Fields and Copy Issue Fields post functions.
The mentioned 403 error also happened with an issue field update, with the JMWE "Set issue fields" post-function. And it seems that it's also something that otherwise causes a bell notification, even if notifications are supposedly disabled for the function.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Zoltán Lehóczky ,
The 403 error is related to using the current user. Only the addon user can disable notifications (it's a Jira cloud limitation).
Can you explain what you mean by "bell notification"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your answers.
see. I kept "Send notifications" unticked even when using the current user, since the checkbox is still there even if you select that as the "Run as user".
By "bell notification" I mean the in-app notifications of Jira, as opposed to notification e-mails:
Do I understand correctly that this is the case?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The only thing you can deactivate are notification emails. In-app notifications cannot be deactivated afaik. And note that the option on the JMWE Configuration page only controls the default value of the same option on the actual post function configuration screens, so what matters is the actual post function configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you tell what you mean by "actual post function configuration screens"? I only see one option, this one:
Apart from the above one, we have another similar field-setting post function, and then only standard built-in one, none of which seem to be related to notifications:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's the one I meant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK, so this story is less then ideal. What I've written above is true though, you can disable notifications for yourself by enabling the notifications for others - which they'd get anyway, since that's not possible to disable...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.