How to Set Up Form and Email Intake in Jira — A Lightweight Service Desk Without Full ITSM

[#1]

Disclosure: I'm Lara, Community Manager at Hipporello. We build Marketplace apps that extend Jira and Trello. This post describes our own product as a solution to a common use case. I've done my best to keep it practical and informative.

How to Set Up a Lightweight Service Desk in Jira (Without Full ITSM Complexity)

The Problem We Keep Seeing

If you've spent any time in this community, you've probably come across threads like these:

"I just need a way for external users to submit requests into my Jira project."

"We don't need full ITSM — just forms, email intake, and a way to reply to customers."

"Why do I need to set up an entire service management project just to collect requests?"

These are legitimate needs. Not every team needs ITIL-aligned workflows, change management, or complex configuration. Some teams — marketing, HR, operations, customer support in smaller organizations, or non-profits — just need the basics done well:

• A form people can fill out
• An email address that creates tickets
• A branded portal that is easy to customize and manage
• The ability to communicate with requesters from inside Jira
• Basic automations (auto-acknowledgment, assignment rules, etc.)

If you're part of a team with similar needs, this guide is for you.

How Hipporello Approaches This as a Lightweight Service Desk

For teams that find Jira's native request-handling options too limited for their needs, Hipporello Service Desk for Jira offers a focused alternative built to handle request management without full ITSM overhead.

It covers the essentials most teams actually need:

• Flexible request intake through forms, email, and embeddable forms — no complex setup required
• A customizable, branded portal that's easy for non-technical users to navigate
• Built on Jira, so requests become Jira issues and your team keeps using familiar workflows
• Two-way communication with requesters directly from Jira, with automatic notifications
• Lightweight automation like auto-acknowledgments and assignment rules
• SLA management to define and track response or resolution targets

Step 1: Install Hipporello Service Desk for Jira

You can find it on the Atlassian Marketplace. Installation takes about two minutes. Once installed, it connects to your Jira project and adds a service desk layer on top of your existing setup.

How it works at a high level:

• Edit and publish forms on your user portal. Define inbound email addresses.
• Receive form submissions and email messages into Jira as new issues.
• Communicate with requesters from inside the created Jira issues.

▶ Watch: Getting started overview

Step 2: Create Your First Form

Hipporello includes a drag-and-drop form builder. You can create forms for different request types — IT support, marketing requests, HR inquiries, customer feedback, or order processing. Each form maps directly to Jira issue fields, so submissions automatically become properly structured Jira issues.

▶ Watch: Creating your first form

A few things worth highlighting:

• Forms can be public — no login or Atlassian account required for submitters.
• Form fields map to both standard and custom Jira fields — so issues arrive pre-populated with the right data.
• You can embed forms on your own website or share them via a direct link.

Step 3: Set Up Email-to-Jira

Hipporello gives you two ways to connect email to Jira:

• Native OAuth connection for Microsoft and Google — connect your existing Microsoft 365 or Google Workspace email account directly. Hipporello handles the OAuth flow, so your team's support address (e.g., support@yourcompany.com) feeds straight into Jira. No mail handler configuration or manual token management.
• Email forwarding — if you prefer not to connect your mailbox directly, or you're using a different provider, you can set up forwarding from your existing address to a Hipporello-provided address. Emails land in Jira as issues automatically.

Either way, the result is the same: incoming emails become Jira issues, replies from your team go back to the requester as email responses, and the entire conversation stays threaded in one place.

▶ Watch: Setting up email-to-Jira

How this differs from Jira's native email handler: With Jira's built-in mail handler, if a sender isn't a licensed Jira user, you typically need to create a default reporter account. That means the issue gets attributed to the default reporter account rather than the person who actually sent the request. With Hipporello, anyone can send requests without a Jira account, the actual sender is captured as the reporter, and you get a two-way conversation thread inside the Jira issue.

A couple of other differences compared to Jira's native email handling:

• Route emails to different projects based on conditions — Jira's native mail handler is locked to one project per handler. Hipporello lets you set up rules to route incoming emails to different projects automatically.
• Map email fields to custom Jira fields — Jira's native handler maps subject to Summary, body to Description, and email priority to issue priority, but there's no built-in way to populate custom fields from email content. Hipporello lets you map subject, sender, and body to custom fields as well.

Your requesters keep using email exactly as they always have. Your team works entirely inside Jira.

Step 4: Customize Your Portal

Hipporello gives you a customizable user portal. Here's what you can configure:

• Add your company logo, colors, and cover image
• Write a custom welcome message
• Publish multiple forms on the same portal
• Add knowledge base articles for self-service
• Control access (public vs. restricted)
• Set up a custom domain (e.g., support.yourcompany.com)

▶ Watch: Customizing your portal

Requesters see a clean, branded interface — which makes a noticeable difference for customer-facing use cases where you want a professional experience.

Step 5: Communicate from Inside Jira

When a request comes in (via form or email), it becomes a Jira issue. Your team can respond to the requester directly from the issue's built-in communication panel. The requester gets the response in their inbox or portal. Replies come back as comments on the Jira issue, so the entire conversation history lives in one place.

▶ Watch: Two-way communication from inside Jira

Who Is This For?

This approach works well for teams already using Jira that want to add request intake without adding complexity. Common use cases:

• Internal IT help desks for smaller teams that don't need full ITSM
• Marketing request intake — creative briefs, campaign requests, content reviews
• HR onboarding and employee requests — equipment, access, policy questions
• Customer support for SaaS products and small businesses
• Order processing and operations — intake forms for orders, returns, service requests
• Non-profit volunteer coordination — applications, scheduling, task assignments
• Feedback management — collecting and tracking product feedback or complaints

---

Get Started: You can install Hipporello Service Desk for Jira from the Atlassian Marketplace. There's a free plan to try it out, plus a 14-day trial of Premium features. For pricing details, see our Marketplace listing.

I'm happy to answer questions in the comments.