Need to log time from tempo for team member assigned to task, not just logged in user.

I am using an Agile Kanban board to manage the operations floor of a shipping and manufacturing area. Because of the nature of our work it is not realistic for every team member to have a computer in front of them throughout operations.

 

In order to allow for agile management we have a single large screen where everyones tasks are available in a Kanban flow (which is really awesome). However whenever a user drags a task they were doing to the done pile and logs the time they worked on that project it ends up assigned to the logged in user instead of the person assigned that task.

 

The logging area already has everything we need, even a way to change who the task was assigned to on the same closeout popup, but logging all of the times against the same user has no value whatsoever for the type of team management that it needs to be used for.

 

For me to be able to make sure my team is distributing work properly, and to manage pay for hourly workers I need to have the ability to collect times efficiently without users having to seperately log times, and I look forward to hearing any suggestions on how we could implement this. If there is a way to write an ad-on for an ad-on I am sure that a change could be made to the closeout window that comes up, but I am hoping there is a less invasive way it could be done.

3 answers

Are you using Tempo ? If you are you can login a user with the ''aprrove timesheet permission on the commun computer and each user can log time as themself. A user with the ''approve timesheet'' can log time for another user.

I am, and it is possible when specifically logging time to log it for another user, but when closing an issue there is no option for time attribution. What I need is to make the attribution default to the assigned team member instead of the logged in user.

 

Right now everything get logged for the manager, and it looks like the workers didn't do anything.

Hi Joseph,

this might be caused by some settings in your JIRA workflow as logging work in Tempo does not affect the assigned user for an Issue. You should take a look at the workflow transitions in your Project and see if you have something like described in https://confluence.atlassian.com/display/AGILEKB/Configuring+Auto-Assign configured.

Kind regards,

Susanne 

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,142 views 6 19
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot