Time tracking with Harvest integration

[janet.saunders]

In Jira fill in the field "Original Estimate"

Open "Harvest Time Tracking" within the Jira ticket and record time on task or start timer.

Once I submit, the time is recorded in Harvest correctly and a link to the Jira ticket is supplied in Harvest.

However, "Time Tracking" is not updated in the Jira ticket because I didn't track the time using that. Is there any way to integrate so time recorded in Harvest, updates the bar so we can see progress against the original estimate?

[Anne Saunders]

I'm also experiencing this, nearly a year later. I'd really like the Time Spent / Time Remaining to update on the ticket when we use the Harvest integration, because my devs are not going to copy their time over.

[Bea Schuhmacher]

I'm also searching for this answer over a year after you posted this looking again

[Anne Saunders]

We are using the paid App from 42nd for this, now.

As long as you have an original estimate, and your board is configured to use Sprints, and your estimation settings look like the image below, and your devs sync their timers, it works. 

[Bea Schuhmacher]

We added it yesterday, glad to know that it was successful for you. Thanks for the response!

[Erika Simon]

@Anne SaundersI am experiencing the same problem you did on March 5 (and @janet.saunders on 24, 2019). We have Harvest Time Tracking Pro (paid version). All my settings match your screen shot and criteria ("As long as you have an original estimate, and your board is configured to use Sprints, and your estimation settings look like the image below, and your devs sync their timers"). 

But the time logged in Harvest Time Tracking is not showing up in Jira's "Time tracking" field -- it still appears as "no time logged" after logging time.

Any idea how to make this original time estimate burn down?

What did you mean by "devs sync their timers"?

Thanks so much in advance for your thoughts.

[Anne Saunders]

So what happens with the 42nd App is that a timer is created and runs in Harvest. If you manually stop it in Jira, the app creates a Jira worklog and applies the time from your Harvest timer to the Jira worklog. 

If you're like me, and you interact with your timer(s) via the Harvest apps & site, starting and stopping them as you go back and forth between tasks, you'll need to synchronize your timers and worklogs at the end of each workday. Each user has to do this on their own, because it draws from their Harvest and Atlassian logins.

1. Click on your Atlassian Account profile icon.
2. Select Synchronize Timers to Issues.
3. Select the date range to sync. We have our devs do this daily. 
4. Click Search for the Harvest timers to sync.
5. If the Harvest timers link up to the correct Jira Issues, and all of the Project/Task billing looks correct, click Sync All. (If it looks wrong, you can correct it in Harvest and Search again.)

[Erika Simon]

Thank you, @Anne Saunders , this is helpful. Unfortunately, my team does not have "Synchronize Timers to Issues" in that drop-down menu (step 2). I've double-checked and everyone does have permissions set to "Work on Issues," "Edit Own Worklogs," "Edit All Worklogs" and "Delete Own Worklogs". But the sync option still isn't showing up. Any further ideas?

We use Jira Software Cloud - Company-Managed - Scrum.

Thank you again!

[Anne Saunders]

Is the app you're using the native one from Harvest or "Harvest Time Tracking by 42nd"? 

The native one seems to have been basically abandoned by Harvest, and their time tracking algorithm left us a lot to be desired, which is why we switched to the one from 42nd. 

[Erika Simon]

Thank you, @Anne Saunders ! We will try the 42nd version.

[Jonathan Aspeling]

Also interested in this - looks like there is a paid market place plugin for this. 

Harvest will show you the time logged to the ticket on the harvest plugin itself witch is cool. 

Wanting to report on estimate vs actual her.

Screenshot example below:

[Anne Saunders]

This looks like the add-on we went with - I love it. Jira and Harvest round time a smidge differently, so sometimes the sync is off by a minute, but if you only bill or track in 6 or 10 minute intervals, it is absolutely adequate. It has freed up a TON of our operational effort that we used to spend on searching out & fixing the incomplete or bad Harvest entries.

You DO still need to pay attention to how you set up your time tracking per project - in Scrum boards, you can select story points or actual time - for this to work the way we wanted it, we work against the estimated actual time. (You can still record Story Points if you want to.)