Hi @Martina Bagnasco , Welcome to the Community!
If the work you've done is A LOT of work, you could consider installing a "dev" instance of JSM and using a backup/restore app to clone that project to the "dev" instance, then clone back the configuration items you want to clone to the "production" project on your existing instance. If that's the case, you have a couple of options:
Install one of the trial apps from the Atlassian Marketplace for data or configuration management, backup, and restore on both instances. They allow you to clone (copy) projects or configuration items that you select plus their dependencies. None of the apps allow you to clone absolutely everything from site to site due to Atlassian API restrictions, but they'll save you a ton of time by cloning most of your project configuration items. I use Revyz's Data Manager for Jira and love it for its ease of use, security, and tons of helpful features for admins, but also check out other great apps like Salto Labs' Salto Configuration Manager for Jira, Appfire's Configuration Manager for Jira (CMJ), HYCU for Jira Service Management, and others (suggest searching "backup" and "configuration" keywords in the Atlassian Marketplace).
Another possibility is the JSM Copy Product Data feature. If you're an admin, you can find this at admin.atlassian.com > Settings tab > Data management. There's a link on that page to find out more and a "wizard" of sorts to walk you through it. It also works for Confluence spaces, groups, and configs.
Note that if you created new forms in your test project, you can just copy those to the existing "production" project (on the same JSM instance) via "test" Project settings > Forms > click the "..." menu for the form > Copy to project > choose your "production" project
Good luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.