Skip to content

Profiles: QTS/Professional Status updates#8666

Open
starswan wants to merge 1 commit intomainfrom
profiles-qts
Open

Profiles: QTS/Professional Status updates#8666
starswan wants to merge 1 commit intomainfrom
profiles-qts

Conversation

@starswan
Copy link
Copy Markdown
Contributor

@starswan starswan commented Mar 27, 2026

Trello card URL

https://trello.com/c/HnQ2ivZL/2672-profile-qualifications-journey
Edit: Think it is this one: https://trello.com/c/xHVsNEI4/2671-profile-professional-status-qts-journey (KM)

Changes in this PR:

QTS Profiles page

Screenshots of UI changes:

Before

After

@starswan starswan changed the title QTS Profile journey Profiles: QTS/Professional Status updates Mar 27, 2026
@starswan starswan added the deploy label Apr 7, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 7, 2026

Review app deployed to https://teaching-vacancies-review-pr-8666.test.teacherservices.cloud on AKS

Copy link
Copy Markdown
Collaborator

@KyleMacPherson KyleMacPherson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ticket seems to suggest that we just want to change some hint text, but this looks like it's adding in an extra, previously deleted field. I may well be missing context here but based on the ticket I don't think this looks quite right

validates_format_of :teacher_reference_number, with: /\A\d{7}\z/, allow_blank: false, if: -> { has_teacher_reference_number }
validates :is_statutory_induction_complete, inclusion: { in: [true, false] }, if: -> { qualified_teacher_status == "yes" }

validates :has_teacher_reference_number, inclusion: { in: [true, false] }
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like we are re-introducing has_teacher_reference_number which we got rid of a few months ago. I don't see this mentioned on the ticket, is this part of this work?

= f.govuk_text_area :qualified_teacher_status_details
= f.govuk_radio_button :qualified_teacher_status, "on_track"

= f.govuk_radio_buttons_fieldset :has_teacher_reference_number, legend: { tag: "h2" },
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like we are re-introducing has_teacher_reference_number which we got rid of a few months ago. I don't see this mentioned on the ticket, is this part of this work?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was following the designs (I think) - we're changing the layout of the page, so I assumed that we were bringing back the radio button?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch @KyleMacPherson. I suspect the design on the Lucid is outdated from the start, since the "Current Profiles" initial screenshots contain the outdated design with the removed radio button, while in reality now looks like this:
image

@starswan you can double-check with Alice, but given how much of a pain was the radio with the has_teacher_reference_number field, and how relieved we were once removed, I wouldn't expect going back to the previous state of that question. So I'm pretty sure it is an outdated design.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I asked in the TV Product channel and it looks like the screenshots used for the Lucid board are in fact just out of date so we don't want to add back in that question. Annoying, I know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants