Trying to validate a field before a transition in my team managed project workflow. There are only about 6 Rules, none of which do this. There is one that checks that a field is a specific value, but not that it is set.
The Atlassian documentation implies there are a variety of rules to chose from for validation. Where are they? Can I create my own?
What validation are you trying to apply?
If you are trying to ensure the field is set to some value without caring what that value is then you can use the rule
"Restrict to when a field is a specific value"
Set "Check if it" to "Doesn't equal".
Leave the "This value" field empty.
This rule is more like a Condition (from Company Managed workflows) in that the transition will not even be selectable if the rule doesn't pass.
This works, as long as I can stomach the warning :-) It quietly disappears the transition when the condition is not met, so we'll see how the team reacts when they can't see the familiar transition... wish the transition stayed, but gave a warning that it cannot proceed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a new feature that is still rolling out, so if you currently do not see it you should see it soon. Sometimes the documentation is describing features that have not yet hit every customer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
By the way, here is the product release note about it, as you can see this started rolling out in January 2023.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was also hoping to use this mechanism to trigger other actions. For instance, there is no bulk clone, but I could add an individual clone to a transition (ANY->CLONE_STATUS) and then use bulk transition to trigger a bulk clone on a subset of the issues...
There are other ideas... it just seems like the pre-baked rules are very limited. Wondering if there is a way to add rules to what is already there...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No there is not a method to add your own custom Rules to the options available in Team Managed project workflows.
You might look for third party apps that can extend workflow capabilities, but I suspect that not many, if any, have been developed that would work specifically with Team Managed projects.
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 confirming this, @Trudy Claspill
Knowing this, I've figured out a different work-around, using automation triggered by a field flipped -- with the advantage that i now can also get a list of new issues that have not been cloned yet. Interestingly, the cloning built into automation seems to work differently than the manual one -- somehow checklists get cloned manually but not through automation....
Any idea what's different between the two?
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.