I want to make Component Field Mandatory only when Resolving the ticket, not while creating while editing a ticket and only for A project (The component linked with Project A , Project B , Project C)
I tried to make changes in Workflow "Resolved" transition validator , i dont see any valid option to add the validator.The option which i see is
1) Validates that the user has a permission.
2) Runs a script to check validation, or a built-in script.
3) Validator that depends on a Boolean expression.
4) Validates that the user has a permission, where the OSWorkflow variable holding the username is configurable. Obsolete.
5) Field Not Empty Workflow Validator
Can you please guide me with a details steps
Hi @Sharadkumar Bangera ,
You can add a transition screen for Resolved transition with component field and field required validator.
Field Not Empty Workflow Validator. Make component/s required.
For Option 2:
You can also use simple scripted validator with "Runs a script to check validation, or a built-in script". Remove the component field from create and edit screen. Add the field to the transition screen. Add the below simple scripted validator
issue.getComponents().size() != 0
Hi @Niranjan
Thanks Niranjan for the update.
For option 1, the transition screen is also shared by other 3 projects and i dont want the other 3 projects are also impacted because of the specific requirement in project 1.
Can you help me how can i implement it without any impact on other projects.
Please elaborate the steps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Niranjan for the update.
For option 1, the transition screen is also shared by other 3 projects and i dont want the other 3 projects are also impacted because of the specific requirement in project 1.
Can you help me how can i implement it without any impact on other projects.
Please elaborate the steps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sharadkumar Bangera ,
In that case, the best option would be to copy the workflow scheme and create a dedicated scheme/workflow for the project that needs the change.
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.