RabbitLabs/vylbot-app

Fork 0

AS a moderator, I want to be able to manually set a user's moon count #300

New issue

Open

opened 2023-05-24 16:59:04 +01:00 by Vylpes · 3 comments

Vylpes commented

2023-05-24 16:59:04 +01:00

Owner

Sorry Points: 3

AS a moderator, I want to be able to manually set a user's moon count
SO THAT I can moderate a user who's misusing the command

Acceptance Criteria

AS a moderator
GIVEN there is a user's moon count which I need to correct
WHEN I run /moonset <user> <count>
THEN the moon count for <user> should be set to <count>

Subtasks

Update moon count to be a setting
Fix sql
Update new and list commands to use moon count user setting
Update new command to use the total moons
Create moonset command
Plan tests
Update tests

Sorry Points: 3 --- AS a moderator, I want to be able to manually set a user's moon count SO THAT I can moderate a user who's misusing the command ## Acceptance Criteria AS a moderator GIVEN there is a user's moon count which I need to correct WHEN I run `/moonset <user> <count>` THEN the moon count for `<user>` should be set to `<count>` ## Subtasks - [x] Update moon count to be a setting - [x] Fix sql - [x] Update new and list commands to use moon count user setting - [x] Update new command to use the total moons - [x] Create moonset command - [x] Plan tests - [x] Update tests

Vylpes added the

labels 2023-05-24 16:59:17 +01:00

Vylpes added this to the 3.3 milestone 2023-05-24 16:59:22 +01:00

Vylpes referenced this issue

2023-05-24 16:59:48 +01:00

Odyssey Moons #216

Vylpes changed title from ~~Moderators should be able to manually alter/set a user's moon count to any number~~ to AS a moderator, I want to be able to manually set a user's moon count

2023-10-22 14:23:51 +01:00

Vylpes removed the

needs criteria

label 2023-10-22 14:26:52 +01:00

Vylpes removed the

needs estimate

label 2023-12-03 14:12:27 +00:00

Vylpes added the

blocked

label 2024-08-09 18:11:44 +01:00

Vylpes commented

2024-08-09 18:11:57 +01:00

Author

Owner

Blocked by #195

Vylpes removed the

blocked

label 2024-09-08 14:35:31 +01:00

Vylpes added this to the 3.3 Sprint 5 project 2024-09-15 19:20:21 +01:00

Vylpes self-assigned this 2024-09-21 15:00:38 +01:00

Vylpes started working 2024-09-25 18:09:47 +01:00

Vylpes commented

2024-09-25 18:14:44 +01:00

Author

Owner

Probably want to change how we handle moon count then

Vylpes stopped working 2024-09-25 18:17:01 +01:00

7 minutes 13 seconds

Vylpes started working 2024-09-25 18:43:01 +01:00

Vylpes stopped working 2024-09-25 19:03:36 +01:00

20 minutes 35 seconds

Vylpes started working 2024-09-27 17:52:29 +01:00

Vylpes stopped working 2024-09-27 18:16:06 +01:00

23 minutes 37 seconds

Vylpes modified the project from 3.3 Sprint 5 to 3.3 Sprint 6

2024-10-27 17:18:54 +00:00

Vylpes started working 2024-10-29 09:59:20 +00:00

Vylpes commented

2024-10-29 10:32:52 +00:00

Author

Owner

I don't think I can do a /moonset command. The issue is if the user sets it to below the biggest moon number, it begins to reuse the moon numbers which we don't want. I'm going to instead have this moon number handled in the background

I don't think I can do a `/moonset` command. The issue is if the user sets it to below the biggest moon number, it begins to reuse the moon numbers which we don't want. I'm going to instead have this moon number handled in the background

Vylpes referenced this issue

2024-10-29 10:52:14 +00:00

Split up moon counter from the database #489

Vylpes stopped working 2024-10-29 10:52:46 +00:00

53 minutes 26 seconds

Vylpes started working 2024-10-30 09:13:43 +00:00

Vylpes stopped working 2024-10-30 09:35:56 +00:00

22 minutes 13 seconds

Vylpes started working 2024-10-31 16:31:04 +00:00

Vylpes stopped working 2024-10-31 16:56:55 +00:00

25 minutes 51 seconds

Vylpes started working 2024-11-04 17:35:10 +00:00

Vylpes stopped working 2024-11-04 18:07:01 +00:00

31 minutes 51 seconds

Vylpes started working 2024-11-07 18:44:56 +00:00

Vylpes stopped working 2024-11-07 19:12:29 +00:00

27 minutes 33 seconds

Vylpes modified the project from 3.3 Sprint 6 to 3.3 Sprint 7

2024-12-08 16:39:07 +00:00

Vylpes started working 2024-12-11 18:16:07 +00:00

Vylpes stopped working 2024-12-11 18:43:09 +00:00

27 minutes 2 seconds

Vylpes started working 2024-12-14 17:26:48 +00:00

Vylpes stopped working 2024-12-14 18:05:02 +00:00

38 minutes 15 seconds

No milestone

No project

No assignees

1 participant

Notifications

Total time spent: 4 hours 37 minutes

Vylpes

4 hours 37 minutes

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: RabbitLabs/vylbot-app#300

No description provided.