Recording Changes in Overlapping Projects

If you use projects to control transports, you can only use requests assigned to your current project to record changes.

When you edit lockable objects, conflicts may arise if the object that you want to change is already locked in a request that is not assigned to the project you are working on. This lock prevents the object from being edited simultaneously in another request. You must also meet the requirements of the project functions.

A dialog box informs you if a conflict of this type has arisen. You can remove the conflict in one of the following ways:

• If the object that you want to edit is locked in a request that is not assigned to a project, then you can assign the request to your project. You must be the owner of the request to do this.
• If the object that you want to edit is locked in a request that is assigned to another project, then you can only record changes in the other request.

  We recommend that you create dependency information between this request and the request you would have saved the changes in if the lock conflict had not arisen.

  You can also add the object to the project object list of your current project if it is not already there. This makes the object a part of your current project.