Hi,
Is it possible to programmatically modify the form submission success page?
Background: I have a Jira automation rule that populates a new ticket's description with a description template.
Use case: for forms that create tickets (ticket template forms), I would like to redirect a user to the ticket so they can populate its description.
A similar question [1] was asked in the past, but I would like to know if I can achieve this programmatically myself (e.g. through a form submission webhook).
Thanks for getting back to me.
I can see what it is you want to do, and it is a shame you can't natively show templates on a form field.
My suggestion was going to be splitting these into individual custom fields on the form and bringing them all back into the single description field via smart values. But as you said you don't want to create custom fields that idea is out of the window.
Thanks.
Aaron.
Sorry, Aaron, you have misunderstood. This post is to find out how I can programmatically modify the page Jira shows after a form is submitted.
Do you know how that could be achieved?
I am not trying to avoid having to edit the description field with a template. That was background information to support that these Jira Cloud native forms are purely for issue creation (that's all they can do).
Thanks for your efforts,
Toby
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.
Hi Aaron,
Firstly, thanks for responding to this.
Since posting the question, I have created a native Jira Cloud form (under the 'Forms' board tab) for each issue type. When any of the forms are submitted, an automation rule sets the new issue's description to a template (see a shortened version below as an example) and then emails the reporter a link to their ticket.
That solution works fine, but the context switching is disappointing and wouldn't be ideal for getting my team to adopt the forms I created (to make ticket creation as easy as possible for them).
Please note that I am not looking to create custom fields to shorten the description template, which I have provided below to illustrate my use case.
Thanks,
Toby
Go
Go
Tips: mention user journeys if relevant, provide test data or its location.
Go.
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.