Changesets and updating work
Note: my job was probably made harder because I didn't want to make the join table a first class model object with a primary key and changesets and all that.
That is, I was working from this bit of documentation: There are users and organizations.
Mercurial revision numbers are never stable when working across repositories, especially when obsolescence is involved. Pushing only adds changesets to a remote repository; it does not update the working directory (unless you have a hook that updates for you).If it was, the previous approvals for qa and prod would apply to the new change set.Management does not want to have to approve delivery to dev.I don't want a developer to be able to associate a change set to a work item that already has delivered change sets associated to it.I see that advisor "prevent linking to approved work items" can do this if approvals are used.