Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a way to mark a job post as filled #573

Open
JoeJasinski opened this issue Dec 20, 2024 · 2 comments
Open

Add a way to mark a job post as filled #573

JoeJasinski opened this issue Dec 20, 2024 · 2 comments

Comments

@JoeJasinski
Copy link
Contributor

As a job poster, I want to indicate if a job that I posted has been filled, so that I can remove the posting but demonstrate that it has been filled.

We should add a column to the job post table to indicate if a job post has been filled and also a date indicating the filled date. The date could default to the current date.

Acceptance Criteria:

  • Modify the model and forms to expose a filled checkbox (or similar) and date field to indicate filled.
    • Filter the job posting to filter out filled jobs
  • A job poster should be able to mark a job as filled on the job update view.
  • (optional) An anonymous viewer should be able to see a list of unfilled and filled jobs.
@eevelweezel
Copy link
Contributor

eevelweezel commented Dec 20, 2024 via email

@elmq0022
Copy link
Contributor

I'm with heather on the above. As a job seeker, if the position is filled I don't want to waste my time looking at it. As an chipy.org admin - I'd like to maybe have a dashboard that shows how many job postings we had over a given period of time and how many of those were filled.

I suggest we add the field and let the owner edit that field. The postings list view would then have a filter such that approved, current, unfilled postings are displayed.

I can take this ticket if you're good with the approach @JoeJasinski

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

No branches or pull requests

3 participants