You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Christopher <ct...@apache.org> on 2016/09/06 22:38:54 UTC
reporter.apache.org off-by-one
Why does reporter use 1 day earlier than JIRA when I use the "Fetch
releases from JIRA" feature?
Re: reporter.apache.org off-by-one
Posted by Christopher <ct...@apache.org>.
On Wed, Sep 7, 2016 at 7:21 PM sebb <se...@gmail.com> wrote:
> On 7 September 2016 at 22:44, Christopher <ct...@apache.org> wrote:
> > Also noticed that it says "It's not possible to amend release details",
> but
> > that's not true. If you give a different day for the same version, it
> > overwrites.
>
> I think amend is being used in the sense of edit.
> Editing a file is not the same as overwriting it.
>
>
This could be an example of poor wording. From the user perspective, the
entry is clearly amended. Further, it explicitly says that one should
"delete the incorrect entry (as above) and add the correct one", and that
is clearly not the case, so I'm guessing the behavior was improved at some
point, but this instruction was not updated to reflect the new behavior.
Re: reporter.apache.org off-by-one
Posted by sebb <se...@gmail.com>.
On 7 September 2016 at 22:44, Christopher <ct...@apache.org> wrote:
> Also noticed that it says "It's not possible to amend release details", but
> that's not true. If you give a different day for the same version, it
> overwrites.
I think amend is being used in the sense of edit.
Editing a file is not the same as overwriting it.
> On Tue, Sep 6, 2016 at 6:38 PM Christopher <ct...@apache.org> wrote:
>
>> Why does reporter use 1 day earlier than JIRA when I use the "Fetch
>> releases from JIRA" feature?
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: reporter.apache.org off-by-one
Posted by Christopher <ct...@apache.org>.
Also noticed that it says "It's not possible to amend release details", but
that's not true. If you give a different day for the same version, it
overwrites.
On Tue, Sep 6, 2016 at 6:38 PM Christopher <ct...@apache.org> wrote:
> Why does reporter use 1 day earlier than JIRA when I use the "Fetch
> releases from JIRA" feature?
>
>
Re: reporter.apache.org off-by-one
Posted by Christopher <ct...@apache.org>.
On Thu, Sep 8, 2016 at 4:54 PM sebb <se...@gmail.com> wrote:
> On 8 September 2016 at 17:18, sebb <se...@gmail.com> wrote:
> > On 8 September 2016 at 01:59, Christopher <ct...@apache.org> wrote:
> >> On Wed, Sep 7, 2016 at 8:51 PM Lefty Leverenz <le...@gmail.com>
> >> wrote:
> >>
> >>> Is this a timezone problem?
>
> Yes.
>
> >>>
> >>>
> >> Possibly. I tried changing my JIRA timezone to UTC+0, just in case, but
> it
> >> had no effect. I don't think JIRA stores the timezone with these dates,
> so
> >> it might be assumed to be midnight when reporter translates it to
> whatever
> >> it considers local time. If the local time reporter is translating it
> to is
> >> east of UTC+0, then that would make sense. It should probably parse the
> >> JIRA dates as UTC+0, and then display them as UTC+0, since there's no
> way
> >> for it to know the intended time zone from JIRA if JIRA isn't storing
> that
> >> (even if it does store it, the UI doesn't allow you to specify, so it's
> >> going to default to midnight).
> >>
> >
> > JIRA stores the dates as YYYY-MM-DD; no time at all. Or at least that
> > is the data that reporter.a.o sees.
> >
> > This is converted to seconds since the epoch, and assumes local time.
> > I think the TZ is UTC on reporter.a.o.
> >
> > The epoch time must be converted back again for display.
> > I suspect this is where the issue lies (given that r.a.o uses UTC)
> >
> > I see the following Accumulo dates:
> >
> > - 1.8.0: Tue Sep 06 2016
> > - 1.7.2: Wed Jun 22 2016
> > - 1.7.1: Fri Feb 26 2016
> >
> > which agree (for me) with the JIRA dates.
>
> However if I change my local timezone to EDT I see dates one day earlier.
>
> > I assume you are seeing one day earlier for each of those?
> > What is your local timezone?
> >
> > In which case it's just a case of finding where the epoch time is
> > converted for display and ensuring that UTC is used.
> >
>
> The dates are displayed using Javascript Date.toDateString() which
> uses the local timezone.
> I can fix that.
>
>
Awesome. That makes sense, because neither JIRA nor reporter handle time
input in the UI, so it makes sense to just display the date without the
timezone conversion in the browser. Thanks!
Re: reporter.apache.org off-by-one
Posted by Christopher <ct...@apache.org>.
Confirmed fixed on my end (after clearing browser cache). Thanks!
On Thu, Sep 8, 2016 at 5:02 PM sebb <se...@gmail.com> wrote:
> On 8 September 2016 at 21:54, sebb <se...@gmail.com> wrote:
> > On 8 September 2016 at 17:18, sebb <se...@gmail.com> wrote:
> >> On 8 September 2016 at 01:59, Christopher <ct...@apache.org> wrote:
> >>> On Wed, Sep 7, 2016 at 8:51 PM Lefty Leverenz <leftyleverenz@gmail.com
> >
> >>> wrote:
> >>>
> >>>> Is this a timezone problem?
> >
> > Yes.
> >
> >>>>
> >>>>
> >>> Possibly. I tried changing my JIRA timezone to UTC+0, just in case,
> but it
> >>> had no effect. I don't think JIRA stores the timezone with these
> dates, so
> >>> it might be assumed to be midnight when reporter translates it to
> whatever
> >>> it considers local time. If the local time reporter is translating it
> to is
> >>> east of UTC+0, then that would make sense. It should probably parse the
> >>> JIRA dates as UTC+0, and then display them as UTC+0, since there's no
> way
> >>> for it to know the intended time zone from JIRA if JIRA isn't storing
> that
> >>> (even if it does store it, the UI doesn't allow you to specify, so it's
> >>> going to default to midnight).
> >>>
> >>
> >> JIRA stores the dates as YYYY-MM-DD; no time at all. Or at least that
> >> is the data that reporter.a.o sees.
> >>
> >> This is converted to seconds since the epoch, and assumes local time.
> >> I think the TZ is UTC on reporter.a.o.
> >>
> >> The epoch time must be converted back again for display.
> >> I suspect this is where the issue lies (given that r.a.o uses UTC)
> >>
> >> I see the following Accumulo dates:
> >>
> >> - 1.8.0: Tue Sep 06 2016
> >> - 1.7.2: Wed Jun 22 2016
> >> - 1.7.1: Fri Feb 26 2016
> >>
> >> which agree (for me) with the JIRA dates.
> >
> > However if I change my local timezone to EDT I see dates one day earlier.
> >
> >> I assume you are seeing one day earlier for each of those?
> >> What is your local timezone?
> >>
> >> In which case it's just a case of finding where the epoch time is
> >> converted for display and ensuring that UTC is used.
> >>
> >
> > The dates are displayed using Javascript Date.toDateString() which
> > uses the local timezone.
> > I can fix that.
>
> Should be OK now.
>
> >>>
> >>>> -- Lefty
> >>>>
> >>>> On Wed, Sep 7, 2016 at 8:48 PM, Christopher <ct...@apache.org>
> wrote:
> >>>>
> >>>> > On Wed, Sep 7, 2016 at 7:19 PM sebb <se...@gmail.com> wrote:
> >>>> >
> >>>> > > On 6 September 2016 at 23:38, Christopher <ct...@apache.org>
> wrote:
> >>>> > > > Why does reporter use 1 day earlier than JIRA when I use the
> "Fetch
> >>>> > > > releases from JIRA" feature?
> >>>> > >
> >>>> > > What exactly do you mean by that?
> >>>> > >
> >>>> >
> >>>> > What I mean is that when I put the release date in JIRA as
> 06/Sep/2016,
> >>>> and
> >>>> > then use the sync feature in reporter.apache.org, the one in
> reporter
> >>>> > shows
> >>>> > Mon Sep 05 2016, which is one day earlier than what is stored in
> JIRA. It
> >>>> > does this for all the releases.
> >>>> >
> >>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: reporter.apache.org off-by-one
Posted by sebb <se...@gmail.com>.
On 8 September 2016 at 21:54, sebb <se...@gmail.com> wrote:
> On 8 September 2016 at 17:18, sebb <se...@gmail.com> wrote:
>> On 8 September 2016 at 01:59, Christopher <ct...@apache.org> wrote:
>>> On Wed, Sep 7, 2016 at 8:51 PM Lefty Leverenz <le...@gmail.com>
>>> wrote:
>>>
>>>> Is this a timezone problem?
>
> Yes.
>
>>>>
>>>>
>>> Possibly. I tried changing my JIRA timezone to UTC+0, just in case, but it
>>> had no effect. I don't think JIRA stores the timezone with these dates, so
>>> it might be assumed to be midnight when reporter translates it to whatever
>>> it considers local time. If the local time reporter is translating it to is
>>> east of UTC+0, then that would make sense. It should probably parse the
>>> JIRA dates as UTC+0, and then display them as UTC+0, since there's no way
>>> for it to know the intended time zone from JIRA if JIRA isn't storing that
>>> (even if it does store it, the UI doesn't allow you to specify, so it's
>>> going to default to midnight).
>>>
>>
>> JIRA stores the dates as YYYY-MM-DD; no time at all. Or at least that
>> is the data that reporter.a.o sees.
>>
>> This is converted to seconds since the epoch, and assumes local time.
>> I think the TZ is UTC on reporter.a.o.
>>
>> The epoch time must be converted back again for display.
>> I suspect this is where the issue lies (given that r.a.o uses UTC)
>>
>> I see the following Accumulo dates:
>>
>> - 1.8.0: Tue Sep 06 2016
>> - 1.7.2: Wed Jun 22 2016
>> - 1.7.1: Fri Feb 26 2016
>>
>> which agree (for me) with the JIRA dates.
>
> However if I change my local timezone to EDT I see dates one day earlier.
>
>> I assume you are seeing one day earlier for each of those?
>> What is your local timezone?
>>
>> In which case it's just a case of finding where the epoch time is
>> converted for display and ensuring that UTC is used.
>>
>
> The dates are displayed using Javascript Date.toDateString() which
> uses the local timezone.
> I can fix that.
Should be OK now.
>>>
>>>> -- Lefty
>>>>
>>>> On Wed, Sep 7, 2016 at 8:48 PM, Christopher <ct...@apache.org> wrote:
>>>>
>>>> > On Wed, Sep 7, 2016 at 7:19 PM sebb <se...@gmail.com> wrote:
>>>> >
>>>> > > On 6 September 2016 at 23:38, Christopher <ct...@apache.org> wrote:
>>>> > > > Why does reporter use 1 day earlier than JIRA when I use the "Fetch
>>>> > > > releases from JIRA" feature?
>>>> > >
>>>> > > What exactly do you mean by that?
>>>> > >
>>>> >
>>>> > What I mean is that when I put the release date in JIRA as 06/Sep/2016,
>>>> and
>>>> > then use the sync feature in reporter.apache.org, the one in reporter
>>>> > shows
>>>> > Mon Sep 05 2016, which is one day earlier than what is stored in JIRA. It
>>>> > does this for all the releases.
>>>> >
>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: reporter.apache.org off-by-one
Posted by sebb <se...@gmail.com>.
On 8 September 2016 at 17:18, sebb <se...@gmail.com> wrote:
> On 8 September 2016 at 01:59, Christopher <ct...@apache.org> wrote:
>> On Wed, Sep 7, 2016 at 8:51 PM Lefty Leverenz <le...@gmail.com>
>> wrote:
>>
>>> Is this a timezone problem?
Yes.
>>>
>>>
>> Possibly. I tried changing my JIRA timezone to UTC+0, just in case, but it
>> had no effect. I don't think JIRA stores the timezone with these dates, so
>> it might be assumed to be midnight when reporter translates it to whatever
>> it considers local time. If the local time reporter is translating it to is
>> east of UTC+0, then that would make sense. It should probably parse the
>> JIRA dates as UTC+0, and then display them as UTC+0, since there's no way
>> for it to know the intended time zone from JIRA if JIRA isn't storing that
>> (even if it does store it, the UI doesn't allow you to specify, so it's
>> going to default to midnight).
>>
>
> JIRA stores the dates as YYYY-MM-DD; no time at all. Or at least that
> is the data that reporter.a.o sees.
>
> This is converted to seconds since the epoch, and assumes local time.
> I think the TZ is UTC on reporter.a.o.
>
> The epoch time must be converted back again for display.
> I suspect this is where the issue lies (given that r.a.o uses UTC)
>
> I see the following Accumulo dates:
>
> - 1.8.0: Tue Sep 06 2016
> - 1.7.2: Wed Jun 22 2016
> - 1.7.1: Fri Feb 26 2016
>
> which agree (for me) with the JIRA dates.
However if I change my local timezone to EDT I see dates one day earlier.
> I assume you are seeing one day earlier for each of those?
> What is your local timezone?
>
> In which case it's just a case of finding where the epoch time is
> converted for display and ensuring that UTC is used.
>
The dates are displayed using Javascript Date.toDateString() which
uses the local timezone.
I can fix that.
>>
>>> -- Lefty
>>>
>>> On Wed, Sep 7, 2016 at 8:48 PM, Christopher <ct...@apache.org> wrote:
>>>
>>> > On Wed, Sep 7, 2016 at 7:19 PM sebb <se...@gmail.com> wrote:
>>> >
>>> > > On 6 September 2016 at 23:38, Christopher <ct...@apache.org> wrote:
>>> > > > Why does reporter use 1 day earlier than JIRA when I use the "Fetch
>>> > > > releases from JIRA" feature?
>>> > >
>>> > > What exactly do you mean by that?
>>> > >
>>> >
>>> > What I mean is that when I put the release date in JIRA as 06/Sep/2016,
>>> and
>>> > then use the sync feature in reporter.apache.org, the one in reporter
>>> > shows
>>> > Mon Sep 05 2016, which is one day earlier than what is stored in JIRA. It
>>> > does this for all the releases.
>>> >
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: reporter.apache.org off-by-one
Posted by sebb <se...@gmail.com>.
On 8 September 2016 at 01:59, Christopher <ct...@apache.org> wrote:
> On Wed, Sep 7, 2016 at 8:51 PM Lefty Leverenz <le...@gmail.com>
> wrote:
>
>> Is this a timezone problem?
>>
>>
> Possibly. I tried changing my JIRA timezone to UTC+0, just in case, but it
> had no effect. I don't think JIRA stores the timezone with these dates, so
> it might be assumed to be midnight when reporter translates it to whatever
> it considers local time. If the local time reporter is translating it to is
> east of UTC+0, then that would make sense. It should probably parse the
> JIRA dates as UTC+0, and then display them as UTC+0, since there's no way
> for it to know the intended time zone from JIRA if JIRA isn't storing that
> (even if it does store it, the UI doesn't allow you to specify, so it's
> going to default to midnight).
>
JIRA stores the dates as YYYY-MM-DD; no time at all. Or at least that
is the data that reporter.a.o sees.
This is converted to seconds since the epoch, and assumes local time.
I think the TZ is UTC on reporter.a.o.
The epoch time must be converted back again for display.
I suspect this is where the issue lies (given that r.a.o uses UTC)
I see the following Accumulo dates:
- 1.8.0: Tue Sep 06 2016
- 1.7.2: Wed Jun 22 2016
- 1.7.1: Fri Feb 26 2016
which agree (for me) with the JIRA dates.
I assume you are seeing one day earlier for each of those?
What is your local timezone?
In which case it's just a case of finding where the epoch time is
converted for display and ensuring that UTC is used.
>
>> -- Lefty
>>
>> On Wed, Sep 7, 2016 at 8:48 PM, Christopher <ct...@apache.org> wrote:
>>
>> > On Wed, Sep 7, 2016 at 7:19 PM sebb <se...@gmail.com> wrote:
>> >
>> > > On 6 September 2016 at 23:38, Christopher <ct...@apache.org> wrote:
>> > > > Why does reporter use 1 day earlier than JIRA when I use the "Fetch
>> > > > releases from JIRA" feature?
>> > >
>> > > What exactly do you mean by that?
>> > >
>> >
>> > What I mean is that when I put the release date in JIRA as 06/Sep/2016,
>> and
>> > then use the sync feature in reporter.apache.org, the one in reporter
>> > shows
>> > Mon Sep 05 2016, which is one day earlier than what is stored in JIRA. It
>> > does this for all the releases.
>> >
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: reporter.apache.org off-by-one
Posted by Christopher <ct...@apache.org>.
On Wed, Sep 7, 2016 at 8:51 PM Lefty Leverenz <le...@gmail.com>
wrote:
> Is this a timezone problem?
>
>
Possibly. I tried changing my JIRA timezone to UTC+0, just in case, but it
had no effect. I don't think JIRA stores the timezone with these dates, so
it might be assumed to be midnight when reporter translates it to whatever
it considers local time. If the local time reporter is translating it to is
east of UTC+0, then that would make sense. It should probably parse the
JIRA dates as UTC+0, and then display them as UTC+0, since there's no way
for it to know the intended time zone from JIRA if JIRA isn't storing that
(even if it does store it, the UI doesn't allow you to specify, so it's
going to default to midnight).
> -- Lefty
>
> On Wed, Sep 7, 2016 at 8:48 PM, Christopher <ct...@apache.org> wrote:
>
> > On Wed, Sep 7, 2016 at 7:19 PM sebb <se...@gmail.com> wrote:
> >
> > > On 6 September 2016 at 23:38, Christopher <ct...@apache.org> wrote:
> > > > Why does reporter use 1 day earlier than JIRA when I use the "Fetch
> > > > releases from JIRA" feature?
> > >
> > > What exactly do you mean by that?
> > >
> >
> > What I mean is that when I put the release date in JIRA as 06/Sep/2016,
> and
> > then use the sync feature in reporter.apache.org, the one in reporter
> > shows
> > Mon Sep 05 2016, which is one day earlier than what is stored in JIRA. It
> > does this for all the releases.
> >
>
Re: reporter.apache.org off-by-one
Posted by Lefty Leverenz <le...@gmail.com>.
Is this a timezone problem?
-- Lefty
On Wed, Sep 7, 2016 at 8:48 PM, Christopher <ct...@apache.org> wrote:
> On Wed, Sep 7, 2016 at 7:19 PM sebb <se...@gmail.com> wrote:
>
> > On 6 September 2016 at 23:38, Christopher <ct...@apache.org> wrote:
> > > Why does reporter use 1 day earlier than JIRA when I use the "Fetch
> > > releases from JIRA" feature?
> >
> > What exactly do you mean by that?
> >
>
> What I mean is that when I put the release date in JIRA as 06/Sep/2016, and
> then use the sync feature in reporter.apache.org, the one in reporter
> shows
> Mon Sep 05 2016, which is one day earlier than what is stored in JIRA. It
> does this for all the releases.
>
Re: reporter.apache.org off-by-one
Posted by Christopher <ct...@apache.org>.
On Wed, Sep 7, 2016 at 7:19 PM sebb <se...@gmail.com> wrote:
> On 6 September 2016 at 23:38, Christopher <ct...@apache.org> wrote:
> > Why does reporter use 1 day earlier than JIRA when I use the "Fetch
> > releases from JIRA" feature?
>
> What exactly do you mean by that?
>
What I mean is that when I put the release date in JIRA as 06/Sep/2016, and
then use the sync feature in reporter.apache.org, the one in reporter shows
Mon Sep 05 2016, which is one day earlier than what is stored in JIRA. It
does this for all the releases.
Re: reporter.apache.org off-by-one
Posted by sebb <se...@gmail.com>.
On 6 September 2016 at 23:38, Christopher <ct...@apache.org> wrote:
> Why does reporter use 1 day earlier than JIRA when I use the "Fetch
> releases from JIRA" feature?
What exactly do you mean by that?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org