This is a big step forward. Two key questions for our use case:
Is there any workaround for people in our org to create requests via email? Our current helpdesk ticketing system operates exclusively off of email ticket creation, and we cannot change the user experience by requiring a form. If we had an Asana user called “Helpdesk” and set up a forwarding rule from that inbox to the Asana Project email, could the original requester be tracked and notified via comments?
We are on a Legacy plan (Business) - any idea if we could get the feature applied to our account by asking nicely or how expensive an upgrade to Advanced would be?
Hi @Kevmoore , I’m not sure about your 1st question (I doubt it is possible) but for your 2nd question, I very much doubt it even if you ask really nicely. But the cost of Advanced is the same as Business, and you will eventually be migrated at some point.
Hey everyone! We had 2 different people in our org try this (non-Asana users, but have a matching domain for our account), but when they click “verify email address”, it just takes them both to a spinning screen. Has anyone else experienced this? Seems like a bug.
It doesn’t need to exist in the organization; it just has to have the same email domain.
Again, it’s not doing any validation at that point; it’s just going to send an email with an authorization code to the address you enter (if it works right, that is, and doesn’t just spin).
So it seems there is an issue on the Asana end that you and @Jess_deCsesznak ran into. @Forum-team maybe you can raise this issue internally?
(Although in your case, @Ka_Nishiyama, if it’s not a valid email address that can receive an authorization email from Asana, even if you got past the spinning cursor you wouldn’t be able to actually test the full flow of the feature.)
Thanks for reporting this @Jess_deCsesznak! I had a look but we haven’t receive similar reports before, I feel it would be better to create a support ticket as @lpb recommended, this way we could see what is the error you are hitting.
When reaching out, make sure to provide them with the following info, it will facilitate their investigations:
URL of this thread (so you don’t have to re-explain everything from scratch
If possible, a screencast illustrating the issue. Make sure to have your Javascript console open. if you’re using Chrome, you can refer to the following article to open your Javascript console (Chrome DevTools - Chrome Developers)
Sorry for not being able to resolve this specific issue via the forum. If you have any other question in the future feel free to reach out here, in most cases we will be able to resolve your issue, and if not, we’ll be able to redirect you to the right place
Similar to @Thomas_Hartmann, I would love to see Request Tracking features available for additional scenarios. Specifically, on tasks created via email. Bidirectional communication with (non-Asana) requesters is a frustratingly elusive feature for project/task management platforms. Asana gets so close with Request Tracking, but it currently lacks functionality for tasks created via email.
Hi Emily,
I know I’m extremely late to the party here, but my organization recently adopted Asana this year and the area I support just made the transition over from Workfront on the 12th. My area serves our entire corporation, so the transition hinged on this feature in particular so thank you for rolling it out! One major issue we’ve had come up repeatedly- while your example screenshot shows a very clear subject line (Re: Device Request: Monitor R&D > $1K) ours have come out extremely vague and based off of the form name (Re: Strategic Services Submission Received), which has lead to pretty valid complaints from users that it’s very difficult to know which request emails are regard to, as most have multiple requests ongoing. I cannot for the life of me find a setting that allows me to change it however. I am entirely likely to be overlooking something since I’m so new to Asana, so I’m hoping I could get a little guidance on that front.
We were a little late to testing this feature out and we’ve run into a very weird scenario.
For context and reference, these are the three pages you are taken to in the authentication flow:
Page 1: Initial landing page where you enter your email address
Page 2: “Verify your email to view the form” page where you are still prompted for a Google email, even if you didn’t choose the google option on the first page.
Page 3: “You’re one click away from less busywork” page that looks a lot like I’m signing up for an Asana account.
One page 3, where you have to complete the captcha – there is a random black box showing above the captcha dialog and below the email field. (see screenshot 1)
If that is supposed to be there, I’m not sure what the point is. It’s orange with a spinning circle arrow icon until the Captcha dialog loads, and then it turns black, no text or any information as to what it is.
Also – when viewed in a private browser session, you don’t even get the captcha. After hitting “continue” on page 2, you are taken to a page where it prompts you to either sign up with your Google Work account or you get the “name@company.com” sign up prompt with a solid black box next to it. (see screenshot 2)
I’m wondering if any of this is an error or if this is all expected behavior. I understand the need to verify the email address to confirm that they are in the organization, but for a simple form, this is a lot of steps to take just to see the form.
@Christina_Molnar, welcome to the forum! I haven’t adopted this feature yet, but I’m guessing that subject line pulls from the task name, which can be configured in the form settings to incorporate question responses. Open the form editor, go to settings, and then click the dropdown about task title.
Hi @Stephen_Li, Thank you for the warm welcome!
Unfortunately, even though that was my hope too, it doesn’t seem to be the case. Our form has a custom name set up (and a rule that auto-amends that to include a unique identifier once it comes in):
I am just here to say that if someone is a guest.. you can use this email access. You can have clients as guests in your organization without paying for them and this feature will work that way. You can limit access to internal projects, but use this form email response capability!
