When a client emails the service desk occasionally it does not create an issue in the project. The example I have in my possession started out as an item that was forwarded to the mailbox. An issue was not created in the project until after the client replied to that email to check on the status of the issue.
I am wondering what data Jira uses to associate issues with the email so that it will create comments for the appropriate issue and what is it that triggers Jira to create (or not create) new issues.
The email properties for the email I'm looking at right now are as follows:
Received: from sn4pr0501cu004.internal.outlook.com (2a01:111:e400:c50c::20) by
BY2PR06MB2198.namprd06.prod.outlook.com with HTTP via
BYAPR02CA0011.NAMPRD02.PROD.OUTLOOK.COM; Mon, 11 Jun 2018 19:12:17 +0000
Received: from SN6PR06MB4078.namprd06.prod.outlook.com
([fe80::edcb:8793:83f8:309]) by SN6PR06MB4078.namprd06.prod.outlook.com
([fe80::edcb:8793:83f8:309%4]) with mapi id 15.20.0841.019; Mon, 11 Jun 2018
19:12:17 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Susan Joyce <Susan.Joyce@meredith.com>
To: Research Insights Team <ResearchInsights.Team@meredith.com>
Subject: Fw: Parents Baby question
Thread-Topic: Parents Baby question
Thread-Index: AQHUAbYg/JFo8M3NDUOU2dRRP3Ro2KRbbMg0
Date: Mon, 11 Jun 2018 19:12:16 +0000
Message-ID: <SN6PR06MB407865A339775F9145BD6C7A95780@SN6PR06MB4078.namprd06.prod.outlook.com>
References: <SN6PR06MB40786DD6CDACCEEE97C1252C95780@SN6PR06MB4078.namprd06.prod.outlook.com>
In-Reply-To: <SN6PR06MB40786DD6CDACCEEE97C1252C95780@SN6PR06MB4078.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: <SN6PR06MB407865A339775F9145BD6C7A95780@SN6PR06MB4078.namprd06.prod.outlook.com>
MIME-Version: 1.0
X-MS-Exchange-Organization-MessageDirectionality: Originating
X-MS-Exchange-Organization-AuthSource: SN6PR06MB4078.namprd06.prod.outlook.com
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 04
X-Originating-IP: [72.82.27.56]
X-MS-Exchange-Organization-Network-Message-Id: 56bbf7a2-cabe-4293-17b2-08d5cfcf3f4f
X-MS-PublicTrafficType: Email
[...]
If it was working before and you see the email in the inbox of the configured mail account I would suggest the following:
Hello, Katie! Thanks for reaching out to the Atlassian Community.
Jira basically follows the steps below in order to create a new issue or leave a comment on an existing one:
Now, you'll also need to check your Service Desk permissions to see if the person sending the message is a user and if he's able to raise tickets. In the project settings, go to Customer permissions and check which option is selected under "Who can raise requests?", this will define if the person sending the e-mail will be able to raise tickets.
Also, another important thing to check is how you've set up the mail server/handler. The Jira Service Desk mail handler needs to be set in Project Settings > Email requests and not in Incoming mail(This is for Jira Core/Software). If the handler is set in the wrong place, there could be issues like the one you're experiencing.
Kind regards,
Maurício Karas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The user has created tickets via email before, so I wouldn't think it would have to do with Service Desk Permission. We do have the email set up in the project as suggested and it was emailed to the address we have set up in the project. That being said, no issue was created and it wasn't added as a comment to another issue that might have matched. I'm trying to figure what would have caused this message to be dropped entirely.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.