How to copy the issue to a new issue changing issue type

[f***@atlassian.com]

I have two workflows: one for support service (a bug issue type) and one for development services (a development issue type).
I then create an issue (bug issue type) to manage an issue reported by a user.
After verifying it, I figure out that this is a bug that must change the project. So, I create (now manually) an issue with development issue type, copied all the fields from the bug issue type and link both.

Is there a mode automated way to to such things?
Eg, I need to clone an issue, linking both but the cloned issue must have another issue type.

Best regards
--
Post by marcoscunhalima - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=25188

[f***@atlassian.com]

No - a clone is an exact copy, barring the key (although Jira does try to be nice - it can add "clone -" to the summary, and create a link back to the original, both of which are quite useful).

I've not actually looked at this, but http://confluence.atlassian.com/display/JIRAEXT/JIRA+Clone+and+Move+Plugin might do the trick - when you try to move an issue, Jira asks for Project AND Issue-type, so my logic is that cloning something and moving it to the same project, but different issue-type might do the trick for you.
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=25188

[f***@atlassian.com]

Nic
Thanks, I'll try (although i cannot change the original key as informed to user).
Best regards
--
Post by marcoscunhalima - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=25188

[f***@atlassian.com]

I (half-) wrote a plugin to do this. I'm not too knowledgeable on plugin development and basically hacked a version someone else started.

What it does is offer a workflow postfunction that creates a clone of the issue, and then that issue is immediately moved to the development project (and appropriate issue type)

The label is called "Transfer to Development (create link)", and what happens is that when the support ticket is moved to be a Bug, this option shows up in the workflow, changing the status to "Transferred to Development" and creating a clone with the links being "Tracked in development issue" and "Derived from Support Issue". I am guessing that if and when I upgrade from 3.6.5 it won't work and I'll probably have to abandon it and use a manual approach of clone/move.
--
Post by napplebaum - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=25188

[f***@atlassian.com]

Neil
Is it working for you? Could you share the code?
Best regards
--
Post by marcoscunhalima - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=25188

[f***@atlassian.com]

Like I said, I could share the code (it has some hardcoded stuff in it), but I doubt it'll work for post 3.6.5 so you might be wasting your time. Contact me off-line if you're interested.

jiradmin at gmail dot com
--
Post by napplebaum - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=25188