Filter issue report to show only those submitted by email?

[Lyndsy-Denk]

I'm trying to report on requests submitted through a request queue's email address. I'm struggling to find a field to filter by. Does anyone know the magic password?

[Sven-iX]

Hi @Lyndsy-Denk 
Not really. No specific field that says "this one came in through email" - a kludge might be to use topics - the email seems to be assigned to the first available topic... So if the UI labels it like "DONT USE - for email" ... you might be able to filter but ugh. 

[Lyndsy-Denk]

So what's considered the "first available topic?" When I submitted a test request by email, I was surprised to see that it indeed was assigned a topic and I couldn't figure out why the system chose that topic. It's not the first alphabetically (I have several others that would come earlier). I suspect it's the first that was created in the queue. But if you don't have that historical memory, how would you know?

I created an idea to fix this: Create reportable value for identifying issues sub... - Adobe Experience League Community - 748170.

[Sven-iX]

It's nutty - i thought an email wouldn't be assigned a topic and agree - picking the first-created topic in the list is harebrained. Thanks for adding the idea!

[skyehansen]

just pointing future readers to this documentation:

https://experienceleague.adobe.com/en/docs/workfront/using/manage-work/requests/create-requests/enab...

for future reference, workfront randomly assigns a queue topic, and it is not always the "first" one.

[Sven-iX]

[Sven-iX · Accepted solution]

Hi @Lyndsy-Denk 

Skye reminded me of a workable solution - even though Adobe don't include this in the documentation: 

Use an additional required field on the form in the UI (can't use subject because that will be filled with the email subject)

If the request is made in the UI that required field MUST have a value (otherwise you cannot submit the form. 

If the request comes via email, no form values are filled out, so you can report on blank required fields and safely assume they're via email. 

Thanks @skyehansen for jogging my memory!

[Lyndsy-Denk]

Y'know, my mind was going in that direction, but stalled out because I couldn't think of a common required field across all request queue forms. But I can create one. Thank you @Sven-iX and @skyehansen!

[skyehansen]

I don't know if a whole other required field is needed (I do agree it's needed if fields are filled out after the submission process).

Maybe just play with a calculated field. e.g. if you have custom forms A, B, C, D, and E, each with a required field, the calculated field might say something like if custom fields A through E are blank, "email", otherwise "regular".