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: *"
11 comments
Comment actions Permalink
youtrack should first look if an issue if <id> already exists ( no matter in wich project )... if no create new issue...
0
Comment actions Permalink
ok after hours of testing this seems to be an bug.

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
0
Comment actions Permalink
I'm having the same problem. All mail fetched from the server is sent to the main project. A reply to issue 213 in a project is creating a new issue: "a-80 Issue s-213: testissue".
0
Comment actions Permalink
I see you created the issue http://youtrack.jetbrains.com/issue/JT-16998, please follow it.

As workaround I can only suggest to use tags/subsystems to mark issues in main project.
0
Comment actions Permalink
It looks like #JT-16998 was closed as obsolete.  I am experiencing the same issue where replies to an email create a new issue in the default project if the ticket was moved to a different project.  This is with YouTrack 4.1.1.  Anyone have a solution?
0
Comment actions Permalink
It was actually a bug. I've just fixed it. Fix will be included in next release.
0
Comment actions Permalink
still present here... can you give me an overview when this bugfix will pushed to all youtrack saas systems?
this is still realy important for our company and we cannot start use our payed youtrack before this works.
0
Comment actions Permalink
Hello Florian,
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!
0
Comment actions Permalink
as i can see a new update is online (YouTrack 4.1.3 (build #5764 [18-Jan-2013 16:58] ))!
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).
0
Comment actions Permalink
Florian,
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.
0

Please sign in to leave a comment.