A great place to post your ideas and vote on others so that you can let us know what is important to you.
Please take the time to register, and then share your detailed use case and how the proposed enhancements could provide value to your organisation.
We endeavour to provide an initial response to all ideas in a timely manner.
Following investigation with the engineering team, it was identified that this unwanted behavior was the result of the nuance on how the ATS was handling job identifiers when the posting content was updated by the user in the ATS.
The team have been able to make an updated to ATS integration logic to allow the job identifier to be used, rather than the posting identifier which is the default set-up.
This will ensure that the job, and by extension, the URL slug will not become invalid when posting updates are made in the ATS.
Additionally, please note that the format https://<careersdomain>/jobs/<ats_identifier> is supported as a method of accessing the job. Please note, the "ATS Identifier" is case sensitive.
--
Steve Oxley
Product Manager
Thanks for taking the time to submit this suggestion Kalpesh.
I am reviewing this with the engineering team, and we'll get back to you in due course.
--
Steve Oxley
Product Manager