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
SSC Custom Tag updated and message added when Bug is not updated #59
Comments
@rsenden is there any update on this? |
Unfortunately I don't have time to look into this right now as I'm very busy with customer engagements. I hope to have some time to look into this somewhere in the coming 2-3 weeks. I think the utility just invokes the SSC API to set the tag value, without taking into account whether the custom tag was already set to that same value. I didn't consider that this would add a message to the issue history on every run (I assume this is why you reported this issue, correct?). So either the utility should check the existing value before updating it, or SSC shouldn't add the history message if the custom tag isn't actually being changed. I'll need to think about and discuss with the SSC team what would be the best option. Please ping me again if you haven't heard back in about 2 weeks. |
Fix will be included in next release |
@rsenden, with FortifyBugUtility-4.2, we are seeing that ADOBugState update messages are added with each bug utility run even when the ADO Bug was closed long ago or no action is taken by the user. Meanwhile, the correct behaviour would be only update custom tag when there is a change from older tag.
The text was updated successfully, but these errors were encountered: