Hi,
We have a modification which are related to two FDDs. Could we check in the code and use associate with these two FDDs at the same time? I am not sure if this will create any potential risk when we merge the code from one branch to another.
Thanks,
Yes, you can associate a changeset with many work items. This association doesn't have any technical impact in the code merge. However you need to consider your task management process - if one task is approved and another is not, what do you want to do with the changeset? Merge or not? Normally it's easier if you associate one changeset with one work item.
But it completely depends on your process, it's not a technical thing.
Hi Yuji,
Can you explain this scenario? I'm used to have related FDDs with references. E.g. if there is a need for an additional parameter, then one FDD describes the change and another will have a reference to this change and a dependency. So, first the parameter should then be developed before someone can continue with the second FDD.
In such a cases you can link those two work items in Azure dev ops as work is related and have dependency . If they share common CS you have to make sure you release/merge those two work items together.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
CA Neeraj Kumar 783
André Arnaud de Cal... 715 Super User 2025 Season 2
Sohaib Cheema 519 User Group Leader
