Attach a form to a Jira issue

Attaching a form to a Jira issue serves the purpose of gathering information or facilitating additional tasks within the context of a Jira issue. There are two distinct methods available for adding a form to a Jira issue:

1. Auto-attach form to issues: Adding one or multiple forms to a Jira issue automatically is beneficial in situations where you require a specific form to be attached instantly upon creating a particular type of Jira issue. Read more.

2. Manual-attach form to issues: The manual method of adding a form to a Jira issue enables you to personally include one or multiple forms in a designated Jira issue. This gives you control over the process. Read more.

Forms statuses & Draft History

When a Form template is incorporated into a Jira issue, it assumes one of three statuses:

• New: This status designates a freshly added form.

Forms in the "New" status can be duplicated in issue. To add multiple identical forms to an issue, first, add one form and then duplicate it as many times as needed.

Deletion is possible for forms in the "New" or "Draft" statuses.

• Draft: A form in "Draft" status has been saved with its elements partially filled but has not yet been submitted. Also, this status gains access to Draft History. In Draft History, it is available to review past draft versions to see changes made or restore a specific version.

The add-on automatically saves form progress as a draft after 30 seconds of inactivity. This feature, similar to draft, periodically saves filled input but with a key difference: instead of creating a new draft each time, it updates the most recent one (unless there wasn't a draft already).

Submission is only allowed for the most recent version of the form, but you have the option to Restore a specific version and submit it if needed.

Deleted attachments cannot be recovered.

• Submitted: This status indicates a form that has been successfully submitted. At this point, you can export the submitted data. Draft History is accessible in this status as well, but only for review purposes.

After submission, a form cannot be deleted, reopened, or restored in Draft History.

Instruction of Forms statuses and Draft History usage

1. Open the add-on and either create a new form or use an existing one.

2. Add the form to a Jira issue using your preferred method, whether it's Automatic Form Addition to a Jira issue or Manual Form Addition to a Jira issue. The form will initially be in the "New" status.

   1. If there are unnecessary forms in the issue, you can delete them by selecting the delete button next to the respective form.

      

3. Begin filling out the form. Afterward, you have two options:

   

   1. Save the Form as a Draft: This allows you to save the form in its current state to return and complete it later. When saved as a Draft, you gain access to Draft History, where you can view all versions of the partially filled form.

      

      You can open and review past draft versions to see changes made or restore a specific version. To return to filling out the form, simply click on the Draft History button.

      

      Additionally, consider exploring the use case of Sending prefilled forms to users outside Jira.

   2. Submit the Form: When you're done working on the form, you can submit it. Once submitted, you can only open the form, review the Draft History, and export the submitted data. Therefore, ensure that no further changes are required for completed forms.

      

If you need help or want to ask questions, please contact us through SaaSJet Support (Time of the First Response ≤ 4 hours) or via email support@saasjet.atlassian.net

Haven't used this add-on yet, then try it now!