Hi,
I created this automation here.
But for some reason, it does not work when the issue is in status "Aguardando cliente". Here's the error log.
I thought the problem was with the Permissions for "Transition Issues". So I added Project Role (Service Desk Customers) to the permission, but the erros still happens.
Please, what should I do? As far as I'm concerned, everything is set correctly.
Thanks,
Gui.
@Gui Ávila,
I would try changing that for sure. If you want that rule to run when you're customers comment back, I could see there being problems with the execution due to that.
Thanks,
Kian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But @Kian Stack Mumo Systems I added permission for "Transition Issues" to the project role "Service Desk Customers". So everything should work ok!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Gui Ávila,
I replicated your configurations - IE I added a customer to my desk, set up an automation rule like you had, and I added the customer Desk Customers role to the transition issue permission.
I was able to replicate your issue and then fix it by changing the rule to execute as "Automation for Jira".
The issue is that even if the project of "Service Desk Customer" is added to the permission of "Transition Issue", it's not going to work right. The Service Desk Customer only has access to specific pieces of information/capabilities and modifying the permission scheme won't give them more capabilities. The only option for you is to change the rule back to rule as the automation actor, or someone else that has Service Desk Team role.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kian Stack Mumo Systems Thanks. But, wow, so why does Atlassian allow to add Transition issue permission to Service Desk Customer, if it does not work? They should fix that :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, you're just allowing the rule to run as the person that initiated it.. I'm not sure how they would prevent that at a global level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the screenshot you shared, the bottom execution you highlighted is not an error, it just didn't match the conditions you've specified.
The top one is a bit more concerning.. The error message makes it seem as though Jira cannot retrieve the issue. Is that the same error you get on the rule that ran on Feb 2nd at 1:37 PM?
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.
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.