It's all about the answers!

Ask a question

Should resolving comments change the comment originator ?


Steve McDuff (3135) | asked Nov 07 '12, 3:34 p.m.
Here is a quick overview of our review process:
1 - Author creates the document and initiates the review
2 - Reviewer creates his comment
3 - Author responds to the comment, makes the necessary change and resolves the comment thread
4 - If the reviewer isn't satisfied with the response, he then opens a new comment.

A problem occurs on step 3 : Resolving the comment thread changes the originator of ALL the resolved comment to be the author, including the one that was originated by the reviewer.

This causes problems when reviewers then want to find out all their comments. Searching by the "From" field no longer works for them.

Are we using the product correctly ?

In my opinion, the originator of a comment should never change. 

There should perhaps be a separate  log that indicates who opened/resolved/re-opened comments for audit purpose.


Comments
Paul Sims commented Nov 07 '12, 4:48 p.m.

Steve, this is a change in behavior from the previous releases.


Robin Bater commented Nov 09 '12, 8:28 p.m. | edited Mar 07 '13, 5:05 p.m.
JAZZ DEVELOPER

Please can you indicate which version of RRC you are using?


Paul Sims commented Nov 10 '12, 5:51 p.m.

Robin, we recently upgrade from 4.0 to 4.0.0.1. We opened PMR 40822 999 000 to report the problem.

Accepted answer


permanent link
Stef van Dijk (2.0k179) | answered Apr 16 '13, 10:23 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
The PMR was confirmed and APAR PM77362 was created for this issue.
It has since been fixed in 4.0.0.2 via (PM77362) Resolving a comment changes author of comment in the Recent comments viewlet (port to 4.0.0.2) (67163) as well as 4.0.1 via Resolving a comment changes author of comment in the Recent comments viewlet (49509).
Steve McDuff selected this answer as the correct answer

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.