Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-69310

New issue detail view won't display the Time estimate in hours

      Atlassian Update - 6th May 2021

      Hi everyone, 

      Work for fixing this bug has begun! This ticket is a priority we're currently working on and will be done shortly. Make sure to watch this bug for updates on our progress. 

      Regards, 

      Atlassian

      Summary

      Even though the Time display format Time tracking global setting is configured to Hours, the Time estimate field in the new issue detail view (both the backlog view and in the active sprint pop-up view) will still display it in Weeks/days/hours, including the placeholder example in the Time Spent field:

      Environment

      Jira Cloud

      Steps to Reproduce

      • Change the Time tracking global settings:
      1. Jira home -> Settings -> Issues -> Time tracking;
      2. Click on Edit global settings -> set the Time display format field to Hours.
      • Change the estimation setting in the board:
      1. Elipses button -> Board settings -> Estimation;
      2. Change the Estimation Statistic option to Original Time estimate.
      • Now test a time estimate value input in a issue in the backlog:
      1. Select an issue in the backlog so the detail -> set 1d in the Time estimate field;
      2. You'll see that the estimate value is correct converted to working hours in the backlog view (right to the card), but in the detail view, the value will be displayed in days.

      Expected Results

      The detail view should display the time estimate in hours, like the global setting was configured.

      Actual Results

      The Time estimate value is still displayed in Weeks/days/hours.

      Workaround

      You can set your working days per week or working hours per day to a higher value than any one ticket's time log would reach. For example:

      • Set your working hours per day to 1000 to replicate format=hours
      • Set your working days per week to 100 to replicate format=days

            [JRACLOUD-69310] New issue detail view won't display the Time estimate in hours

            just encounters this bug, this does still not work on latest Jira Datacenter!

            Awesome Atlassian! Really Awesome!

            Maximilian Weißböck added a comment - just encounters this bug, this does still not work on latest Jira Datacenter! Awesome Atlassian! Really Awesome!

            fonda added a comment -

            You guys, let's all go buy lotto - this issue has finally been fixed! It feels surreal... I can't believe it took them over 3 years to look at such a simple thing!

            fonda added a comment - You guys, let's all go buy lotto - this issue has finally been fixed! It feels surreal... I can't believe it took them over 3 years to look at such a simple thing!

            Still not fixed.  Is there any work around?

            Nina Marshall added a comment - Still not fixed.  Is there any work around?

             We need to have it fixed  before 31th March. Do you have any update?

            joanna.pietruszka@loyic.com added a comment - - edited  We need to have it fixed  before 31th March. Do you have any update?

            Kåre Lund added a comment -

            This soooo annoying. Fix issues like this before forcing people to use the new view

            Kåre Lund added a comment - This soooo annoying. Fix issues like this before forcing people to use the new view

            When at 30 March 2021 the new issue view will become the standard then the workarround to use old view will not work. Also the other workarround to set hours per day to 1000 has the sideeffect that when entering 1d it will translate to 1000 hours.

            So in my opinion a fix for this issue is needed more urgently now!

             

            Albert van Geemen added a comment - When at 30 March 2021 the new issue view will become the standard then the workarround to use old view will not work. Also the other workarround to set hours per day to 1000 has the sideeffect that when entering 1d it will translate to 1000 hours. So in my opinion a fix for this issue is needed more urgently now!  

            Ricardo N added a comment -

            Ricardo N added a comment - https://getsupport.atlassian.com/browse/JST-630837  

            Victor Zagorodniuc added a comment - - edited

            Turning off the Labs feature fixes it, but considering that "From March 31, 2021 we’ll be moving all users on the old issue view to the new issue view", you need to fix that issue like mentioned in the Summary.

            Please note that additionally to the three screenshots attached to this ticket, this problem is also reproducible on the Active Sprints view when I configure the board and add fields:

            • Original Estimate
            • Σ Time Spent

            Go to Active Sprints, click on the menu icon from top-left region and select "Board settings" menu option.
            On the left menu select "Card layout" and add mentioned fields to the "Active sprints table" - 
            https://gyazo.com/515abb9d3d142cbe519d2c9bf6522516 

            Note: initially those fields were affected, after turning off the Labs feature then only hours were shown and I can't reproduce the problem even if I turn on the Labs feature again.

            Victor Zagorodniuc added a comment - - edited Turning off the  Labs  feature fixes it, but considering that "From March 31, 2021 we’ll be moving all users on the old issue view to the new issue view", you need to fix that issue like mentioned in the Summary. Please note that additionally to the three screenshots attached to this ticket, this problem is also reproducible on the Active Sprints view when I configure the board and add fields: Original Estimate Σ Time Spent Go to Active Sprints, click on the menu icon from top-left region and select "Board settings" menu option. On the left menu select "Card layout" and add mentioned fields to the "Active sprints table" -  https://gyazo.com/515abb9d3d142cbe519d2c9bf6522516   Note: initially those fields were affected, after turning off the  Labs  feature then only hours were shown and I can't reproduce the problem even if I turn on the  Labs  feature again.

            In my org we have many teams that use 5 hours/day, but other teams that use 8 hours/day. This is severely interfering with our ability to estimate projects and the fact that this setting is global instead of per-project is causing us a lot of frustration.

             

            Can you consider escalating either scoping the setting per-project or escalating this bug? We just recently came from using Trello with Plus for Trello, and I'm surprised to see that Jira is less useful in this area

            Parker Shepherd added a comment - In my org we have many teams that use 5 hours/day, but other teams that use 8 hours/day. This is severely interfering with our ability to estimate projects and the fact that this setting is global instead of per-project is causing us a lot of frustration.   Can you consider escalating either scoping the setting per-project or escalating this bug? We just recently came from using Trello with Plus for Trello, and I'm surprised to see that Jira is less useful in this area

            fonda added a comment -

            Can this please please be fixed already? Been waiting patiently for so long now, the estimates in days is absolutely useless to us.

            We can see that when a ticket loads, the hours are displayed first but then once the page has fully rendered, it converts to days/weeks... surely it's not a difficult fix? Whatever the case... please fix it. It'd be a quick win and you guys really need more of those!

            fonda added a comment - Can this please please be fixed already? Been waiting patiently for so long now, the estimates in days is absolutely useless to us. We can see that when a ticket loads, the hours are displayed first but then once the page has fully rendered, it converts to days/weeks... surely it's not a difficult fix? Whatever the case... please fix it. It'd be a quick win and you guys really need more of those!

              Unassigned Unassigned
              lalmeida@atlassian.com Leonardo De Almeida
              Affected customers:
              147 This affects my team
              Watchers:
              109 Start watching this issue

                Created:
                Updated:
                Resolved: