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 <lars.fran...@gmail.com> 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: <https://spark-project.atlassian.net/rest/api/2/issue/SPARK-378> > New: <https://issues.apache.org/jira/rest/api/2/issue/SPARK-378> > > 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&startIndex=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 >
