-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New directive : bypassrule #83
Comments
Can you elaborate your scenario more? I can easily imagine one of the following two scenarios and the solution using existing features:
Looking forward for your reply |
Sorry I didn't explain myself well, I talk about the possibility to use the parameter bypassRules in this method. So, we can update a workitem and Azure DevOps process rules can be ignored. In my case, I made a mandatory field but in tfsaggregator I want to update a workitem without being obliged to fill it in (this must be done by the user). |
I see: adding backlog labels |
should this be an option or always valid? BUT: Having this Option set to true, the provided PAT needs to have the appropriate permission to bypass rule validation (see also #74). |
I understand your point of view, but as you say, if it's always valid, it means giving an additional right all the time, which managers may not want ? |
Feature added in 1.1 |
Hello,
In a rule, have possibility to specify this directive :
.bypassrule=true
In this case, when a workitem is update, the process rules are ignored.
Thank you.
The text was updated successfully, but these errors were encountered: