shoko/jigaido
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

UAT: Bounty Commands Testing #38

New Issue
Closed
opened 2026-04-04 04:27:55 +02:00 by shoko · 8 comments
shoko commented 2026-04-04 04:27:55 +02:00
Owner
Copy Link

Objective

Validate all bounty-related commands work correctly for real user workflows.

Scope

Phase A testing - NO tracking features involved.

Test Commands

/add

  • Add bounty with text only
  • Add bounty with URL link
  • Add bounty with natural language due date (tomorrow, in 3 days, april 15)
  • Add bounty with text + link + due date (all fields)

/bounty (list)

  • Empty state (no bounties)
  • List with multiple bounties

/edit

  • Edit bounty text only
  • Edit bounty link only
  • Edit bounty due date only
  • Edit all fields at once

/delete

  • Delete own bounty
  • Try to delete another user's bounty (should fail with permission error)

Expected Behavior

  • All commands should respond within reasonable time
  • Success/error messages should be clear and user-friendly
  • Due dates should parse correctly regardless of phrasing

Notes

Report issues with: command, scenario, expected behavior, actual behavior

## Objective Validate all bounty-related commands work correctly for real user workflows. ## Scope Phase A testing - NO tracking features involved. ## Test Commands ### /add - [x] Add bounty with text only - [x] Add bounty with URL link - [x] Add bounty with natural language due date (tomorrow, in 3 days, april 15) - [x] Add bounty with text + link + due date (all fields) ### /bounty (list) - [x] Empty state (no bounties) - [x] List with multiple bounties ### /edit - [x] Edit bounty text only - [x] Edit bounty link only - [x] Edit bounty due date only - [x] Edit all fields at once ### /delete - [x] Delete own bounty - [x] Try to delete another user's bounty (should fail with permission error) ## Expected Behavior - All commands should respond within reasonable time - Success/error messages should be clear and user-friendly - Due dates should parse correctly regardless of phrasing ## Notes Report issues with: command, scenario, expected behavior, actual behavior
han commented 2026-04-04 04:59:41 +02:00
Collaborator
Copy Link

the /bounty list is working properly but I'd like to change the format, something like

[#id] description (but we slice them so we can make it a title)
ends (duedate) | (link)

I think in the bounty list we don't have to show who added it. also we want to have a better date formatting in display something like "4 April 2026"

the /bounty list is working properly but I'd like to change the format, something like ``` [#id] description (but we slice them so we can make it a title) ends (duedate) | (link) ``` I think in the bounty list we don't have to show who added it. also we want to have a better date formatting in display something like "4 April 2026"
han commented 2026-04-04 05:03:31 +02:00
Collaborator
Copy Link

/add bounty are working well, but there are several things to improve:

  • date should be fixed instead of relative, for example "04-04-2026" which means 4 April 2026
  • we should allow date format to be a timestamp for a precision
  • I think we should add time as well as the additional input param, so we can add them in the list of bounty and during update as well
  • currently we can add multiple bounty with the same link, we shouldn't allow that because what's the point of having bounties with same registration link, isn't it just the same bounty? but bounty without link should be able to added multiple times. I think rather than an opinionated like this, we can have like a setting which is differs for each group/dm. but by default we are not allowing them to add bounty with same link, unless they disable those enforcement (we let them know during add and update if the add or update fail because of link constraint
/add bounty are working well, but there are several things to improve: - date should be fixed instead of relative, for example "04-04-2026" which means 4 April 2026 - we should allow date format to be a timestamp for a precision - I think we should add time as well as the additional input param, so we can add them in the list of bounty and during update as well - currently we can add multiple bounty with the same link, we shouldn't allow that because what's the point of having bounties with same registration link, isn't it just the same bounty? but bounty without link should be able to added multiple times. I think rather than an opinionated like this, we can have like a setting which is differs for each group/dm. but by default we are not allowing them to add bounty with same link, unless they disable those enforcement (we let them know during add and update if the add or update fail because of link constraint
han commented 2026-04-04 05:19:44 +02:00
Collaborator
Copy Link

since we are slicing /bounty, it means that we should have show command to show all the information of a bounty by putting the id of it, and we will returned everything. all the description, link, due date, and who posted/informed this bounty

since we are slicing /bounty, it means that we should have show command to show all the information of a bounty by putting the id of it, and we will returned everything. all the description, link, due date, and who posted/informed this bounty
han commented 2026-04-04 05:20:48 +02:00
Collaborator
Copy Link

also for /bounty list, I think we should default to limit the amount of bounty we show. maybe by default is 5, but user can always ask more. maybe we use pagination or limit or both

also for /bounty list, I think we should default to limit the amount of bounty we show. maybe by default is 5, but user can always ask more. maybe we use pagination or limit or both
han commented 2026-04-04 05:23:51 +02:00
Collaborator
Copy Link

for /edit, I'd like to have a specific command to update each of its attribute. for example only edit the text, only update the url, only update the date, only update the time. why? because if we use /edit and it has a long text while we just want to change the url or the time, we have to copy all the text and its painful. so its for better UX

and for /edit, should has the same checking logic like /add. like for the date and time format. and then for the link as well. if user update an existing bounty link to a link that already registered, we should fail the update and inform that the link already exist in bounty <#id> <description[sliced]>

for /edit, I'd like to have a specific command to update each of its attribute. for example only edit the text, only update the url, only update the date, only update the time. why? because if we use /edit and it has a long text while we just want to change the url or the time, we have to copy all the text and its painful. so its for better UX and for /edit, should has the same checking logic like /add. like for the date and time format. and then for the link as well. if user update an existing bounty link to a link that already registered, we should fail the update and inform that the link already exist in bounty <#id> <description[sliced]>
han commented 2026-04-04 05:25:50 +02:00
Collaborator
Copy Link

also with current update, I can't remove the existing link or date

also with current update, I can't remove the existing link or date
han commented 2026-04-04 05:29:55 +02:00
Collaborator
Copy Link

I think delete should be soft delete, in a way we can recover them. so checking logic like the link, doesn't check to soft deleted bounty. also delete should be able to delete multiple items in a single command

I think delete should be soft delete, in a way we can recover them. so checking logic like the link, doesn't check to soft deleted bounty. also delete should be able to delete multiple items in a single command
han commented 2026-04-04 05:31:16 +02:00
Collaborator
Copy Link

also I think I'd like to have timezone config setting. each group can set their own timezone. so we render the date and time according to the timezone, with their timezone format as well. but by default we are using UTC+0

also I think I'd like to have timezone config setting. each group can set their own timezone. so we render the date and time according to the timezone, with their timezone format as well. but by default we are using UTC+0
shoko closed this issue 2026-04-04 16:46:48 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
Storage adapter
 architecture
Architecture/design
 cleanup
Cleanup task
 cli
CLI application
 core
Core domain layer
 enhancement
need-user-approval
phase-1
Phase 1 task
 phase-2
Phase 2 implementation task
 telegram-bot
Telegram bot app
 tests
Tests
 v2
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
han shoko
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/jigaido#38
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?