You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Backlog of issues in a project were created with a form that attached to the ticket. Currently, that form is outdated and isn't capturing all the data that is required for the issue. It's requiring manually deleting the forms on each individual ticket (automation can attach the new form to every ticket and the fields will transpose to the updated form) but curious how to create an automation in Jira project settings to get the form to delete on all tickets first if the same form isn't able to added twice.
Hi @Jakob Hernandez , thanks for your question.
You can use an automation, yes, to delete the obsolete forms attached to the tickets.
My question is, how are you creating the tickets now? If you are using the portal, you can personalize the Request type forms or use custom Forms in the JSM project to ask for exactly the information you want, or are you not using the portal for this project?
Hi Valerie - that's correct the forms are able to be personalized and attached to the request view for the request type when customers are on the portal. My previous sentiment was in reference to having an automation that attaches the form whenever tickets are created via Atlassian's add-ons with other tools and not from the JSM project portal. So, these tickets wouldn't be coming from the portal originally but the users submitting the request can follow up in the portal viewing personalized form.
I'll check your solution to use the Deleted attachments in the automation! Thanks!