Details

    • Type: New JIRA Project New JIRA Project
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: None
    • Component/s: JIRA
    • Labels:
      None

      Issue Links

        Activity

        Hide
        Matei Zaharia added a comment -
        One question on this -- we'd like to start the JIRA by importing issues from our old JIRA instance, https://spark-project.atlassian.net. How do you guys recommend doing that?
        Show
        Matei Zaharia added a comment - One question on this -- we'd like to start the JIRA by importing issues from our old JIRA instance, https://spark-project.atlassian.net . How do you guys recommend doing that?
        Hide
        Henry Saputra added a comment -
        Hi Chris, could you add my username as initial developers for the Spark JIRA? Thanks.
        Show
        Henry Saputra added a comment - Hi Chris, could you add my username as initial developers for the Spark JIRA? Thanks.
        Hide
        Chris A. Mattmann added a comment -
        Hey Henry, np, what's your JIRA username? Also, ping to INFRA -- guys any chance you'll have a sec to work on this soon?
        Show
        Chris A. Mattmann added a comment - Hey Henry, np, what's your JIRA username? Also, ping to INFRA -- guys any chance you'll have a sec to work on this soon?
        Hide
        Chris A. Mattmann added a comment -
        OK Henry I added you to the request.
        Show
        Chris A. Mattmann added a comment - OK Henry I added you to the request.
        Hide
        Henry Saputra added a comment -
        Ah sorry Chris, it's hsaputra
        Show
        Henry Saputra added a comment - Ah sorry Chris, it's hsaputra
        Hide
        Suresh Marru added a comment -
        Henry, Unless you have multiple JIRA accounts it auto-completes by your name, so your username should automatically get picked up.
        Show
        Suresh Marru added a comment - Henry, Unless you have multiple JIRA accounts it auto-completes by your name, so your username should automatically get picked up.
        Hide
        Andy Konwinski added a comment -
        Hi infra, Just wondering if there is any time estimate for when the Spark podling might get a JIRA set up? Thanks for all your hard work!
        Show
        Andy Konwinski added a comment - Hi infra, Just wondering if there is any time estimate for when the Spark podling might get a JIRA set up? Thanks for all your hard work!
        Hide
        Daniel Gruno added a comment -
        project created as per specs. Please let me know if it works out for you guys.
        As per the import of the old JIRA instance, I will consult with Tony, as he has some experience in the matter (and thus, I can't say yes/no to the question at the moment)
        Show
        Daniel Gruno added a comment - project created as per specs. Please let me know if it works out for you guys. As per the import of the old JIRA instance, I will consult with Tony, as he has some experience in the matter (and thus, I can't say yes/no to the question at the moment)
        Hide
        Gavin added a comment -
        Don't start creating issues if you still intend to import your old one.!
        Show
        Gavin added a comment - Don't start creating issues if you still intend to import your old one.!
        Hide
        Suresh Marru added a comment -
        @Daniel, @Gavin: will INFRA have to do the import or the podling? I am assuming project admin may not have enough karma to do the import. Thanks for setting the jira up. --Suresh
        Show
        Suresh Marru added a comment - @Daniel, @Gavin: will INFRA have to do the import or the podling? I am assuming project admin may not have enough karma to do the import. Thanks for setting the jira up. --Suresh
        Hide
        #asfinfra IRC Bot added a comment -
        <Humbedooh> Infra will do the import. We will need access to an export of your old JIRA project.
        Show
        #asfinfra IRC Bot added a comment - <Humbedooh> Infra will do the import. We will need access to an export of your old JIRA project.
        Hide
        #asfinfra IRC Bot added a comment -
        <pctony> Guys, we need more info about the import. We need to be very careful about this, as we have been caught out in the past with these. Does thr KEY name match in both, if so we have an issue already. Also, the export you give us needs to match our exact version of JIRA for the import to be successful.
        Show
        #asfinfra IRC Bot added a comment - <pctony> Guys, we need more info about the import. We need to be very careful about this, as we have been caught out in the past with these. Does thr KEY name match in both, if so we have an issue already. Also, the export you give us needs to match our exact version of JIRA for the import to be successful.
        Hide
        #asfinfra IRC Bot added a comment -
        <pctony> I see the KEY names do match. Please do NOT CREATE any issues in the new instance until we have run the import. Otherwise it will fail.
        Show
        #asfinfra IRC Bot added a comment - <pctony> I see the KEY names do match. Please do NOT CREATE any issues in the new instance until we have run the import. Otherwise it will fail.
        Hide
        #asfinfra IRC Bot added a comment -
        <pctony> Also, please do not configure the project as we will likely need to delete it to import it. Can you let me know when you have the export, *AND* the attachments. We can then liaise as to where you should put them.
        Show
        #asfinfra IRC Bot added a comment - <pctony> Also, please do not configure the project as we will likely need to delete it to import it. Can you let me know when you have the export, *AND* the attachments. We can then liaise as to where you should put them.
        Hide
        Andy Konwinski added a comment -
        I'll help with this (I help set up the Atlassian hosted JIRA for Spark originally). We won't configure or import anything till the import into our new JIRA is complete. Do the versions need to match up exactly? If so that is a problem because Atlassian is hosting v6.1-OD-04-1 vs Apache's v5.2.8#851-sha1:3262fdc
        Show
        Andy Konwinski added a comment - I'll help with this (I help set up the Atlassian hosted JIRA for Spark originally). We won't configure or import anything till the import into our new JIRA is complete. Do the versions need to match up exactly? If so that is a problem because Atlassian is hosting v6.1-OD-04-1 vs Apache's v5.2.8#851-sha1:3262fdc
        Hide
        Andy Konwinski added a comment -
        I just used "Backup Manager" to export our JIRA (with "Backup attachments" box checked). The zip file is 28.5MB. Let me know where to put it for you.
        Show
        Andy Konwinski added a comment - I just used "Backup Manager" to export our JIRA (with "Backup attachments" box checked). The zip file is 28.5MB. Let me know where to put it for you.
        Hide
        #asfinfra IRC Bot added a comment -
        <pctony> Andy, im fairly confident that will just fail due to version mismatch. Unless the export from the hosted version is extra special somehow, but I doubt it. Do you want to put it in your ~ on people.a.o - and then email infra@ with the path, and the an md5/sha sum of the files.
        Show
        #asfinfra IRC Bot added a comment - <pctony> Andy, im fairly confident that will just fail due to version mismatch. Unless the export from the hosted version is extra special somehow, but I doubt it. Do you want to put it in your ~ on people.a.o - and then email infra@ with the path, and the an md5/sha sum of the files.
        Hide
        Andy Konwinski added a comment -
        Sounds good. I just put it in my home directory on people.a.o. It's a file called JIRA-backup-20130730.zip

        If importing that doesn't work as you suspect, then perhaps I can get it into a CSV format? Manually entering everything and losing history sounds really painful :(
        Show
        Andy Konwinski added a comment - Sounds good. I just put it in my home directory on people.a.o. It's a file called JIRA-backup-20130730.zip If importing that doesn't work as you suspect, then perhaps I can get it into a CSV format? Manually entering everything and losing history sounds really painful :(
        Hide
        Andy Konwinski added a comment -
        BTW, I'm /home/andrew
        Show
        Andy Konwinski added a comment - BTW, I'm /home/andrew
        Hide
        #asfinfra IRC Bot added a comment -
        <pctony> Andrew thanks, I'll take a look as soon as I can.
        Show
        #asfinfra IRC Bot added a comment - <pctony> Andrew thanks, I'll take a look as soon as I can.
        Hide
        Matei Zaharia added a comment -
        I'm curious, did you guys ever get the chance to try this out? We'll probably have to make a new zip because there's been activity on our JIRA but it would be good to know whether this works.
        Show
        Matei Zaharia added a comment - I'm curious, did you guys ever get the chance to try this out? We'll probably have to make a new zip because there's been activity on our JIRA but it would be good to know whether this works.
        Hide
        #asfinfra IRC Bot added a comment -
        <Humbedooh> We had some trouble with the test import, please hang on while we fix that :) and yes, another export sounds like a plan, I'll let you know when we are ready to go, so we can get as fresh a copy as possible
        Show
        #asfinfra IRC Bot added a comment - <Humbedooh> We had some trouble with the test import, please hang on while we fix that :) and yes, another export sounds like a plan, I'll let you know when we are ready to go, so we can get as fresh a copy as possible
        Hide
        Matei Zaharia added a comment -
        Cool, thanks!
        Show
        Matei Zaharia added a comment - Cool, thanks!
        Hide
        Matei Zaharia added a comment -
        Just wondering, any news on this? Do you need us to export in a different format?
        Show
        Matei Zaharia added a comment - Just wondering, any news on this? Do you need us to export in a different format?
        Hide
        Matei Zaharia added a comment -
        Here's a new backup of our JIRA by the way. We only need the SPARK project in there: http://cs.berkeley.edu/~matei/JIRA-backup-20130831.tgz
        Show
        Matei Zaharia added a comment - Here's a new backup of our JIRA by the way. We only need the SPARK project in there: http://cs.berkeley.edu/~matei/JIRA-backup-20130831.tgz
        Hide
        Michael Joyce added a comment -
        Hi Infra,

        Last we heard on this Jake Farrell said he would look into the problem on the test server. Have you guys had any luck?

        Cheers for all the hard work!
        Show
        Michael Joyce added a comment - Hi Infra, Last we heard on this Jake Farrell said he would look into the problem on the test server. Have you guys had any luck? Cheers for all the hard work!
        Hide
        Matei Zaharia added a comment -
        Any update on this? Is there anything we can do to help the process? Basically we'd like to know if it's feasible to import the old issues.. if not we may also start anew here, but it would be good to figure this out soon, since we've migrated most of our other infrastructure to Apache now.
        Show
        Matei Zaharia added a comment - Any update on this? Is there anything we can do to help the process? Basically we'd like to know if it's feasible to import the old issues.. if not we may also start anew here, but it would be good to figure this out soon, since we've migrated most of our other infrastructure to Apache now.
        Hide
        Daniel Gruno added a comment -
        I expect we'll have an update on this issue this week, so please stay tuned, and apologies for the long wait.
        Show
        Daniel Gruno added a comment - I expect we'll have an update on this issue this week, so please stay tuned, and apologies for the long wait.
        Hide
        Matei Zaharia added a comment -
        No worries, thanks for looking into it!
        Show
        Matei Zaharia added a comment - No worries, thanks for looking into it!
        Hide
        Daniel Gruno added a comment -
        An email snafooey caused us to update our JIRA instance to 6.1 before we had a chance to test the import on our test instance (it didn't work properly for those who tried to whack at it). We have a guy looking into getting it in shape now, but it will require you to update your current JIRA instance to 6.1 before doing another export for us. I'm truly sorry for this inconvenience, but JIRA is really strict about the versions being equal when doing an import. So, good news is we finally have a chance of testing the exports very soon, bad news is, it will require an update on your side to be able to transfer the spark JIRA data. I hope you can figure out how to upgrade, and if you have any questions or need help, feel free to reach out to us.
        Show
        Daniel Gruno added a comment - An email snafooey caused us to update our JIRA instance to 6.1 before we had a chance to test the import on our test instance (it didn't work properly for those who tried to whack at it). We have a guy looking into getting it in shape now, but it will require you to update your current JIRA instance to 6.1 before doing another export for us. I'm truly sorry for this inconvenience, but JIRA is really strict about the versions being equal when doing an import. So, good news is we finally have a chance of testing the exports very soon, bad news is, it will require an update on your side to be able to transfer the spark JIRA data. I hope you can figure out how to upgrade, and if you have any questions or need help, feel free to reach out to us.
        Hide
        Matei Zaharia added a comment -
        Alright, here's a new export of our JIRA: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131002.tgz. It's from JIRA 6.1 as well. Let me know if that works.

        Note that our JIRA contains four projects -- we only need the SPARK one. Also, the project name in the export is identical to the project name we want on Apache, in case you need to take special care of that.
        Show
        Matei Zaharia added a comment - Alright, here's a new export of our JIRA: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131002.tgz . It's from JIRA 6.1 as well. Let me know if that works. Note that our JIRA contains four projects -- we only need the SPARK one. Also, the project name in the export is identical to the project name we want on Apache, in case you need to take special care of that.
        Hide
        Matei Zaharia added a comment -
        Just wondering, have you guys had a chance to look at this? This is now the main thing blocking us from fully transitioning to Apache. It's unfortunate because we've even made a release via Apache, but we have to point people to the old JIRA. Let us know if you need any help with it. If an import is impossible, we could also start anew in the worst case.
        Show
        Matei Zaharia added a comment - Just wondering, have you guys had a chance to look at this? This is now the main thing blocking us from fully transitioning to Apache. It's unfortunate because we've even made a release via Apache, but we have to point people to the old JIRA. Let us know if you need any help with it. If an import is impossible, we could also start anew in the worst case.
        Hide
        Daniel Gruno added a comment -
        Hi Matei,
        I'll be testing the import tomorrow (now +12h) on our test instance, and if all goes well, I'll be prepared to import it into our main instance.
        If you've made any updates to your JIRAs, you might want to contribute with an updated export, so we can get everything imported, and if not, just sit back and relax, as things should hopefully progress a lot tomorrow. :)
        Show
        Daniel Gruno added a comment - Hi Matei, I'll be testing the import tomorrow (now +12h) on our test instance, and if all goes well, I'll be prepared to import it into our main instance. If you've made any updates to your JIRAs, you might want to contribute with an updated export, so we can get everything imported, and if not, just sit back and relax, as things should hopefully progress a lot tomorrow. :)
        Hide
        Chris A. Mattmann added a comment -
        Thank you very much Daniel!
        Show
        Chris A. Mattmann added a comment - Thank you very much Daniel!
        Hide
        Matei Zaharia added a comment -
        Awesome, thanks! Here's a new backup: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131008.zip
        Show
        Matei Zaharia added a comment - Awesome, thanks! Here's a new backup: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131008.zip
        Hide
        Daniel Gruno added a comment -
        I'll try to get in touch with the other admins, see if we can somehow beat JIRA into procuring a restore feature (which currently seems to be missing from my dashboard), hang on.
        Show
        Daniel Gruno added a comment - I'll try to get in touch with the other admins, see if we can somehow beat JIRA into procuring a restore feature (which currently seems to be missing from my dashboard), hang on.
        Hide
        Daniel Gruno added a comment -
        Matei, can you supply me with the backup as a ZIP file (like how JIRA itself exports the backup)? If so, I'll try importing that. It seems to be picky about importing the .tgz file or the uncompressed XML.
        Show
        Daniel Gruno added a comment - Matei, can you supply me with the backup as a ZIP file (like how JIRA itself exports the backup)? If so, I'll try importing that. It seems to be picky about importing the .tgz file or the uncompressed XML.
        Hide
        Matei Zaharia added a comment -
        I've attached a zip file above -- see my comment from October 8th. It is a backup for the whole JIRA though. I'll see if I can get just the Spark issues as a CSV.
        Show
        Matei Zaharia added a comment - I've attached a zip file above -- see my comment from October 8th. It is a backup for the whole JIRA though. I'll see if I can get just the Spark issues as a CSV.
        Hide
        Daniel Gruno added a comment -
        Sorry about that, I seem to have missed your comment with the attached file. I'll try it out. Shouldn't be any need for the CSV if this works :)
        Show
        Daniel Gruno added a comment - Sorry about that, I seem to have missed your comment with the attached file. I'll try it out. Shouldn't be any need for the CSV if this works :)
        Hide
        Daniel Gruno added a comment -
        I've tested the export in out test JIRA, and while it _is_ possible for us to import one single project, there are some things blocking this import - if you could fix/edit them on your end and create a new export with these fixes, that would ease the migration a lot. These errors are mostly standard errors due to your JIRA not following the JIRA defaults on issues:

        - Unable to import custom field '[CHART] Time in Status'. The custom field type does not support project imports. (I'm guessing we just don't have that plugin available)
        - There are '1' user(s) referenced that JIRA can not automatically create. (this is the user 'reynold' which doesn't seem to have an email or a name, if you could just set...something there, that'd be swell)
        - The Issue Link Type 'Blocks' is required for the import but does not exist in the current JIRA instance. (This is supposed to be called 'Blocker')
        - The Issue Link Type 'Relates' is required for the import but does not exist in the current JIRA instance. (This is supposed to be called 'Related')

        If all else fails, I can try to manually edit the XML and change the link types, but I don't think we have the chart thing it complains about. If it's not possible to remove the 'time in status' chart thingermajig, I'll have to talk to the other admins on whether or not we can add that to our instance.

        But we're getting somewhere now! :)
        Show
        Daniel Gruno added a comment - I've tested the export in out test JIRA, and while it _is_ possible for us to import one single project, there are some things blocking this import - if you could fix/edit them on your end and create a new export with these fixes, that would ease the migration a lot. These errors are mostly standard errors due to your JIRA not following the JIRA defaults on issues: - Unable to import custom field '[CHART] Time in Status'. The custom field type does not support project imports. (I'm guessing we just don't have that plugin available) - There are '1' user(s) referenced that JIRA can not automatically create. (this is the user 'reynold' which doesn't seem to have an email or a name, if you could just set...something there, that'd be swell) - The Issue Link Type 'Blocks' is required for the import but does not exist in the current JIRA instance. (This is supposed to be called 'Blocker') - The Issue Link Type 'Relates' is required for the import but does not exist in the current JIRA instance. (This is supposed to be called 'Related') If all else fails, I can try to manually edit the XML and change the link types, but I don't think we have the chart thing it complains about. If it's not possible to remove the 'time in status' chart thingermajig, I'll have to talk to the other admins on whether or not we can add that to our instance. But we're getting somewhere now! :)
        Hide
        Matei Zaharia added a comment -
        Cool, thanks! So to be clear, we should just edit our old JIRA to rename / remove these fields? I'll try that out.
        Show
        Matei Zaharia added a comment - Cool, thanks! So to be clear, we should just edit our old JIRA to rename / remove these fields? I'll try that out.
        Hide
        #asfinfra IRC Bot added a comment -
        <Humbedooh> yeah, there is a mismatch between what we call the fields (the default names) and what you have (re)named yours, so they will need to have the same name.
        Show
        #asfinfra IRC Bot added a comment - <Humbedooh> yeah, there is a mismatch between what we call the fields (the default names) and what you have (re)named yours, so they will need to have the same name.
        Hide
        Matei Zaharia added a comment -
        Alright, try this: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131010.zip . I think I've addressed all the issues above.

        Sorry for the delay in getting it -- apparently Atlassian's hosted JIRA service doesn't let you grab backups more often than 2 days (!).
        Show
        Matei Zaharia added a comment - Alright, try this: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131010.zip . I think I've addressed all the issues above. Sorry for the delay in getting it -- apparently Atlassian's hosted JIRA service doesn't let you grab backups more often than 2 days (!).
        Hide
        #asfinfra IRC Bot added a comment -
        <Humbedooh> The export is valid and passed our test instance with (almost) flying colors. I will be importing it into our main instance one of the following days :)
        Show
        #asfinfra IRC Bot added a comment - <Humbedooh> The export is valid and passed our test instance with (almost) flying colors. I will be importing it into our main instance one of the following days :)
        Hide
        Matei Zaharia added a comment -
        Cool, very exciting!
        Show
        Matei Zaharia added a comment - Cool, very exciting!
        Hide
        Henry Saputra added a comment -
        Nice!
        Show
        Henry Saputra added a comment - Nice!
        Hide
        Matei Zaharia added a comment - - edited
        Hey there, in case you haven't imported the old archive yet, here's a new backup: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131019.zip .

        Oops, edited to have right URL.
        Show
        Matei Zaharia added a comment - - edited Hey there, in case you haven't imported the old archive yet, here's a new backup: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131019.zip . Oops, edited to have right URL.
        Hide
        Daniel Gruno added a comment -
        Hi Matei,
        "As usual", we have a version mismatch which is preventing us from importing the project. This time it's the Greenhopper (Agile) plugin, which you need to update to 6.3.3 on your machine before we can continue the import. Also, for future reference, please supply us with the ZIP file created by the JIRA export feature, and not one you created on a Mac :) JIRA seems to be very sensitive about that.
        Show
        Daniel Gruno added a comment - Hi Matei, "As usual", we have a version mismatch which is preventing us from importing the project. This time it's the Greenhopper (Agile) plugin, which you need to update to 6.3.3 on your machine before we can continue the import. Also, for future reference, please supply us with the ZIP file created by the JIRA export feature, and not one you created on a Mac :) JIRA seems to be very sensitive about that.
        Hide
        Matei Zaharia added a comment -
        Daniel, would it be easier if I gave you an account on our old JIRA so you could do the exports? If so just go to https://spark-project.atlassian.net/browse/SPARK, sign up for an account, and tell me the name you used.

        Also, our JIRA instance is hosted by Atlassian so we have little control over the plugin versions. I'd be happy just dropping Greenhopper support. I'll look into updating it but no guarantees.
        Show
        Matei Zaharia added a comment - Daniel, would it be easier if I gave you an account on our old JIRA so you could do the exports? If so just go to https://spark-project.atlassian.net/browse/SPARK, sign up for an account, and tell me the name you used. Also, our JIRA instance is hosted by Atlassian so we have little control over the plugin versions. I'd be happy just dropping Greenhopper support. I'll look into updating it but no guarantees.
        Hide
        Matei Zaharia added a comment -
        Actually, our GreenHopper *is* at 6.3.3 apparently. Have you tried the zip I posted on 10/19? I can make a new one too but it's only a few days ago.
        Show
        Matei Zaharia added a comment - Actually, our GreenHopper *is* at 6.3.3 apparently. Have you tried the zip I posted on 10/19? I can make a new one too but it's only a few days ago.
        Hide
        Matei Zaharia added a comment -
        Any update on this? I'm also happy to post a new XML dump, but it's just unfortunate that after we create it, people post new issues/comments. Can we maybe pick a time to work together on getting this imported?
        Show
        Matei Zaharia added a comment - Any update on this? I'm also happy to post a new XML dump, but it's just unfortunate that after we create it, people post new issues/comments. Can we maybe pick a time to work together on getting this imported?
        Hide
        Chris A. Mattmann added a comment -
        Guys, can we get this wrapped up? I know the Spark community is looking to get this taken care of and they have been very patient. I appreciate your help.
        Show
        Chris A. Mattmann added a comment - Guys, can we get this wrapped up? I know the Spark community is looking to get this taken care of and they have been very patient. I appreciate your help.
        Hide
        Gavin added a comment -
        Just had a look at importing, using the last provided zip:

        The backup project 'Spark' requires custom field named 'Epic Colour' with full key 'com.pyxis.greenhopper.jira:gh-epic-color'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.
        The backup project 'Spark' requires custom field named 'Epic Link' with full key 'com.pyxis.greenhopper.jira:gh-epic-link'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.
        The backup project 'Spark' requires custom field named 'Epic Name [deprecated, this field is no longer being used]' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.
        The backup project 'Spark' requires custom field named 'Epic Name' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.
        The backup project 'Spark' requires custom field named 'Epic Status' with full key 'com.pyxis.greenhopper.jira:gh-epic-status'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.
        The backup project 'Spark' requires custom field named 'Rank' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.
        The backup project 'Spark' requires custom field named 'Release Version History' with full key 'com.pyxis.greenhopper.jira:greenhopper-releasedmultiversionhistory'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.
        The backup project 'Spark' requires custom field named 'Sprint' with full key 'com.pyxis.greenhopper.jira:gh-sprint'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.

        Show
        Gavin added a comment - Just had a look at importing, using the last provided zip: The backup project 'Spark' requires custom field named 'Epic Colour' with full key 'com.pyxis.greenhopper.jira:gh-epic-color'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'. The backup project 'Spark' requires custom field named 'Epic Link' with full key 'com.pyxis.greenhopper.jira:gh-epic-link'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'. The backup project 'Spark' requires custom field named 'Epic Name [deprecated, this field is no longer being used]' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'. The backup project 'Spark' requires custom field named 'Epic Name' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'. The backup project 'Spark' requires custom field named 'Epic Status' with full key 'com.pyxis.greenhopper.jira:gh-epic-status'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'. The backup project 'Spark' requires custom field named 'Rank' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'. The backup project 'Spark' requires custom field named 'Release Version History' with full key 'com.pyxis.greenhopper.jira:greenhopper-releasedmultiversionhistory'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'. The backup project 'Spark' requires custom field named 'Sprint' with full key 'com.pyxis.greenhopper.jira:gh-sprint'. In the current instance of JIRA the plugin is at version '6.3.4.3', but in the backup it is at version '6.3.2.2'.
        Hide
        Matei Zaharia added a comment -
        Hey Gavin,

        I've tried disabling GreenHopper and exporting without it. Please try this version: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131204.zip

        If there are more problems, I'm also happy to give you an admin account on our old JIRA.
        Show
        Matei Zaharia added a comment - Hey Gavin, I've tried disabling GreenHopper and exporting without it. Please try this version: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131204.zip If there are more problems, I'm also happy to give you an admin account on our old JIRA.
        Hide
        Gavin added a comment -
        vicious cycle going on here:

        This data appears to be from an older version of JIRA. Please upgrade the data and try again. The current version of JIRA is at build number '6144', but the supplied backup file was for build number '6206'.

        Yes please make me admin on your jira. username : ipv6guru
        Show
        Gavin added a comment - vicious cycle going on here: This data appears to be from an older version of JIRA. Please upgrade the data and try again. The current version of JIRA is at build number '6144', but the supplied backup file was for build number '6206'. Yes please make me admin on your jira. username : ipv6guru
        Hide
        Gavin added a comment -
        So the OnDemand Jira is now at JIRA v6.2-OD-03 and we are on 6.1 , making the import impossible again until we catch up
        Upgrading Jira is not on my radar, but I'll ask [~markt] if he has time to assist with that part.

        Or, perhaps open an Atlassian ticket describing whats happening and if they can provide a sane export for us.
        Show
        Gavin added a comment - So the OnDemand Jira is now at JIRA v6.2-OD-03 and we are on 6.1 , making the import impossible again until we catch up Upgrading Jira is not on my radar, but I'll ask [~markt] if he has time to assist with that part. Or, perhaps open an Atlassian ticket describing whats happening and if they can provide a sane export for us.
        Hide
        Matei Zaharia added a comment -
        Yeah, good idea. It's pretty ridiculous that they can't transfer data between minor versions like this.. maybe we can manually change the version in the export. In any case I've made you an admin on our old JIRA now, so you can try this later too. You can grab the backup by going to (gear button at top right) -> System -> Backup Manager.
        Show
        Matei Zaharia added a comment - Yeah, good idea. It's pretty ridiculous that they can't transfer data between minor versions like this.. maybe we can manually change the version in the export. In any case I've made you an admin on our old JIRA now, so you can try this later too. You can grab the backup by going to (gear button at top right) -> System -> Backup Manager.
        Hide
        Mark Thomas added a comment -
        The latest supported version we can install is 6.1.4.

        I'm guessing that 6.2-OD-03 is equivalent to 6.2-m03 from the early access program. Running a version from the early access program in production is not supported by Atlassian.

        There are two options here.

        1. Stick to supported versions which means this issue will be blocked until Jira OnDemand and the ASF Jira instance are on compatible versions. That may take a while.

        2. Run on an unsupported version. My main concern with this is rolling back if it doesn't work and the chance that a plug-in we depend on won't work.

        I'm more than happy to upgrade to 6.1.4 and I'll see if I can find time to do that today (not that that will help).

        I think this needs to be raised with Atlassian.
        Show
        Mark Thomas added a comment - The latest supported version we can install is 6.1.4. I'm guessing that 6.2-OD-03 is equivalent to 6.2-m03 from the early access program. Running a version from the early access program in production is not supported by Atlassian. There are two options here. 1. Stick to supported versions which means this issue will be blocked until Jira OnDemand and the ASF Jira instance are on compatible versions. That may take a while. 2. Run on an unsupported version. My main concern with this is rolling back if it doesn't work and the chance that a plug-in we depend on won't work. I'm more than happy to upgrade to 6.1.4 and I'll see if I can find time to do that today (not that that will help). I think this needs to be raised with Atlassian.
        Hide
        Matei Zaharia added a comment -
        Hey Mark,

        I was wondering if we can try manually editing the current export to say it's from 6.1.3 in case that works. Otherwise we'll definitely follow up with Atlassian. We are on their hosted JIRA offering so hopefully they can be responsive about this. I've also disabled GreenHopper on our JIRA so I don't think there are a ton of plugins left.
        Show
        Matei Zaharia added a comment - Hey Mark, I was wondering if we can try manually editing the current export to say it's from 6.1.3 in case that works. Otherwise we'll definitely follow up with Atlassian. We are on their hosted JIRA offering so hopefully they can be responsive about this. I've also disabled GreenHopper on our JIRA so I don't think there are a ton of plugins left.
        Hide
        Andy Konwinski added a comment - - edited
        I just created an issue with Atlassian to see if we can get some support from them.

        https://support.atlassian.com/browse/JST-84001
        Show
        Andy Konwinski added a comment - - edited I just created an issue with Atlassian to see if we can get some support from them. https://support.atlassian.com/browse/JST-84001
        Hide
        Andy Konwinski added a comment -
        Sorry, pasted wrong URL at first above. Edited my comment now. Correct url is https://support.atlassian.com/browse/JST-84001
        Show
        Andy Konwinski added a comment - Sorry, pasted wrong URL at first above. Edited my comment now. Correct url is https://support.atlassian.com/browse/JST-84001
        Hide
        Andy Konwinski added a comment -
        And since it looks like anonymous reads are not allowed for Atlassian's OnDemand support system, for the record, here is the title/description I used for the issue:

        Title: Migrating from Apache Spark project's OnDemand JIRA to the apache.org hosted JIRA

        Description:

        I'm a contributor to the open source Apache Spark project, and we are trying to migrate from the onDemand JIRA for Spark hosted by Atlassian (spark-project.atlassian.net) to the version of JIRA hosted by Apache for their projects (https://issues.apache.org/jira).

        We are having some issues because the versions of the two don't seem to be compatible for the export-then-import we need to perform.

        You can see what steps we've taken in this issue https://issues.apache.org/jira/browse/INFRA-6419
        Specifically, the existing Spark OnDemand Jira is now at JIRA v6.2-OD-03 and the Apache version is 6.1.

        We have about 1000 issues now so it would be very expensive to either lose or have to manually copy over all issues.

        Would you be able to assist us in exporting a version of our OnDemand JIRA that can successfully be imported to the JIRA hosted by the Apache Foundation? Perhaps it would be enough to just change the version number in the exported file and try to import it, or are the changes between these two versions significant enough that this would fail (or worse)?

        Thanks a ton in advance!
        Show
        Andy Konwinski added a comment - And since it looks like anonymous reads are not allowed for Atlassian's OnDemand support system, for the record, here is the title/description I used for the issue: Title: Migrating from Apache Spark project's OnDemand JIRA to the apache.org hosted JIRA Description: I'm a contributor to the open source Apache Spark project, and we are trying to migrate from the onDemand JIRA for Spark hosted by Atlassian (spark-project.atlassian.net) to the version of JIRA hosted by Apache for their projects ( https://issues.apache.org/jira ). We are having some issues because the versions of the two don't seem to be compatible for the export-then-import we need to perform. You can see what steps we've taken in this issue https://issues.apache.org/jira/browse/INFRA-6419 Specifically, the existing Spark OnDemand Jira is now at JIRA v6.2-OD-03 and the Apache version is 6.1. We have about 1000 issues now so it would be very expensive to either lose or have to manually copy over all issues. Would you be able to assist us in exporting a version of our OnDemand JIRA that can successfully be imported to the JIRA hosted by the Apache Foundation? Perhaps it would be enough to just change the version number in the exported file and try to import it, or are the changes between these two versions significant enough that this would fail (or worse)? Thanks a ton in advance!
        Hide
        Andy Konwinski added a comment -
        Hi folks, I got the following response from the Atlassian support person:

        <quote>
        Hi Andy,
        Thanks for letting us know the goal you are trying to achieve.
        As mentioned in Migrating from JIRA OnDemand to a JIRA Installed Site:
        "You will need to download and install the latest production release of JIRA"
        The latest version available is 6.1.5.
        While editing the build number may allow import to occur, it would create the potential for data corruption.
        Cheers,
        Paul
        </quote>

        Mark, earlier you said "The latest supported version we can install is 6.1.4.", is there a reason why we can't bring the Apache version up to 6.1.5, or maybe that release just wasn't out when you said that before?
        Show
        Andy Konwinski added a comment - Hi folks, I got the following response from the Atlassian support person: <quote> Hi Andy, Thanks for letting us know the goal you are trying to achieve. As mentioned in Migrating from JIRA OnDemand to a JIRA Installed Site: "You will need to download and install the latest production release of JIRA" The latest version available is 6.1.5. While editing the build number may allow import to occur, it would create the potential for data corruption. Cheers, Paul </quote> Mark, earlier you said "The latest supported version we can install is 6.1.4.", is there a reason why we can't bring the Apache version up to 6.1.5, or maybe that release just wasn't out when you said that before?
        Hide
        Chris A. Mattmann added a comment -
        Guys this is a chicken and egg problem here -- is there any way that we can:

        1. create a separate 6.1.5 instance (warm spare) and then load Spark's JIRA onto it
        2. if all good in #1, then import Spark from the 6.1.5 warm spare into 6.1.4 prod for ASF JIRA?

        If not, the project needs an answer that brings its JIRA bits onto the ASF infra somehow. So, need some infra-fu and mojo here :)
        Show
        Chris A. Mattmann added a comment - Guys this is a chicken and egg problem here -- is there any way that we can: 1. create a separate 6.1.5 instance (warm spare) and then load Spark's JIRA onto it 2. if all good in #1, then import Spark from the 6.1.5 warm spare into 6.1.4 prod for ASF JIRA? If not, the project needs an answer that brings its JIRA bits onto the ASF infra somehow. So, need some infra-fu and mojo here :)
        Hide
        Mark Thomas added a comment -
        I don't see any chicken and egg problem here at all. As long as Atlassian provide an option to export from Jira on demand to a supported Jira standalone version then this is simple.

        I've already updated Jira to the latest version (6.1.4 at the time) once for this issue. I've no objection to upgrading to the latest supported version again (6.1.5 as I type this). Upgrades mean down time for users - anything from 1 to ~8 hours depending on how the upgrade goes, what it breaks and how easy it is to fix. Point releases are usually near 1 than 8 hours but even so I'd rather do this at a weekend. I'll see if I can find time to do the upgrade this coming weekend.
        Show
        Mark Thomas added a comment - I don't see any chicken and egg problem here at all. As long as Atlassian provide an option to export from Jira on demand to a supported Jira standalone version then this is simple. I've already updated Jira to the latest version (6.1.4 at the time) once for this issue. I've no objection to upgrading to the latest supported version again (6.1.5 as I type this). Upgrades mean down time for users - anything from 1 to ~8 hours depending on how the upgrade goes, what it breaks and how easy it is to fix. Point releases are usually near 1 than 8 hours but even so I'd rather do this at a weekend. I'll see if I can find time to do the upgrade this coming weekend.
        Hide
        Chris A. Mattmann added a comment -
        Thanks Mark, look forward to seeing the upgrade this weekend and hopefully it goes smooth.
        Show
        Chris A. Mattmann added a comment - Thanks Mark, look forward to seeing the upgrade this weekend and hopefully it goes smooth.
        Hide
        Matei Zaharia added a comment -
        Hey Mark, did you successfully do the update? I see that our JIRA now says v6.1.5. If you updated it, can you try importing this zip: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131225.zip ? (Just the SPARK project).

        If the zip up there is too new, please just import the previous one that we needed to update to 6.1.5 for. The most important thing is to get the bulk of the issues in there... we can deal manually with any changes since that export.
        Show
        Matei Zaharia added a comment - Hey Mark, did you successfully do the update? I see that our JIRA now says v6.1.5. If you updated it, can you try importing this zip: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131225.zip ? (Just the SPARK project). If the zip up there is too new, please just import the previous one that we needed to update to 6.1.5 for. The most important thing is to get the bulk of the issues in there... we can deal manually with any changes since that export.
        Hide
        Matei Zaharia added a comment -
        Show
        Matei Zaharia added a comment - Here's a new backup: http://www.cs.berkeley.edu/~matei/JIRA-backup-20131230.zip
        Hide
        Mark Thomas added a comment -
        Some folks in the Spark project appear to have got the incorrect impression that I will be doing the import and are now hassling about this me via direct mail while I am on holiday. As far as I am aware (based on who this issue is assigned to) Daniel Gruno will be doing the import. My involvement to date has been limited to upgrading Jira and being hassled via direct mail has done absolutely nothing to encourage me to look at the import.
        Show
        Mark Thomas added a comment - Some folks in the Spark project appear to have got the incorrect impression that I will be doing the import and are now hassling about this me via direct mail while I am on holiday. As far as I am aware (based on who this issue is assigned to) Daniel Gruno will be doing the import. My involvement to date has been limited to upgrading Jira and being hassled via direct mail has done absolutely nothing to encourage me to look at the import.
        Hide
        Matei Zaharia added a comment -
        Sorry Mark, I didn't realize that you were only doing the upgrade.
        Show
        Matei Zaharia added a comment - Sorry Mark, I didn't realize that you were only doing the upgrade.
        Hide
        #asfinfra IRC Bot added a comment -
        <Humbedooh> Matei, I will be looking into performing the import this week, but please be patient and don't start sending out emails to every man and their kitchen sink. If you want to ping the ticket, ping the ticket in JIRA
        Show
        #asfinfra IRC Bot added a comment - <Humbedooh> Matei, I will be looking into performing the import this week, but please be patient and don't start sending out emails to every man and their kitchen sink. If you want to ping the ticket, ping the ticket in JIRA
        Hide
        Matei Zaharia added a comment -
        Thanks Daniel. As I mentioned above, please just take any export that works, we don't need it to be the latest.
        Show
        Matei Zaharia added a comment - Thanks Daniel. As I mentioned above, please just take any export that works, we don't need it to be the latest.
        Hide
        Matei Zaharia added a comment -
        Hey Daniel, any update on this?
        Show
        Matei Zaharia added a comment - Hey Daniel, any update on this?
        Hide
        Andy Konwinski added a comment -
        Hi folks, any word about this upgrade?
        Show
        Andy Konwinski added a comment - Hi folks, any word about this upgrade?
        Hide
        #asfinfra IRC Bot added a comment -
        <pctony> Andy, sorry, the issue we have with just throwing up the latest version is having the time to go through it. The work is either currently done by Mark or myself. We try to avoid just tracking the latest release unless their are security issues to roll up. I will try and do this over the weekend.
        Show
        #asfinfra IRC Bot added a comment - <pctony> Andy, sorry, the issue we have with just throwing up the latest version is having the time to go through it. The work is either currently done by Mark or myself. We try to avoid just tracking the latest release unless their are security issues to roll up. I will try and do this over the weekend.
        Hide
        Chris A. Mattmann added a comment -
        Thanks Tony how did it go?
        Show
        Chris A. Mattmann added a comment - Thanks Tony how did it go?
        Hide
        Matei Zaharia added a comment -
        Hey guys, any progress setting up the test server? I've uploaded a new export of our JIRA at http://www.cs.berkeley.edu/~matei/JIRA-backup-20140225.zip . As mentioned before, it would be fine to load in any relatively recent version, but we'd like an estimate on the feasibility of this as we continue development. We do want to end up with JIRA in Apache eventually, and mirrored onto ASF lists, so if you guys cannot import a previous version, we may simply start anew over here and point people to the previous one for old issues.
        Show
        Matei Zaharia added a comment - Hey guys, any progress setting up the test server? I've uploaded a new export of our JIRA at http://www.cs.berkeley.edu/~matei/JIRA-backup-20140225.zip . As mentioned before, it would be fine to load in any relatively recent version, but we'd like an estimate on the feasibility of this as we continue development. We do want to end up with JIRA in Apache eventually, and mirrored onto ASF lists, so if you guys cannot import a previous version, we may simply start anew over here and point people to the previous one for old issues.
        Hide
        Chris A. Mattmann added a comment -
        Guys, can we get this export/import completed? I hate to be a pest, but at this point it's been 9 months since this issue was created. Thank you.
        Show
        Chris A. Mattmann added a comment - Guys, can we get this export/import completed? I hate to be a pest, but at this point it's been 9 months since this issue was created. Thank you.
        Hide
        Joe Schaefer added a comment -
        I hate to be a pest back, but versioning in Jira is a sick joke. Please don't blame us for the problems associated with importing from one jira to another, they are endemic to the software. As it turns out today Atlassian published another set of security advisories for all their products including jira, so we'll be looking to upgrade yet again before dealing with this ticket.
        Show
        Joe Schaefer added a comment - I hate to be a pest back, but versioning in Jira is a sick joke. Please don't blame us for the problems associated with importing from one jira to another, they are endemic to the software. As it turns out today Atlassian published another set of security advisories for all their products including jira, so we'll be looking to upgrade yet again before dealing with this ticket.
        Hide
        Chris A. Mattmann added a comment -
        Yeah Joe I was trying to be careful with my words, but at the same time identify that in general there has to be a way to do this. I realize this is a difficult problem and that we don't control Atlassian, but at the same time, the message to our projects coming in with external JIRAs that have more issues in them than would be easy to recreate by starting over shouldn't be it takes 9 months to import the issues. We manage one of the largest JIRA instances in the world, right? Can't we get Atlassian on the horn or looking at this issue specifically for us? We ought to have some pull with them, they use a ton of our products. If that doesn't work, then what suggestion do you have back to the Spark project? Should it be that they should simply start over creating their JIRA issues in our JIRA and keeping 2 JIRAs, maybe their old on demand instance for old JIRA issues, and then recommending that folks create new issues here in the ASF one? I'm looking for answers here, not blaming anyone.
        Show
        Chris A. Mattmann added a comment - Yeah Joe I was trying to be careful with my words, but at the same time identify that in general there has to be a way to do this. I realize this is a difficult problem and that we don't control Atlassian, but at the same time, the message to our projects coming in with external JIRAs that have more issues in them than would be easy to recreate by starting over shouldn't be it takes 9 months to import the issues. We manage one of the largest JIRA instances in the world, right? Can't we get Atlassian on the horn or looking at this issue specifically for us? We ought to have some pull with them, they use a ton of our products. If that doesn't work, then what suggestion do you have back to the Spark project? Should it be that they should simply start over creating their JIRA issues in our JIRA and keeping 2 JIRAs, maybe their old on demand instance for old JIRA issues, and then recommending that folks create new issues here in the ASF one? I'm looking for answers here, not blaming anyone.
        Hide
        Gavin added a comment -
        So I just tried to import using the backup of 2 days ago.

        "...This data appears to be from an older version of JIRA. Please upgrade the data and try again. The current version of JIRA is at build number '6160', but the supplied backup file was for build number '6252'...."

        So we are yet again at a version mismatch.

        I also found :-

        https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+maintenance+windows

        which I interpret as OnDemand Jira gets updated weekly, no wonder we cant keep up!

        We are due to upgrade our Jira again, will try the import again after that.
        Show
        Gavin added a comment - So I just tried to import using the backup of 2 days ago. "...This data appears to be from an older version of JIRA. Please upgrade the data and try again. The current version of JIRA is at build number '6160', but the supplied backup file was for build number '6252'...." So we are yet again at a version mismatch. I also found :- https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+maintenance+windows which I interpret as OnDemand Jira gets updated weekly, no wonder we cant keep up! We are due to upgrade our Jira again, will try the import again after that.
        Hide
        Joe Schaefer added a comment -
        Give us another week to take a crack at upgrading jira and trying again. We'll let you
        know then whether it's time to go fish or cut bait.
        Show
        Joe Schaefer added a comment - Give us another week to take a crack at upgrading jira and trying again. We'll let you know then whether it's time to go fish or cut bait.
        Hide
        Matei Zaharia added a comment -
        If updating the ASF's JIRA still does not bring it to a compatible version, I like Chris's suggestion of contacting Atlassian directly. We use so few features in our JIRA that I don't imagine *that* much changes between versions... maybe we can just take the file and mark it as another version for example.
        Show
        Matei Zaharia added a comment - If updating the ASF's JIRA still does not bring it to a compatible version, I like Chris's suggestion of contacting Atlassian directly. We use so few features in our JIRA that I don't imagine *that* much changes between versions... maybe we can just take the file and mark it as another version for example.
        Hide
        Joe Schaefer added a comment -
        Contacting Atlassian is almost invariably worthless for collaborative problem solving. What we get from them is to instruct us to upgrade everything to the latest version and ensure we are running on a supported platform before they will say anything else. After jumping through all their hoops, they never offer guidance about how to deviate from published documentation. Of course hope springs eternal but I'm far from optimistic about that line of inquiry.
        Show
        Joe Schaefer added a comment - Contacting Atlassian is almost invariably worthless for collaborative problem solving. What we get from them is to instruct us to upgrade everything to the latest version and ensure we are running on a supported platform before they will say anything else. After jumping through all their hoops, they never offer guidance about how to deviate from published documentation. Of course hope springs eternal but I'm far from optimistic about that line of inquiry.
        Hide
        Matei Zaharia added a comment -
        I saw you guys recently upgraded to 6.2, and our Atlassian instance said the same, so here's a new export from that: http://www.cs.berkeley.edu/~matei/JIRA-backup-20140304.zip
        Show
        Matei Zaharia added a comment - I saw you guys recently upgraded to 6.2, and our Atlassian instance said the same, so here's a new export from that: http://www.cs.berkeley.edu/~matei/JIRA-backup-20140304.zip
        Hide
        Andy Konwinski added a comment -
        Hi Infra,

        I totally understand if nobody has had a chance to try importing Matei's upload from March 4 yet, but it looks like our Hosted JIRA is at version 6.2-OD-10-004-WN build 6253 and this Apache JIRA is at version 6.2#6252-sha1:aa34325 so *the versions are still the same at 6.2* and the build numbers are off by 1.

        It seems like a rare window of time in which the versions are compatible for an import!

        We know your time is super valuable and this ticket has been around for a long time, and is probably feeling like a painful thorn in infra's side. We would be *very* grateful if you could find time to try out an import using the backup Matei linked to above from March 4, 2014.

        Another option, since your time is limited, is to bump me to have more admin karma on the JIRA so that we can try the import ourselves. I've been an active Apache contributor for a few years and managed lots of infrastructure (CI, wiki, code review, issue tracking, etc.) for both the Apache Mesos and Apache Spark projects before during and after their incubation/graduation, and I have managed multiple production JIRA instances including Spark's current onDemand instance and at companies as well, and am happy to step up and participate as a member of Apache Infra here.

        Andy
        Show
        Andy Konwinski added a comment - Hi Infra, I totally understand if nobody has had a chance to try importing Matei's upload from March 4 yet, but it looks like our Hosted JIRA is at version 6.2-OD-10-004-WN build 6253 and this Apache JIRA is at version 6.2#6252-sha1:aa34325 so *the versions are still the same at 6.2* and the build numbers are off by 1. It seems like a rare window of time in which the versions are compatible for an import! We know your time is super valuable and this ticket has been around for a long time, and is probably feeling like a painful thorn in infra's side. We would be *very* grateful if you could find time to try out an import using the backup Matei linked to above from March 4, 2014. Another option, since your time is limited, is to bump me to have more admin karma on the JIRA so that we can try the import ourselves. I've been an active Apache contributor for a few years and managed lots of infrastructure (CI, wiki, code review, issue tracking, etc.) for both the Apache Mesos and Apache Spark projects before during and after their incubation/graduation, and I have managed multiple production JIRA instances including Spark's current onDemand instance and at companies as well, and am happy to step up and participate as a member of Apache Infra here. Andy
        Hide
        Andy Konwinski added a comment -
        Actually, since a lot of activity has happened in the OnDemand in the last 20 days, in case somebody has a minute to try this out, I just created another export: http://cs.berkeley.edu/~andyk/JIRA-backup-20140324.zip
        Show
        Andy Konwinski added a comment - Actually, since a lot of activity has happened in the OnDemand in the last 20 days, in case somebody has a minute to try this out, I just created another export: http://cs.berkeley.edu/~andyk/JIRA-backup-20140324.zip
        Hide
        Gavin added a comment -
        [~andyk] I'm happy to give this a stab tomorrow.
        Show
        Gavin added a comment - [~andyk] I'm happy to give this a stab tomorrow.
        Hide
        Gavin added a comment -
        Ok had a go, we got much much further this time - a bit of export file hackery was needed.
        Please take a look at the latest failure image.

        What you need to do is create a new export (sorry!) but do it quickly please before fall out of versions too much again.!!!!!

        BEFORE you export, please resolve these issues:-

        1. - Custom Field Configuration:
              Unable to import custom field '[CHART] Time in Status'. The custom field type does not support project imports.

        2. - Issue Link Type:
              The Issue Link Type 'Related' is required for the import but does not exist in the current JIRA instance.

        2. - Attachments:
              There are more than twenty attachment entries that do not exist in the attachment directory. See your logs for full details.

        For 1, change the custom field to a standard one that you know is present in our Jira.
        For 2, Change link type to a standard one that you know is present in our Jira.
        For 3, not sure, it might import ok without these attachments but try and validate the export.

        Also, I had to DELETE the current SPARK jira project, done worry I save the 4 issues in TST project and will move them back after.

        ** - PLEASE TRY AND DO THIS ASAP, LIKE TODAY :) - **
        Show
        Gavin added a comment - Ok had a go, we got much much further this time - a bit of export file hackery was needed. Please take a look at the latest failure image. What you need to do is create a new export (sorry!) but do it quickly please before fall out of versions too much again.!!!!! BEFORE you export, please resolve these issues:- 1. - Custom Field Configuration:       Unable to import custom field '[CHART] Time in Status'. The custom field type does not support project imports. 2. - Issue Link Type:       The Issue Link Type 'Related' is required for the import but does not exist in the current JIRA instance. 2. - Attachments:       There are more than twenty attachment entries that do not exist in the attachment directory. See your logs for full details. For 1, change the custom field to a standard one that you know is present in our Jira. For 2, Change link type to a standard one that you know is present in our Jira. For 3, not sure, it might import ok without these attachments but try and validate the export. Also, I had to DELETE the current SPARK jira project, done worry I save the 4 issues in TST project and will move them back after. ** - PLEASE TRY AND DO THIS ASAP, LIKE TODAY :) - **
        Hide
        #asfinfra IRC Bot added a comment -
        <gmcdonald> FYI there are 76 attachments in the export.
        Show
        #asfinfra IRC Bot added a comment - <gmcdonald> FYI there are 76 attachments in the export.
        Hide
        Andy Konwinski added a comment - - edited
        Thanks so much for your help!

        I'm working on this now.

        1. I just removed that custom field.

        2. I can't figure out how to see details of the link types that are present in the Apache JIRA. Looking at the list link types in our OnDemand instance, I see that a link type consists of a Name, Outward Description, and Inward Description.

        We have 28 "Related" links in our JIRA and I just need to know what to change that instance type to so that it match an existing instance type in the Apache JIRA.

        Here is what the "Related" link type has for the following values:

        Name: Related
        Outward Description: relates to
        Inward Description: relates to

        Can you look at what the equivalent link type in our Apache JIRA has for these settings? Settings are under [gear icon] > System. Select Issue Features > Issue Linking. I *think* that the outward description is "relates to" and the inward is "is related to", can you please confirm that and also the Name of the link type?

        3. I tried googling to see how I might verify the attachments. I found https://answers.atlassian.com/questions/143808/project-import-attachments-do-not-exist-in-the-attachment-directory which says "When trying to import the project to a different instance, have you copy the Attachments for the instance into the $Target_JIRA_HOME/import/attachments folder before proceed with the import". If necessary, we might consider just doing the export without attachments to get this done.
        Show
        Andy Konwinski added a comment - - edited Thanks so much for your help! I'm working on this now. 1. I just removed that custom field. 2. I can't figure out how to see details of the link types that are present in the Apache JIRA. Looking at the list link types in our OnDemand instance, I see that a link type consists of a Name, Outward Description, and Inward Description. We have 28 "Related" links in our JIRA and I just need to know what to change that instance type to so that it match an existing instance type in the Apache JIRA. Here is what the "Related" link type has for the following values: Name: Related Outward Description: relates to Inward Description: relates to Can you look at what the equivalent link type in our Apache JIRA has for these settings? Settings are under [gear icon] > System. Select Issue Features > Issue Linking. I *think* that the outward description is "relates to" and the inward is "is related to", can you please confirm that and also the Name of the link type? 3. I tried googling to see how I might verify the attachments. I found https://answers.atlassian.com/questions/143808/project-import-attachments-do-not-exist-in-the-attachment-directory which says "When trying to import the project to a different instance, have you copy the Attachments for the instance into the $Target_JIRA_HOME/import/attachments folder before proceed with the import". If necessary, we might consider just doing the export without attachments to get this done.
        Hide
        Mark Thomas added a comment -
        Name: Reference
        Out: relates to
        In: is related to
        Show
        Mark Thomas added a comment - Name: Reference Out: relates to In: is related to
        Hide
        Andy Konwinski added a comment -
        Great, thanks!

        I changed that link type to match in our OnDemand JIRA and tried to export another backup. Sadly, I then got this message: "Sorry. Backup frequency is limited. You can not make another backup right now. Approximate time till next allowed backup: 21h 1m".

        I'll see if I can create a ticket and get them to run this sooner. Otherwise, I'll rerun the export and post a link to it here tomorrow.
        Show
        Andy Konwinski added a comment - Great, thanks! I changed that link type to match in our OnDemand JIRA and tried to export another backup. Sadly, I then got this message: "Sorry. Backup frequency is limited. You can not make another backup right now. Approximate time till next allowed backup: 21h 1m". I'll see if I can create a ticket and get them to run this sooner. Otherwise, I'll rerun the export and post a link to it here tomorrow.
        Hide
        Gavin added a comment -
        yeah I get a 10+ hr wait for the backups too
        Show
        Gavin added a comment - yeah I get a 10+ hr wait for the backups too
        Hide
        Andy Konwinski added a comment -
        Show
        Andy Konwinski added a comment - New download from today http://cs.berkeley.edu/~andyk/JIRA-backup-20140326.zip
        Hide
        Gavin added a comment -
        We have a new error now:

        Custom Field Configuration
        The custom field 'Epic Name [deprecated, this field is no longer being used]' of type 'Name of Epic' is required for the import but does not exist in the current JIRA instance.

        We need that fixed as we can not create Agile custom fields in our Jira.

        Best thing to do is rename it back to the original name 'Epic Name' and remove the bracketed wording.

        Please provide a new download once done.
        Show
        Gavin added a comment - We have a new error now: Custom Field Configuration The custom field 'Epic Name [deprecated, this field is no longer being used]' of type 'Name of Epic' is required for the import but does not exist in the current JIRA instance. We need that fixed as we can not create Agile custom fields in our Jira. Best thing to do is rename it back to the original name 'Epic Name' and remove the bracketed wording. Please provide a new download once done.
        Hide
        Andy Konwinski added a comment -
        Here is the most recent version with that field deleted http://cs.berkeley.edu/~andyk/JIRA-backup-20140328.zip

        If this one fails, would you possibly consider copying and pasting (or take a screenshot of) the full list of custom fields in the Apache JIRA so I can try to remove any others that we might not have caught yet.
        Show
        Andy Konwinski added a comment - Here is the most recent version with that field deleted http://cs.berkeley.edu/~andyk/JIRA-backup-20140328.zip If this one fails, would you possibly consider copying and pasting (or take a screenshot of) the full list of custom fields in the Apache JIRA so I can try to remove any others that we might not have caught yet.
        Hide
        Gavin added a comment -
        SUCCESS!!


        Project Import: Results
        The project import completed successfully in 1 minute.
        Project Summary
        Key:
        SPARK
        Description:
        Spark is fast and general cluster computing system.
        Lead:
        Matei Zaharia
        URL:
        http://spark.apache.org
        Sender Address:
         
        Default Assignee:
        Unassigned
        Components:
        20
        Versions:
        21
        Users
        Users:
        181 out of 181
        Project Roles
        Administrators:
        1 users, 0 groups
        Developers:
        10 users, 0 groups
        Users:
        6 users, 1 groups
        Issues
        Issues created:
        1060 out of 1060
        Attachments:
        23 out of 23


        Still a few things like permissions to sort out and notifications, but take a look around, and please TURN OFF your previous Jira
        Show
        Gavin added a comment - SUCCESS!! … Project Import: Results The project import completed successfully in 1 minute. Project Summary Key: SPARK Description: Spark is fast and general cluster computing system. Lead: Matei Zaharia URL: http://spark.apache.org Sender Address:   Default Assignee: Unassigned Components: 20 Versions: 21 Users Users: 181 out of 181 Project Roles Administrators: 1 users, 0 groups Developers: 10 users, 0 groups Users: 6 users, 1 groups Issues Issues created: 1060 out of 1060 Attachments: 23 out of 23 … Still a few things like permissions to sort out and notifications, but take a look around, and please TURN OFF your previous Jira
        Hide
        Gavin added a comment -
        Notification Scheme enabled and go to dev@spark.a.o
        Show
        Gavin added a comment - Notification Scheme enabled and go to dev@spark.a.o
        Hide
        Chris A. Mattmann added a comment -
        wow AWESOME Gav!!!
        Show
        Chris A. Mattmann added a comment - wow AWESOME Gav!!!
        Hide
        Patrick Wendell added a comment - - edited
        Hi [~ipv6guru] - I noticed that this JIRA has been set-up in a way where all of the github comments are posted as JIRA comments. For us it's pretty common to have hundreds of small code-level feedback comments on a pull request. It's not desirable for those to show up as comments in the JIRA (actually it will make JIRA pretty un-usable for large features).

        We are currently sending these to a commits@ mailing list that people can opt-into. Is there any way we can disable these from showing up as JIRA comments?
        Show
        Patrick Wendell added a comment - - edited Hi [~ipv6guru] - I noticed that this JIRA has been set-up in a way where all of the github comments are posted as JIRA comments. For us it's pretty common to have hundreds of small code-level feedback comments on a pull request. It's not desirable for those to show up as comments in the JIRA (actually it will make JIRA pretty un-usable for large features). We are currently sending these to a commits@ mailing list that people can opt-into. Is there any way we can disable these from showing up as JIRA comments?
        Hide
        Patrick Wendell added a comment - - edited
        You can see this really is polluting the history stream on our JIRA:

        https://issues.apache.org/jira/browse/SPARK/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel

        In fact I think we might just prefer to totally disable github integration for the time being, if it's possible.
        Show
        Patrick Wendell added a comment - - edited You can see this really is polluting the history stream on our JIRA: https://issues.apache.org/jira/browse/SPARK/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel In fact I think we might just prefer to totally disable github integration for the time being, if it's possible.
        Hide
        #asfinfra IRC Bot added a comment -
        <gmcdonald> this must have been asked for and set up previously as I imported your jira, nothing else
        Show
        #asfinfra IRC Bot added a comment - <gmcdonald> this must have been asked for and set up previously as I imported your jira, nothing else
        Hide
        Patrick Wendell added a comment -
        Ah okay - it's totally possible this was set up at some other point. That said, would it be possible for you to disable it? I think since infra controls both the github and the jira, it's not something we can do directly. I'm guessing it's just a matter of switching integration off on either JIRA or github.
        Show
        Patrick Wendell added a comment - Ah okay - it's totally possible this was set up at some other point. That said, would it be possible for you to disable it? I think since infra controls both the github and the jira, it's not something we can do directly. I'm guessing it's just a matter of switching integration off on either JIRA or github.
        Hide
        Matei Zaharia added a comment -
        +1, this is extremely spammy.
        Show
        Matei Zaharia added a comment - +1, this is extremely spammy.
        Hide
        Matei Zaharia added a comment -
        BTW forgot to add, but thanks for getting this migrated over! It's awesome to have this infrastructure on Apache now.
        Show
        Matei Zaharia added a comment - BTW forgot to add, but thanks for getting this migrated over! It's awesome to have this infrastructure on Apache now.
        Hide
        Chris A. Mattmann added a comment -
        just want to emphasize what a GREAT job everyone did here, thanks Gavin for finally getting it imported; thanks to Matei and Patrick and others for being persistent here!
        Show
        Chris A. Mattmann added a comment - just want to emphasize what a GREAT job everyone did here, thanks Gavin for finally getting it imported; thanks to Matei and Patrick and others for being persistent here!
        Hide
        Jake Farrell added a comment -
        I disabled pull request comments as asked for in INFRA-7517, this should stop the stream from github being added to the jira issues as mentioned
        Show
        Jake Farrell added a comment - I disabled pull request comments as asked for in INFRA-7517 , this should stop the stream from github being added to the jira issues as mentioned
        Hide
        Matei Zaharia added a comment -
        Thanks Jake, really appreciate it!
        Show
        Matei Zaharia added a comment - Thanks Jake, really appreciate it!
        Hide
        Gavin added a comment -
        good job everyone, all done.
        Show
        Gavin added a comment - good job everyone, all done.

          People

          • Assignee:
            Gavin
            Reporter:
            Chris A. Mattmann
            JIRA Admin:
            Chris A. Mattmann
            Initial Developers:
            Andrew Hart, Chris A. Mattmann, Henry Saputra, Matei Zaharia, Paul Ramirez, Suresh Marru, Thomas Dudziak
          • Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development