Loading...

XML

Word

Printable

Feedback Policy:

We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

This was recently fixed in Jira, where in Issue Navigator issues now show their Epic's name rather than the Epic's Issue Key.

In Confluence, the Epic's Issue Key is still displayed when using the JIRA macro.

causes

CONFSERVER-51568 JIRA issues Macro instead of Epic Name showing Epic Link column

has a regression in

CONFSERVER-45325 Epic Name/Link column on JIRA issues macro displaying wrong Epic Name

is blocked by

JSWSERVER-10115 Improve the XML view of the Epic Link and Sprint custom fields so that the Confluence Issues Macro can present better information

is duplicated by

CONFSERVER-41537 Epic Names and Version using JIRA Issue/Filter macro (in Confluence), cannot be displayed

is related to

CONFSERVER-32317 custom field type URL should be clickable link

relates to

CONFCLOUD-31534 When Epic Link is chosen as a display field in the JIRA macro, it should show Epic Name.

CONFSERVER-33651 Display the Sprint Name for items in the JIRA Report

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(2 relates to, 9 mentioned in)