We have a Defect workflow that uses multiple projects. In that workflow, from the In Progress transition, the field was made required through a validator. It was applicable to all projects. Now, one user has requested that the field be optional for their project. How can we implement this in Jira without changing the existing workflow? Any ideas?
Hey @keerthika Narra,
It sounds like you are referring to a "logical validator," which suggests that you might be using Jira Workflow Toolbox.
If that's the case, an expression like
%{issue.cf00000} != null OR %{issue.project.key} = "ABC"
should do the trick - using the correct custom field ID and project key, obviously.
If you're using something else, please provide additional details as requested here.
Regards from Germany,
Thorsten
Hi Throrsten,
Thanks for helping in the logic, the logic is working fine, But i have one issue for other projects it was not displaying the field name , it was displaying just error message, how can i modify
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @keerthika Narra,
Have you checked the 'Error message' section at the bottom of the validator configuration?
Besides, if your initial problem is resolved, please don't forget to accept the answer.
Regards,
Thorsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Thorsten Letschert _Decadis AG_
After posting the thread i got an idea, to update the message in Error tab, i did that and it was working fine.
Thanks for your support....!
Regards,
Keerthika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @keerthika Narra ,
You're more than welcome! Would you mind accepting my answer then?
Regards,
Thorsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are using the standard validator, you can't set it as not required only for that one project; you will need to use another workflow. This is true if the scheme is shared.
You can copy the workflow you are using and delete the validator from the new workflow.
If you are using a third-party app like JMWE, you can set the validator as not required for that project.
Or you could create a new custom field and use that one in the project.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In existing work flow transition can we create a new validator with logical validator?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The reason behind my question what Apps you have because with a specific one you can get the desired outcome.
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.
In same existing workflow can we update validators?
I have one solution but I am not sure it will work or not
in validators logical validator if we keep the x field = null and project = xyz and x field != null
just i have the logic but i am not sure how to implement
anh inputs Acceptable
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since your existing process is working, definitely you don't want to break it. Which Atlassian Marketplace Apps do you have in your instance?
Best,
Fadoua
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.