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

Possible to use references from Microsoft.VSTS.Common? #54

Open
kleeklee opened this issue Feb 1, 2017 · 4 comments
Open

Possible to use references from Microsoft.VSTS.Common? #54

kleeklee opened this issue Feb 1, 2017 · 4 comments

Comments

@kleeklee
Copy link

kleeklee commented Feb 1, 2017

More specifically trying to use Microsoft.VSTS.Common.Priority and Microsoft.VSTS.Common.Severity.

@kria
Copy link
Owner

kria commented Feb 1, 2017

What do you want do with them?

To display those fields in a notification, you should be able to add them to wiCreatedDisplayFields (displayed during WorkItemCreated) or wiChangedDisplayFields (displayed during WorkItemChanged).

To have a rule that matches when any of them change, you'd add them to the workItemfields in the rule element.

@kleeklee
Copy link
Author

kleeklee commented Feb 1, 2017

Attempting to get priority and severity to be displayed for each bug notification. I've added them to workItemfields with no luck. However, system.state, system.iterationpath, system.reason, etc. all seem to work fine.

@kria
Copy link
Owner

kria commented Feb 1, 2017

Like I said, workItemfields doesn't determine what is displayed, it's those other two settings that are of interest to you.
I tried it and the way it's coded, it only works when you change the values. These aren't core fields so they will only show up in changed fields in the event. I should probably merge those two structures and look in both. This is what it looks like if I have added them to wiChangedDisplayFields and change both of them.
image

You probably are interested in seeing them when the bug is first created, right?

@kleeklee
Copy link
Author

kleeklee commented Feb 1, 2017

Ah OK I think I have a better idea of it now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants