It's all about the answers!

Ask a question

RRC 4.0.1: lock an artifact beyond editing?


Frank Ning (50025119133) | asked Feb 27 '13, 1:53 p.m.
Hello,

I understand that one can lock a file for editing and the lock will be released after the edit is done or user logs off. We can also assign ownership to artifacts to control who can do editing (write).

I am wondering another option: can we lock an artifact like what we can do for a source file in RTC so that no one can change the artifact?

Thanks and regards

Accepted answer


permanent link
Robin Bater (3.4k47) | answered Feb 27 '13, 2:53 p.m.
JAZZ DEVELOPER
On the RM V4.0.3 release plan there is this plan item

[RM] Simplify RRC Locking to Support Artifact Creation/Editing

which is trying to help answer the following scenarios

  1. User needs to edit an artifact without having somebody editing at the same time and potentially losing their edits.
  2. User needs to edit an artifact (or artifacts) over an extended period of time without having anybody else edit the artifact during that time.
  3. Admin needs to be able to easily identify (and release) existing locks

Frank Ning selected this answer as the correct answer

One other answer



permanent link
Brian Fleming (1.6k11928) | answered Feb 27 '13, 2:50 p.m.
In 4.0.1 only wrapped artifacts allow for a persistent lock.  Native artifacts have the edit locking you have described.

The locking behavior is changing in 4.0.3 to allow for persistent locks across all artifacts (among other changes).  See
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=55816
and
https://jazz.net/rm/web#action=com.ibm.rdm.web.pages.showArtifact&artifactURI=https%3A%2F%2Fjazz.net%2Frm%2Fresources%2F_yhJiEHnaEeKkK5jNQNV-cw
for details.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.