<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Can&#039;t un-assign a person from a ticket</title> 
  <pubDate>Fri, 10 Apr 2026 00:42:29 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/9540</link> 
  <atom:link rel="self" type="application/rss+xml" title="Can&#039;t un-assign a person from a ticket" href="https://bugs.horde.org/ticket/9540/rss" /> 
  <description>Can&#039;t un-assign a person from a ticket</description> 
 
   
   
  <item> 
   <title>Doing shift-click unselect from user in assigned list doesn&#039;</title> 
   <description>Doing shift-click unselect from user in assigned list doesn&#039;t do anything (at least if that user is the only user assigned to a ticket).</description> 
   <pubDate>Tue, 25 Jan 2011 21:58:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9540#t61605</link> 
  </item> 
   
  <item> 
   <title>This broken behavior is even mentioned in the commit that br</title> 
   <description>This broken behavior is even mentioned in the commit that broke it. Michael (R.), why was this commit necessary in the first place? http://git.horde.org/horde-git/-/commit/6e57615ef92b4e06bd04378c159dcbd271c8a5a4?rt=horde-git&amp;ws=1</description> 
   <pubDate>Sun, 13 Feb 2011 17:49:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9540#t61791</link> 
  </item> 
   
  <item> 
   <title>&gt; This broken behavior is even mentioned in the commit that </title> 
   <description>&gt; This broken behavior is even mentioned in the commit that broke it. 

I&#039;m not sure this commit caused the broken behavior. Without this patch it was impossible to make ANY changes at all since the form validation would always fail.

The specific issue the patch addresses is the fact that Whups_Driver::getOwners returns both users and group owners, while the form needs them set individually.


&gt; Michael (R.), why was this commit necessary in the first place? 
&gt; http://git.horde.org/horde-git/-/commit/6e57615ef92b4e06bd04378c159dcbd271c8a5a4?rt=horde-git&amp;ws=1
</description> 
   <pubDate>Sun, 13 Feb 2011 20:23:23 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9540#t61792</link> 
  </item> 
   
  <item> 
   <title>I just changed the values passed to the setDefault() call in</title> 
   <description>I just changed the values passed to the setDefault() call in that commit, but what is probably needed is to set the value of the $var, instead of setting the default of the form field. Not in front of my computer at the moment, so I&#039;ll investigate this later if needed.</description> 
   <pubDate>Sun, 13 Feb 2011 20:39:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9540#t61793</link> 
  </item> 
   
  <item> 
   <title>Testing</title> 
   <description>Testing</description> 
   <pubDate>Mon, 14 Feb 2011 00:52:12 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9540#t61794</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

Fix ticket f</title> 
   <description>Changes have been made in Git for this ticket:

Fix ticket form editing.
No need to set *any* value here at all, anything added here will override the
submitted value of the form. Not sure how this ever worked...

Fixes Bug: 9540

http://git.horde.org/horde-git/-/commit/617f0ed9e23ec8281a7e90fe78c7cc530b9047db</description> 
   <pubDate>Mon, 14 Feb 2011 01:08:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9540#t61798</link> 
  </item> 
   
  <item> 
   <title>Fixed.</title> 
   <description>Fixed.</description> 
   <pubDate>Mon, 14 Feb 2011 01:31:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9540#t61799</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
