Rename user failed with stack trace when using 'status changed to Closed after' in filter

Description

*This issue has moved*

This issue has been moved permanently to Adaptavist's Product Support JIRA instance.

All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.

Renaming user failed with stack trace when using 'status changed to closed after' in filter. See issue GRV-98.

Regards
Wilm

Environment

JIRA 4.4.5
Tomact 6
Oracle DB 11g

Activity

Show:
Jamie Echlin
March 13, 2012, 12:43 PM

It's difficult to keep up with the changing interfaces for the jql stuff. To be honest I'm likely just to remove the code that deals with updating filters. Is updating the old to the new user in filters useful to you?

Former user
March 14, 2012, 1:06 AM

Updating the filters is useful but a working rename script is more important. Isn't it enough to replace every old_username with the new_username via sql (function replace)?

Otherwise the filters are created by users and when they use usernames in the filters that are changed, they have to edit the filter again. That's life.

If you create a new version of your plugin, please include a fix to handle multiple directories (GRV-26).

Jamie Echlin
March 18, 2012, 12:03 PM

> Isn't it enough to replace every old_username with the new_username via sql (function replace)?

That's one way of doing it but arguably it's a bit naive, as you change the user name if it coincidentally appears in strings etc.

I'm going to change it so that if it can't modify a filter it just logs that and moves on. As you say the important thing is that it works and doesn't crash.

Assignee

Jamie Echlin

Reporter

Former user

Labels

None

Internal Complexity

Unknown

Internal Value

Unknown

Affects versions

Priority

Major
Configure