We access our internal JIRA via the URL https://jira
The plugin (version 1.6.3) is installed and licensed correctly (real license, no eval). The Outlook add-in 1.6.3 is installed in outlook and configured for https://jira with a valid username and password. When I try to create an issue, I get the error "Could not access license. JIRA status code: forbidden". When I test the connection in the connection settings of the Outlook add-in, I get "Could not login as user 'someuser': JIRA status code: Forbidden".
I heard about the work-around of using the FQDN "https://jira.mycompany.com", but is not an option because
a) we use local URLs by convention inside the company
sorry for the late reply, unfortunately we did not get an email notifcation even though you used the correct tag.
Please raise a ticket here https://servicedesk.catworkx.de/servicedesk/customer/portal/4
The upcoming release will inculude an option to disable SSL validation check, such that ttps://jira.mycompany.com should work.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs