Currently the emails sent out by the Request Tracking feature all have a subject line based off of the form name (ie. Re: “Form Name” submission received), leading to a complete lack of clarity on the submitter end as to what request emails are referring to when they have multiple requests in, which is the norm. Ideally the subject line should refer to the task/request title (ie. Re: “Task name”), which would keep it clear and unique.
1 Like
@Christina_Molnar, Don’t forget to click the title to scroll to the top and vote by clicking the Vote button, as I just did; that’s the quickest and most effective way to express your support for a request.
Thanks,
Larry
Yes, would love this too. We have people who submit multiple responses to a form per week (for project intake requests), and they are getting frustrated that all their confirmation emails are essentially in one lengthy email thread from Asana, since there’s no variable data based on their submission inserted into the email subject.
It’d be a huge win if we could customize what that confirmation email subject line is, but at the very least, have it default to incorporate a variable from the submission.
1 Like
I agree this would be really useful to improve clarity.
Voted!
Just FYI, the Forms Support workflow in our Flowsana integration allows you to customize the subject (and body) of the confirmation email, including incorporating data in custom fields mapped from form questions.
1 Like
You’re absolutely right — having all email replies use the form name as the subject line (e.g., Re: “Form Name” submission received) can quickly get messy, especially when a requester has multiple submissions in progress. It makes it hard to track which email thread belongs to which request.
If you’re looking for more flexibility, Hipporello Service Desk for Asana offers a solution designed exactly with this in mind.
With Hipporello, email subject lines are fully customizable.
You’re not limited to the form name — you can configure subjects to include:
- The task title
- Any form field (like requester name, request type, etc.)
- Static or dynamic text (e.g., “Support Request – {{Issue Type}} for {{Full Name}}”)
This makes each email clear, unique, and instantly recognizable for the requester.
Example:
Re: Access Issue – Jane Doe (HR System)
Re: Equipment Request – MacBook Pro for John Smith
All this happens without your team ever leaving Asana — Hipporello turns form submissions and inbound emails into Asana tasks and keeps the conversation going directly from there.
Let me know if you’d like to see a quick demo — it’s all up and running in under 5 minutes.