Bug 492875 - Can't assign tickets to anybody with 3.6.7
Can't assign tickets to anybody with 3.6.7
Status: CLOSED NOTABUG
Product: Fedora EPEL
Classification: Fedora
Component: rt3 (Show other bugs)
el5
All Linux
low Severity high
: ---
: ---
Assigned To: Xavier Bachelot
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-30 10:03 EDT by Chris Adams
Modified: 2009-03-30 10:35 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-03-30 10:23:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Adams 2009-03-30 10:03:00 EDT
I upgraded RT3 from 3.6.5-3 to 3.6.7-1 and lost the ability (even as superuser) to assign tickets to anybody.  When I pull up the "Basics" screen for a ticket, the "Owner" drop-down only lists "Nobody" (none of my users are in there).  I rolled back to 3.6.5-3 and it works again.
Comment 1 Chris Adams 2009-03-30 10:23:40 EDT
It looks like a newer version of DBIx::SearchBuilder is required.  I grabbed 1.54-2 from rawhide, rebuilt it for RHEL 5, and RT3 is happy again.  See also:

http://lists.bestpractical.com/pipermail/rt-users/2008-March/050830.html

I'll file an update request for DBIx::SearchBuilder I guess.
Comment 2 Xavier Bachelot 2009-03-30 10:35:55 EDT
perl-DBIx-Search builder was already updated in EPEL 5 on my request, to fix this issue. I've since then pushed another rt3 release which enforce the requirement on both perl-DBIx-SearchBuilder >= 1.53 and perl-Devel-StackTrace >= 1.19 (security fix). This new rt3 release is available in EPEL5-testing. It's not flagged for the next stable push, but I will ask Thorsten to add it to the push.

Note You need to log in before you can comment on or make changes to this bug.