Skip to content

Comments

YJDH-788 | Backend: Add organization type, job type & make business ID unique (+frontend translations)#3867

Merged
karisal-anders merged 3 commits intomainfrom
YJDH-788-employer-changes
Feb 4, 2026
Merged

YJDH-788 | Backend: Add organization type, job type & make business ID unique (+frontend translations)#3867
karisal-anders merged 3 commits intomainfrom
YJDH-788-employer-changes

Conversation

@karisal-anders
Copy link
Collaborator

@karisal-anders karisal-anders commented Feb 3, 2026

Description ✨

  • Backend:
    • Add Company.organization_type and OrganizationType enum
    • Add EmployerSummerVoucher.job_type and JobType enum
    • Make Company.business_id unique
  • Frontend:
    • Add translations for organization type and job type

Issues 🐛

YJDH-788

Testing ⚗️

Screenshots 📸

Additional notes 🗒️

@karisal-anders karisal-anders changed the title YJDH-788 | Backend: Add Company.organization_type & EmployerSummerVoucher.job_type & their enums YJDH-788 | Backend: Add organization type, job type & make business ID unique (+frontend translations) Feb 3, 2026
checked that dev/test/staging/production have only unique business_id
values in Company objects, so this should be safe to do

refs YJDH-788
@karisal-anders karisal-anders force-pushed the YJDH-788-employer-changes branch from 4f96694 to 12e322f Compare February 3, 2026 14:40
@karisal-anders karisal-anders marked this pull request as ready for review February 3, 2026 14:41
@karisal-anders karisal-anders requested a review from a team as a code owner February 3, 2026 14:41
@karisal-anders karisal-anders requested review from nikomakela and removed request for a team February 3, 2026 14:41
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 3, 2026

@azure-pipelines
Copy link

YJDH-KESASETELI-API branch is deployed to platta: https://yjdh-kesaseteli-pr3867.api.dev.hel.ninja 🚀🚀🚀

@azure-pipelines
Copy link

HANDLER branch is deployed to platta: https://kesaseteli-handler-ui-pr3867.dev.hel.ninja 🚀🚀🚀

@azure-pipelines
Copy link

YOUTH branch is deployed to platta: https://nuortenkesaseteli-pr3867.dev.hel.ninja 🚀🚀🚀

@azure-pipelines
Copy link

TestCafe result is success for https://kesaseteli-handler-ui-pr3867.dev.hel.ninja 😆🎉🎉🎉

@azure-pipelines
Copy link

EMPLOYER branch is deployed to platta: https://kesaseteli-pr3867.dev.hel.ninja 🚀🚀🚀

@azure-pipelines
Copy link

TestCafe result is success for https://nuortenkesaseteli-pr3867.dev.hel.ninja 😆🎉🎉🎉

@azure-pipelines
Copy link

TestCafe result is success for https://kesaseteli-pr3867.dev.hel.ninja 😆🎉🎉🎉

# needs to be asked from the user.
max_length=64,
verbose_name=_("organization type"),
blank=True,
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a note, that since NULL is not allowed, this blank string means that "question is seen, but left unanswered".

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Same here as in comment #3867 (comment)

job_type = models.CharField(
max_length=64,
verbose_name=_("job type"),
blank=True,
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a note, that since NULL is not allowed, this blank string means that "question is seen, but left unanswered".

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, intentionally allowed empty string. This helps with e.g. old data and with the current way of handling employer applications/summer vouchers in the employer UI & backend (it saves partial data so data can be not set).

Also it's Django's best practice not to allow null for CharFields:

Avoid using null on string-based fields such as CharField and TextField.

The requirement can be handled at the UI level.

@karisal-anders karisal-anders merged commit e89e4dc into main Feb 4, 2026
74 checks passed
@karisal-anders karisal-anders deleted the YJDH-788-employer-changes branch February 4, 2026 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants