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
As a form builder I would like to control the usage of the Send/Cancel buttons when a user is filling out a form. For example, I have a comprehensive form with dynamic sections that contain required information. However, when the form is initially displayed, the "Send" button is visible at the bottom of the screen and should not be available.
@Louis Tominack it sounds like you are using the new Forms feature in JSM.
Am I right in thinking that what you want is for the Send button to not be shown until the form is completed/valid? If so I'll take your idea on board and feed it back to the team for consideration.
it is not possible to simply hide these buttons, as these are built into Jira's UI in order to create the request or to back out of the form.
You can however do a few things to prevent the issue from being created unless particular fields are filled in:
Hope this helps!
@Callum Carlile _Automation Consultants_ - Thanks for the feedback. I do have fields set as Required so that should help. I will have to test these options to assess the overall user experience.
I don't fully understand the timing and dynamics between Jira Service Management Request Types, Issue Types, Workflows, and the initial Form. Seems like a lot of moving parts.
@Louis Tominack For your particular use case, I would say that making the field required on the request form should be sufficient - as users won't be able to click on 'Send' without the fields being filled in, and the 'Cancel' button is basically just a back button which takes you to the previous page.
It can certainly be a bit confusing though! In Jira you create workflows, and then you map issue types to this workflow using a Workflow Scheme, which you then associate with a project.
Jira Service Management essentially sits on top of regular Jira, and gives you more capabilities such as the cutomer portal. When creating a request type (a 'form') this is always mapped to a single issue type, so whenever someone goes into a form and submits it,this is still creating a normal issue, however it has a Request Type also associatde to it.
You can also have multiple different request types mapped to the same issue type, and these are then distinguished by the 'request type' field.