Mailbox Workflow
hi got a question to our workflow ( is there anything wrong ? ):
1.) customer sends email to support@mail.de
2.) a new issue is created in our general project called "support"
3.) customer get's notification mail
3.) we view the issue and change the project to best matching one ( at moment for example customername-typo3 ), ( support project is just a temporary pipeline to fetch and order )
3.) the customer get's a mail that means something like "your issue was assigned to project customername-typo3"
all fine...
but if the customer now replies to any new mail ( it doesn't matter if its a comment mail from inside YT or the change status mail ) YT generates a new issue.
is there any wrong configuration in our YT or is it just impossible to add comments by mail after change issue's project.
thx for your help
ps.: we cant create mailboxes per project... maybe a wildcard filter in mailboxsettings "Project: *"
1.) customer sends email to support@mail.de
2.) a new issue is created in our general project called "support"
3.) customer get's notification mail
3.) we view the issue and change the project to best matching one ( at moment for example customername-typo3 ), ( support project is just a temporary pipeline to fetch and order )
3.) the customer get's a mail that means something like "your issue was assigned to project customername-typo3"
all fine...
but if the customer now replies to any new mail ( it doesn't matter if its a comment mail from inside YT or the change status mail ) YT generates a new issue.
is there any wrong configuration in our YT or is it just impossible to add comments by mail after change issue's project.
thx for your help
ps.: we cant create mailboxes per project... maybe a wildcard filter in mailboxsettings "Project: *"
Please sign in to leave a comment.
create issue in project P1 -> issue gets issue number P1-1
open issue and change project to P2 -> issue gets issue number P2-1
write email to support@mail.de with subject ... P2-1: ... -> new issue is created in project P1
write email to support@mail.de with subject ... P1-1: ... -> comment get assigned to P2-2
seems that youtrack didnt update the ralation to issue id when we change its project ( it should keep both the old and new id )
can someone confirm that?
flo
As workaround I can only suggest to use tags/subsystems to mark issues in main project.
this is still realy important for our company and we cannot start use our payed youtrack before this works.
The next release is planned for the mid of February for now, but we might have a minor release earlier.Promise to do our best to make it happen as fast as possible. Normally we upgrade our InCloud servers according to the Maintenance Calendar, so the next Monday after the official release all the servers are upgraded normally:http://confluence.jetbrains.net/pages/viewpage.action?pageId=46046683
Thank you for your patience, we really appreciate it!
but the error is still present!
another problem is that everytime a customer sends mail to system he gets an old test mail ( old issue ).
please give me info when this bug is fixed finally (or not).
We Apologize for misleading you, this fix will be included to the YouTrack 4.2 that is planned for the mid of February for now. Unfortunately, we couldn't include it to the 4.1.3 bug fix.