After switching jira to https users can't add epic link to issue, before using https JIRA worked stable.
Some users can't add epic link to issue, though they have full rights and access to use epics.
In addition they can chose epic name from list in filed "Epic Link", but after this issue doesn't update.
What could be the problem?
What method did you use to enable HTTPS with Jira? Typically SSL is either being terminated directly in Jira's tomcat instance, OR SSL is being terminated by a reverse proxy sitting in front of Jira.
In either case, you should have had to make changes to the $JIRAINSTALL/conf/server.xml file to reflect this change. My concern is that your config file might not have the proxyName, proxyPort, and scheme parameters on the connector serving up this traffic that are required to make this work (if using a proxy, redirect, port forwarding, load balancer, etc, basically anything that redirects connections to Jira will force you to have those proxyName and proxyPort parameters in that config file).
I have seen all sorts of strange behavior can happen when Jira's traffic is being redirected without its knowledge.
Integrating Jira with Apache using SSL one guide that might be a helpful reference, even if you are not using apache specifically. If that does not help, please tell us more about your setup.
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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