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, Nathan,
I have deliberately added this again here, because this problem has received sufficient attention here. This task was opened 8 months ago. Since there are already some smaller addons that seem to refer to the same fields in the backend. I therefore assume that only a small view and no deeper business logic has been developed here. For such a small function 8 months development time is extremely long. I'm afraid that this will take as long with the planning views that are absolutely necessary as it has been the case here.

As desired, I have noted my additions in the linked process. However, I ask you to listen to the community here. The forum is full of requests in this direction.

Many thanks and best regards

Ben

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"