Closed amba178 closed 8 years ago
This is the link to all wireframes: http://zc6evg.axshare.com. Under the discussion, you can leave comment or suggestion.
@patmbolger : You raised a good point on the jobs wireframe even though this story is specific to CRUD, I do have some feature on wireframe which are not related to the task. For example as you pointed out in the jobs/:id or jobs. These features will be stubbed out or hard coded as place holder.
See also #34
A couple of questions:
Before going to your question, this task/story purely deals with job CRUD behaviors
simple stuff, there are no any associations implemented yet. Probably, you will some placeholder in the UIs which are either stubbed or hard coded.
For example, in the job list edit and delete links should be hidden from jobseeker or from unauthorized person and so on.
Ok.
On your first point, Yes those are two possibilities a jobseeker can apply for the job.
if the contact info belongs to hiring manager than probably that is right. But let say if a jobseeker assigned to CM, than he should be able to see the contact info.
Your questions are valid, and we should discuss as a group.
Mean while, Checkout the Job model and its associations.
Isn't this done? Salem has a pull request for #173, which was for the implementation. So the design was probably finished some time ago.
I agree Amy. Your questions here are also good and should not be forgotten about - but they pertain to work that will occur as follow-on to this story, so we can revisit them then.
In the meantime, I will move this to "Archive" status.
As a developer, I want put wireframes together before start implementing UI.