View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 4814 | Composr | quizzes | public | 2022-01-30 02:08 | 2022-01-31 01:52 |
| Reporter | Adam Edington | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 10.0.41 | ||||
| Summary | 4814: Usergroup option for completed tests | ||||
| Description | There is text which explains that a user who completes a test can be put into a group. I can currently tie a quiz to a newsletter but I see no option to select a group. If there is a tutorial on how to achieve this, I haven't seen it and that text makes me want to do it to avoid people from gaining extra points through reattempts. | ||||
| Additional Information | If I need a group for each test, maybe this is not something I want to achieve ;) | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
For reference, this is the source of the text... DESCRIPTION_POINTS_FOR_COMPLETING=The number of points a member gains for completing the quiz. In the case of a test, these will only be allocated if the test is passed. Please note that for a competition these points will be given to anyone entering – “prizes” must be given manually. In order to stop members getting the same points many times, you may wish to set a very high “Reattemption time”; alternatively if you want a low reattemption time but only allow a test to be passed, you may want to put successful members in a different usergroup that does not have permission to access the test (you can use match-key permissions to set that). |
|
|
I've resolved this issue in v11. It's not a bug, it's just the language is confusing and process labourious. It's suggesting you MANUALLY move people to a usergroup upon passing a test, before they try again. Over complex and impractical. In v11 it will now automatically know not to assign points more than once. And, hence I was able to carve out a lot of the DESCRIPTION_POINTS_FOR_COMPLETING language string. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-01-30 02:08 | Adam Edington | New Issue | |
| 2022-01-31 00:55 | Chris Graham | Note Added: 0007338 | |
| 2022-01-31 01:51 | Chris Graham | Assigned To | => Chris Graham |
| 2022-01-31 01:51 | Chris Graham | Status | Not Assigned => Resolved |
| 2022-01-31 01:51 | Chris Graham | Resolution | open => fixed |
| 2022-01-31 01:52 | Chris Graham | Note Added: 0007340 |
