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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are using the ProForma Forms add-on. When a form is integrated in the request the mandatory fields "summary" and "description" can be hide but need to be pre-filled. These leads to allways the same summary even if the form data of each request may differ due to options in the form what results in different types of request.
Is there a way of hiding the summary field but filling it with content depending on selections of the regarding form selections?
Summary 1: Standard Service Request: Create a new account
Form section 1: new users first name, last name ....
Summary 2: Standard Service Request: Modify an existing account
Form section 2: account name, changed data
Summary 3: Standard Service Request: Delete an existing account
Form section 3: name of account tot delete
Before you ask: The selections/options are all in one request/form. We don´t want to split in three different requests, each with each own form.
This question goes in a similar direction: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Can-I-set-my-summary-field-based-on-data-from-proforma-forms/qaq-p/2221524
But solves not mine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.