Hi,
I'm curious -- let's say you move an issue from one project to another. I know you can look at the history and see the old issue id -- but is there a way to capture the old issue id, and save it in a custom field? This would make my migration project a lot easier.
Well, if you already have the issue created you may use Bob Swift's CLI plugin. Using this tool, you can copy issue's key field and paste it to the custom field. First method would only work for the future issues.
Thanks -- I'll do that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Bryan,
I think you can try the following if you get the "JIRA Misc Workflow Extensions" plugin. It's free:
This way you have your original key stored in a seperate field.
Best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bryan,
You can copy the key to custom field within same project by moving issues to a test status and back to original. Then move issues from one project to another.
Thanks,
Arpit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You'd want to put the custom field on the view screen only or make it a read only field so users don't mess with the value. However, I think the original intent was to do it when the issue is moved to a new project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks guys -- yes, I want to move issues to a new project, and retain original key in a custom field. I followed the above tips, but it is not populating the field. I'm guessing an issue move is not considered a workflow task (or at least not a create new issue task?)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.