We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
This issue is a:
Current behavior:
As of now, every schedules are automatically named as 'Untitled' after it is saved. It can only be renamed after you open the schedule detail page.
Requested behavior:
The design team from Ristek proposed that it would be better if user get the chance to give each schedules' name before (and not after) saving it.
Related Issue:
Also see this issue on SusunJadwal's frontend repository: ristekoss/susunjadwal-frontend#15
Why this behavior is better:
It is suggested by Ristek's design team that this would lead to a better and more coherent user flow.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This issue is a:
Current behavior:
As of now, every schedules are automatically named as 'Untitled' after it is saved. It can only be renamed after you open the schedule detail page.
Requested behavior:
The design team from Ristek proposed that it would be better if user get the chance to give each schedules' name before (and not after) saving it.
Related Issue:
Also see this issue on SusunJadwal's frontend repository:
ristekoss/susunjadwal-frontend#15
Why this behavior is better:
It is suggested by Ristek's design team that this would lead to a better and more coherent user flow.
The text was updated successfully, but these errors were encountered: