Answers.Body: <p>This is a defect. See issue CRM-18698 for details.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-31T01:08:49.447Z
Answers.LastActivityDate: 2016-05-31T01:08:49.447Z
Answers.UserDisplayName: Ken West
Body: <p>In 4.7, when managing a case, I try to reassign a role to another contact, but it adds a new one.</p>
  
  <p>It should delete the old relationship. The button is an 'edit' pencil and the hover text says 'reassign'. There is a separate add role button.</p>
  
  <p>The function that is invoked is relationship() in CRM/Contact/Page/AJAX.php but the "cid" value is not set (this should be the Contact Id of the current person holding that role). So the existing relationship is not deleted.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-26T05:13:23.470Z
Comments.Text: Can you reproduce this on the public demo at demo.civicrm.org? If so, you should file a bug report at issues.civicrm.org, and if possible, a suggested patch fix.
Comments.UserDisplayName: Demerit
Tags: <civicase><issues>
Title: In 4.7 CiviCase, why does reassigning a role not delete the old one?
ThreadText: # In 4.7 CiviCase, why does reassigning a role not delete the old one?
  
  (Asked by: username_0 on 2016-04-20)
  
  In 4.7, when managing a case, I try to reassign a role to another contact, but it adds a new one.
  
  It should delete the old relationship. The button is an 'edit' pencil and the hover text says 'reassign'. There is a separate add role button.
  
  The function that is invoked is relationship() in CRM/Contact/Page/AJAX.php but the "cid" value is not set (this should be the Contact Id of the current person holding that role). So the existing relationship is not deleted.
  
  **Tags:** civicase, issues
  
  > **Comments:**
  > **username_1**: Can you reproduce this on the public demo at demo.civicrm.org? If so, you should file a bug report at issues.civicrm.org, and if possible, a suggested patch fix.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-05-31. Score: 2
  
  This is a defect. See issue CRM-18698 for details.
  
  
  ---
  
  