Azure DevOps | Work Item strategy

[gioce90]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Azure DevOps

Please tell us more about your question or problem

Following issue #3395, we now have a Work Item linked to a Pull Request on Azure DevOps. My question is: is this approach sufficient?

Sometimes it might be better to have a specific Work Item dedicated to a specific repository. Other times, it could make sense to have one Work Item for all low-impact updates (e.g., covering all patches and minor updates) and separate Work Items for each major update.

Additionally, assigning the Work Item ID dynamically doesn’t seem possible (correct me if I'm wrong). Maybe a sort of pre-upgrade task would be more appropriate?

I’d be curious to hear about your strategies on this topic. How do you use the azureWorkItemId configuration options?

Logs (if relevant)

No response