How do you accept a changeset into a stream, when the changeset is associated with a workitem in another project area.
One answer
You would typically not accept changes from a work item into a stream.
You would accept them into a repository workspace and then deliver them to your Stream in Project A.
If you flow from one stream to another, you need to be able to see both objects.
Comments
Thanks for the reply. The question is not about accepting changes from a work item into a stream but from a parent stream into a child stream. If the changeset is associated with a work item from another project, which the user does not have access to, then they cannot accept the changeset from the parent stream into the child stream even though it shows as incoming to the child stream. The user has full access to both parent and child stream. They can however accept it into a workspace.
What message comes up if you try?
deliver failed - missing work item
You have a precondition on delivery configured to have a work item connected to the change set. Have a look at the operational behavior. If the work item can not be found by the operational behavior it will fail. You can configure what you want there:
yes the project has that operational behaviour set - but this is an accept not a deliver - the message says 'deliver failed' when the user tries to accept - and the changeset already has a work item associated so meets the behaviour requirement.
An accept from another stream into a stream is effectively the same as a deliver to a stream.
Can the operational behavior "See" the work item? If the user does not have access to the project area where it lives in, the operational behavior, which runs in the context of the current user, will not be able to see it.
ok - but can the operational behaviour not see that a work item is already associated even though the work item itself cannot be viewed? and why does it allow the user to accept the changeset into their workspace?
Because accepting into a workspace does not trigger the behavior. The behavior will however be triggered if the user delivers the changes from the workspace to the stream.
If the change sets are linked to work items the operation can't see, you will get the same error then.
You could override this for a specific role, or the integrator has access to both team areas.
ok - thanks for the prompt response.