Hi,
I have two linked issues having the same type but in differents status.
I'm trying to automatically change the status of one to the status of the other using a manual trigging automation
This rule doesn't work when issues' status are not successive.
Could you please help to find other solution.
thanks
Hi,
I have this Workflow:
My automation dosen't work when it takes more than one transition to reach the new status
Example:
Requested change: from "Draft" to " Approved "
Possible transitions : Draft --> Review --> Approved Or
Draft --> Review --> Checking --> Approved
Is there any change to be made to the automation or I have to implement another solution
Thanks
As far as I got it right:
for example you have Request A and Request B. Request B is linked to Request A.
Within Request A you click the manual trigger and expect Request B to be transitioned to the same status than Request A.
The point is within your workflow issues cannot transition "globally" from any status to another one.
eg.:
Request A is in status "Checking", Request B in status "Draft" --> If you know trigger the automtion rule within Request A the transition action cannot be done as it is trying to transition Request B from "Draft" --> "Checking" but the workflow doesn´t allow such a transition (as seen in the screenshot).
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your prompt response.
Using "Allow transition for all status " is not suitabale for me.
Could you please help me to find another solution ?
thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess it‘s a question of yout requirement and/or your way of working.
I get your point that global transitions are not an option. Workflow are designed to follow a certain process. There comes the difficulty:
as it seems the linked issue you r trying to transition is not in the correct. otherwise it could inherit the status from the trigger.
Or maybe the requirement needs to be broken down into different behaviours on different conditions.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If this could solve your problem please consider to click the "Accept" button in order to have this question marked as solved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Unfortunatly it doesn't solve my problem but it makes sense.
Thank you for your quick support,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Wafa SELLEMI and welcome to the community,
Could you please also add a screenshot of the involved issues? That might make it easier to understand and analyze your problem/requirement.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure what you mean by "successive". However, the transition of the linked issue will only work if allowed by the workflow, I.e. there is a transition from the current status to the new status. If this is what is preventing the automation to run as you desire then I suggest changing the workflow to use the "all" transition for all statuses.
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.