-
Bug
-
Resolution: Fixed
-
High
-
3.12.0
-
10
-
Severity 2 - Major
-
23
-
Atlassian status update as of 20th June 2018
Thank you for your patience. The fix is now available on Jira Service Desk Version 3.13.1. For a complete list of issues resolved in this fix please refer here.
— Jira Service Desk Team
Atlassian status update as of 6th June 2018
Hello All,
Thank you everyone who has voted or commented on this bug.
We've assessed this request and will be putting out a fix in an upcoming release. Stay tuned.
Thank you for your support.
— Jira Service Desk Team
Summary
Unable to create an email channel using POP /SECURE POP due to incorrect inbox empty validation.
How to Replicate
- in Service Desk 3.12.0
- Set up a new inbox
- Create an email channel : Project Settings > Email Requests> Enter the email server details with POP or Secure POP
- Click next
Expected results
- The Wizard should continue to : Set up email channel
Actual result
Workaround
- Setup the email inbox with a pop connection
- Run the following query first in the JIRA database:
select * from "AO_54307E_EMAILCHANNELSETTING";
- Take the ID from there and replace it for the <id> in the following Query and run in your database:
update "AO_2C4E5C_MAILCONNECTION" set "PROTOCOL" = 'pop3s' ,"PORT" = 995 where "ID" = <id>;
- relates to
-
JSMDC-2268 You do not have permission to view this issue
Form Name |
---|
I managed to fix our Service Desks eventually.
We upgraded our JSD version to .14 a couple of weeks ago, after which the left hand side column with the queues didn’t render correctly. After looking through the various forums I read the article saying to change the project type from a SD to Business and then back again.
Once I did that the Queue column rendered correctly (although we lost all the customizations). The SD project configs also went back to default, so I setup all the incoming email address again.
However the old email config tables were still in the DB so I guessed that’s why things might not be working. I deleted everything in the affected tables and reconfigured and the mails started processing again.