<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:27:50 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[UIREC-211] Adding tenant&apos;s timezone in UI</title>
                <link>https://folio-org.atlassian.net/browse/UIREC-211</link>
                <project id="10020" key="UIREC">ui-receiving</project>
                    <description>&lt;p&gt;Items information in Receiving is displayed with UTC +00:00 time, whilst tenant&apos;s timezone is set to UTC+12 (Pacific/Auckland):&#160;&lt;/p&gt;

&lt;p&gt;&quot;Where it says 17/01/2022 &#160;it should say 18/01/2022 and where it says 19/01/2022 it should say 20/01/2022: &lt;a href=&quot;https://massey.folio.ebsco.com/receiving/93302663-8a0b-44fd-9a91-6f9c42a24916/view?pieces.receivingStatus=Received&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://massey.folio.ebsco.com/receiving/93302663-8a0b-44fd-9a91-6f9c42a24916/view?pieces.receivingStatus=Received&lt;/a&gt;&quot;&lt;br/&gt;
&#160;&lt;br/&gt;
&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;/rest/api/3/attachment/content/24249&quot; height=&quot;342&quot; width=&quot;361&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;Please, add the possibility to display info using tenant&apos;s timezone&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Expected Results:&lt;/b&gt;&#160;the dates (e.g. Receive date) are displayed correctly (e.g. with UTC+12 for tenants in New Zealand)&lt;/p&gt;</description>
                <environment></environment>
        <key id="33687">UIREC-211</key>
            <summary>Adding tenant&apos;s timezone in UI</summary>
                <type id="10001" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium">Bug</type>
                            <parent id="10790">UXPROD-1146</parent>
                                    <priority id="10001" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p2.svg">P2</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="557058:2f7b6349-450b-419a-ba54-c181f51383ad">Dennis Bridges</assignee>
                                                                <reporter accountid="712020:f3088ade-db74-499a-8e6f-5c8d4eb6f5bf">Hleb Surnovich</reporter>
                                    <labels>
                            <label>Known-issue-kiwi</label>
                            <label>front-end</label>
                            <label>known-issue-juniper</label>
                            <label>support</label>
                    </labels>
                <created>Wed, 26 Jan 2022 10:09:59 +0000</created>
                <updated>Mon, 27 Jun 2022 08:32:55 +0000</updated>
                            <resolved>Thu, 10 Feb 2022 23:13:12 +0000</resolved>
                                                    <fixVersion>2.1.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                <comments>
                                                            <comment id="74508" author="5af5e627525ba96b58654f12" created="Wed, 26 Jan 2022 11:28:36 +0000"  >&lt;p&gt;moved from FOLIO project to UIREC&lt;/p&gt;</comment>
                                                            <comment id="74509" author="615afd1cd9820f0070a09ef0" created="Wed, 26 Jan 2022 13:10:48 +0000"  >&lt;p&gt;The problem is in stripes-acq-components&apos; &lt;a href=&quot;https://github.com/folio-org/stripes-acq-components/blob/8ce3df0d1f52876494fd94ab5f5dbcee030e96c2/lib/utils/formatDate.js&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;&lt;tt&gt;formatDate&lt;/tt&gt; function&lt;/a&gt; where &lt;tt&gt;timeZone&lt;/tt&gt; is made an explicit argument instead of using &lt;a href=&quot;https://github.com/folio-org/stripes-core/blob/f6a4e078f8ec05a4a99e7bb4ba7244680c9af291/src/components/Root/Root.js#L162&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;the tenant&apos;s value configured by stripes-core&lt;/a&gt;. IOW, I think UISACQCOMP is the right place for this, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5e627525ba96b58654f12&quot; class=&quot;user-hover&quot; rel=&quot;5af5e627525ba96b58654f12&quot; data-account-id=&quot;5af5e627525ba96b58654f12&quot; accountid=&quot;5af5e627525ba96b58654f12&quot; rel=&quot;noreferrer&quot;&gt;Ann-Marie Breaux&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;If there is a need to format a time-independent date value (e.g. a birthdate or a holiday that should always be on a specific date regardless of the time) use &lt;a href=&quot;https://github.com/folio-org/stripes-components/tree/69c0ed2eb3c368a35198b605ce445907eafe7bd5/lib/FormattedUTCDate&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FormattedUTCDate&lt;/a&gt;.&#160;&lt;/p&gt;</comment>
                                                            <comment id="74510" author="5d6eeadef989e00d8c7e897b" created="Wed, 26 Jan 2022 14:15:46 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt;&#160;this is impacting Massey.&#160;&lt;/p&gt;</comment>
                                                            <comment id="74511" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Wed, 26 Jan 2022 18:46:58 +0000"  >&lt;p&gt;Note: Date is stored correctly so no data is being corrupted here. It is a matter over covering the stored date to the appropriate timezone&lt;/p&gt;</comment>
                                                            <comment id="74512" author="557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67" created="Thu, 27 Jan 2022 06:55:01 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5e627525ba96b58654f12&quot; class=&quot;user-hover&quot; rel=&quot;5af5e627525ba96b58654f12&quot; data-account-id=&quot;5af5e627525ba96b58654f12&quot; accountid=&quot;5af5e627525ba96b58654f12&quot; rel=&quot;noreferrer&quot;&gt;Ann-Marie Breaux&lt;/a&gt;&#160;I found original bug &lt;a href=&quot;https://folio-org.atlassian.net/browse/UISACQCOMP-23&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UISACQCOMP-23&lt;/a&gt;, why we show dates in UTC, by fixing&#160;
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIREC-211&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIREC-211&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Adding tenant&amp;#39;s timezone in UI&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            UIREC-211
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 we revert&#160;UISACQCOMP-23&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt;&#160;I think it will be interesting for you as well as datepicker uses UTC&#160;&lt;/p&gt;</comment>
                                                            <comment id="74513" author="615afd1cd9820f0070a09ef0" created="Thu, 27 Jan 2022 12:47:29 +0000"  >&lt;p&gt;Thanks for encouraging me to re-read 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UISACQCOMP-23&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UISACQCOMP-23&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Check the date picker in orders and invoices&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            UISACQCOMP-23
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; class=&quot;user-hover&quot; rel=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; data-account-id=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; accountid=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; rel=&quot;noreferrer&quot;&gt;Mikita Siadykh&lt;/a&gt;. I had looked at the PR but not read the Jira carefully. My understanding is that the desire here is to store and display a &quot;received date&quot; in much the same way as a birthdate or holiday would be displayed, i.e. it is a date rather than a moment in time. The backend doesn&apos;t provide a way to handle this kind of data so our usual approach is to provide a date-time value like &lt;tt&gt;2022-01-27T10:58:19+00:00&lt;/tt&gt; (the &lt;tt&gt;+00:00&lt;/tt&gt; indicating UTC) and then to use &lt;a href=&quot;https://github.com/folio-org/stripes-components/tree/69c0ed2eb3c368a35198b605ce445907eafe7bd5/lib/FormattedUTCDate&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FormattedUTCDate&lt;/a&gt; to display it. FormattedUTCDate does nothing other than provide &lt;tt&gt;UTC&lt;/tt&gt; as the timezone when formatting a date-time value, which should have the effect of displaying a consistent date, e.g. given a value like &lt;tt&gt;2022-01-27T23:45:67+00:00&lt;/tt&gt; it will display &lt;tt&gt;2022-01-27&lt;/tt&gt;, even if the local timezone is UTC+12, whereas a regular react-intl FormattedDate would display &lt;tt&gt;2022-01-28&lt;/tt&gt;. &lt;/p&gt;

&lt;p&gt;This is a long way of saying: it sounds to me like the real problem described in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UISACQCOMP-23&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UISACQCOMP-23&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Check the date picker in orders and invoices&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            UISACQCOMP-23
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, is that &lt;a href=&quot;https://github.com/folio-org/stripes-components/tree/104e6837d7019c995372fab49816be9be27979f0/lib/Datepicker&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;DatePicker&lt;/a&gt; was flawed, acting as a &quot;moment in time picker&quot; rather than a date picker. Maybe the real problem behind it was 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STCOM-822&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STCOM-822&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Custom Coverage Date entered is not honored &quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            STCOM-822
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
. Both were patched on the same day (&lt;a href=&quot;https://github.com/folio-org/stripes-components/pull/1533&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Datepicker&lt;/a&gt;, &lt;a href=&quot;https://github.com/folio-org/stripes-acq-components/pull/474&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;formatDate&lt;/a&gt;). It feels like those PRs where ships passing in the night, unaware. &lt;/p&gt;</comment>
                                                            <comment id="74514" author="615afd1cd9820f0070a09ef0" created="Thu, 27 Jan 2022 17:39:35 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; class=&quot;user-hover&quot; rel=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; data-account-id=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; accountid=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; rel=&quot;noreferrer&quot;&gt;Mikita Siadykh&lt;/a&gt;, after talking with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt;, I think I finally have a full picture of what&apos;s happening here. The &quot;Expected receipt date&quot; and &quot;Received date&quot; fields in the attached screenshots &lt;em&gt;appear&lt;/em&gt; to handle the same kind of data, but in fact, they&apos;re different: &quot;Expected receipt date&quot; is derived from a Datepicker entry (i.e. like a birthday, it should always be the same value no matter the timezone, and therefore must be displayed with the timezone set to UTC for the value to be correct; both &lt;tt&gt;&amp;lt;FormattedUTCDate&amp;gt;&lt;/tt&gt; and &lt;tt&gt;formatDate&lt;/tt&gt; handle this scenario), whereas &quot;Received date&quot; is derived from a timestamp (and thus needs to include the local timezone during display). &lt;/p&gt;

&lt;p&gt;Thus, I think the right fix is to leave &lt;tt&gt;formatDate&lt;/tt&gt; alone and change the handling for &quot;Received date&quot; to use &lt;tt&gt;&amp;lt;FormattedDate&amp;gt;&lt;/tt&gt;. &lt;/p&gt;</comment>
                                                            <comment id="74515" author="557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67" created="Fri, 28 Jan 2022 06:29:51 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt;&#160;thank you for diving into this issue&lt;/p&gt;


&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt;&#160;seems we need to review our modules to find places where we need to show dates in UTC or applying timezone&lt;/p&gt;</comment>
                                                            <comment id="74516" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Fri, 28 Jan 2022 19:18:36 +0000"  >&lt;p&gt;This is still little confusing for me so I want to layout two different examples one with Date picker and one without.&lt;/p&gt;

&lt;p&gt;Using Massey as the example library - Local date/time is 12pm NZDT Jan 28, 2022 and current offset is&#160;UTC/GMT +13 hours&lt;/p&gt;

&lt;p&gt;Scenario 1: Expected receipt date (date picker)&lt;/p&gt;

&lt;p&gt;User opens date picker and indicates expected receipt date is 12pm Jan 31, 2022 (NZDT)&lt;br/&gt;
 FOLIO captures this as&#160;23:00:00 Sunday January 30, 2022 (UTC)&lt;br/&gt;
 User look at piece in MCL and expected receipt date reads&#160;Jan 31, 2022&lt;/p&gt;

&lt;p&gt;Scenario 2: Expected receipt date (No date picker)&lt;/p&gt;

&lt;p&gt;User is receiving a piece and clicks the &quot;Quick receive&quot; button at 11pm Jan 31, 2022 (NZDT)&lt;br/&gt;
 FOLIO captures this as&#160;22:00:00 Sunday January 30, 2022 (UTC)&lt;br/&gt;
 User looks at piece in MCL and receipt date reads&#160;Jan 31, 2022&lt;/p&gt;

&lt;p&gt;To me it seems like there&apos;s no real difference here for the user. They wan to see the exact date. I cannot think of a situation in Acquisitions apps where we would want the following to happen&lt;/p&gt;

&lt;p&gt;Scenario 1: Store specific date and time and show to all users without conversion&lt;/p&gt;

&lt;p&gt;User opens date picker and indicates expected receipt date of 12pm Jan 31, 2022 (NZDT)&lt;br/&gt;
 FOLIO captures this as&#160;&lt;b&gt;23:00:00 Sunday January 30, 2022 (UTC)&lt;/b&gt;&lt;br/&gt;
 Different user in Canada logs in with timezone MDT&lt;br/&gt;
 looks at piece in MCL and expected receipt date reads 12pm Jan 31, 2022 (NZDT)&lt;/p&gt;

&lt;p&gt;For date ordered, created date, export date etc.. it always makes sense that we store the exact time in UTC and then convert for the user. Which means when we capture a time it should always be converted to UTC for storage. If the user says 3pm &quot;My time&quot; we convert that and store it. That way it can be converted for any other user that needs to see it.&lt;/p&gt;

&lt;p&gt;By this same logic there is NO reason to display a date in UTC as all users will be operating in a Location time zone.&lt;/p&gt;

&lt;p&gt;Perhaps in the task app there would be a need to allow someone to input Jan 31 as a general date. Meaning this task needs to be done on Jan 31 NZDT or MDT does not matter just has to be done by end of week. This seems very specific and none of the dates we are dealing with in acq apps would be expected to perform this way.&lt;/p&gt;

&lt;p&gt;I see that this may be difficult to facilitate if we only have a date. So I guess I&apos;m saying even when we only display a date we should be capturing the data as a date/time.&lt;/p&gt;

&lt;p&gt;I hope that makes sense.&lt;/p&gt;</comment>
                                                            <comment id="74517" author="615afd1cd9820f0070a09ef0" created="Mon, 31 Jan 2022 13:46:02 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt;, almost, but not quite. The crux of the problem is that we&apos;re using the same format (an ISO-8601 timestamp formatted like YYYY-MM-DDTHH:MM:SS.sss+00:00) to store two different kinds of data:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;datestamps that represent things like &quot;Expected receipt date&quot;. Typically, we zero-out the time and store values like &lt;tt&gt;2022-01-30T00:00:00.000+00:00&lt;/tt&gt; but this is just a convention and it doesn&apos;t happen consistently.&lt;/li&gt;
	&lt;li&gt;timestamps that represent things like &quot;The exact moment in time a user clicked the &quot;Quick receive&quot; button.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;IOW, we can&apos;t tell by looking at a value like &lt;tt&gt;2022-01-30T22:44:55.391+00:00&lt;/tt&gt; whether it represents a date or a date-time. We have to know what the intent was when the value was stored. If we know that value is supposed to represent a date, then we&apos;ll provide &lt;tt&gt;+00:00&lt;/tt&gt; (UTC) as the offset when formatting it for display because the question we&apos;re answering is &quot;Ignoring the time-portion of this value, how do we express the date-portion?&quot; e.g. 2022-01-30, or 1/30/2022 in the US or 30/01/2022 in NZ. If we know that value is supposed to represent a moment in time, however, then we will provide the local timezone to calculate the date based on that timezone&apos;s offset, because the question we&apos;re answering is &quot;What was the date in the given timezone at the moment in time recorded by this value?&quot; Somebody in MT would have experienced at click on 2022-01-30, but somebody in NZDT would have experienced it on 2022-01-31.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Scenario 1: Expected receipt date (date picker)&lt;br/&gt;
 User opens date picker and indicates expected receipt date is 12pm Jan 31, 2022 (NZDT)&lt;br/&gt;
 FOLIO captures this as 23:00:00 Sunday January 30, 2022 (UTC)&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Not quite. Since &lt;tt&gt;&amp;lt;Datepicker&amp;gt;&lt;/tt&gt; only captures a date, it&apos;s like #1 above and can&apos;t be used to express a value like &quot;12 pm Jan 31, 2022&quot;; it can only indicate &quot;Jan 31, 2022&quot;. The stored value here will be &lt;tt&gt;2022-01-31T00:00:00+00.00&lt;/tt&gt;, and to make sure the date value stays fixed, we provide the same offset on display as we provided on storage (&lt;tt&gt;+00:00&lt;/tt&gt;.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Scenario 2: Expected receipt date (No date picker)&lt;br/&gt;
 User is receiving a piece and clicks the &quot;Quick receive&quot; button at 11pm Jan 31, 2022 (NZDT)&lt;br/&gt;
 FOLIO captures this as 22:00:00 Sunday January 30, 2022 (UTC)&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Not quite. Clicking &quot;Quick receive&quot; captures the moment in time when the button was clicked, i.e. a timestamp representing &quot;now&quot;. We choose to store that value in UTC. 11 pm on January 31 in UTC+13 (NZDT) corresponds to 9 a.m on January 31, so the captured value stored in the backend would be &lt;tt&gt;2022-01-31T10:00:00+00:00&lt;/tt&gt;. Because this value represents a fixed moment in time (i.e. the moment the user clicked the button), we provide the local timezone when displaying it. In this case, the date won&apos;t shift because 10 + 13 &amp;lt; 24, so the date doesn&apos;t roll over. Similarly, if a piece were &quot;Quick received&quot; at 11 a.m. NZDT on January 31, the captured value would be &lt;tt&gt;2022-01-30T22:00:00+00:00&lt;/tt&gt;. Again, providing the local timezone on display, this would appear as 2022-01-31 given any timezone &amp;gt;= 2 hours ahead of UTC, and 2022-01-30 given any timezone &amp;lt; 2 hours ahead of UTC.&lt;/p&gt;

&lt;p&gt;Dealing with time is sooooooo confusing. There are &lt;a href=&quot;https://yourcalendricalfallacyis.com/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;many&lt;/a&gt;, &lt;a href=&quot;https://zachholman.com/talk/utc-is-enough-for-everyone-right&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;many&lt;/a&gt;, &lt;a href=&quot;https://queue.acm.org/detail.cfm?id=2745385&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;many&lt;/a&gt; websites dedicated to this (provided as evidence of how challenging this is, not as expected reading material &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; ).&lt;/p&gt;</comment>
                                                            <comment id="74518" author="557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67" created="Thu, 3 Feb 2022 12:20:18 +0000"  >&lt;p&gt;hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt; &lt;br/&gt;
 places I found where we display dates, please review them to define right scenario&lt;/p&gt;

&lt;p&gt;Orders:&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;PO Renewal date&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; PO Review date&lt;/font&gt;&lt;br/&gt;
 PO updatedDate&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;POL activationDueDate&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; POL expectedActivation&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; POL subscriptionFrom&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; POL subscriptionTo&lt;/font&gt;&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;POL receiptDue&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; POL expectedReceiptDate&lt;/font&gt;&lt;br/&gt;
 POL receiptDate&lt;br/&gt;
 POL updatedDate&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;invoiceDate&lt;/font&gt;&lt;/p&gt;

&lt;p&gt;DB: These are all specific moments in time and should be entered as timezone specific (Users should see them in System timezone)&lt;/p&gt;

&lt;p&gt;Receiving:&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;piece receiptDate&lt;/font&gt;&lt;br/&gt;
 piece receivedDate&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;POL expectedReceiptDate&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; POL subscriptionFrom&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; POL subscriptionTo&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; POL expectedReceiptDate&lt;/font&gt;&lt;/p&gt;

&lt;p&gt;Organizations:&lt;br/&gt;
 Integ config schedulingDate&lt;/p&gt;

&lt;p&gt;DB: This is definitely a specific moment in time as it is associated with a time in the ui (Users should see them in System timezone)&lt;/p&gt;

&lt;p&gt;Finance:&lt;br/&gt;
 budget fiscalStart&lt;br/&gt;
 budget fiscalEnd&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;FY periodStart&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; FY periodEnd&lt;/font&gt;&lt;/p&gt;

&lt;p&gt;DB: These are all specific moments in time and should be timezone specific. There is logic that defines start as 12am of that day and defines end as 11:59pm of the specified day (Users should see them in System timezone)&lt;/p&gt;

&lt;p&gt;Invoice:&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;invoiceDate&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; paymentDue&lt;/font&gt;&lt;br/&gt;
 approvalDate&lt;br/&gt;
 paymentDate&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;subscriptionStart&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#de350b&quot;&gt; subscriptionEnd&lt;/font&gt;&lt;br/&gt;
 voucherDate&lt;br/&gt;
 &lt;font color=&quot;#de350b&quot;&gt;disbursementDate&lt;/font&gt;&lt;/p&gt;

&lt;p&gt;DB: These are actually all specific moments in time and should be entered as timezone specific (Users should see them in System timezone)&lt;/p&gt;</comment>
                                                            <comment id="74519" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Thu, 3 Feb 2022 18:49:26 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; class=&quot;user-hover&quot; rel=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; data-account-id=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; accountid=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; rel=&quot;noreferrer&quot;&gt;Mikita Siadykh&lt;/a&gt;&#160;I added comments into your comment but ultimately all of these dates should be treated like specific moments in time. If the user enters the date or performs the required action they are referring to a specific date or date and time.&lt;/p&gt;

&lt;p&gt;With date picker it does make sense to just display the date the same in any timezone (I highlighted all date pickers in Red) Because conversion is not possible and it would very rarely be a problem. However, Fiscal year state and end are unique because we do apply logic when loading fiscal year that assumes the start and end times. Unless these are actually stored as date/time? I don&apos;t know how it was implemented.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                                                            <comment id="74520" author="557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67" created="Fri, 4 Feb 2022 08:31:08 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;thank you, as for&#160;Fiscal year dates, they are stored in UTC, but tenant timezone is applied in some cases, so it&apos;s better to review and discuss it separately&lt;/p&gt;</comment>
                                                            <comment id="74521" author="557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67" created="Wed, 9 Feb 2022 05:02:22 +0000"  >&lt;p&gt;hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae2abe74b-7529-4518-8893-0d4570f0f1a2&quot; class=&quot;user-hover&quot; rel=&quot;557058:e2abe74b-7529-4518-8893-0d4570f0f1a2&quot; data-account-id=&quot;557058:e2abe74b-7529-4518-8893-0d4570f0f1a2&quot; accountid=&quot;557058:e2abe74b-7529-4518-8893-0d4570f0f1a2&quot; rel=&quot;noreferrer&quot;&gt;Kyrylo Brener&lt;/a&gt;&#160;changes are available on snapshot env, please review&lt;/p&gt;</comment>
                                                            <comment id="74522" author="557058:e2abe74b-7529-4518-8893-0d4570f0f1a2" created="Thu, 10 Feb 2022 16:41:01 +0000"  >&lt;p&gt;Re-assigned to Dennis&lt;/p&gt;</comment>
                                                            <comment id="74523" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Thu, 10 Feb 2022 23:12:59 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; class=&quot;user-hover&quot; rel=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; data-account-id=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; accountid=&quot;557058:7fb61edd-2bf6-4f3a-9e98-eb9b7444cf67&quot; rel=&quot;noreferrer&quot;&gt;Mikita Siadykh&lt;/a&gt;&#160;I believe I tested this correctly. I set the timezone to Massey time and did some receiving. The date seems to appear as the correct time for massey were it shows as the previous day when I perform that same tasks in bugfest-kiwi.&lt;/p&gt;</comment>
                                                            <comment id="74524" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Thu, 10 Feb 2022 23:13:12 +0000"  >&lt;p&gt;test successful in folio-snapshot&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10001">
                    <name>Cloners</name>
                                                                <inwardlinks description="is cloned by">
                                        <issuelink>
            <issuekey id="30771">UINV-351</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="25514">UIOR-910</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="73608">UISACQCOMP-78</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                            <outwardlinks description="defines">
                                        <issuelink>
            <issuekey id="12095">UXPROD-3221</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="73638">UISACQCOMP-23</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="24249" name="Screenshot 2022-01-25 at 19.15.30.png" size="88355" author="712020:f3088ade-db74-499a-8e6f-5c8d4eb6f5bf" created="Wed, 26 Jan 2022 10:07:50 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                        <customfield id="customfield_10107" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Affected Institution</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10388"><![CDATA[!!!ALL!!!]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10185"><![CDATA[Thunderjet]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10014" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue key="$xmlutils.escape($text)">Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10045" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Potential Workaround</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>The dates are stored in UTC in the database and the issue is that they are also being displayed in UTC. Depending on your timezone this may mean that the day is actually ahead or behind your current time and expectation. </customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10106" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>RCA Group</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10374"><![CDATA[Incomplete/missing requirements]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzx49i:dv8zc9g3ewanqzyy0cfpyxnzg2r</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10046" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Release</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10052"><![CDATA[Lotus R1 2022]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="520">ACQ Sprint 133</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10044" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10108" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Tester Assignee</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>557058:2f7b6349-450b-419a-ba54-c181f51383ad</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 26 Jan 2022 11:28:36 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>