-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Component/s: TAP - Linking Platform
-
None
-
2
-
Severity 3 - Minor
Issue Summary
The new Jira issue macro shows the component field as an API call link instead of a text.
In addition, when the Jira issue is embedded in the Confluence Database, the component renders the same link pointing to the API url {site}.atlassian.net/rest/api/3/component/{component ID}
Steps to Reproduce
- In Jira: create an issue with one or more Jira Component
- In Confluence: Create a page with the new Jira issue macro and add the column to show the components

- Also In confluence: create a database, and reference that issue key in a row. Create a details column to show the component
Expected Results
no link or at least a usable link would be produced
Jira legacy macro shows as no link:

Actual Results
a rest call link is presented to the user.

Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is implemented by
-
EDM-10704 Loading...