-
Suggestion
-
Resolution: Won't Fix
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Currently, JIRA uses XMLRPC to communicate with Confluence in four ways:
- Retrieve lists of spaces from the instance.
- Search for content in the instance (globally or by space).
- Given a pageId, retrieve page titles and urls for Confluence content.
- Given a URL, retrieve a pageId for what is assumed to be Confluence content.
JIRA should use Confluence's REST API to achieve (3). This would resolve issues with ClassCastExceptions and other remote errors that occur when retrieving Confluence content via XMLRPC.
- incorporates
-
JRACLOUD-60872 Issue link feature in JIRA does not load Confluence blog post
- Closed
-
JRACLOUD-37054 Confluence pages containing a colon cannot be linked to an issue if you need to do login dance first.
- Closed
-
JRACLOUD-38776 Confluence page link plugin unable to interpret url encoding
- Closed
-
JRACLOUD-42880 Cannot link a jira issue to a confluence page when the page title contains ":"
- Closed
-
JRACLOUD-44784 NPE linking to Confluence Page with a Comma, colon, or parenthesis in Page Title over SSL
- Closed
-
JRACLOUD-59008 Encoded urls throw null pointer exceptions when you link a Confluence page to a JIRA issue
- Closed
-
JRACLOUD-60559 Pages with special character on the title cannot be linked with issues on JIRA
- Closed
-
JRACLOUD-38153 Support for section anchors in issue link to authenticated Confluence pages
- Closed
- is related to
-
JRACLOUD-63965 Use Confluence's REST API to search for page content
- Closed
-
JRACLOUD-64357 Use Confluence's REST API to search for and filter spaces
- Closed
-
JRASERVER-63964 Use Confluence's REST API to retrieve Confluence page link data
- Closed
- was cloned as
-
JRACLOUD-64358 Improve the lookup of Confluence content IDs when linking them in JIRA
- Closed
- was split into
-
JRACLOUD-64358 Improve the lookup of Confluence content IDs when linking them in JIRA
- Closed