-
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 (2). This would resolve a number of issues related to successful searching for content in Confluence – e.g., searching terms that include UTF8 characters (like Japanese, Chinese, etc.).
This is related to JRA-63964, but this issue is concerned with searching for Confluence content, whereas JRA-63964 is concerned with retrieving info for already-linked content.
- incorporates
-
JRACLOUD-61128 JIRA should use REST API to search Confluence pages
- Closed
- is related to
-
JRASERVER-63965 Use Confluence's REST API to search for page content
- Closed
- relates to
-
JRACLOUD-63964 Use Confluence's REST API to retrieve Confluence page link data
- Closed
-
JRACLOUD-64358 Improve the lookup of Confluence content IDs when linking them in JIRA
- Closed
- was cloned as
-
JRACLOUD-64357 Use Confluence's REST API to search for and filter spaces
- Closed
- was split into
-
JRACLOUD-64357 Use Confluence's REST API to search for and filter spaces
- Closed