Currently this is our workflow for the issue where i had below queries

[Manochandar]

Currently once we assigned an issue to our team member as "To Do" we are asking the assignee to move that as "In progress" while he is working and move it to "Apporval" by changing the assignee as Approver. Once the approver done with the task he will mark the status as "Done" if there is no rework. 

The challenge we are facing is the time tracking log where we defined people to change assignee, currently we are loosing the track of individual time log, also the assignation of task per resource cannot be traced as we change the assignee during approval.

We need to have a time tracking of each individual in all stages of workflow and have to perform this workflow without changing the default assignee

Is there any better way to define the workflow? Please suggest

[John Funk · Accepted solution]

Hi @Manochandar 

My suggestions would be first not to try to micromanage users like this. If you can't trust your team member, then you need a different team member. Second would be, why do you need this information? What are you trying to do with it? Finally, if you MUST do it, you might consider using a system of custom field so to capture the changes as they happen using automation rules. 

[Manochandar]

@John Funk - Thanks for the input. We aren't planned to micromanage. since we are into research and development we need to spend more time than expected in some task. So this will give a clear clarity on who and where they spend their efforts.

[John Funk]

Brother you need to look up the definition of micromanage because your last sentence might be the best definition of it. Regardless, what will you do with that data? 

[Manochandar]

Ha Ha.. The intention behind that is as we are a smaller group, we are planning to identify the actual hours spent on each task so that it will help us to define when we can complete our product development. Also this help us to identify the intensity of each work people are doing irrespective of quantity of task they performed. We are focusing two major stuff 1) Overall Task per resource 2) Time taken on each task

[John Funk]

Thanks for the additional information. This is what Time in Status apps and functionality are for. These are built specifically for that, I suggest you use one of those. 

[Manochandar]

Thanks for the response

[John Funk]

You are welcome. 

[Megha · Accepted solution]

HI @Manochandar 

1.Do not change the assignee at any stage. The person assigned stays the same throughout.
2. Use Statuses to Track Progress:
Create these statuses in the workflow:
To Do
In Progress
Pending Approval
Done

3. Use a custom field called Approver to assign the reviewer. This avoids reassigning the task.
4. Ask team members to log their time for each task at every stage (e.g., while working or reviewing).
5. Set up Jira Automation to:
Notify the approver when a task moves to Pending Approval.
Remind users to log time when tasks move to In Progress or Done.

Thank you

[Manochandar]

Hi @Megha  thanks for your answer. Below is also one of our workflow we created for Purchase tracking where we are having multiple stages to track entire purchase flow. Do you think the above practice will work for the same

[Megha]

@Manochandar  Try this

1.Same Assignee for All Stages:
Keep the same person assigned to the task from start to finish. This helps maintain clear ownership.
2.Use an "Approver" Field:
Instead of changing assignees during approval stages (e.g., Feedback, Approved), use a custom field for the Approver to track who is handling approvals.
3.Track Time at Each Stage:
Use log work to track how much time is spent at each stage (e.g., Product Received, Invoice Submitted).

[Manochandar]

Thanks for your response