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.

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

Incomplete Schedule Warning #6

Open
1 of 3 tasks
fairuzi10 opened this issue Sep 1, 2020 · 0 comments
Open
1 of 3 tasks

Incomplete Schedule Warning #6

fairuzi10 opened this issue Sep 1, 2020 · 0 comments

Comments

@fairuzi10
Copy link
Contributor

This issue is a:

  • bug report
  • feature request
  • styling change request

Current behavior:

Currently, if someone logged in with unregistered major, they will get something like this
image
What's funny is after that initial "error", they can log in one hour later due to our scheduler mechanism. This is because we will register that major after the initial log in, but we don't have the schedule for that major yet since the latest scheduler has run before that initial log in.

Requested behavior:

The easy fix would be to register all majors to our database, we have the data in backend/sso/additional-info.json. This will enable all majors to log in but we will give them an incomplete schedule from Jadwal -> Jadwal Kuliah Keseluruhan. We propose a better solution to also have a warning if we are showing an incomplete schedule so users can help Ristek with their credentials if they want to.

Why this behavior is better:

Avoid users complaining they can't log in to SusunJadwal.

@fairuzi10 fairuzi10 changed the title Change Complete Schedule Notification Change Incomplete Schedule Notification Sep 1, 2020
@fairuzi10 fairuzi10 changed the title Change Incomplete Schedule Notification Incomplete Schedule Warning Sep 1, 2020
@fahdikrie fahdikrie transferred this issue from ristekoss/susunjadwal Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants