Azure-devops-docs: Closed By field is copied when copying a work item
This document says that no history is copied over, but we noticed that the "Closed by" field is copied from a Closed work item (TFS 2017, Update 3). Is that part of the History? Is this a bug in the docs, or a bug in TFS?
This is like #4200, but it looks like I had the wrong link in that one - this time I made sure to grab the link specific to TFS 2017.
pabrams
>All comments
@pabrams - Thank you for your inquiry. I received this reply from our engineer on this feature:
It all depends on the customer’s process. If they have no state transition rule on their work item type that says to clear “ClosedBy” field when State is “New” or “Active”, it will get copied over. Our OOB templates have this rule so we wont be able to repro this issue with our OOB processes, but customers can define their process any way they want. We should ask the customer to give us their process (atleast for their particular affected work item type) so we can look at it.
I see a similar DTS from 3 months ago which explains the detailed reason in the discussion. To not have similar issues in future, we made a change in our copy logic to not copy some hardcoded field and ClosedBy is one such field, but this change is not in TFS 2017.
I will update the topic to clarify the behind-the-scenes actions and the versions they apply to.
KathrynEE
on 3 Aug 2019
Related issues
letmaik
·
3Comments
dannyvv
·
3Comments
atrauzzi
·
3Comments
adnanebrahimi
·
3Comments
KacperMucha
·
3Comments
Most helpful comment
@pabrams - Thank you for your inquiry. I received this reply from our engineer on this feature:
It all depends on the customer’s process. If they have no state transition rule on their work item type that says to clear “ClosedBy” field when State is “New” or “Active”, it will get copied over. Our OOB templates have this rule so we wont be able to repro this issue with our OOB processes, but customers can define their process any way they want. We should ask the customer to give us their process (atleast for their particular affected work item type) so we can look at it.
I see a similar DTS from 3 months ago which explains the detailed reason in the discussion. To not have similar issues in future, we made a change in our copy logic to not copy some hardcoded field and ClosedBy is one such field, but this change is not in TFS 2017.
I will update the topic to clarify the behind-the-scenes actions and the versions they apply to.