The following release notes cover recent changes from the past 14 days and provide an outlook for the upcoming release.
✨Focus topics of this release
The following milestones were achieved:
| Improvements | |
| Add bundles of subscriptions easily to an organization | If you sell bundles of subscriptions (e.g. a job flat rate as well as a premium organization profile) on your job board, it is now possible to add them to an organization via the backend using one click. |
| First autosuggestion of location search list applied automatically | If a user types a location into the location search field and does not select it manually, the first result will be applied automatically to the search results. |
| User Registration | The registration interface has been reworked in order to make it more clearly visible if a user is registering as an applicant or recruiter. This should reduce false sign-ups. |
| Simple job widget integration | A simpler version of the job widget integration is now available. |
| Bug Fixes | |
| Unpublished articles visible in blog search | In some cases, unpublished blog articles were visible within the blog search (the article itself was not reachable). |
For a comprehensive list of recently implemented features, improvements, or bug fixes, please read the section "More Details".
🏁 Outlook (Release 11, 23.05.2023)
The following goal are set for the next release.
- Recruiter verification by site admin
- Importer UI improvements for site admins (improved setup)
- UI improvements for GDPR automatic deletion module
🔎More Details
Here's an extended overview of all changes that will be released this time:
| Improvement | Add bundles of subscriptions easily to an organization | If you sell bundles of subscriptions (e.g. a job flat rate as well as a premium organization profile) on your job board, it is now possible to add them to an organization via the backend using one click. The individual parts of the subscription bundle are then added automatically. |
| Improvement | First autosuggestion of location search list applied automatically | If a user types a location into the location search field and does not select it manually, the first result will be applied automatically to the search results. |
| Improvement | Add descriptive text to the address book field | The address book field with the saved addresses is now clearly marked and described in the checkout process. |
| Improvement | Clickable title for the saved job searches | An applicant can easily go to the prefitered search results from his saved job searches. |
| Improvement | Reduce white spacing on jobs detail page | Visual improvements to the jobs detail page to reduce white space |
| Improvement | Avoid use of h-elements in the footer | In order to improve SEO, h-elements will not be used in the footer anymore. |
| Improvement | User Registration | The registration interface has been reworked in order to make it more clearly visible if a user is registering as an applicant or recruiter. This should reduce false sign-ups. |
| Improvement | Simple job widget integration | A simpler version of the job widget integration is now available. |
| Improvement | Remove G4J schema if requried fields are missing | In order to only send properly filled jobs to Google 4 Jobs, the G4J schema will be hidden if a job does not contain all necessary information to fill the required fields. |
| Improvement | Word "Publishing date" removed from mobile view (job search teasers) | Only the publishing date itself will be shown in the job search teasers (without the explanatory text). |
| Bug Fix | Upgrades were removed upon publishing from a scheduled job | If an upgrade was added to a job with a publishing date in the future, the upgrade was mistakenly removed from the job. |
| Bug Fix | Ensure that heading styles are applied on mobile | In order to preserve the readability of the job description on mobile, we ensured that heading styles are properly applied on mobile devices. |
| Bug Fix | Unpublished articles visible in blog search | In some cases, unpublished blog articles were visible within the blog search (the article itself was not reachable). |