Description
Failures may occur for different reasons. Some of which can likely be ignored, others may need better descriptors for why they failed. Some examples are:
- The Sakai site has been softly deleted
- The user trying to be added is already in the site and/or Kit
- The site is connected to a combined Kit and thus unsure which roster to add user to
To Reproduce
- Aggregate a list of site IDs from Sakai with states as described in Description. Include a control site that should work without any above described issues
- Go to Kits Batch Add (https://kits.duke.edu/admin/batch_add)
- Enter site IDs
- Select user(s)
- Complete batch add process
Expected behavior
The email delivered when kits has completed processing changes includes descriptors of why each case failed.
Screenshots
Example of failures from a batch add. Most of the 'Course doesn't support this role' failures were due to site being connected to a combined kit.
Additional context
Discovered while completing https://cit56.zendesk.com/agent/tickets/13301
Discussed briefly in Teams DM between Liz & Marty on Sept 15, 2022. Teams is too dumb to allow linking to a DM so screenshot of discussion attached.
Description
Failures may occur for different reasons. Some of which can likely be ignored, others may need better descriptors for why they failed. Some examples are:
To Reproduce
Expected behavior
The email delivered when kits has completed processing changes includes descriptors of why each case failed.
Screenshots
Example of failures from a batch add. Most of the 'Course doesn't support this role' failures were due to site being connected to a combined kit.
Additional context
Discovered while completing https://cit56.zendesk.com/agent/tickets/13301
Discussed briefly in Teams DM between Liz & Marty on Sept 15, 2022. Teams is too dumb to allow linking to a DM so screenshot of discussion attached.