Hello,

This is a good idea.
The request already exists in the roadmap ticket #2199 "Receive Tickets as Emails" with low priority (high cost, low benefit)

It's quite the same thing except my evolution is not linked to ticket but is linked to activities

We do not plan to insert activities from tickets.
This is bad design : activities must be created by project leader.
Only tickets, recording user requests, may be created from tickets.

Ok, i understand it.

However, this is not a bad design. I's another point of view of implementing activiites to a project.

Here is how we work :
Project leader is still the big boss but he allows ressources to propose activities. This new activities are tagged with the activity status "Backlog". The proejct leader choose to pass the activity status to "planified" if is agree, or to "shutdown" the activity (it's his role to choose what is interesting or not for the project).

By implementing the creation of activities through mails, we simplify the process for ressources.

Thank you again for your answer, and for Projeqtor

Hi,

Expected process in ProjeQtOr is almost the same, but based on Tickets :
- user requests a change through a ticket
- project leader analyses and when validates, copies the ticket into an activity
We have 2 items to distinguish the request (ticket) and the work to do (activity) so that we don't have activities (that impact planning calculation even if not validated) when not needed.