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

Time tracking global settings allow adding unreasonable values for Working hours per day and Working days per week which leads to break the application

XMLWordPrintable

      Issue Summary

      Time tracking global settings allow adding unreasonable values for Working hours per day and Working days per week which leads to break the application.

      Steps to Reproduce

      1. Go to Cog icon > Issues > Time tracking
      2. Click on “Edit global settings” and add the value 9999999 on Working hours per day and Working days per week.
      3. Save the changes.

      Expected Results

      It shows an error message informing that the value must be between 1 - 7 for days and 1 - 24 for hours.

      Actual Results

      The changes are saved and the configurations won’t load anymore. Tickets will show error messages and the time tracking tab won’t show anything.

      Workaround

      Reach out to support to fix the issue.

            [JRACLOUD-76527] Time tracking global settings allow adding unreasonable values for Working hours per day and Working days per week which leads to break the application

            Matthew Hunter added a comment -
            Atlassian Update - April 29, 2022

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - April 29, 2022 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              adaluz Angélica Luz
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: