Hidden fields are a powerful way to pass metadata, track context, and automate processes behind the scenes—without overloading your users with too many questions.
But Jira’s support for hidden fields varies depending on the product you’re using — and the way you collect data.
Let’s break down how hidden fields work in Jira Service Management, what’s not available in Jira Software, and where an add-on like Smart Forms for Jira can fill in the gaps.
Why Hidden Fields?
Hidden fields allow you to:
Pass internal metadata without asking users
Trigger Jira automations behind the scenes
Record where a form came from (campaign, department, project)
Segment submissions by source or intent
- Reduce human error by removing fields the user shouldn’t touch
Not sure whether your data belongs in a hidden field or a visible one? Start here: Designing Jira Intake in 2026: When to Use a Field vs. a Form.
Are Hidden Fields Available in Jira?
Jira Service Management (JSM)
How hidden fields work in Jira Service Management
Yes - Jira Service Management supports hidden fields in the portal view, meaning:
You can hide a field from the customer.
Set a default value that will be submitted with the request.
Use section logic (on Jira Cloud) to control conditional visibility of fields.
However:
You can’t prefill fields dynamically (e.g., via URL parameters).
Hidden fields are only supported within the portal forms — not on shared forms or issue views.
They don’t exist in Jira Software or Jira Product Discovery.
Jira Software
Jira Software does not support hidden fields in native forms. If you're trying to gather internal info invisibly or use conditionally displayed logic — you’ll need a third-party solution.
Smart Forms for Jira doesn’t reinvent hidden fields — it provides a consistent way to create hidden fields across Jira, including:
Jira Software
Jira Service Management
Jira Product Discovery
While hidden fields in Smart Forms behave similarly to native JSM hidden fields, Smart Forms unlocks use across more Jira products and contexts, such as:
Forms shared via public or internal links
Forms embedded in issues (in any project)
Forms used outside the portal (e.g., internal requests, onboarding)
Additionally, Smart Forms allows:
Hidden fields to be prefilled with URL parameters
Mapping hidden field values to Jira fields
Using hidden values in automation rules
Full history of submitted values in the Responses tab
This means your hidden data can still be used, tracked, and acted on — even if it’s not shown to the user.
🔧 How URL Parameter Prefilling Works in Smart Forms
Want to track campaign source or internal team ID? Use a form link like:
<span><a href="https://smart-forms.saasjet.com/external?token=abc&uteam=marketing&source=linkedin" target="_blank" rel="nofollow noopener noreferrer">https://smart-forms.saasjet.com/external?token=abc&uteam=marketing&source=linkedin</a></span>
You can set hidden fields to capture values like:
…and map them to internal Jira fields or just keep them in your form records.
This makes it easy to use one form across different teams or campaigns — and still know where each submission came from.
This works for hidden fields, but you can also pre-fill visible fields with existing Jira data — see How to Automatically Pre-Fill Jira Forms with Work Item Data.
Create a new form
Add a Hidden Field → set a default value
Optionally map the hidden field to a Jira field (e.g., label, component)
- Submit → hidden data goes into the issue or triggers automation
NEW Jira Automation for Forms: Attach the Right Form at the Right Moment
Works across:
Jira Software
Jira Service Management
Jira Product Discovery
Data Center + Cloud
🔗 Using URL Parameters to Pre-Fill Hidden Fields
Smart Forms for Jira supports pre-filling hidden fields using URL parameters, so you can customize the form behavior based on where the form is shown or how it’s shared.
How It Works:
If your form has a field with Field Key = source, you can use this format of link:
<span><a href="https://smart-forms.saasjet.com/external?token=abc&source=webinar" target="_blank" rel="nofollow noopener noreferrer">https://smart-forms.saasjet.com/external?token=abc&source=webinar</a></span>
Even if the source field is hidden, Smart Forms will:
📌 You can pre-fill:
Text fields (e.g., campaign=Q4Launch)
Select fields (e.g., team=HR)
Hidden fields (as shown above)
User pickers (e.g., manager=john.doe@example.com)
Date fields (e.g., startDate=2025-10-01)
Real-World Use Cases
Internal Operations: Employee Requests
For a full HR intake setup, see Building HR Self-Service with JSM, Rovo, and Smart Forms.
Marketing Campaigns: Lead Collection
Use Case: A product demo request form is placed on 3 different landing pages (ads, email, website).
Hidden Field: "Source = Email Campaign Q3"
Purpose: Track lead source inside Jira without asking users to self-report.
IT Support: Dynamic Request Routing
Use Case: You have a single “Help Request” form but want to route to different teams (HR, IT, Facilities) based on where the form is embedded.
Hidden Field: “Team = IT”
Purpose: Automatically assign or label the issue, or route it to the correct project.
Product Feedback & Idea Intake
Use Case: Users submit product ideas from different locations: the app, website, or email footer.
Hidden Field: “Feedback Source = In-App Widget”
- Purpose: Segment submissions in Jira Product Discovery for prioritization or analysis.
More ways to route ideas into Jira Product Discovery: 4 Practical Ways to Collect JPD Ideas from Everyone.
Legal & Compliance: Audit Trails
Use Case: A finance form is submitted for audit logging.
Hidden Field: “Submitted By Department = Finance” or "Form Version = v1.2"
Purpose: Ensure traceability and internal control without relying on manual input.
Final Thoughts
If you’re looking to:
…then hidden fields and pre-filled parameters are your secret weapons.
Smart Forms for Jira makes this easy—with full compatibility across Jira Cloud, Data Center, Software, Service Management, and Product Discovery.
Want to try it out? Start by embedding a Smart Form with a hidden “source” field and watch your processes get smarter—automatically.
