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

✨ Employee profile page #12002

Open
1 task
Tracked by #12249
tristan-orourke opened this issue Nov 15, 2024 · 3 comments · May be fixed by #12371
Open
1 task
Tracked by #12249

✨ Employee profile page #12002

tristan-orourke opened this issue Nov 15, 2024 · 3 comments · May be fixed by #12371
Assignees
Labels
feature New feature or request.

Comments

@tristan-orourke
Copy link
Member

tristan-orourke commented Nov 15, 2024

✨ Feature

Create the Employee Profile page.

🕵️ Details

  • URL - /applicant/employee-profile
  • only accessible to Gov employees. If user visits page without having a verified gov email, show an unauthorized message

🎨 Design

https://www.figma.com/design/Xnkie0dSq9RujvQRAZwrY4/Employee-profile-(Employees)?node-id=1-2&p=f&t=fgUwHFuIO4afnVea-0

@JoshBeveridge

🙋‍♀️ Proposed Implementation

  • Create page component at ~/pages/Users/EmployeeProfile
  • Add page to router and routes hook under /applicant/employee-profile
  • Create a root query for the current user me
    • If any forms are created with fragments, add them now
  • Add table of contents with the following sections (to be populated in other tickets):
  • If any forms have been completed, add them to the appropriate sections

✅ Acceptance Criteria

  • Page created and accessible at /applicant/employee-profile
  • If user visits page without having being a verified gov employee, show an unauthorized message
  • Add root query
  • Table of contents added with three nested sections, with StatusItem links
  • Forms added if they exist
  • Design review by @JoshBeveridge
  • Language review by @NienkeBr

🛑 Blockers

Blocked By

Preview Give feedback
  1. feature
@tristan-orourke tristan-orourke added the feature New feature or request. label Nov 15, 2024
@tristan-orourke tristan-orourke added this to the Career Planning milestone Nov 15, 2024
@tristan-orourke tristan-orourke changed the title ✨ create Career Planning page ✨ [WIP] Career Planning page Nov 15, 2024
@esizer esizer changed the title ✨ [WIP] Career Planning page ✨ Career planning page Nov 19, 2024
@tristan-orourke tristan-orourke added the review in refinement Ready to be looked at and pulled into "ready to dev" label Nov 25, 2024
@tristan-orourke
Copy link
Member Author

tristan-orourke commented Nov 25, 2024

Question: only accessible to Gov employees. How strict do we want to be on that? Give 404s to non-employees? backend validation? Or simply avoid sharing links?
Answer: if its not difficult to do, we'll hide the page from non-employees. We'll show the same thing we'd show to users blocked by RequireAuth.

@tristan-orourke tristan-orourke removed the review in refinement Ready to be looked at and pulled into "ready to dev" label Nov 25, 2024
@gobyrne gobyrne changed the title ✨ Career planning page ✨ Employee profile page Nov 26, 2024
@tristan-orourke
Copy link
Member Author

I anticipate this question: why are there nested links in the ToC if there is only one top-level link? Well, the plan is to add more.

@tristan-orourke tristan-orourke moved this to 🏭 Ready for Estimate in GC Digital Talent Dec 12, 2024
Copy link

Status: Error ⚠️

Issues blocking this PR:

  • #NaN ⚠️ Issue/PR not found

This comment was automatically written by the Blocking Issues bot, and this PR will be monitored for further progress.

@tristan-orourke tristan-orourke moved this from 🏭 Ready for Estimate to 📋 Ready for Dev in GC Digital Talent Dec 19, 2024
@esizer esizer self-assigned this Dec 23, 2024
@esizer esizer moved this from 📋 Ready for Dev to 🏗 In progress in GC Digital Talent Dec 23, 2024
@esizer esizer linked a pull request Dec 24, 2024 that will close this issue
@esizer esizer moved this from 🏗 In progress to 👀 In review in GC Digital Talent Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request.
Projects
Status: 👀 In review
Development

Successfully merging a pull request may close this issue.

2 participants