Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6599

Jira Service Desk not saving Holiday on the select date.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • High
    • 4.8.0
    • 4.4.0, 4.6.0, 4.4.1, 4.5.1, 4.5.2, 4.6.1
    • SLA
    • None

    Description

      Issue Summary

      When you set a new holiday on JSD and save the date Jira automatically modifies to a day before: E.g Set the holiday to Oct 20th, after saved, the date changes automatically to Oct 19th.

      Environment

      • Jira Software/Core - 8.4.0
      • Jira Service Desk - 4.4.1
      • Database: Postgres

      Steps to Reproduce

      1. Set the server to the NY time zone(america/New_York).
      2. Start Jira
      3. Set the profile of the admin for the Toronto Time zone. 
      4. Add a new holiday under the calendar on Project Settings.
      5. Click on save

      Expected Results

      That Jira will be able to save the selected date.

      Actual Results

      Jira saves the new holiday for a day before (E.g pick the day 25 of December, When you click on save Jira will save it to 24th of December)

      Notes

      I was able to replicate with the server on the following time zones (GMT -5, GMT -4, GMT -3). And the user profile on (GMT -5, GMT -4, GMT -3).

      Workaround

      We will have to follow the steps below in order to proceed with the workaround:

      • Go to the darkfeature page: <Jira_URL>/secure/SiteDarkFeatures!default.jspa
      • Add the following feature:
        sd.workinghours.new.page.disabled
        
      • Try to add a new holiday again.

      Attachments

        Issue Links

          Activity

            People

              ashubovych moofoo (Inactive)
              slenz@atlassian.com Susane Lenz (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync