Sneaking in tickets to close does not change the Community's opinion...
It is and remains crap how this topic and the necessity for the customers is handled. One could at least take the trouble and enter into dialogue. Honestly, that is just outrageous.

https://jira.atlassian.com/browse/JSWCLOUD-17248

jules1 I am about to get an email sent out to admins (yours is one of them). Your global setting for time tracking is off, so if you can reach out to your admin and ask for that to be turned on. It should then appear in your view issue.

Regards,
Nathan

I've added it to the ticket type, but don't see Time to track anywhere on my ticket? What am I doing wrong? 

Hi benjamin.kapelle,

I like to be really upfront so that customers are aware what is going and informed as we continue to build out functionality in Next-gen projects.

We only picked up Time-Tracking as a team ~ a month ago. I know that for some customers that this crucial for their process and they might be questioning, why just a month ago?

To clarify each month we triage in-product customer feedback and the votes on feature requests like this ticket. We also monitor the changes in the feedback over time. Based off this features like Workflows and Subtasks were ranked above other features due to the large and consistent volume of requests for these features. Releases, estimation and other high ranked features are all crucial features that we know users want and need. That's why we are hustling to deliver them but based off customer value, we just have some other things to deliver first. I know that might be frustrating to hear, but I just want to be really upfront.

In the case of Estimation we want to better understand how customers work and the problems customers are trying to solve, so that we can see how we can improve this experience. So some features like this Time-tracking feature was just a simple port, other features like Project Configuration and Workflows have been completely overhauled. These overhauls provide a vast improvement over the existing experience, but there was a lot of work involved in terms of research, conceptualising and then development to bring these new experiences.

But in regards to the estimation ticket, that's why I would really love for you to go over and be involved on that ticket. So that you can be included in the conversation and help up build out the best solution that we can for our customers.

Warm regards,
Nathan

Hi benjamin.kapelle,

Thanks for taking the time to comment.

Please see my previous comment regarding the scope of this ticket and head on over to the estimation ticket , where it would be great to collate your and other user's information on how you are doing planning, estimation and have a central means by which to manage your requests.

Thanks mate,
Nathan

Hi, Nathan,

the feature works in my opinion. However, I think it hasn't been thought through to the end. The time recording is still not usable for sprint planning. For this to work properly, the estimated hours would have to be shown in the overview analogous to the story points and the balances of the hours would have to be transferred to the following sprint and also displayed there. Would this be poossible?

Kind regards

Benjamin

Hi guys, this is now rolled out to 100%.

As I mentioned before this ticket relates to the ability for users to:

• Add the "Time tracking" field to an Issue Type in Next-gen Project settings.
• Log time and Time remaining from the Issue View
• Have logged time show up in the Worklogs

Thanks for the patience guys, any requests/comments for Estimation related functionality should be made here

Looks like you can add the field to all the issue types, but the top-level views, such as the boards, don't show the time remaining (estimates), where story points are shown.  Likewise, from a issue, you can't see the time remaining for subtasks without going into the subtask.  I assume these things will be coming?  Logging time on a subtask also doesn't seem to burndown the time remaining on the parent task.

You have to go to project settings > issue types > drag the new field from the right column 

you have the "time racking by jira"

I do not see it.

Did you have to turn it on?

Hi everyone,

just to check with you all.

It just appears this morning that Time Tracking by Jira is available on Next-Gen project. 

Do you confirm on your side ? Even if Time Estimate is not here yet ^^

Unfortunately not everyone has approval from their company to add 3rd party apps to Jira.

@Dam,

You can add estimates through the Clockwork app as per @Pawel's comment above

@Emily done ! Thanks for also sharing this issue.

@Dam Mulhem:

Please upvote and comment on this issue for time estimation. I am in the same boat; time tracking is useless to me without time estimation. https://jira.atlassian.com/browse/JSWCLOUD-17248

hello,

Time tracking is missing for all of us but there's many ways to let users add time spent, with Dashboard, plugin from marketplace or more... and I know will be able to add it soon. 

The main problem to me is for Time Estimate, there's no easy way to add some, it's a real issue. I even tried to make custom field (easy with next-gen) and make formula then on reports but because there's no way to create default template we need each time to create it with same characters for each kind of issue...

Please you need a realease date for that important feature !! 

Thanks !!!! 

PS : if we can help let us know ^^

Same for us. One more team relies on this feature. Please consider this in your upcoming sprint. Thanks!

It's very close to being rolled out corderol

Time tracking is an essential part of why we actually pay for Jira. We're quite dissapointed it's been more than 6 months, and there's no deadline to deliver this feature.

Until then, Next-Gen is useless to my team.

@Iftikhar

I know using Clockwork's Log work might not be intuitive for setting the estimate but you can actually save/edit the estimate alone, you don't have to report the time spent. So I believe it does what you want but is a bit unintuitive. We will bring the estimate to a separate field in the future but that was the best place to put it now - as we want to allow editing the estimate while logging the time too (so currently it serves both purposes). 

@Pawel, Thanks for getting in touch. I can't find any option in the Clockwork to enter the estimate before the time is started.

They have the option to enter/update the estimate at the time of Logging a time to a task. We need the option to add time estimates before the task is assigned to the worker.

@Iftikhar

Clockwork supports entering/updating estimates now.

We desperately need the time tracking feature in the next-gen project. I don't understand why it is taking this much time when the fields are already there in the database.

Clockwork is fine for logging the work but there is no way to put the total estimate of task before it is started. Is there?

Need a time tracker for each task, stop and start button to track time please.

Found the new Time Tracking field in Issue types of Project settings, added, but not working. Really need this feature for my team badly. Please let us know soon when the possible deliverable date, thank you!

Very badly this feature needs for my team
+1

Sorry guys can't give a deliverable date, but I can say that we are working on it now, it is not a large body of work, we get a lot for free as the fields already exist for the Next-gen projects and the UI element already exists for the issue view. We just need to expose the field type in the UI in Next-gens project settings and handle the interaction with the global time tracking settings/toggle.

Hope that helps.

@nathan Sturgess - Bumping @bartłomiej Jańczak 's request - could You at least give us a period for timeLogging in NG? Like more Q3 or Q4? Or perhaps it's next year shipping?

Also need to see the work history. When a client calls and says what have you done, it takes too long to run reports. A quick view of who has worked on it and what they have done is essential.

I can confirm that Clockwork saves tracked time to Jira worklog, so it is 100% compatible with Jira backend.
One can confirm that by visiting the "History" tab of the Next-Gen issue. The time logged and changes made to, e.g., "remaining estimate" is visible there.

Thank you Tudor and Nathan for your help!  

Hi alexandru.bogdan, tudor.munteanu is correct (thanks Tudor for jumping on that question): If any of the apps set the two Jira fields (log work and time remaining), that data will persist as it is stored in Jira's database.

Salut Alex,

We're using Clockwork for Jira Cloud (1) a free add-on. From what I've been reading, it is using an existing backend of time tracking for Jira so I am expecting 100% compatibility with whatever Atlassian will release.

Also, the backend for time tracking in next-gen projects already exists, there's no FrontEnd (again, from what I know) so if Toggl uses this backend, then all the information will be then but accessible through Jira's time tracking FrontEnd as well, besides Toggl.

Another thing about the Clockwork (1) add-on I am using is that it is working for both next-gen and classic projects. And classic projects already have Jira's time tracking FrontEnd. So I'm expecting full compatibility, at least for this plugin, with what Jira will release for the Next Gen ones.

Anyway, cheers!

P.S.: Cum sa nu mai ai time tracking, frate?!

(1): https://marketplace.atlassian.com/apps/1219213/clockwork-automated-timesheets?hosting=cloud&tab=overview

Hello Nathan,

We are also expecting the introduction of the time tracking feature in Next Gent

In the mean time I was looking on integrating one of the available add ons as a temporary solution
What do you think is the best option for that in order to migrate the time tracking data with ease into Jira when the feature becomes available?
e.g. Toggl for example is synchronising your worklogs. If at some point in the future we decide to opt out from Toggl will the Jira worklogs still remain? Can we then directly switch to tracking time into Next Gen without any side effects? 
https://marketplace.atlassian.com/apps/1215495/toggl-integration-for-jira?hosting=cloud&tab=overview

Thank you  

Thanks Nathan for a quick update. 

Looking forward to receive further updates on this issue. 

Nathan,
I don't expect exact date, I know how software development works . Shipt it expectancy in quarters will do. 2019 Q2 is possible?

Come on bartlomiej.janczak1218621652 you should know that I can't give you a ship date 😉. But I can say that the porting over of the field shouldn't be too complex. I will reply on this ticket when it is available in product and shipped to 100% of customers.

Warm regards,
Nathan

Nathan,

That is a great news! When are you going to ship it?

Best Regards,
Bartek

Hi msheth, thanks again for your comments.

My team has started working on bringing the Time tracking field into Jira. To be specific what that means, see the following pictures to see what you will get in Next-gen when we are done:

We also met with Tempo this morning and will be continuing discussion to bring Tempo into Next-gen. That functionality will take more time, as there is a much larger scope and surface area involved.

For those interesting in Time estimation that is a seperate body of work and is covered by in this ticket: https://jira.atlassian.com/browse/JSWCLOUD-17248. So please go upvote and comment there if you are needing this feature.

Warm regards,
Nathan Sturgess

Hi Nathan, 

Now that you have lot of valuable inputs from the user community, can you please let us know what is the plan of action and by when can we have the Time tracking feature released in Next Gen projects. 

It is extremely important for me to have this feature ASAP for me and my teams to effectively work with Next Gen projects. Alternatively, we will need to rollback to classic Jira Project or some other alternate Tools. 

I truly feel that Atlassian has rushed in launching the Next Gen Project without many such important features that are absolutely required to manage projects. This is very likely to adversely impact the Jira user community.

Regards,

Manish Sheth

Hi

Echoing what others have said;

As a Product Manger who deals with external development resources, I need time tracking for two main reasons.

1. So that remote resource can log work completed for billing & project progress purposes. "Log Time" "Description" 
2. So that I can estimate reports, identify progress against milestones and understand whats left to plan ahead for the next sprints "Time estimate" "Time Remaining"

This is a key function for me as my resource can often be working in different locations/timezones so to be able to pull a report before the next retrospective/sprint planning session would be amazing.

Please add this feature in, I feel like it's a critical feature (in my vision anyway). If you could just carbon-copy the previous time tracking functionality across that would be amazing.

Apologies if these examples have already been given, but I would like to put more down than just +1 

Kind Regards

Seconding Manish Sheth's comment.

My team needs:

• "Time Estimate" field
• "Log Time" field
• "Time Remaining" field
• "Description" field for what work was done
• Maintaining Classic Jira's "Original Estimate" functionality would be ideal, so that if the estimation is update we still can reference the original estimate.

I currently generate my reports by exporting the "Original Estimate", "Time Logged" and "Work Ratio" fields to excel, so that I can monitor time spent on projects, and how accurate our estimations were. Ideally Jira would be able to directly report this, instead of having to export.

Hi Nathan,

Our use case is pretty simple:

1. A Project/Product Manager inputs the "Time Estimate" in the task/to-do
2. A team member logs their time directly from that task
   1. The "Time Tracked" is an input option for the team member (either manually, or through an automated counter)
   2. Optionally, "Time Remaining" can be displayed
3. Team member can also manually input "Percent Complete" (this is independent of the "Time Tracked" and "Time Estimate")
4. A Project/Product Manager must be able to run various reports based on project names, task names, team members, time spent, time estimates, etc.

Note: It would be great to categorize tasks under a certain type, e.g. design, development, QA, marketing, copywriting, r&d, etc.

Hi Nathan,

Sorry for the late reply. We need to export the time logged as a report so we can:

1. invoice our customers, since most of them are charged by the hour
2. keep internal records of time spent and activities for audit purposes

The format of the report could be very similar to that of Timesheets Plugin.

Two very important bonus features, if you can take these into account, are:

a) the option to make the description field required, when someone logs time

b) the option to flag if that time entry is billable or not, this could be done via a checkbox and then reflected in the time report

If I may join, as a "one-man band", I use time tracking for 2 main purposes:

1. To log any time spent on projects. I make a report at the end of the month to see how much I actually worked and if I reached my target. For now, since multi-project reports are not possible (but they once were, without any additional paid/free addons), I have to use Team worklog reports app, which is fortunately free for now. Tempo is overkill for me. I would rather use another Project management solution, which includes such basic features.
2. To log time that needs to be billed to clients. I have a custom field "Billable" and considering the type of the request, I set it accordingly (e.g. for support/warranty tasks, it's set to no).
   Then in the previously mentioned addon I can set this parameter in the JQL query and get a total hours worked report by employee.
   For the list of tasks, I have to use the Search issues feature, again setting the Billable parameter. I print this list to a PDF and attach it to the invoice. On the invoice, for the sum of the billable hours, I just add "Application development - see specification".

When I manage to get around it, I will implement this procedure in an external application with the help of the API, so this time and click wasting will not be necessary.

Hi Nathan, 

Thanks for asking.

We are currently using 3 different reports - one detailed excel sheet with rows for: Task name, person, epic name, logged time, time log comment, and 4 custom fields (customer, project manager, link to ticket system and indication of whether logged time is billable)

And two simple reports to see total logged time per week grouped by epic and by person.

msheth perfect! 💥 This is exactly the kind of informative response that I am looking for, so thanks.

So to set expectations, we are currently working on the ability to expose the native Jira time-tracking functionality that I mentioned in my comment above. But I believe this will not be enough alone to unblock Tempo in Next-gen. In response, I am meeting with Tempo next week and discussing how we can make that happen.

Thanks again for your reply.

Hi @ Nathan,

We would need fields like Time logged, Time Remaining, Billable Time, Description at the time of logging time by respective scrum team members. Once the scrum team logs the time, respective scrum master will need a feature to generate a report and review scrum team wise or task wise time logs. Also to download the timelogs to Excel, CVS formats. We are currently using Jira Classic Projects along with Tempo across multiple clients and scrum teams. We have moved some of our projects to Next Gen Projects and are eagerly waiting for Time tracking, Reporting and Downloading functionality to get released for Next Gen Projects..

Hope this helps.

Manish.

Hi @Nathan,

I love using this feature because I work with a lot of freelancers and it creates some sort of competition, where the freelancers try to outdo each other because of those times being public.

I then turn around and invoice my clients based on those hours worked!

Best,

Chris

Hi jack503457770, the field is not yet available but starting the work to bringing this into Next-gen projects. So what are we talking about here? For everyone's clarity:

This would appear in the righthand side of your issue view:

And when clicked you would see a modal:

After someone logs work you could see that history in the Activity section of the issue view by selecting History or Work log from the dropdown:

Re: New Api? No. This just exposing what exists in Jira already in the UI in Next-gens. But if you could answer my question from about that would be most appreciated: "Assuming that you guys have that field available now and were able to log time, what would you do with that information?" Do you use reports? Export it to Excel? I want to fully understand what happens with all that logged info, after the fact.

Regards,
Nate

Hi @Nathan,

Could you let us know what field has been added and what information can we put into it? Is there any documentation that explains what you guys added/implemented? I cannot see anything in my Next-Gen project.

Also, what you mean that the new field won't be compatible with Tempo? Is there a new API to handle time tracking in Next-Gen?

Thanks,
Jack

Hi ebellhiggins, kasper.moller, jack503457770, paul120, e.larard, gordon1 thanks for replying.

Assuming that you guys have that field available now and were able to log time, what would you do with that information? I assume it is to produce some sort of report or summary. The hey part here is: can you guys tell me how you are going about that in Classic please?

Thanks @Jack

I will take a look at Clockwork

Hi Nathan,

My team needs the ability to do the following before we can switch to Next-Gen projects:

• Estimate the time required for a task
• Log time spent on a task
• Generate a report that compares the Time Estimate vs the Time Spent so we can gauge how accurate our time estimation actually is. Being able to filter reports by user would also be helpful, so we can determine if certain team members have a harder time producing accurate estimations than others.

Thanks.