• 10
    • 12
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update – 13 Jan 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; however there are no immediate plans to put this suggestion on our near term roadmap.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Daniel Franz
      dfranz@atlassian.com
      Principal Product Manager, JIRA Platform

      I am thinking of having a field that serves as an time estimator field. That means, that the assignee can specify in days or weeks estimate of period they need to complete an assignment.

      Unfortunately I don't find one in the JIRA custom fields section.

      Any ideas for this? Or is there any alternative to this?

            [JRASERVER-12920] Convert Date Picker to A Time Tracker

            +1

            rfabrizio added a comment -

            Is there any updates on this?

             

            I want to be able to create a custom time tracking fields so that different groups such as QA and Developers have their own estimate fields that will then populate towards the original estimate. 

             

            Thanks.

            rfabrizio added a comment - Is there any updates on this?   I want to be able to create a custom time tracking fields so that different groups such as QA and Developers have their own estimate fields that will then populate towards the original estimate.    Thanks.

            I think why Jira is not giving custom time fields is because then people will innovate and create their own formula's of effort calculation which is a good thing.. but then people won't buy plugins ...  I was hoping if we could get custom time storing fields like the one there is in worklog it could solve many of our issues.

            rajnarayan.sahu added a comment - I think why Jira is not giving custom time fields is because then people will innovate and create their own formula's of effort calculation which is a good thing.. but then people won't buy plugins ...  I was hoping if we could get custom time storing fields like the one there is in worklog it could solve many of our issues.

            Hi Team,

            Any news on this feature ?

            Cheers,

            Aziz El Yacoubi added a comment - Hi Team, Any news on this feature ? Cheers,

            Kitty Lee added a comment -

            Would be nice to have a time tracking field for QA to track their time.

            Kitty Lee added a comment - Would be nice to have a time tracking field for QA to track their time.

            Thom Detko added a comment -

            We need resource tracking which is achieved by adding a time estimation field for issues. Without this we are considering another software instead so I think its pretty important, especially for agile scrum. This should feed into the planner as well. Additional functionality might be Epics should tally the work estimation from story's and tasks, or the epics should limit the estimation if it goes over the epics total time estimation.

            Thom Detko added a comment - We need resource tracking which is achieved by adding a time estimation field for issues. Without this we are considering another software instead so I think its pretty important, especially for agile scrum. This should feed into the planner as well. Additional functionality might be Epics should tally the work estimation from story's and tasks, or the epics should limit the estimation if it goes over the epics total time estimation.

            Hi Team,

             

            Please provide an update on this as this requested by users in our Jira instance where different project require these custom fields as per their business requirements.

            Surbhi Kaushik added a comment - Hi Team,   Please provide an update on this as this requested by users in our Jira instance where different project require these custom fields as per their business requirements.

            Kent Chiu added a comment -

            Hi,

            At our company, we have received a lot of requests to have a separate time tracking for different departments: Development, QA, Custom team, etc. So they are able to track effectively the resource utilization for each departments.

            Currently, we use a single time tracking for all of them which is very hard to calculate how much resource time spent from each department. 

            What we need is we would create a separate custom field with time tracking type for each department that enable them to track their resources. Currently, there is no way to achieve this in JIRA. 

            What is the plan to get this feature added to Jira custom field type?

            Thanks,

            Kent

             

            Kent Chiu added a comment - Hi, At our company, we have received a lot of requests to have a separate time tracking for different departments: Development, QA, Custom team, etc. So they are able to track effectively the resource utilization for each departments. Currently, we use a single time tracking for all of them which is very hard to calculate how much resource time spent from each department.  What we need is we would create a separate custom field with time tracking type for each department that enable them to track their resources. Currently, there is no way to achieve this in JIRA.  What is the plan to get this feature added to Jira custom field type? Thanks, Kent  

            Hi,

            I see over net that this is a very hot and problematic issue with Jira: many companies (including us) are willing to estimate and track the dev and the qa time separately and so willing to have the dev and the QA reports, burndown graphs, version statuses, etc separately.

            Seems that for the cloud users there is no option to do it at all.

            Is there any plan to have additional time tracking field?

            Alona Shkolnik added a comment - Hi, I see over net that this is a very hot and problematic issue with Jira: many companies (including us) are willing to estimate and track the dev and the qa time separately and so willing to have the dev and the QA reports, burndown graphs, version statuses, etc separately. Seems that for the cloud users there is no option to do it at all. Is there any plan to have additional time tracking field?

            I've got the same need at my company.

            We're a web dev agency.  Our developers receive a ticket with an estimate for 4h.  How do they know if that's all available for them, or if there's QA/feedback/iteration time?   I'd love to be able to show "Dev estimate" and "Other estimate" and then have the real, existing Estimate field calculated based on those two, or manually entered if those two are not applicable.   And show all this in the "Time Tracking" area of an issue.

            Mark Haller added a comment - I've got the same need at my company. We're a web dev agency.  Our developers receive a ticket with an estimate for 4h.  How do they know if that's all available for them, or if there's QA/feedback/iteration time?   I'd love to be able to show "Dev estimate" and "Other estimate" and then have the real, existing Estimate field calculated based on those two, or manually entered if those two are not applicable.   And show all this in the "Time Tracking" area of an issue.

              Unassigned Unassigned
              6d7295ce5db0 Melvin Mah
              Votes:
              227 Vote for this issue
              Watchers:
              107 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - 24h
                  24h
                  Remaining:
                  Remaining Estimate - 24h
                  24h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified