-
-
Notifications
You must be signed in to change notification settings - Fork 80
[BUG]: Capture inbound recruiter interest *@*careers*.com #353
Copy link
Copy link
Open
Labels
cat:codedevelop, automate, debug, implement featuresdevelop, automate, debug, implement featureshelp wantedOpen to participation from the communityOpen to participation from the communitypythonPull requests that update python codePull requests that update python code✨ goal: improvementImprovement to an existing featureImprovement to an existing feature🏁 status: ready for devReady for workReady for work🟨 P2 / severity: minorNot blocking but should be fixed soonNot blocking but should be fixed soon
Metadata
Metadata
Assignees
Labels
cat:codedevelop, automate, debug, implement featuresdevelop, automate, debug, implement featureshelp wantedOpen to participation from the communityOpen to participation from the communitypythonPull requests that update python codePull requests that update python code✨ goal: improvementImprovement to an existing featureImprovement to an existing feature🏁 status: ready for devReady for workReady for work🟨 P2 / severity: minorNot blocking but should be fixed soonNot blocking but should be fixed soon
Is there an existing issue for this?
Current Behavior
Inbound message from a recruiter First Last first.last@companyABCcareers.com
did not get captured as an app, even though it was about a job opportunity
Expected Behavior
We should capture inbound messages too. This would have an application_status of "request for availability". Inbound messages are super positive signals - very important to capture for jobseekers.
Steps To Reproduce
No response
Environment
Criteria for Completion
No response
Anything else?
Not sure if this is a bug or a feature lol
Code of Conduct