I have a business need to hand off a JSM form from one project to another.
The new JSM Forms make the UX alot simpler for our customers but I'm having trouble when I need to hand a 'form' off from one project to another.
This scenario doesn't happen often but it happens afew times a month.
I've tried tweaking the Jira Form settings to ensure it creates a PDF (thinking that the automation could forward the PDF as an attachment) but that didn't work
I've tried creating an identical form in both projects but I think because not all of the Jira Form fields are linked not everything is being migrated
I've tried using the 3rd Party App "Backbone" and whilst that came close I still can't get it to work.
As a minimum what I need is
And before anyone asks, I've looked at all of the Jira Forms documentation and I cannot find a solution to my problem
@Anthony R
This is Umer from K15t, the creators behind Backbone Issue Sync for Jira.
I am sorry to hear that you are having a tough time syncing JSM with your internal instance, especially about how Backbone couldn't really fit your use case.
Could you maybe elaborate a little more on what kind of error(s) you ran into when trying to sync the 2 internal projects?
And if you want to discuss your specific use case with us or require a demo, let us know via support.k15t.com or book a demo here.
Regards!
Hi @Umer Sohail _K15t_ Thanks for getting in touch.
Please Note, After more investigation I believe there's an underlying issue with Jira forms on my cloud instance, as it is not allowing me to generate the forms as PDF attachments to a job (as it's supposed to). So I've raised the issue with Atlassian and they are investigating.
Once I hear back from them I'll let you know how I go.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Anthony R
Wish you all the best and hope you can resolve the problem soon! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Anthony R,
I am Marlene from codefortynine.
It is also possible to clone and move tickets (including forms) with our Jira cloud app Deep Clone for Jira.
To clone and move a ticket including "forms" and "attachments", you simply would have to:
It is also possible to trigger a Deep Clone on a workflow transition or integrate it with Jira Automation.
If you have feedback or questions about our app, don't hesitate to reach out to us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Marlene Kegel - codefortynine ,Is this post-functionality still working? I have Deep Clone set up as you show above, yet my forms still don't copy fromService Management projecttoSoftware Management project"
EDIT: For anyone reading this, Deep Clone does work perfectly for this. My issue was user error, or failing to publish my edited post function prior to testing 🤦🏻♂️
Thanks,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mark Ellis,
I am happy to read that your issue was solved. Thank you for updating your reply to share that.
You can also reach out to us directly, if you experience an issue with Deep Clone for Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Anthony R
If you really want to stick with Automation, I would recommend adding a screenshot of your rule so some of the Automation experts on Community can give you some pointers on fixing your rule (which on paper should work if the form is an attached PDF).
But I'll mention that the app Elements Copy & Sync just released the compatibility with forms (FYI, I work for the vendor) and for a classic case of escalating an issue from JSM to a software project, you can just add Jira Forms to the list of things you want to copy over to the new issue.
This is what it looks like to configure (I also activated the synchronization so if the form changes on the original request the dev team automatically sees it):
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.