Forms for Jira makes data collection simple—but the real transformation begins when that data fuels automation.
Whether you're a Jira Software user managing sprint planning, or an HR lead using Jira Work Management to onboard new hires, mapped form fields (converted into Smart Values) unlock a new layer of efficiency.
Let’s break down practical automation use cases by department and show how to map form fields for maximum workflow value.
Smart Values are dynamic references that pull live data from Jira issues into your automation rules. They allow you to make decisions, send custom notifications, and update fields—all automatically.
When paired with Smart Forms for Jira, form data submitted by users is seamlessly mapped into Jira issue fields and immediately available for use in automations via {{issue.fields.<fieldName>}}
.
Step 1: Design your Smart Form
Include structured fields like priority, due dates, affected systems, and contact emails.
Step 2: Map fields to Jira issue fields
Use the "Create New Work Item" setting in the form builder to create new issue and to map form resposnes to Jira system or custom fields.
Step 3: Leverage Smart Values in Automations
Use Smart Values like {{issue.priority.name}}
, {{issue.duedate}}
, or {{issue.customfield_XXXXX}}
inside automation conditions and actions.
To include a direct link to a Smart Form in your Jira automation (e.g., in email notifications), the form must be attached to the issue. This can be done manually or automatically using auto-attach rules.
Smart Forms generate a unique, shareable URL as soon as they are added to a Jira issue.
To auto-attach a form to an issue type (e.g., for customer requests), go to the Smart Forms settings and configure Auto-Attach based on Project and Issue Type.
{{#issue.properties."saasjet.forms.formsSharedUrls"}}
{{#if(equals(formName, "Your Form Name"))}}{{url}}{{/}}
{{/}}
Scenario: A product manager collects feedback via a feature request form. The form includes a field for product area (e.g., Mobile, Web, Backend).
Mapped Field: Product Area → Custom field Product Component
Automation Rule:
Trigger: Issue created
Condition: {{issue.Product Component}} = "Mobile"
Action: Assign issue to the Mobile Team lead and post in #mobile-roadmap Slack
Scenario: IT team uses a form to intake internal tech requests with fields like “Department” and “Urgency”.
Mapped Fields:
Department → Custom field
Urgency → Jira Priority
Automation Rule:
Trigger: Issue created
Condition:
{{issue.Department}} = "Finance"
{{issue.priority.name}} = "High"
Action:
Assign to senior IT agent
Send escalation email to IT manager
Scenario: HR submits an onboarding form with fields like “Role Type”, “Start Date”, and “Manager Email”.
Mapped Fields:
Role Type → Label
Start Date → Due Date
Manager Email → Custom field
Automation Rule:
Trigger: Issue created
Actions:
Create sub-tasks (e.g., "Create Laptop Account")
Send onboarding checklist to {{issue.Manager Email}} include the link of Smart Form with onboarding checklist
Set issue due date as {{issue.duedate.minusBusinessDays(3)}}
Scenario: A form captures customer feedback post-resolution. Data like “Satisfaction Level” and “Contact Email” are critical.
Mapped Fields:
Satisfaction → Custom field
Contact Email → Custom field
Automation Rule:
Trigger: Status = Resolved
Condition: {{issue.Satisfaction}} = "Low"
Action:
Notify CSM
Send follow-up survey link to {{issue.Contact Email}}
Bonus Flow: To ensure forms are added and shared properly:
Configure feedback form to auto-attach to the "Customer Request" issue type.
When the issue is created, the feedback form is added automatically.
Use automation to send the survey form URL using the smart value as shown above.
Scenario: A compliance request form includes fields like “Region”, “Regulatory Type”, and “Due Date”.
Mapped Fields:
Region → Custom field
Regulatory Type → Labels
Due Date → Jira Due Date
Automation Rule:
Trigger: Issue created
Condition: {{issue.Region}} = "EU"
Action:
Set priority to "High"
Notify EU Compliance team
Schedule reminder 3 days before {{issue.duedate}}
Feature | Benefit in Automation |
---|---|
Conditional Logic | Show/hide fields dynamically to gather relevant info |
External Sharing | Intake from users outside Jira (vendors, partners) |
Anonymous Submission | Allow surveys or feedback without identity barriers |
Pre-fill Fields | Use existing issue fields to pre-populate form values |
File Upload | Automate file or screenshot intake attached to work item |
Name fields logically so their mapped field names are recognizable in Smart Values
Keep form field types consistent with their destination Jira fields
Use help text and validation to avoid bad inputs that break automations
Use test issues to preview how values map and resolve in automation previews
Whether you're leading product strategy, running support, or managing cross-functional projects—your form data shouldn't live in isolation. With Smart Forms for Jira and field mapping, every response becomes a trigger for action.
By combining Smart Values with powerful automation and auto-shared form links, you're not just collecting data—you’re launching workflows.
Ready to start building smarter workflows from form submissions? → Try Smart Forms for Jira Cloud and Data center today.
Olha Yevdokymova_SaaSJet
Product Marketing Manager
SaaSJet
Ukraine
17 accepted answers
0 comments