|
Its a shame this feature is broken, it is certainly a Magnet
We are having the same problem.
Confluence 2.7 and JIRA 3.12-#298. We are using LDAP (same Active Directory) for both. JIRA and Confluence are setup to be trusted applications. The jiraissues macro works fine. jiraportlet is blank unless appended with the hardcorded os_username & password. A few extra pieces of information which may be helpful: 1) I have a $ in my password and the hardcoded password failed until I escaped it using %24. I did not know of this issue here and I opened a counterpart one on JIRA
The IOException handling is the portlet macro is a little flaky. There's a good chance that and IO problems which occur during rendering the macro end up as an empty span on the page (i.e. nothing is rendered)
Should be able to verify this by checking the HTML source for occurrences of <span class="error"></span> As indicated by some comments this might be a problem with certain portlets given that some others seem to work. Chris My company also have the same problem, and our situation is totally same with Partha Kamal.
Confluence 2.7 + jira 3.12 on windows 2003, tomcat 6.0.14, jdk1.6 Hope the bug could get fixed ASAP. I just submitted a support ticket last week with exactly the same symptoms. This needs to be fixed.
We have the same problem in our test area
Symptoms
Going to production could be done but I will need to disable the jiraportlet macro and activate it later when a solution is available Exactly the same versions and symptoms here as previous commenter Jean-Michel Rottiers.
Brad Fuller - 17/Jan/08 06:44 PM - The 'mulitple users in the manage permissions' problem is a bug in 2.7 and is listed as a fix in 2.7.1 - I cannot vouch it fixes the problem you describe, it has other things that break for me, so...
Exactly same problem.
jiraissues macro works fine in trusted environment but not jiraporlet without os_username and os_password. What's a shame! Please fix this ASAP. QA did not do a good job here. Trusted application feature was introduced in fanfare and there're only 2 JIRA macros to tests... Exatly same problem.
Please fix. Any due date for this to be fixed? This bug will be addressed in our next point release 2.7.2.
Patch InstructionsIf you are using Confluence 2.7.x, you can patch this by following these steps :
Cheers, Hi Bob. Yes, that's because of the way Confluence includes the macro in the product. In future, and even in 2.8, more of the plugins that come with Confluence will be included as bundled plugins, so that they can be upgraded using the plugin repository rather than WEB-INF/lib.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1) Setup confluence as a trusted application within Jira
2) Create a page within confluence, within it setup a jiraissues macro and jiraportlet macro and a jiraportlet macro with os_username and os_password defined.
When you save the page, the jiraissues macro will display the correct results as will the jiraportlet with the hardcorded os_username & password. However the jiraportlet without the username and passoword will be utterly blank, with no corresponding errors in either confluence or jira logs.