Open camille-readbean opened 6 months ago
Thank you for the feedback. We have assigned this issue a response of Rejected
as this behaviour is intended. Note that it is possible for an offer made to a candidate to be rejected by the candidate, and thus it should be permitted to add applications for a job even when the number of offers made is equal to the total number of vacancies for the job (aka 0 slots left).
Team chose [response.Rejected
]
Reason for disagreement: In this case it should be a documentation bug:
I like to note that the response messages using the same, vacancies, interchangeably is at least a DocumentationBug as it causes potential confusion.
On top of that you have an area for misunderstanding where slots_left shows 0 vacancies but the UI still shows 1. The messages can be made more clear or be added to an FAQ or a section highlighting the
Right now to me as a user and reader, this feature is hard to understand.
As it stands I can only have a complete understanding of the vacancies feature after reading 20 out of 39 pages of the UG.
The differentiation between remaining vacancies and vacancies are also not clear.
add_app section can be improved to preempt this error.
Add app can clarify that the number of vacancies do not decrease by offer.
If a tester had a hard time understanding the app, it is not impossible some users will misunderstand the feature as well.
Suggestion: add to FAQ or brief overview of how the app works at the start.
Extremely confusing that jobs can still be added to a job with no slots left
Term slots vs vacancy is hard to understand upfront as well.