Skip to main content
Skip table of contents

Auto-attach form to issues

This feature enables you to automatically attach a form to specific Jira issue types upon creation. It ensures forms are consistently added based on project and issue type configuration, eliminating the need for manual setup and promoting standardized data collection across your Jira instance.

How Does It Work?

  1. Configure Form Rules: Specify the projects and issue types where a particular form should be auto-attached.

  2. Create an Issue: When a new issue of the configured type is created, the form is automatically attached to it.

  3. Fill Out the Form: The user sees the form immediately within the issue and can begin filling it out without any additional setup.

  4. Submit the Form: The form can update the issue’s fields or trigger the creation of new issues (if configured).

  5. Reuse & Automation: The same configuration applies each time such an issue is created, ensuring uniformity.


Things to Keep in Mind

  1. Form Reuse After Creation

    • Any issue created with this rule will always receive the pre-configured form unless the rule is removed.

  2. Field Updates and Issue Creation

    • If you’ve enabled "Update existing issue fields" or "Create a new issue" settings, these actions will apply to auto-attached forms as well.

  3. Drafts and Versions

    • Auto-attached forms support draft saving, version history, and duplication inside the issue.


How to Set It Up

Step 1: Create or Use an Existing Form

  • Open the Smart Forms for Jira.

  • Click + Create form or choose an existing form from your list.

Step 2: Configure Auto-Attach Settings

  • Go to the Settings tab of the form.

  • Click Add to issues automatically.

  • In the modal window, select the desired projects and issue types.

    Screenshot 2025-06-10 at 11.58.39.png

Step 3: Trigger the Rule by Creating an Issue

  • Create a new issue in a configured project using the selected issue type.

  • The form will be automatically attached and visible within the issue.

Step 4: Work with Form

  • Users can:

    • Save the form as a draft

    • Submit it to trigger field updates or issue creation

    • Export the responses to Excel/PDF


Usage Scenarios

🔄 Standardized Bug Reporting

Use Case: Ensure that every Bug issue includes a detailed intake form.

How It Works: Automatically attach a "Bug Report" form to all new Bug issues in development projects.

Example:

  • Fields: Affected Module, Steps to Reproduce, Screenshot Upload

  • Benefit: No bugs get reported without critical reproduction data.


📝 Onboarding Task Tracker

Use Case: Ensure that onboarding checklists are applied to every new task for new hires.

How It Works: Attach an onboarding checklist form to each “Task” created in the HR project.

Example:

  • Fields: Access to tools, Welcome call scheduled, Office space prepared

  • Benefit: Consistency in the onboarding experience.


💼 Project Intake Form

Use Case: Standardize the initiation of projects by collecting scoped data upfront.

How It Works: Forms auto-attached to “Project Request” issue types gather information about goals, budget, and timeline.

Example:

  • Fields: Project Name, Department, Estimated Budget

  • Benefit: Ensures all necessary information is collected at project creation.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.