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.
Since this article was first published, Atlassian has renamed issues to work items, and Smart Forms for Jira has added new automation options—including dedicated Jira Automation actions that attach forms on any trigger. This update covers both, so you'll see "issue" and "work item" used interchangeably below. The Smart Values syntax itself hasn't changed: it still starts with {{issue.…}}.
Let’s break down practical automation use cases by department and show how to map form fields for maximum workflow value.
What Are Smart Values and Why Do They Matter?
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>}}.
Jira Automation Smart Values Cheat Sheet for Form Fields
The Smart Value you need depends on the type of Jira field the form response is mapped to. Use this table as a quick reference:
Form response mapped to | Example | Smart Value |
|---|
Priority | Urgency → Priority | {{issue.priority.name}} |
Due date | Start Date → Due date | {{issue.duedate}} or {{issue.duedate.format("dd/MM/yyyy")}} |
Single-select custom field | Department | {{issue.Department.value}} |
Multi-select or checkbox custom field | Regions | {{issue.Regions.value}} (returns a comma-separated list) |
Text or email custom field | Contact Email | {{issue.Contact Email}} |
Number custom field | Total Cost | {{issue.Total Cost}} — or do math: {{#=}}{{issue.Total Cost}} * 1.2{{/}} |
Labels | Role Type | {{issue.labels}} |
Any custom field by ID | — | {{issue.customfield_XXXXX}} |
Link to an attached Smart Form | Customer Satisfaction form | See "Smart Value to Use in Automation" below |
Tip: select-list fields are objects, so {{issue.Department}} alone won't compare cleanly with a text value—add .value. If a Smart Value comes back empty, add a Log action to your rule and check the output in the audit log.
Getting Started with Smart Form Field Mapping
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
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. For conditions on Smart Values, use the Advanced compare condition; for standard fields such as Priority, the Work item fields condition is enough.
Step 4: Decide how the form reaches the work item
A form can be attached in three ways, and each one opens different automation scenarios:
Auto-Sharing Form Links in Automation
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, automatically using auto-attach rules, or with a Jira Automation action.
Enabling Auto-Share and Auto-Attach
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.
New: Attach Smart Forms with Jira Automation Actions
Auto-attach works on creation. When the form should appear later in the workflow—for example, a satisfaction survey only after resolution—use the Smart Forms actions in Jira Automation:
- Attach Smart Form — attaches one or more forms. They open blank, and the respondent fills everything in.
- Attach Smart Form with values — attaches one form and pre-fills selected form elements with data from the work item, so the respondent opens the form with context already filled in. To pre-fill several forms, add one action per form.
[New image: Jira Automation rule with the "Attach Smart Form" action — real Jira UI]
A typical rule: Trigger: Work item transitioned to Resolved → Action: Attach Smart Form ("Customer Satisfaction") → Action: Re-fetch work item data → Action: Send email with the form link (Smart Value below). Re-fetching makes sure the newly generated form URL is available to the next action in the same rule.
Smart Value to Use in Automation
{{#issue.properties."saasjet.forms.formsSharedUrls"}}
{{#if(equals(formName, "Your Form Name"))}}{{url}}{{/}}
{{/}}
For more ways to send forms by email, see How to Automatically Send Jira Forms to Anyone and how to reference form data and ticket links in confirmation messages.
Use Case 1 – Product Teams: Auto-Assign and Notify Based on Feature Requests
Scenario: A product manager collects feedback via a feature request form. The form includes a field for product area (e.g., Mobile, Web, Backend). The form can be shared externally or embedded on your website as a feedback widget, so customers and internal teams submit through the same intake.
Mapped Field: Product Area → Custom field Product Component
Automation Rule:
- Trigger: Work item created
- Condition: {{issue.Product Component.value}} equals "Mobile"
- Action: Assign the work item to the Mobile Team lead
- Action: Create a linked idea in your Jira Product Discovery project, so the feedback is connected to the roadmap as evidence instead of living in a separate backlog
Read more about feedback flows for JPD in Collect Internal and External Ideas for JPD via Automated Forms and Building a Sustainable External Feedback System for Jira Product Discovery.
Use Case 2 – IT Helpdesk: Route Tickets by Department and Severity
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: Work item created
- Condition: {{issue.Department.value}} equals "Finance"
- Condition: {{issue.priority.name}} equals "High"
- Action: Assign to senior IT agent
- Action: Send escalation email to IT manager
Need to route requests to separate team backlogs instead? See Move Issues to Department Backlogs Based on Form Submissions. To catch bad inputs before they reach the rule, use regex validation.
Use Case 3 – HR Teams: Automate Employee Onboarding Tasks
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: Work item created
- Action: Create sub-tasks (e.g., "Create Laptop Account") and set each sub-task due date to {{triggerIssue.duedate.minusBusinessDays(3)}}, so equipment is ready before the start date
- Action: Attach the onboarding checklist form with the "Attach Smart Form with values" action, pre-filled with the new hire's role and start date
- Action: Send the onboarding checklist to {{issue.Manager Email}}, including the link to the Smart Form
For the full process, see Seamless Path to Employee Onboarding in Jira and Building HR Self-Service with JSM, Rovo, and Smart Forms.
Use Case 4 – Customer Success: Feedback Collection Based on Status and Auto-share satisfaction survey
Scenario: A form captures customer feedback post-resolution—a CSAT survey in Jira. 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.value}} equals "Low"
- Action: Notify CSM
- Action: 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—or attach it at resolution with the "Attach Smart Form" automation action.
- When the issue is created (or resolved), the feedback form is added automatically.
- Use automation to send the survey form URL using the smart value as shown above.
Respondents don't need a Jira account, and you can enable anonymous access for more honest feedback.
Use Case 5 – Legal or Compliance Teams: Auto-Route Form-Based Approvals
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: Work item created
- Condition: {{issue.Region.value}} equals "EU"
- Action: Set priority to "High"
- Action: Notify EU Compliance team
Reminder rule: Scheduled trigger (daily) with JQL duedate = 3d AND statusCategory != Done → send a reminder 3 days before {{issue.duedate}}.
If the approver depends on the answer (region, amount, department), let the form choose them—see Dynamic Approvers: Let the Form Pick the Approver.
Use Case 6 – Finance and Procurement: Approval Thresholds from Calculated Fields
Scenario: A purchase request form asks for quantity and unit price. A calculation field in the form computes the total live, while the requester is filling it in.
Mapped Fields:
- Total (calculation field) → Number custom field "Total Cost"
- Cost Center → Custom field
Automation Rule:
- Trigger: Work item created
- Condition: {{issue.Total Cost}} greater than 5000
- Action: Transition to "Director Approval" and notify the budget owner
- Else: Transition to "Manager Approval"
Learn how to set up the formula in How to Use Live Calculated Fields in Jira Forms.
Use Case 7 – AI-Ready Intake: Form Data for Rovo
Scenario: Your team uses Rovo to search across work and run agents. Structured form data gives agents reliable inputs instead of free-text descriptions.
Smart Forms for Jira integrates with Atlassian Teamwork Graph: form responses are published to it, so they're searchable in Rovo Search and Rovo Chat. Combine that with field mapping and the same submission powers both your automation rules and your AI workflows.
Read more in Agent-Ready Intake in Jira: From Forms to Rovo Agents and Your Rovo Agent Is Only as Smart as Your Jira Data.
Additional Smart Form Features to Enhance Automations
Smart Tips for Building Automation-Ready Forms
- 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
- Add .value for select-list fields and .name for Priority or Status
- Add a Log action while building a rule—the audit log shows exactly what each Smart Value returns
- Use "Re-fetch work item data" after an action that changes the work item if a later action in the same rule depends on that change
- Use default responses so optional fields never reach automation empty
Final Thoughts
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, auto-shared form links, and the new automation actions, you're not just collecting data- you’re launching workflows.
Related Reading
Q&A
Question: What are Jira Smart Values and how do Smart Forms make them useful for automation?
Smart Values are dynamic references to live issue data that you can use in automation conditions and actions. When you map Smart Form fields to Jira issue fields, submitted form data is immediately available to rules via issue fields (for example: {{issue.priority.name}}, {{issue.duedate}}, or {{issue.customfield_XXXXX}}). This lets you auto-assign work, send tailored notifications, update fields, and drive decisions without manual updates.
Question: How do I map Smart Form fields to Jira fields and reference them in rules?
- In the form builder, use “Create New Work Item” to create an issue and map each form question to a Jira system or custom field (for example, map “Urgency” to Priority, “Start Date” to Due date, “Department” to a custom field).
- In automation, reference the mapped values with Smart Values such as {{issue.priority.name}}, {{issue.duedate}}, {{issue.Department.value}}, or {{issue.customfield_XXXXX}} (custom fields can be referenced by name or by their customfield ID).
- Design forms with structured fields (priority, dates, emails, labels) so values cleanly map and resolve in rules.
Question: How can I include a direct link to a Smart Form in an automated email or comment?
You can place the form link manually to your automation rule or automatically. For automatic form including in the rule the form must be attached to the issue first. Enable Auto-Attach in Smart Forms settings (by Project and Issue Type) so new issues get the form automatically, or use the "Attach Smart Form" automation action on any trigger. Then, use the shared-URL Smart Value in your automation content: {{#issue.properties."saasjet.forms.formsSharedUrls"}} {{#if(equals(formName, "Your Form Name"))}}{{url}}{{/}} {{/}} Smart Forms generates a unique, shareable URL as soon as it’s added to an issue, so your emails, comments, or notifications can include a live link to the correct form.
Question: Can I attach a Smart Form to a work item with Jira Automation?
Yes. Smart Forms for Jira adds two actions to Jira Automation: "Attach Smart Form" attaches one or more blank forms, and "Attach Smart Form with values" attaches one form pre-filled with data from the work item. Both work with any trigger—creation, transition, field change, or schedule.
Question: Why does my Smart Value for a select field return nothing or fail the condition?
Select-list custom fields are objects. Use {{issue.FieldName.value}} instead of {{issue.FieldName}}. For Priority and Status, use .name. Add a Log action to the rule to see what a Smart Value returns in the audit log.
Question: What are some practical automation examples by team?
- Product: If Product Area (mapped to a custom “Product Component”) is “Mobile,” auto-assign to the Mobile lead and create a linked idea in Jira Product Discovery.
- IT Helpdesk: Route Finance + High priority tickets to a senior agent and email the IT manager.
- HR: On issue creation, create onboarding subtasks with due dates 3 business days before the start date, attach a pre-filled checklist form, and email it to {{issue.Manager Email}}.
- Customer Success: When Status = Resolved and Satisfaction = Low, notify the CSM and send a follow-up CSAT survey to {{issue.Contact Email}}; auto-attach and auto-share the survey form.
- Legal/Compliance: If Region = EU, set Priority = High, notify the EU Compliance team, and schedule a reminder 3 days before {{issue.duedate}}.
- Finance: If a calculated Total Cost is above a threshold, route the request to director approval.
Question: Can Rovo use data from Smart Forms?
Yes. Smart Forms for Jira integrates with Atlassian Teamwork Graph, so form responses are searchable in Rovo Search and Rovo Chat.
Question: Any tips and features to make forms more automation-ready?
Smart tips:
- Name fields clearly so their Smart Values are recognizable.
- Keep form field types aligned with target Jira fields (dates to dates, selects to labels, etc.).
- Use help text and validation to prevent bad inputs.
- Test with sample issues to confirm values resolve in rule previews.
Helpful features:
- Conditional logic to show/hide fields and collect only relevant data.
- External sharing for intake from vendors/partners.
- Anonymous submission for surveys/feedback.
- Pre-fill to pull existing issue values into the form.
- File upload to capture attachments and process them in automations.
- Calculation fields, hidden fields, and dynamic approvers for threshold-based and routed approvals.
