Hi All,
I am looking to move all Asset objects from one object schema to another.
As part of this requirement, I would like to maintain the historical data of each asset (created, updated, comments, attachments etc.) on each object.
Also as some of these objects are referenced in other schemas, I would appreciate suggestions on how best to maintain these so that after the move, the information is persisted as best as possible.
I came across this as a possible solution for Cloud and I expect I will run into some of the shortcomings listed here as well.
Any help or suggestions here would be appreciated.
Thanks.
Hello @Ismael Jimoh
I don't find any links within your post to the solution and limitations you say you found. Can you provide those?
Are you open to using a third party plugin?
Hi @Trudy Claspill
Really sorry I missed that and also sorry for the late reply.
Here is the link: https://support.atlassian.com/jira/kb/how-to-bulk-clone-assets-objects-to-a-different-object-type-or-schema-using-automation/ in question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the same limitations would apply. You would not retain historical information like created and updated timestamps, and the solution does not encompass "cloning" the attachments or comments.
Do note that the solution provided in that KB can't be applied to the Jira Data Center environment. Automation for Jira Data Center does not offer the same features, like Branch on AQL. At least not in Jira version 9.12. Maybe more features like that one are available in newer Jira DC versions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.