Re: JIRA: Wrong dates from imported JIRAs

[Lars Francke]

Okay thanks guys, that's two -1s and that's fair enough. I'll leave it at
that.

On Thu, Dec 17, 2015 at 1:39 AM, Josh Rosen 
wrote:

> Personally, I'd rather avoid the risk of breaking things during the
> reimport. In my experience we've had a lot of unforeseen problems with JIRA
> import/export and the benefit here doesn't seem huge (this issue only
> impacts people that are searching for the oldest JIRAs across all projects,
> which I think is pretty uncommon). Just my two cents.
>
> - Josh
>
> On Wed, Dec 16, 2015 at 8:45 AM, Lars Francke 
> wrote:
>
>> Any other opinions on this?
>>
>> On Fri, Dec 11, 2015 at 9:54 AM, Lars Francke 
>> wrote:
>>
>>> That's a good point. I assume there's always a small risk but it's at
>>> least the documented way from Atlassian to change the creation date so I'd
>>> hope it should be okay. I'd build the minimal CSV file.
>>>
>>> I agree that probably not a lot of people are going to search across
>>> projects but on the other hand it's a one-time fix and who knows how long
>>> the Apache Jira is going to live :)
>>>
>>> On Fri, Dec 11, 2015 at 9:05 AM, Reynold Xin 
>>> wrote:
>>>
 Thanks for looking at this. Is it worth fixing? Is there a risk
 (although small) that the re-import would break other things?

 Most of those are done and I don't know how often people search JIRAs
 by date across projects.

 On Fri, Dec 11, 2015 at 3:40 PM, Lars Francke 
 wrote:

> Hi,
>
> I've been digging into JIRA a bit and found a couple of old issues
> (~250) and I just assume that they are all from the old JIRA.
>
> Here's one example:
>
> Old: 
> New: 
>
> created": "0012-08-21T09:03:00.000-0800",
>
> That's quite impressive but wrong :)
>
> That means when you sort all Apache JIRAs by creation date Spark comes
> first: <
> https://issues.apache.org/jira/issues/?jql=order%20By%20createdDate%20ASC=250
> >
>
> The dates were already wrong in the source JIRA.
>
> Now it seems as if those can be fixed using a CSV import. I still
> remember how painful the initial import was but this looks relatively
> straight forward <
> https://confluence.atlassian.com/display/JIRAKB/How+to+change+the+issue+creation+date+using+CSV+import
> >
>
> If everyone's okay with it I'd raise it with INFRA (and would prepare
> the necessary CSV file) but as I'm not a committer it'd be great if
> one/some of the committers could give me a +1
>
> Cheers,
> Lars
>


>>>
>>
>

Re: JIRA: Wrong dates from imported JIRAs

[Josh Rosen]

Personally, I'd rather avoid the risk of breaking things during the
reimport. In my experience we've had a lot of unforeseen problems with JIRA
import/export and the benefit here doesn't seem huge (this issue only
impacts people that are searching for the oldest JIRAs across all projects,
which I think is pretty uncommon). Just my two cents.

- Josh

On Wed, Dec 16, 2015 at 8:45 AM, Lars Francke 
wrote:

> Any other opinions on this?
>
> On Fri, Dec 11, 2015 at 9:54 AM, Lars Francke 
> wrote:
>
>> That's a good point. I assume there's always a small risk but it's at
>> least the documented way from Atlassian to change the creation date so I'd
>> hope it should be okay. I'd build the minimal CSV file.
>>
>> I agree that probably not a lot of people are going to search across
>> projects but on the other hand it's a one-time fix and who knows how long
>> the Apache Jira is going to live :)
>>
>> On Fri, Dec 11, 2015 at 9:05 AM, Reynold Xin  wrote:
>>
>>> Thanks for looking at this. Is it worth fixing? Is there a risk
>>> (although small) that the re-import would break other things?
>>>
>>> Most of those are done and I don't know how often people search JIRAs by
>>> date across projects.
>>>
>>> On Fri, Dec 11, 2015 at 3:40 PM, Lars Francke 
>>> wrote:
>>>
 Hi,

 I've been digging into JIRA a bit and found a couple of old issues
 (~250) and I just assume that they are all from the old JIRA.

 Here's one example:

 Old: 
 New: 

 created": "0012-08-21T09:03:00.000-0800",

 That's quite impressive but wrong :)

 That means when you sort all Apache JIRAs by creation date Spark comes
 first: <
 https://issues.apache.org/jira/issues/?jql=order%20By%20createdDate%20ASC=250
 >

 The dates were already wrong in the source JIRA.

 Now it seems as if those can be fixed using a CSV import. I still
 remember how painful the initial import was but this looks relatively
 straight forward <
 https://confluence.atlassian.com/display/JIRAKB/How+to+change+the+issue+creation+date+using+CSV+import
 >

 If everyone's okay with it I'd raise it with INFRA (and would prepare
 the necessary CSV file) but as I'm not a committer it'd be great if
 one/some of the committers could give me a +1

 Cheers,
 Lars

>>>
>>>
>>
>

Re: JIRA: Wrong dates from imported JIRAs

[Lars Francke]

Any other opinions on this?

On Fri, Dec 11, 2015 at 9:54 AM, Lars Francke 
wrote:

> That's a good point. I assume there's always a small risk but it's at
> least the documented way from Atlassian to change the creation date so I'd
> hope it should be okay. I'd build the minimal CSV file.
>
> I agree that probably not a lot of people are going to search across
> projects but on the other hand it's a one-time fix and who knows how long
> the Apache Jira is going to live :)
>
> On Fri, Dec 11, 2015 at 9:05 AM, Reynold Xin  wrote:
>
>> Thanks for looking at this. Is it worth fixing? Is there a risk (although
>> small) that the re-import would break other things?
>>
>> Most of those are done and I don't know how often people search JIRAs by
>> date across projects.
>>
>> On Fri, Dec 11, 2015 at 3:40 PM, Lars Francke 
>> wrote:
>>
>>> Hi,
>>>
>>> I've been digging into JIRA a bit and found a couple of old issues
>>> (~250) and I just assume that they are all from the old JIRA.
>>>
>>> Here's one example:
>>>
>>> Old: 
>>> New: 
>>>
>>> created": "0012-08-21T09:03:00.000-0800",
>>>
>>> That's quite impressive but wrong :)
>>>
>>> That means when you sort all Apache JIRAs by creation date Spark comes
>>> first: <
>>> https://issues.apache.org/jira/issues/?jql=order%20By%20createdDate%20ASC=250
>>> >
>>>
>>> The dates were already wrong in the source JIRA.
>>>
>>> Now it seems as if those can be fixed using a CSV import. I still
>>> remember how painful the initial import was but this looks relatively
>>> straight forward <
>>> https://confluence.atlassian.com/display/JIRAKB/How+to+change+the+issue+creation+date+using+CSV+import
>>> >
>>>
>>> If everyone's okay with it I'd raise it with INFRA (and would prepare
>>> the necessary CSV file) but as I'm not a committer it'd be great if
>>> one/some of the committers could give me a +1
>>>
>>> Cheers,
>>> Lars
>>>
>>
>>
>

Re: JIRA: Wrong dates from imported JIRAs

[Lars Francke]

That's a good point. I assume there's always a small risk but it's at least
the documented way from Atlassian to change the creation date so I'd hope
it should be okay. I'd build the minimal CSV file.

I agree that probably not a lot of people are going to search across
projects but on the other hand it's a one-time fix and who knows how long
the Apache Jira is going to live :)

On Fri, Dec 11, 2015 at 9:05 AM, Reynold Xin  wrote:

> Thanks for looking at this. Is it worth fixing? Is there a risk (although
> small) that the re-import would break other things?
>
> Most of those are done and I don't know how often people search JIRAs by
> date across projects.
>
> On Fri, Dec 11, 2015 at 3:40 PM, Lars Francke 
> wrote:
>
>> Hi,
>>
>> I've been digging into JIRA a bit and found a couple of old issues (~250)
>> and I just assume that they are all from the old JIRA.
>>
>> Here's one example:
>>
>> Old: 
>> New: 
>>
>> created": "0012-08-21T09:03:00.000-0800",
>>
>> That's quite impressive but wrong :)
>>
>> That means when you sort all Apache JIRAs by creation date Spark comes
>> first: <
>> https://issues.apache.org/jira/issues/?jql=order%20By%20createdDate%20ASC=250
>> >
>>
>> The dates were already wrong in the source JIRA.
>>
>> Now it seems as if those can be fixed using a CSV import. I still
>> remember how painful the initial import was but this looks relatively
>> straight forward <
>> https://confluence.atlassian.com/display/JIRAKB/How+to+change+the+issue+creation+date+using+CSV+import
>> >
>>
>> If everyone's okay with it I'd raise it with INFRA (and would prepare the
>> necessary CSV file) but as I'm not a committer it'd be great if one/some of
>> the committers could give me a +1
>>
>> Cheers,
>> Lars
>>
>
>

Re: JIRA: Wrong dates from imported JIRAs

[Reynold Xin]

Thanks for looking at this. Is it worth fixing? Is there a risk (although
small) that the re-import would break other things?

Most of those are done and I don't know how often people search JIRAs by
date across projects.

On Fri, Dec 11, 2015 at 3:40 PM, Lars Francke 
wrote:

> Hi,
>
> I've been digging into JIRA a bit and found a couple of old issues (~250)
> and I just assume that they are all from the old JIRA.
>
> Here's one example:
>
> Old: 
> New: 
>
> created": "0012-08-21T09:03:00.000-0800",
>
> That's quite impressive but wrong :)
>
> That means when you sort all Apache JIRAs by creation date Spark comes
> first: <
> https://issues.apache.org/jira/issues/?jql=order%20By%20createdDate%20ASC=250
> >
>
> The dates were already wrong in the source JIRA.
>
> Now it seems as if those can be fixed using a CSV import. I still remember
> how painful the initial import was but this looks relatively straight
> forward <
> https://confluence.atlassian.com/display/JIRAKB/How+to+change+the+issue+creation+date+using+CSV+import
> >
>
> If everyone's okay with it I'd raise it with INFRA (and would prepare the
> necessary CSV file) but as I'm not a committer it'd be great if one/some of
> the committers could give me a +1
>
> Cheers,
> Lars
>

JIRA: Wrong dates from imported JIRAs

[Lars Francke]

Hi,

I've been digging into JIRA a bit and found a couple of old issues (~250)
and I just assume that they are all from the old JIRA.

Here's one example:

Old: 
New: 

created": "0012-08-21T09:03:00.000-0800",

That's quite impressive but wrong :)

That means when you sort all Apache JIRAs by creation date Spark comes
first: <
https://issues.apache.org/jira/issues/?jql=order%20By%20createdDate%20ASC=250
>

The dates were already wrong in the source JIRA.

Now it seems as if those can be fixed using a CSV import. I still remember
how painful the initial import was but this looks relatively straight
forward <
https://confluence.atlassian.com/display/JIRAKB/How+to+change+the+issue+creation+date+using+CSV+import
>

If everyone's okay with it I'd raise it with INFRA (and would prepare the
necessary CSV file) but as I'm not a committer it'd be great if one/some of
the committers could give me a +1

Cheers,
Lars