Rights not migrating

I’m migrating from RT v.3.0.9, Postgres to v3.6.0, MySQL v 5.0.22 on
Fedora Core 5. Our old setup has a group called RT_Admin to which I
belong. This group has SuperUser rights.

I’m using the script for moving from Postgres to MySQL posted on the
wiki by, I believe, Jesse. Previously, I’ve had no problems with this
process. However, now when I move the database dump-file over to the
new version the rights of that group are apparently wiped out as no one
in the RT_Admin group has access to the Configuration menu.

Have others had this happen? As I said, previously it wasn’t an issue.
It suddenly has become one though. Any help would be appreciated.

Mathew Snyder

Grant ShowConfigTab rights to the group. This was, IIRC, a change in
the 3.4.x branch so that root wasn’t a ticket owner simply because of
SuperUser rights.

Mathew Snyder wrote:

I’m migrating from RT v.3.0.9, Postgres to v3.6.0, MySQL v 5.0.22 on
Fedora Core 5. Our old setup has a group called RT_Admin to which I
belong. This group has SuperUser rights.

I’m using the script for moving from Postgres to MySQL posted on the
wiki by, I believe, Jesse. Previously, I’ve had no problems with this
process. However, now when I move the database dump-file over to the
new version the rights of that group are apparently wiped out as no one
in the RT_Admin group has access to the Configuration menu.

Have others had this happen? As I said, previously it wasn’t an issue.
It suddenly has become one though. Any help would be appreciated.

Mathew Snyder


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

We’re hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html

Drew Barnes
Applications Analyst
Raymond Walters College
University of Cincinnati

I’ll try that though I’ve found since posting my question that the group
isn’t even being brought over. It wasn’t a problem a couple of weeks
ago though.

However, having inherited the system, I didn’t know the root user
password. I’ve since found out what it is and am able to correct the
problem after migrating all the data by re-adding the group as root.

Mathew Snyder

Drew Barnes wrote: