Project

General

Profile

Actions
Copy link

Bug #15094

closed

Group admins added to site as authors, not admins

Added by Gina Cherry almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Boone Gorges
Category name:
Group Invitations
Target version:
2.0.0
Start date:
2021-12-14
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Hi,

I created a group and invited some folks with the admin role. When they accepted their invitation, they were successfully added to the group as admins, but were added to the site as authors. I manually changed their role in the site to admin. Is this the expected behavior?

This is the group: https://commons.gc.cuny.edu/groups/aanapisi-bridge-initiative-faculty-seminar-series-winter-2022/

Actions
Copy link
 #1

Updated by Boone Gorges almost 3 years ago

  • Category name set to Group Invitations
  • Assignee set to Boone Gorges
  • Target version set to 1.18.25

No, it's not intended behavior. The group-site role mapping is defined here https://commons.gc.cuny.edu/groups/aanapisi-bridge-initiative-faculty-seminar-series-winter-2022/admin/group-blog/ and it suggests that they should have been added as Administrators.

The process of inviting a user to a group with a given role, then having them accept the invitation and be granted the specified role, has a lot of moving parts, and it's possible that the group-site mapping is taking place after the user becomes a member of the group but before they are promoted to group admin. I'll try to take a look before the next release to see whether I can isolate it.

Actions
Copy link
 #2

Updated by Boone Gorges almost 3 years ago

  • Target version changed from 1.18.25 to 1.19.1
Actions
Copy link
 #3

Updated by Boone Gorges almost 3 years ago

  • Target version changed from 1.19.1 to 1.19.2
Actions
Copy link
 #4

Updated by Boone Gorges almost 3 years ago

  • Target version changed from 1.19.2 to 1.19.3
Actions
Copy link
 #5

Updated by Boone Gorges almost 3 years ago

  • Target version changed from 1.19.3 to 1.19.4
Actions
Copy link
 #6

Updated by Boone Gorges almost 3 years ago

  • Target version changed from 1.19.4 to 1.19.5
Actions
Copy link
 #7

Updated by Boone Gorges over 2 years ago

  • Target version changed from 1.19.5 to 1.19.6
Actions
Copy link
 #8

Updated by Boone Gorges over 2 years ago

  • Target version changed from 1.19.6 to 1.19.7
Actions
Copy link
 #9

Updated by Boone Gorges over 2 years ago

  • Target version changed from 1.19.7 to 1.19.8
Actions
Copy link
 #10

Updated by Boone Gorges over 2 years ago

  • Target version changed from 1.19.8 to 1.19.9
Actions
Copy link
 #11

Updated by Boone Gorges over 2 years ago

  • Target version changed from 1.19.9 to 1.19.10
Actions
Copy link
 #12

Updated by Gina Cherry over 2 years ago

Just ran into this issue again. Any update on when it might be fixed?

Actions
Copy link
 #13

Updated by Boone Gorges over 2 years ago

  • Status changed from New to Staged for Production Release
  • Target version changed from 1.19.10 to 2.0.0

Hi Gina - Thanks for your patience and for the ping. I was able to reproduce the issue and identify the underlying cause. It'll be fixed in the upcoming 2.0.0 release, scheduled for later this week.

Actions
Copy link
 #14

Updated by Boone Gorges over 2 years ago

  • Status changed from Staged for Production Release to Resolved
Actions
Copy link

Also available in: Atom PDF