I'm setting up a project management system. Many, not all, of the tasks will have an assignee who completes the task and an approver who checks and approves the work. Is it best to set the task up as 1) one task with one 'assignee' field and one 'approver' field; 2) one task with two assignees in the same field; 3) two tasks...one as for doing the task and one for checking/approving the task. Maybe there are other options I've not considered. Thanks for your advice!
Either #1 or #3 would work. With #1, you could create a status field with a "ready for review" option to help create views and automations. With #3, you could create an automation that creates a new approval record when the original task record is closed.
There's many ways to approach this. The final answer is really dependent on the needs of your team. It's possible to set up an approvals workflow, but these can get complex and bloated depending on your needs and how much time you're willing to put into implementation.
That being said, out of what you described, the simplest method would be to implement two fields, with one being for your task assignee and the other being for designating your reviewer.
Either #1 or #3 would work. With #1, you could create a status field with a "ready for review" option to help create views and automations. With #3, you could create an automation that creates a new approval record when the original task record is closed.
There's many ways to approach this. The final answer is really dependent on the needs of your team. It's possible to set up an approvals workflow, but these can get complex and bloated depending on your needs and how much time you're willing to put into implementation.
That being said, out of what you described, the simplest method would be to implement two fields, with one being for your task assignee and the other being for designating your reviewer.
