Heya Hansen,
As I do agree with Alexey, it could be also caused by some authentication related or we could be facing the same symptoms from this new bug report: https://jira.atlassian.com/browse/JRA-39264which describes exactly our situation and the workaround would be to use directly the URL.
However, for more information and to confirm the symptoms, can you clarify which version of the applications are you using? Also, don't forget to take a look at the information in your atlassian-confluence/jira.log file which is inside <Confluence Home|JIRA/logs> directory.
Hope it helps ya!
Cheers,
Giu
Either you have broken integration between jira and confluence either you have something broken inside the application. Could you please provide log files for confluence and jira app (atlassian-jira.log and atlassian-confluence.log files from appropriate folders - there maybe additional info related to your question
https://confluence.atlassian.com/pages/viewpage.action?pageId=16121981
https://confluence.atlassian.com/display/DOC/Working+with+Confluence+Logs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
confluence:5.5.4
JIRA:6.3.3
atlassian-confluence.log
2014-08-13 09:49:46,009 WARN [http-bio-9001-exec-47] [atlassian.confluence.cache.TransactionalCacheFactory] warning Transactional cache update outside transaction. All updates to this cache should be performed from a thread with a valid transaction context.
-- action: fourohfour
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.