Hi,
I would like to create a manually triggered automation, to transition an issue to rejected or done status. I am creating a issue transition to desired status from all statusses. But automation does not work this way, it only works if a direct transition exists.
Is there a solution for this error. I am a site admin so there should not be a permission issue.
Hi @Alkan Arun and welcome to Community!
Is there a specific reason why you want to trigger an automation rule instead of configuring the workflow itself? You could restrict the transition to Rejected/Done to only site-admins:
Hope this helps!
- Manon
Hi thank you for your response, I would like to restrict this action to a specific group for example sales team. But all transitions are already restricted to only current asignees. So I have to create a bypass.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you want both the assignee and the sales team group to be able to transition the issue, you’ll need to adjust the rule settings to "can be any". See example below:
You'd just need to select the "sales team" group instead of "administrators".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yes but the problem is issue transitions are only permitted to assignees so this solution doesnt work. Because they would like to close the issue whenever they want. That's why i tried to create a rule that only they would see and execute this rule from any status when they are not the assignee. and by this rule they could transition issue to done or rejected status. Workflow is too crowded to create a transition from all of the status, so i used the "any" transition on first pic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Akun,
As you stated, Automation cannot do something that a regular user also cannot do (in most cases). So, if a transition does not exist, then Automation cannot make the ticket go to 'REJECTED' straight away.
You've mentioned in the first picture that the 'Any' transition 'doesn't work'. Can you clarify? You can set limitations in that transition in the workflow editor by defining who is allowed to make that transition.
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.
Hi thank you for your response, I explained to Manon why I need this. You know you can give a transition to a status from "Any" statuses. I already did that so there is a transtition. but it is not accepted as a transition.
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.