Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Group Sync with Canvas Not Working Properly #556

Closed
timkato opened this issue Feb 6, 2018 · 2 comments · Fixed by #557
Closed

Group Sync with Canvas Not Working Properly #556

timkato opened this issue Feb 6, 2018 · 2 comments · Fixed by #557
Assignees
Milestone

Comments

@timkato
Copy link

timkato commented Feb 6, 2018

UBC PRB0043608
After initial student group sync from Canvas to iPeer; subsequent re-syncs of student groups (if any changes in Canvas groups) are not synced properly (for example some students appearing in iPeer groups twice)

Steps to reproduce:

  1. Create multiple student groups in Canvas course
  2. Sync iPeer and Canvas groups
  3. Move student from group A to group B in Canvas course
  4. iPeer > attempt to re-sync Canvas group (select all Canvas groups, choose Replace group rather than merge)
@wynnset
Copy link
Contributor

wynnset commented Feb 6, 2018

I have verified the bug. As a temporary workaround, you can delete all the groups in iPeer and then do the sync again.

I already have a working fix for this bug, but I just need you to confirm what happens in the case where you do what you explain above, except in step 4, you do not select the "Replace group..." checkbox.

i.e. You have these groups after step 3:

Group iPeer Members Canvas Members
Group A Joe, Mark Joe
Group B Alice Alice, Mark

There are 2 possible options for what happens after step 4 is performed (without checking the checkbox):

  1. We would keep Mark in Group A and also add him into Group B (this is the current functionality)
  2. We would show an error message saying that Mark is already in another group

Note that iPeer, unlike Canvas, allows the same member to exist in more than 1 group. So option 1 is totally a valid solution, and it's how it's currently implemented as I think it makes the most sense. Let me know if this makes sense to you as well, then we can push an update.

@wynnset
Copy link
Contributor

wynnset commented Feb 9, 2018

As per our meeting today, we will soon be taking out the "merge" option, so I no longer need an answer for the above. We will keep things as-is until that option is removed.

@wynnset wynnset added this to the 3.3.1 milestone Feb 14, 2018
@wynnset wynnset removed their assignment Feb 15, 2018
xcompass added a commit that referenced this issue Mar 2, 2018
Fix issues with the group sync with "Replace" strategy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants