| Reporter |
a. e. (a.e)
|
|---|---|
| Created | Feb 20, 2013 4:55:23 PM |
| Updated | Jul 26, 2013 6:05:32 PM |
| Resolved | Mar 21, 2013 8:00:13 PM |
| Priority | Normal |
| Type | Bug |
| State | Fixed |
| Assignee | Mariya Davydova (mariyafomkina) |
| Subsystem | Mailbox |
| Fix versions | 5.0 |
| Fixed in builds | 5970, 6395 |
| Affected versions | 4.2 |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Анастасия Миллер (stacy-miller) |
| Reviewed by | Anna Zhdan (Anna.Zhdan) |
| Severity | Routine |
After update to YouTRACK 4.2 we have a problem with the mailbox integration.
What steps will reproduce the problem?
1. create an issue by sending an email to the configured mailbox
2. upate the issue in YouTRACK
3. update notification emails are sent automatically to the configured mailbox
4. new issues are created that consist of the YouTRACK notification email text
What is the expected result?
YouTRACK should ignore it's own notification mails when scanning mailboxes. It did this in the past because after the update to 4.2. 3 months worth of unread notification mails were converted to new tickets.
What happens instead?
YouTRACK doesn't recognize it's own notification mails and creates new issues.
What steps will reproduce the problem?
1. create an issue by sending an email to the configured mailbox
2. upate the issue in YouTRACK
3. update notification emails are sent automatically to the configured mailbox
4. new issues are created that consist of the YouTRACK notification email text
What is the expected result?
YouTRACK should ignore it's own notification mails when scanning mailboxes. It did this in the past because after the update to 4.2. 3 months worth of unread notification mails were converted to new tickets.
What happens instead?
YouTRACK doesn't recognize it's own notification mails and creates new issues.