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
To give some context on how we are using Forms with JSM. We are completely replacing the request form section of our Request Types with Forms. Having to create a custom Jira fields every time we want to ask a different question is extremely tedious and creates a ton of fields that we really don't need to be Jira fields because we don't need to track the data beyond that one request. Also the fact that you can't rename the fields in the agent view like you can in the request form view means you have to be incredibly mindful of the fields when you are creating them.
The Forms interface is just so much easier to work with and we don't need every single question to be a custom Jira field. Whenever we DO want field data retained and reportable, we will create it and link it then as needed. Also it allows us to have dynamic content, which is huge for keeping requests simple for our employees to read and follow.
There are a handful of constraints that we are running into at the moment that I hope gets addressed. If anyone knows if there is an active feature request open for any of these, please let us know in a comment so I and other can go upvote it.
Honestly I hope that they complete replace the current Request Type mechanics with Forms entirely as long as they move all the current capabilities into Forms.