I have setup conditions on my workflow so that a user cannot transition when the Report = 'itteam' or 'Technology Security', but my tests all let me transition with those values in place on the Reporter field.
Any idea why the workflow is ignoring the conditions?
Using a condition in this instance and setup is correct for the requirement. But the condition was failing because it was set to 'Any of the following conditions', instead it should be set to 'All of the following conditions'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jack
Can you think what could be causing my setup not to work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is not what that condition is doing. It prevents the itteam or technology security “users” from invoking the transition. Actually I spoke prematurely here. Let me ponder this further. I will have to test this out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for taking a look. But isn't what you describe supposed to be if I had used one of the 'User in...' condition types?
Any idea how I can stop an issue transition based on the value in the reporter field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I haven’t ever done this personally. However, I will have a look and see if I can achieve your goal and get back with you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think the issue here is that you are using string on a user picker field but need to validate that theory.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tafara Mugwangi , In fact this does work just fine for me.
When I tested, if I set the Reporter to the user that is listed in the != condition then the transition does not show in the list of available transitions. As soon as I change the Reporter I see the transition.
Can you share more details/screenshots? Did you publish the workflow?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jack
I thought so it should work. I'm not sure what else to show so I have just took some screenshots along my etstign journey. I had previously published my changes but did it again just in case. See attached.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am on my phone so hard to see images fully. However can you check to ensure you have all transition into Assessment covered? Can you share workflow image?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jack
There are no other transitions into Assessment other than the one I covered. I have added an image of the workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm missing something here...
You OP has an image of a transition (Start work) from Waiting for support to In Development. This is where you have your conditions. However, the workflow is not illustrating that transition at all. Unless the line are hidden. Later you are showing the transition (Assessment) going from W4S --> Assessment with those same conditions. Which transition are you wanting the condition on and are you sure you have things setup as you want, have published the latest updates and are testing in accordance w/ the latest published WF? If so then I'm unsure where the problem might be. I might suggest you try a test project and WF and see if you can get the logic to work to assess if it is something unique w/ this project/WF or systemic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jack
Apologies I have two workflows on the same project that need and have the conditions. In my first screenshot I was showing workflow 1, later I was showing workflow two setup so pardon me. I will continue to use workflow two in the thread since I have posted all other screenshots based on that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've created a support ticket, will update what that route finds.
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.