• 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?

          Form Name

            [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.

            This is the same thing we need in our company! It would be very useful for dividing the time estimated in different processes in the same flow, for example: for adding a time to test a task. 

            Isabel Aguilar added a comment - This is the same thing we need in our company! It would be very useful for dividing the time estimated in different processes in the same flow, for example: for adding a time to test a task. 

            This would be very useful at our company to log time that we bill on a task, and have it visible in the task's view screen. (without addon's which may require clicking to view and payment)

            Robert Wojtowicz added a comment - This would be very useful at our company to log time that we bill on a task, and have it visible in the task's view screen. (without addon's which may require clicking to view and payment)

            ZachE added a comment -

            My use case for a field like this would be for specifying a "time duration". Let the users enter it in whatever format, but be able to query it with REST and get back a single number (which could represent milliseconds or seconds or minutes or hours, doesn't matter to me).

            ZachE added a comment - My use case for a field like this would be for specifying a "time duration". Let the users enter it in whatever format, but be able to query it with REST and get back a single number (which could represent milliseconds or seconds or minutes or hours, doesn't matter to me).

            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

            dan (Inactive) added a comment - 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

            We would also like the ability to extend estimate time tracking based on multiple contributing teams as described by Lynne.

            ISG Support added a comment - We would also like the ability to extend estimate time tracking based on multiple contributing teams as described by Lynne.

            This custom field type would be great to be in the core as Cloud subscribers cannot install custom plugins.

            Leevi Graham added a comment - This custom field type would be great to be in the core as Cloud subscribers cannot install custom plugins.

            This feature would also be useful for us, as described by Lynne Billig. Any update as to whether this will be coming any time soon?

            Darlene Pike added a comment - This feature would also be useful for us, as described by Lynne Billig. Any update as to whether this will be coming any time soon?

            This ticket is 7 years old, can we have an update on whether or not this is even in the upcoming roadmap? We'd really like to have the ability to create additional custom fields with a field type parallel to the existing time tracking fields.

            Celina Kincaid added a comment - This ticket is 7 years old, can we have an update on whether or not this is even in the upcoming roadmap? We'd really like to have the ability to create additional custom fields with a field type parallel to the existing time tracking fields.

            My request is better explained by the CLOSED issue JRA-13610.
            There are multiple groups who contribute to the resolution of an issue: Development (Design and Development activities); QT (integrated quality testing); Documentation (User Help, Release Notes, Feature Descriptions). Completion time for delivery is dependent on availability of resources from all these groups. So each of their estimates and real hours need to be tracked.

            Lynne Billig added a comment - My request is better explained by the CLOSED issue JRA-13610 . There are multiple groups who contribute to the resolution of an issue: Development (Design and Development activities); QT (integrated quality testing); Documentation (User Help, Release Notes, Feature Descriptions). Completion time for delivery is dependent on availability of resources from all these groups. So each of their estimates and real hours need to be tracked.

            The problem with the KCF plug-in field is that the way the data is stored is incompatible with the time tracking fields. I cannot, for example, run the following query:

            expression("", "timespent + remainingestimate > originalestimate + customfield_12345")

            Having a native field type with the same behaviors is still needed.

            Deleted Account (Inactive) added a comment - The problem with the KCF plug-in field is that the way the data is stored is incompatible with the time tracking fields. I cannot, for example, run the following query: expression("", "timespent + remainingestimate > originalestimate + customfield_12345") Having a native field type with the same behaviors is still needed.

            You may use freely the Interval custom field from the KCF plugin.

            Florin Haszler (Alten Kepler) added a comment - You may use freely the Interval custom field from the KCF plugin .

            Ken,

            Any chance of sharing this code? Perhaps you want to add it to the current Codegeist:
            http://confluence.atlassian.com/display/CODEGEIST/Atlassian+Codegeist

            :o)

            We're keen on extending our jira for our own requirements too, and would be keen to collaborate with others doing the same in this area.

            Nick Jones added a comment - Ken, Any chance of sharing this code? Perhaps you want to add it to the current Codegeist: http://confluence.atlassian.com/display/CODEGEIST/Atlassian+Codegeist :o) We're keen on extending our jira for our own requirements too, and would be keen to collaborate with others doing the same in this area.

            Tom Miller added a comment -

            In addition, I would want a business analysis estimate for designing the feature. No only an estimate, but a way to log work.

            Tom Miller added a comment - In addition, I would want a business analysis estimate for designing the feature. No only an estimate, but a way to log work.

            Ken Roland added a comment -

            We did wind up developing our own custom field. From no substantial knowledge of Jira plugins to complete was about 3 days. However, the tutorials for Jira plugins were not extremely helpful and seemed to jump around between topics. The walk-throughs don't really contain a lot of relevant information for this one and a lot of Java knowledge is assumed.

            However, the beauty of rolling your own is that we've implemented many more features with it (load by developer by version applied to time automatically), implemented our own "Pretty Values" in the format we like, etc. We have now completely disabled the time tracking in Jira and just use this field.

            Our implementation involved storing the value in Minutes, then doing the conversion toPretty (6d 2h30), toLongPretty (6 Days, 2 Hours and 30 Minutes) and fromPretty back to minutes in a separate class.

            I would highly recommend doing the plugin yourself just to get in there and start expanding Jira, we've got 3 other custom plugins running now.

            Good luck!

            Ken Roland added a comment - We did wind up developing our own custom field. From no substantial knowledge of Jira plugins to complete was about 3 days. However, the tutorials for Jira plugins were not extremely helpful and seemed to jump around between topics. The walk-throughs don't really contain a lot of relevant information for this one and a lot of Java knowledge is assumed. However, the beauty of rolling your own is that we've implemented many more features with it (load by developer by version applied to time automatically), implemented our own "Pretty Values" in the format we like, etc. We have now completely disabled the time tracking in Jira and just use this field. Our implementation involved storing the value in Minutes, then doing the conversion toPretty (6d 2h30), toLongPretty (6 Days, 2 Hours and 30 Minutes) and fromPretty back to minutes in a separate class. I would highly recommend doing the plugin yourself just to get in there and start expanding Jira, we've got 3 other custom plugins running now. Good luck!

            AntonA added a comment -

            Tyler,

            While this Custom Field Type is not available out of the box in JIRA, custom field types are plugins, so it is possible to code your own. For more information please see:
            http://confluence.atlassian.com/display/JIRA/How+to+create+a+new+Custom+Field+Type

            If you would like to get help on making a plugin, you may wish to involve an Atlassian partner. If so, please send an e-mail to:
            partners at atlassian dot com

            Cheers,
            Anton

            AntonA added a comment - Tyler, While this Custom Field Type is not available out of the box in JIRA, custom field types are plugins, so it is possible to code your own. For more information please see: http://confluence.atlassian.com/display/JIRA/How+to+create+a+new+Custom+Field+Type If you would like to get help on making a plugin, you may wish to involve an Atlassian partner. If so, please send an e-mail to: partners at atlassian dot com Cheers, Anton

            We need a custom time field as well - We are getting ready to track production outage issue in JIRA, and though we have an incident start and end fields, there's no way to specify the total outage time in a way that can be reported. A custom time field, just like used in work logs, would fit the bill. I've voted for this issue.

            Tyler Tyler added a comment - We need a custom time field as well - We are getting ready to track production outage issue in JIRA, and though we have an incident start and end fields, there's no way to specify the total outage time in a way that can be reported. A custom time field, just like used in work logs, would fit the bill. I've voted for this issue.

            Ken Roland added a comment -

            This is what I'm looking for as well. Is there example code to write your own anywhere?

            Ken Roland added a comment - This is what I'm looking for as well. Is there example code to write your own anywhere?

            I have the same need. I want to record a work estimate, but there is no field type to do this. I thought I logged this issue but I cannot find it.

            Neal Applebaum added a comment - I have the same need. I want to record a work estimate, but there is no field type to do this. I thought I logged this issue but I cannot find it.

            Melvin Mah added a comment -

            That's exactly what I have in mind.

            Melvin Mah added a comment - That's exactly what I have in mind.

            AntonA added a comment -

            Melvin,

            Do you mean you would like to have a custom field where you select a duration, e.g. "1d 2h"?

            Cheers,
            Anton

            AntonA added a comment - Melvin, Do you mean you would like to have a custom field where you select a duration, e.g. "1d 2h"? Cheers, Anton

              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