Hi Tony,
Discussion inline below.
Thanks!
Kevin.
On 4/2/13 11:05 AM, Tony Stevenson wrote:
Kevin,
There are several big painful gotchas to be aware of here.
- If we import, and you already have a JIRA project they will be tagged on the
end of your current issues, and not in the number order you might expect.
I'm not concerned about the imported issues being assigned new numbers.
- The project KEY you export from cannot be the same as you import into, this
will cause overwriting or a failed import.
These will be coming from issues with keys like BUG-NNNN and I assume
they will be imported with keys like KNOX-NNNN right? This is fine.
- Attachments must be provided at the time of the initial import
I don't think we have any attachments so this should be fine.
- The version from which you export must be exactly the same version we import
into (double check this before shipping us anything, please).
Apache: Atlassian JIRA (v5.2.8#851-sha1:3262fdc)
Hortonworks: JIRA
(6.0-OD-09-3#6060-sha1:a4642c9a73ee448a9294273e0bad12d9670c7015)
I guess this is a deal breaker? I was assuming that we would use XML as
the interchange format. So you are saying that an XML export from 6.0
can't be imported into 5.2.8?
Tony
On 2 Apr 2013, at 14:34, Kevin Minder <[email protected]> wrote:
Hi,
I'm a committer on the Knox podling project. We are discussing possibly trying
to do a bulk import of the exting Jira issues in an external Jira system. I
can see how to export them from the external system but it looks like I don't
have the privs equired to do an import. Is this even possible? If so, what is
the processes?
Kevin.
Cheers,
Tony
----------------------------------
Tony Stevenson
[email protected]
[email protected]
http://www.pc-tony.com
GPG - 1024D/51047D66
----------------------------------
