Debating with the amazing community about building a certain process

[zeremeser]

Hey guys, I need your help!

I have 3 tables -
1. Projects
2. Items
3. Tasks

In general - each project has linked items and each item has linked tasks.

Because that was the goal, the only place where a specific employee is associated is at the tasks stage.

Because each task is linked to an item and each item is linked to a project, I knew that if I associated an employee with a specific task, he would also be associated with the appropriate item and task.

The problem - the client now says that he does not want each item to have a task.
Now, this creates a problem for me because in such a situation I do not have a task to link to this item and then the employee "does not know" that he is associated with this item because there is no task under it.

How do I overcome this?
Did I build the entire system incorrectly?

Do I need to create an "employee" field that we will have to enter at each stage? Task, item and project?

I would really appreciate your help!

[TheTimeSavingCo]

Hmm could you talk about the business logic a bit more? 

What's an 'Item' in this context? 
Why doesn't the client want to have a 'Tasks' table?  Do they just not want to track task progress or something? 
It seems like you need to track an employee per Item but there's an issue with linking an Item to an Employee, is that right?

[VikasVimal]

It is a terminology issue. Call it a Project Stage, or Task Group or something like that.

Else, Get rid of Items and connect projects to tasks directly.