View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007260 | mantisbt | plug-ins | public | 2006-07-06 05:23 | 2013-06-06 05:35 |
Reporter | cas | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | new | Resolution | open | ||
Summary | 0007260: Moving multiple issues from an obsolete user to an existing user | ||||
Description | In case you want to delete a user, Mantis shows odd behavior when issues are updated in case they are related to this particular user. | ||||
Additional Information | The process for removing a user would be:
| ||||
Tags | patch, plugin | ||||
Attached Files | |||||
Thanks for the script. In my opinion the proper solution is for Mantis to populate the list of users in update as follows:
If you provide a patch for this, I can integrate it into Mantis 1.1. |
|
Would the following be a proper alternative :
|
|
I slightly modified cas job to replace entries for user id with drop down lists. |
|
Will transfer this one into a plugin for 1.2.0 |
|
Attached a plugin to be used as of version 1.2.0 |
|
I installed plugin but it doesn't work. When I converge from one user to another I get this message Database query failed. Error received from database was 0001146: Table 'bugtracker.mantis_project_category_table' doesn't exist for the query: update mantis_project_category_table set user_id=2 where user_id=304. |
|
I will review this plugin over the next few days and provide fix. |
|
Please verify if all fixed in version 0.96 |
|
would this work for two user accounts, both with data/issues? ie merge one to another, preserve the others data? I tried and recieved.. Database query failed. Error received from database was 0001062: Duplicate entry '6-2079' for key 1 for the query: update mantis_project_user_list_table set user_id=2079 where user_id=111 |
|
seems I had to remove the sync from user from the project, or else they would conflict after the sync. |
|
@Matthew, |
|
Version 0.98 loaded due to an existing typo. Would appreciate if someone can delete syncuser097.zip |
|
@cas Nice plugin. However, I now have converted my whole history instead of only the assigned to user. I would like to know who entered issues in the past and have the complete history available....is that possible as well? |
|
Could be an option in a next version........... |
|
Added an option to only convert active issues |
|
@cas That is indeed an improvement. However, active issues should have a remaining history as well. I don't want (e.g.) the reporter to change, only the "assigned to" since I need to know from whom the issue originated and what happened in the meantime.... That status is the most improtant because no-one picks up issues that are assigned to other people... |
|
So that can be achieved relative easy in standard Mantis. |
|
That is not possible since the user is disabled and therefore not visable in the filter anymore. That means I have to enable him, then filter, reassign and disable again. Fine if it is one user, but we are talking about 50 users...lot of work.... |
|
In that case, use the latest version where you can specify alow and a high limit for the status. Issues within the range will be handled. |
|
A, cheers...however: |
|