XMLWordPrintable

Details

    Description

      CB: Guys, let's implement this if its needed for logical consistency. If not, it becomes more of a nice-to-have than a must-have and I would not prioritize it. Even if it's "not a big deal" from a dev perspective, the testing is significant and it's not clear to me how much user value this has, on it's own.

      Purpose: To implement the ability to set a time zone at the tenant level. We plan to later also allow the option to have FOLIO use local (browser) timezone for dates. These would be the two tenant-level options. But we need to get at least one of these options in place asap, or we will have inconsistencies between dates set by users (e.g. at check in or in the calendar) and dates displayed by the system.

      User story:
      As a user of FOLIO
      I want the times and dates displayed in FOLIO to be displayed in my institution's main time zone
      So that all times and dates use the same time zone

      Scenarios:

      1. Scenario
        • Given Settings > Organization > Language and localization
        • When displayed
        • Then a new field should display below the Locale field
          • Label: Time zone (time zone used when showing date time information)
          • Type: Timezone picker (like thisor any other standard picker should be fine)
          • Default: UTC
      2. Scenario
        • Given Settings > Organization > Language and localization
        • When displayed
        • Then the field currently labelled "Select locale for rendering dates, etc." should be renamed "Locale (for language display, date format etc.)"
      3. Scenario
        • Given Time zone = Time zone A
        • When system-generated dates and times are displayed
        • Then they should be captured and displayed in Time zone A. Specifically:
          • Check out:
            • Due date
            • Time
          • User details:
            • Record last updated
            • Record created
            • Proxy: Relationship created (displays for both prox. and spons.)
            • Loans (Open):
              • Due date
              • Loan date
            • Loans (Closed):
              • Due date
              • Loan date
              • Return date
            • Loan details:
              • Due date
              • Loan date
              • Return date
              • Action date in Loan Actions table (test loan actions for renewal, request created and check in) Renewals: Request created: Checkin:
          • Check in
            • Date loaned
            • Time returned
              • Processed As
              • Actual
          • Inventory
            • Record last updated
            • Record created
          • Requests
            • Request list:
              • Request date
            • Request details:
          • Settings
            • Settings > Users > Patron groups "Last updated"
      4. Scenario
        • Given a user entered date or time (e.g. User expiration date, Hold shelf expiration date, Process as date in Check in etc.)
        • When displayed
        • Then date should be displayed exactly as entered
      5. Scenario
        • Given the general record metadata component used in many records to display the date created and date last updated
        • When dates are displayed
        • Then they should always reflect the selected time zone
      6. Scenario
        • Given the general controlled vocab CRUD component being created to support CRUD of things like patron groups and material types
        • When the Last updated data is displayed
        • Then it should always be displayed in the tenant time zone

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                adityamatukumalli Aditya matukumalli
                cboerema Cate Boerema
                Theodor Tolstoy Theodor Tolstoy
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 3 hours
                    3h

                    TestRail: Runs

                      TestRail: Cases