Have the "os_username" and "os_password" parameter in the Confluence JIRA issues macro been deprecated?

I upgraded my Confluence instance from 5.1.2 recently, and the JIRA issues macro from 4.0.29 to 5.0 and the XML URLs that I put into the JIRA issues macro no longer work when I append a username and password to it. It reported the following issue: "Error rendering macro 'jiraissues' : com.atlassian.confluence.macro.MacroExecutionException: java.net.SocketTimeoutException: Read timed out"

I rolled back JIRA issues to 4.0.29 and now I get a different issue: "Error rendering macro 'jiraissues' : Unable to determine if sort should be enabled." The only troubleshooting help I can find is the following: https://confluence.atlassian.com/display/CONFKB/Unable+to+Determine+if+Sort+Should+be+Enabled+When+Using+the+JIRA+Issues+Macro

But this doesn't help. The issues table renders correctly if I remove the parameters for the username and password (which I've checked are correct) but not if they're present.

1 answer

1 accepted

1 vote
Accepted answer

The answer is "no".

I left on Friday feeling annoyed and frustrated having spent a few hours trying to fix it, and then I come back on Monday and see that it's working perfectly fine.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in New to Confluence

How to use Confluence Cloud for stakeholder management

Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...

1,123 views 2 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you