Rename of group is a MUST for Jira.

Changing group name is a feature you have in Windows, Netware, email servers, etc.

Alvaro Alonso
Bogota, Colombia (South America)

We need this functionnality because of workflow reorganisation.
Please fix it.

Thanks

Somehow two diffferent groups have been created with the SAME group name (shouldn't that be checked and forbidden at first ?). Now, when assigning groups to users, we have two entries that look identical but correspond in fact to these two different groups. As expected, people often choose the wrong entry.

As they are different, the easy solution is to rename one of them. So please, fix it.

Thanks.

Ps: This feature has been request for almost 4 years... Is it that hard to implement ? How is it that today, people are still writing applications for which you can't edit dumb strings like a group name... ?

So i am currently digging around and maybe someone can help me to find something in this direction. I have created a table with oldgroupname and newgroupname which i called tab_groupmigration.

This SQL-Script looks good as i restarted my 3.7 testinstance on mysql:

update membershipbase x inner join tab_groupmigration z on
x.GROUP_NAME = z.oldgroupname
set GROUP_NAME = z.newgroupname

update schemepermissions x inner join tab_groupmigration z on
x.perm_parameter = z.oldgroupname
set perm_parameter = z.newgroupname

I would be nice i someone could state that i did not forget any relevant field.

p.s. i am aware of that the same field exists for the notification scheme table. Maybe i will comment later on again (if no one replies ).

1. Shut down JIRA
2. Run the following SQL-Script:

   update membershipbase x inner join tab_groupmigration z on
   x.GROUP_NAME = z.oldgroupname
   set GROUP_NAME = z.newgroupname;
   
   update schemepermissions x inner join tab_groupmigration z on
   x.perm_parameter = z.oldgroupname
   set perm_parameter = z.newgroupname
   where perm_type = 'group';
   
   update notification x inner join tab_groupmigration z on
   x.notif_parameter = z.oldgroupname
   set notif_parameter = z.newgroupname
   where notif_type = 'Group_Dropdown';
   
   update schemeissuesecurities x inner join tab_groupmigration z on
   x.sec_parameter = z.oldgroupname
   set sec_parameter = z.newgroupname
   where sec_type = 'group';
   
   update searchrequest x inner join tab_groupmigration z on
   x.groupname = z.oldgroupname
   set groupname = z.newgroupname;
   
   update filtersubscription x inner join tab_groupmigration z on
   x.groupname = z.oldgroupname
   set groupname = z.newgroupname;

3. Start up JIRA again

I would appriciate any confirmation to this or other hints to this
cheers
Frank

select obj.name+ '.' +col.name from syscolumns col, sysobjects obj
where col.name like '%group%' and col.id=obj.id order by obj.name,col.name

It found this:

changeitem.groupid, filtersubscription.groupname, groupbase.groupname, jiraperms.groupname,
membershipbase.GROUP_NAME, qrtz_job_details.JOB_GROUP, qrtz_triggers.TRIGGER_GROUP,
searchrequest.groupname, sysfilegroups.groupid, sysfilegroups.groupname, sysfiles.groupid,
sysindexes.groupid, sysmembers.groupuid, sysusers.isntgroup

It's not 100% complete in finding the columns you need (the name of the column is all that's checked), but it can be helpful. I would also check that the viewable by Group for comments is included in your search. In the XML it looks like this:
<Action id="12170" issue="11160" author="jonhd" type="comment" level="groupname"
e.g. select * from jira.jiraaction where actiontype='comment' and actionlevel is not NULL

Of course i forgot the most important Table groupbase. And the good hint to the jiraaction-table ended in these 2 additional SQL-Statements:

update groupbase x inner join tab_groupmigration z on
x.groupname = z.oldgroupname
set groupname = z.newgroupname;

update jiraaction x inner join tab_groupmigration z on
x.actionlevel = z.oldgroupname
set actionlevel = z.newgroupname;

I dont think the rest must be modified. The Parameter-Columns are not in your resultset as they didnt contain the group in its name, but i think it is quite a good base to work with now.

It seems to be a fairly basic requirement, which is really helpful.

please please implement this feature.

update groupbase x inner join tab_groupmigration z on
x.groupname = z.oldgroupname
set groupname = z.newgroupname;

update membershipbase x inner join tab_groupmigration z on
x.GROUP_NAME = z.oldgroupname
set GROUP_NAME = z.newgroupname;

update schemepermissions x inner join tab_groupmigration z on
x.perm_parameter = z.oldgroupname
set perm_parameter = z.newgroupname
where perm_type = 'group';

update notification x inner join tab_groupmigration z on
x.notif_parameter = z.oldgroupname
set notif_parameter = z.newgroupname
where notif_type = 'Group_Dropdown';

update schemeissuesecurities x inner join tab_groupmigration z on
x.sec_parameter = z.oldgroupname
set sec_parameter = z.newgroupname
where sec_type = 'group';

update searchrequest x inner join tab_groupmigration z on
x.groupname = z.oldgroupname
set groupname = z.newgroupname;

update filtersubscription x inner join tab_groupmigration z on
x.groupname = z.oldgroupname
set groupname = z.newgroupname;

update jiraaction x inner join tab_groupmigration z on
x.actionlevel = z.oldgroupname
set actionlevel = z.newgroupname;

update worklog x inner join tab_groupmigration z on
x.grouplevel = z.oldgroupname
set grouplevel = z.newgroupname;

update projectroleactor x inner join tab_groupmigration z on
x.roletypeparameter = z.oldgroupname
set roletypeparameter = z.newgroupname
where roletype = 'atlassian-group-role-actor'

it looks stable from my point of view.

100 votes, 5 years later...

Maybe 1 more vote and another 5 years...

Why does it need that long to implement this feature? 5 years in the IT world is like 20 years in real world.

Then I looked on here, found the improvement and voted for it. Then I saw the notes about changing the DB. The script that Neil gives gives an error, something about syscolumns not found. So I tried Franks script and set the new and the old and ran the script and nothing is changed since nothing was found.

Help?

How did this get designed without rename in mind?

Russ

Edit: you can test whether your script will have effect while trying something like this:

select * from tab_groupmigration where oldgroupname in (select groupname from groupbase)

To get the changes properly showing up in your Instance you must reindex JIRA and i for sure restart the JIRA-Service as i always have sideeffects with SQL-Scripts and JIRA.

A share filters were not showing up for users on JIRA 3.13.2. On investigation we found that there is one more DB table called 'sharepermission' with a column name PARAM1 that contains old group names.

MS-SQL
update x set x.PARAM1=t.newgroupname from sharepermissions x,tab_groupmigration t where x.PARAM1=t.oldgroupname

Thanks,
Ganesh