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.

Sign up for GitHub

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

Jump to bottom

Add more events statuses and refactor existing enums #52

Closed
raczu opened this issue Jun 8, 2024 · 1 comment · Fixed by #53
Closed

Add more events statuses and refactor existing enums #52

raczu opened this issue Jun 8, 2024 · 1 comment · Fixed by #53
Assignees
@raczu
Labels
scope: backend Indicates that PR relates to backend changes. scope: database Indicates that PR relates to database changes. type: feature request Issues categorised as feature request.

Comments

@raczu
Copy link
Collaborator

raczu commented Jun 8, 2024

What new thing should be implemented?

The aim is to add a status that will inform that the event has been canceled and one more with information about its rejection by administrator. The rest of the exisitng statuses should be refactored to try to describe its condition in a single word.

What is your acceptance criteria?

As described above.
@raczu raczu added scope: backend Indicates that PR relates to backend changes. scope: database Indicates that PR relates to database changes. type: feature request Issues categorised as feature request. labels Jun 8, 2024
@wzarek
Copy link
Owner

wzarek commented Jun 8, 2024

Why in a single word? Can't we just leave as it is and when creating enums on FE side just format them properly and hardcode the info about it to display it as a tooltip when you hover or click info icon for example? But cancelled yeah, agree that it should be added

@raczu raczu mentioned this issue Jun 8, 2024
Merged
@raczu raczu self-assigned this Jun 8, 2024
@wzarek wzarek closed this as completed in #53 Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@raczu raczu

Labels
scope: backend Indicates that PR relates to backend changes. scope: database Indicates that PR relates to database changes. type: feature request Issues categorised as feature request.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[RSN-67] Add more event statuses and fix some errors wzarek/Reasn
2 participants
@raczu @wzarek