Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-18871

Σ Time Spent-aggregatetimespent on Epics does not sum up child issue time spent values on Classic projects

    • 2
    • 23
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      • There is a field called "aggregatetimespent" in Jira
      • The native time tracking features use this field
      • At the time of writing(14-Apr-2020), in next-gen projects, this field sums up the time spent data on child issues(Stories)
      • This does not happen in Classic projects

      Suggested Solution

      • Change the behavior in Classic projects so that time spent is summed up to the parent Epic and other hierarchy within Plans/Advanced roadmaps.

      Why this is important

      • Currently working for next-gen projects
      • Allows summed up time spent data to be used by customers + Jira automation features or third-party apps

      Workaround

      • No known workarounds

            [JSWCLOUD-18871] Σ Time Spent-aggregatetimespent on Epics does not sum up child issue time spent values on Classic projects

            Tom added a comment -

            We urgently need a solution here as well.

            Tom added a comment - We urgently need a solution here as well.

            Atlassian this is a BUG not a new Feature!!!!
             
            If you say that ∑Time spent is only available for standard issues, than why do I get correct results on Epic level except for the subtasks?
            It does add up all the time spent correctly from its childs.
             
            When issues of the type story have subtasks with logged time and you check the box on story level to include the hours of the subtasks, why are they then not included in the summed total on Epic level.  The checkbox clearly states "include" 
             
            Technically I do think that solving this issue is of very low impact.  as the data is already logged somewhere as it shows on the screen under the story. Just a matter of taking the correct value for calculating the Total time spent. 
             
            For detailed description and examples see PCS-305281.
             
            Again, I hope that Atlassian is taking its responsibility and acknowledge that sometime things go wrong, and makes the effort to correct it.
             
            We are paying an awful fee for Jira premium and I cannot accept as answer to this problem that as work around I have to buy some third party add-ons.

            jeroen.wilmes added a comment - Atlassian this is a BUG not a new Feature!!!!   If you say that ∑Time spent is only available for standard issues, than why do I get correct results on Epic level except for the subtasks? It does add up all the time spent correctly from its childs.   When issues of the type story have subtasks with logged time and you check the box on story level to include the hours of the subtasks, why are they then not included in the summed total on Epic level.  The checkbox clearly states "include"     Technically I do think that solving this issue is of very low impact.  as the data is already logged somewhere as it shows on the screen under the story. Just a matter of taking the correct value for calculating the Total time spent.    For detailed description and examples see PCS-305281.   Again, I hope that Atlassian is taking its responsibility and acknowledge that sometime things go wrong, and makes the effort to correct it.   We are paying an awful fee for Jira premium and I cannot accept as answer to this problem that as work around I have to buy some third party add-ons.

            It is now more than a month without any news on how Atlassian is going to solve this bug, what they keep incorrectly reporting as a product improvement. Is anyone ever looking into this issue?

            jeroen.wilmes added a comment - It is now more than a month without any news on how Atlassian is going to solve this bug, what they keep incorrectly reporting as a product improvement. Is anyone ever looking into this issue?

            Oeps, again an issue that has to solve a bug and which is there already for almost 4 years without resolution.
            Current situation is that Time Spent and aggregated Time Spent give exactly the same result, as Aggregated time spent completely opposite of what it says it does, does not aggregate anything at all.   

            jeroen.wilmes added a comment - Oeps, again an issue that has to solve a bug and which is there already for almost 4 years without resolution. Current situation is that Time Spent and aggregated Time Spent give exactly the same result, as Aggregated time spent completely opposite of what it says it does, does not aggregate anything at all.   

              Unassigned Unassigned
              dnguyen4 Derrick Nguyen
              Votes:
              14 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: