DKingston149028 (Community Member) asked a question.
I've followed the basic instructions for configuring the Flaw Importer (https://help.veracode.com/reader/zriMYydma5AUKAFYh3xDnw/3Z209IgT7putezHGfEbKwA), but my next hurdle is the required custom fields on the bug work item template.
Failed to create WorkItem 'Azure Devops: Veracode Flaw (Static): Information Leakage, <Veracode Profile Name>, Flaw 271' Error: Failed Request: Bad Request(400) - TF401320: Rule Error for field Environment. Error code: Required, HasValues, LimitedToValues, AllowsOldValue, InvalidEmpty. 2 additional errors occurred during validation of the work item. Please correct all errors and try again.
Is there a way to configure the importer plugin or the build to supply the necessary values to any required custom fields on the bug it's trying to create?
.png){kind=logo}
Hi @DKingston149028 (Community Member) - thank you for your question! I will share your question in the @Integrations Group for visibility. In the meantime, I am also reaching out to other community members as well as Veracoders, see if anyone has some experience on this. Stay tuned!
HI @DKingston149028 (Community Member) - I checked with our support team and confirmed that the issue is that you are using in your Azure DevOps a custom process template that uses required fields to construct their new .NET work items from the exported Veracode flaws. The Veracode Azure DevOps extension does not currently support this. I encourage you to submit this enhancement request to the Ideas portal - it will give other customers the opportunity to weight in with upvotes/comments that increases visibility as the Veracode Product team prioritize the roadmap. (check out this knowledge article on how to submit your Idea). Look forward to seeing your feedback up there! 💡
Thanks Shuning,
Support has already created an ticket for this implementation, besides I've also created the Idea to prioritize it.