Remove Form Submit Button

[spacesas]

Hi,

We have setup change requests using a form attached to the change request type. After initial submission the issue goes to a "Plan" (Not Started) status where pre-populated fields are updated and the user can edit the request before sending off to CAB etc.

The issue we are facing now with the "Open for edits" form is that there are two different Submit buttons (screenshots attached):

• Save/Submit buttons at the bottom of the form
• Workflow submission button

The form submission doesn't do anything other than save changes and close the form from edits. The only way to progress the request is through the request submission button at the top right of the portal page.

I could not find a way to resolve this through automation as the only form trigger is "Form Submission" however the form is already initially submitted but open for edits and this trigger doesn't work when the user closes edits.

This is causing confusion due to the redundancy of "Submission" buttons, is there any way to hide the form buttons or automate the request to progress through them?

[Olha Yevdokymova_SaaSJet]

Hello @spacesas !

For managing change requests, Smart Forms for Jira, developed by my team, could offer some helpful features to help. Here are a few ways it can help address your setup and requirements:

1. Form Submission and Draft Management: Once a form is submitted, however, it becomes locked from further edits to ensure a secure, unalterable record.  Unlike the native forms, Smart Forms for Jira allows users to save drafts and access draft history. 

2. Change Issue Status After Form Submission: Unlike native Jira forms, Smart Forms for Jira allows you to change the issue status automatically after a form is submitted, without needing additional automation. This could eliminate the need for the “Workflow submission” button and help requests move smoothly through your workflow.

3. Field Mapping and Automation: With Smart Forms for Jira, you can map form fields directly to Jira issue fields. This mapping allows the form data to be used in Jira automation, making it easy to change the issue status or trigger specific actions based on form submissions—ideal for progressing requests through change management workflows.

4. Flexible Form Placement: You can add Smart Forms to Jira Service Management (JSM) as a secondary form within a request or link it under Related Resources. This flexibility allows you to include additional forms at various stages of your workflow, such as CAB review, and position them based on user needs.

5. External Sharing Options: Smart Forms for Jira can be shared externally via a link or added to issues in Jira Software or Work Management, either manually or automatically (based on conditions). This is helpful if you need to collect information from external users or stakeholders who don’t have Jira access.

These features make Smart Forms for Jira a versatile tool for forms and requests in Jira, offering options to configure form-based issue progression, control data edits, and integrate with external users where needed.

Let me know if this helps or if you have other questions!

[Tomislav Tobijas _Koios_]

Hi @spacesas ,

Sadly, there's no way to hide the submit buttons at the bottom of the forms (at least I'm not aware of it). Here's a feature suggestion for this functionality: JSDCLOUD-11465 JSM Forms: Bring back the option to hide the submit button on the portal 

On this note:

I could not find a way to resolve this through automation as the only form trigger is "Form Submission" however the form is already initially submitted but open for edits and this trigger doesn't work when the user closes edits.

I've just tested this and it seems that if the customer selects Submit button (so, closes the form) automation will be triggered if you use Forms submitted trigger.

Also, it seems to work in case the form is submitted, reopened by an agent and then submitted again by the customer.

Please correct me if I'm wrong, but you're saying that this isn't working on the instance you're testing?

Cheers,
Tom

[spacesas]

Apologies for the delayed response.

I have now managed to figure it out, and you were correct the form submitted trigger did start working. Not really sure what I was doing wrong the first time around but it works now.

Just created an automation to transition the issue if the form is submitted ("Closed") so both buttons now progress the change request. Still not ideal as it's redundant but at least solves a part of the problem.

Thanks.