Skip to content
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

Closed
adu80 opened this issue Dec 9, 2019 · 6 comments
Closed

New directive : bypassrule #83

adu80 opened this issue Dec 9, 2019 · 6 comments
Labels
enhancement New feature or request good first issue Good for newcomers pinned Stops stale[bot] from closing this issue

Comments

@adu80
Copy link

adu80 commented Dec 9, 2019

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.

@giuliov
Copy link
Member

giuliov commented Dec 9, 2019

Can you elaborate your scenario more? I can easily imagine one of the following two scenarios and the solution using existing features:

  1. you do not want trigger a rule for a specific event -- disable or remove the mapping in the DevOps Project
  2. you want to disable a rule altoghether -- disable the rule using Aggregator CLI or any Azure interface like Portal, Az CLI etc.

Looking forward for your reply

@adu80
Copy link
Author

adu80 commented Dec 10, 2019

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).

@giuliov giuliov added enhancement New feature or request good first issue Good for newcomers labels Dec 10, 2019
@giuliov
Copy link
Member

giuliov commented Dec 10, 2019

I see: adding backlog labels

@giuliov giuliov added the pinned Stops stale[bot] from closing this issue label Dec 10, 2019
@BobSilent
Copy link
Collaborator

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).

@adu80
Copy link
Author

adu80 commented Dec 11, 2019

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 ?
I'm divided. Personally, I wouldn't mind if it was still activated.

@giuliov giuliov removed the pinned Stops stale[bot] from closing this issue label Dec 26, 2019
@giuliov giuliov added the pinned Stops stale[bot] from closing this issue label Sep 19, 2020
@giuliov giuliov mentioned this issue Jun 12, 2021
@giuliov
Copy link
Member

giuliov commented Jun 12, 2021

Feature added in 1.1

@giuliov giuliov closed this as completed Jun 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers pinned Stops stale[bot] from closing this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants