There's not a lot to go on here, but there's several ways of tracking multiple inputs on a piece of work.
The usual one is to simply have each person work on the issue and assign it to someone else when the next person needs to do something. You then use the work logs or logging fields extracting information from the history to capture who has been involved in the issue.
Or, you break it down into sub-tasks, with each sub-task being allocated to one of the employees, and you don't let the parent issue move on through the workflow until they have all closed their sub-tasks.
Or, if you have a linear stepped process where each employee has to give a conclusion in turn, you model that in the workflow. (e.g. Unapproved -> Person X approved -> Person Y approved -> Done)
Or, with a bit of code or an add-on, you can make a linear stepped workflow appear to be non-linear (Unapproved -> X or Y has approved -> Both have approved -> Done)
Or, you add a field that lets people add their name as an approver.
Those are some ideas of how to approach it, but I don't know what your desired real-world process is, or how you would like to report on it, so I can't recommend any one of them over another. There's probably other ways to do it as well, and it is possible to use hybrids of those approaches too.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs