-
Notifications
You must be signed in to change notification settings - Fork 948
Description
When a new user logs in via username and password, the Tasks tab is not shown in the navbar—even if a valid Tasks template already exists. This happens because the decision to render the tab is embedded in the HTML returned before authentication. Since no refresh occurs during the username/password login flow, the page doesn't re-render with updated user-specific context.
This creates an issue for new users who are expected to see Tasks immediately after login, particularly in workshop/demo environments where users log in cold and are not aware they need to visit /tasks
or refresh manually.
Steps to Reproduce
- Run
develop.sh
- Add the recommended Tasks template as admin
- Open an incognito browser window
- Log in as
member@coder.com
(or any other new user via username/password flow) - Observe that the Tasks tab is missing from the navbar
- Manually visit
/tasks
→ tab still doesn't appear - Refresh the page → tab appears
Expected Behavior
If a Tasks template exists, users should see the Tasks tab in the navbar immediately upon login—without needing to refresh or manually visit /tasks
.
Actual Behavior
Users logging in via username/password:
- Do not see the Tasks tab initially
- Must visit
/tasks
and refresh the page to make it appear
Environment
- Host OS: Linux
- Coder Version:
d817640
Impact
- Workshops and demos: Instructors distribute demo accounts with the expectation that users can immediately access Tasks.
- New customers: First-time experience is broken unless users know to refresh manually.
- Inconsistency: Behavior differs between login methods (OIDC vs username/password).