When we exchange Tracker artifacts with other lifecycle management tools, we want to have one system in the lead at any moment in time.
Therefore when artifacts are mirrored to another system only one of the two applications can be in charge.
For this reason we want to have the option a Tracker artifact is read-only if it is not in charge.

Via a dedicated role the artifact can then be updated to reflect the latest status or become again in charge.

Comments