Hi guys, it seems that importing some cloud JIRA issues into a JIRA server is quite a burden. The process is mainly manual, with a lot of steps to follow (see https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server).
At this point, we have a choice to make. We can decide to not importing the existing JIRA at all, and start with a brand new JIRA, for instance. The reason I'm suggesting this approach is that if you look at the existing JIRA's, there are only two people who have opened issues : Shawn and me. That means they were mainly issues regarding bugs we both found during a development phase. If we consider that JIRA is a tool allowing users to fill issues they found, as much as a developpers tool, we can consider that we can start from a blank page as we don't have any users atm. We can also decide to migrate by hand the few issues that might interest a user (ie, those users are likely to face when using Fortress, and where they can find an answer). Creating the 4 required JIRAs would be quite quick. Migrating all the existing issues would take at least one more week, assuming we do a part of the migration process on our side (ie migrating from cloud to a local server). So, wdyt ? Starting from a blank JIRA does sound reasonnable to you ?
