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

Make 'date started' field in Log Work configurable

XMLWordPrintable

    • 51
    • 28

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

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

      In certain use cases, it is required that work must be logged only for the current day/date and the ability to log work on any date (including previous and future) may not be desirable.

      While the current ability to log work against a date in the past for instance is fine for many use cases. It would be great to make this Date Started field/feature more configurable in JIRA, by making it possible to configure or restrict the 'date started' field, perhaps so that it can be restricted to only certain users, or hidden entirely to cater for other use cases as described in the previous paragraph.

          Form Name

            [JRACLOUD-34156] Make 'date started' field in Log Work configurable

            Claudio de Lima Sales added a comment -

            1+

            Claudio de Lima Sales added a comment - 1+

            Nikhil Kundra added a comment - - edited

            PLEASE can we do this, Jira?

            It's a huge accounting, tax, and compliance nightmare that Jira allows users to:

            • Submit, log—and thus, bill—time in the future.
            • Edit submissions of worklogs—and thus, billings (whether they be already billed, collected, or not billed yet)—in the past and without any limitations.

            I am not saying there are no use cases, but Jira Admins should be able to:

            1. Configure if these Time/Billing/Work-Description Logs can even be submitted or edited in the first place, based on their system-of-record and accounting, tax, and compliance requirements.
            2. And we should also have the ability to restrict the submitting of these aforementioned Time/Billing/Worklog Submissions to a certain number of hours, days, or weeks in the past (or in the future).
            3. And we should also have the ability to restrict the editing of these aforementioned Time/Billing/Worklog Submissions:
              • to a certain number of hours, days, or weeks in the past (or in the future)
              • to a certain number of hours, days, or weeks after the initial creation of the Time/Billing/Worklog Submission.

            Otherwise, the integrity of these logs inside Jira is incredibly compromised and can't even be relied on for accurate forecasting and planning.

             

             

            Most important from the above (e.g. "Biggest ROI" for Atlassian):
            • Restrict how far into the past a Worklog can be edited or submitted
            • Prohibit Worklogs from being submitted as starting in the future

             

            Nikhil Kundra added a comment - - edited PLEASE can we do this, Jira? It's a huge accounting, tax, and compliance nightmare that Jira allows users to: Submit, log—and thus, bill—time in the future . Edit submissions of worklogs—and thus, billings (whether they be already billed, collected, or not billed yet)—in the past and without any limitations. I am not saying there are no use cases, but Jira Admins should be able to: Configure if these Time/Billing/Work-Description Logs can even be submitted or edited in the first place, based on their system-of-record and accounting, tax, and compliance requirements. And we should also have the ability to restrict the submitting of these aforementioned Time/Billing/Worklog Submissions to a certain number of hours, days, or weeks in the past (or in the future). And we should also have the ability to restrict the editing of these aforementioned Time/Billing/Worklog Submissions: to a certain number of hours, days, or weeks in the past (or in the future) to a certain number of hours, days, or weeks after the initial creation of the Time/Billing/Worklog Submission. Otherwise, the integrity of these logs inside Jira is incredibly compromised and can't even be relied on for accurate forecasting and planning.     Most important from the above (e.g. "Biggest ROI" for Atlassian): Restrict how far into the past a Worklog can be edited or submitted Prohibit Worklogs from being submitted as starting in the future  

            Kaviraj Kyatam added a comment -

            Yes this should be configurable.
            +1

            Kaviraj Kyatam added a comment - Yes this should be configurable. +1

            Seamus Reynolds (they/them) added a comment -

            I'd love to be able to configure this field to

            1. Not be required
            2. Not be visible at all.

            Seamus Reynolds (they/them) added a comment - I'd love to be able to configure this field to Not be required Not be visible at all.

            Sivarama Krishna K added a comment -

            Log work is basically the work done.
            So, future date and time duration is not correct.
            It should be restricted in the system.

            Sivarama Krishna K added a comment - Log work is basically the work done. So, future date and time duration is not correct. It should be restricted in the system.

            Daniel Courtney added a comment - - edited

            Taiwo thank you very much for adding this suggestion. Please see another suggestion I have added that is similar: JRA-62317

            Daniel Courtney added a comment - - edited Taiwo thank you very much for adding this suggestion. Please see another suggestion I have added that is similar:  JRA-62317

            ChirannjeviP added a comment -

            this is a basic feature/configuration, we don't why Atlassian missed this simple concept, i would like to see this configuration in JIRA.

            ChirannjeviP added a comment - this is a basic feature/configuration, we don't why Atlassian missed this simple concept, i would like to see this configuration in JIRA.

              Unassigned Unassigned
              takindele Taiwo Akindele (Inactive)
              Votes:
              43 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated: