Page MenuHomePhabricator

Allow application email to create new tasks using a task template
Closed, InvalidPublic


I saw T6819 and understand it's related, but I think our use case here might be a little different.

We would like to have a flow where any user can send an email to, and have a new task created with the appropriate, pre-defined tags -- maybe similar to using a template to create a new task. The reason we have this ask is because the user submitting the request will not have knowledge of the appropriate project, subscribers, etc necessary for the task, but all emails going to that address will belong in the same project, have the same subscribers, etc.

It looks like we are capable of setting up application emails, but then they fall into a black abyss with no project, subscribers, tags associated.

Let me know if this is an education issue on my part! @devd can provide more details if necessary.

Event Timeline

angie updated the task description. (Show Details)
angie added a project: Restricted Project.
angie added subscribers: angie, jhurwitz, devd.

Looks like a bunch is supported out of Herald already:

pasted_file (550×665 px, 81 KB)

@devd, do you have the ability to create a global rule/would this work for your purpose?
I don't have the ability to create a global rule on this install, so if it were up to me to make this flow, herald doesn't work as a solution.

(and personal rules don't have enough flexibility to do what you need)

ohh cool! yeah .. let me try this out. thanks @chad

this works. The only problem is that every response will create a new task. I can hack around it, I think, but was wondering if there was a way to tell Phabricator to not create a task in those cases.

angie moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Oct 15 2015, 11:33 PM
In T9582#140572, @devd wrote:

this works. The only problem is that every response will create a new task. I can hack around it, I think, but was wondering if there was a way to tell Phabricator to not create a task in those cases.

I don't really understand the problem. You want people to file bugs but tasks to not really be created in some cases? This sounds more like Nuance (our help desk tool).

Sorry, that was badly phrased. My apologies.

The high level hope was that I could just add the incoming email id to a mailing list we have for people to ask questions. This way evry new thread could get its own task. Only problem is that any reply to an existing thread (which got its own task already) will create a whole new task..

Maybe Nuance is the right thing for this?

Would this work?

  • Create a "Mailing List" user for mailing list (
  • Have users email a different inbound address (
  • Have Herald add the Mailing List user as a subscriber as part of your inbound processing.

So the user would send "Need help getting the Orange Product working" to Phabricator would create a task, then send T9232: Need help getting the Orange Product working to the mailing list and the user. Replies by anyone would go to the task.

Nuance will refine this sort of workflow, too, but I think the approach above would work today. If you make the mailing list thread the primary coordinating object Phabricator won't really be able to reconcile that discussion into a single task thread, but if you make the task thread the primary object it should have better luck. Then activity directly on the task will also be sent to everyone, whereas if the task creation address is just subscribed to a mailing list updates from the web interface would not be sent out to the same users by default.

good point. Unfortunately, the mailing list is already set up and migrating that might be more effort than needed (there are all the existing links; subscribers; guidelines etc).

The option I was thinking of was to just add a filter in my inbox that says "emails to this list that don't start with a RE:" should forward to the phabricator alias. I think I am gonna try that as a lower cost solution.

angie claimed this task.

If the filter doesn't work, we will reopen this task.