-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
5.6.5
-
Production
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Hi team,
Need your help in resolving the following bug asap. Any help would be much appreciated.
Issue: I have a couple of epics and some stories associated with each of them in JIRA. When I created a wiki page in Confluence, I inserted some issues from JIRA using "JIRA Issue/Filter" built-in macro to display all the Epics and their respective stories in a table.
While all the other attributes appear correctly I am not able to get to display, the names of the Epics in the table. I have included Epic Name and Epic Link both the columns, but Epic Name column in the table is empty, while Epic Link just populates the JIRA Id of the Epic in question.
Ultimately, I need to display Epic Names in the table and not their ids. Please suggest how this could be fixed.
Also, for your reference, please find the screen shot attached with the ticket
Update
This issue seems to also affect other fields like Version. When user generates a report; instead of showing the version number; it shows the version ID instead.
For example.
jira=> select * from projectversion where id = 17718; id | project | vname | description | sequence | released | archived | url | releasedate | startdate -------+---------+-------+-------------+----------+----------+----------+-----+-------------+----------- 17718 | 11200 | 1.9 | | 10 | | | | | (1 row)
When a report is generated; instead of showing version 1.9 for an issue in a report; it shows 17718 instead.
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
- was cloned as
-
-
- Closed
-
-
-
- Closed
-
[CONFSERVER-36033] Epic Names and Version using JIRA Issue/Filter macro (in Confluence), cannot be displayed
| Workflow | Original: JAC Bug Workflow v3 [ 2889883 ] | New: CONFSERVER Bug Workflow v4 [ 2982236 ] |
| Workflow | Original: JAC Bug Workflow v2 [ 2803074 ] | New: JAC Bug Workflow v3 [ 2889883 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JAC Bug Workflow [ 2734638 ] | New: JAC Bug Workflow v2 [ 2803074 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2391461 ] | New: JAC Bug Workflow [ 2734638 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2271512 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2391461 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2221671 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2271512 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2166903 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2221671 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1942235 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2166903 ] |
Mythreyi Vattikuti
added a comment - This is still not resolved. In Screen Shots attached on this ticket it shows the EPIC Name, but it is not working like this in our queries. EPIC Name is still coming empty in Confluence page. When I add EPIC Name column in the JIRA Query Results also EPIC Name is coming blank, However EPIC Link is populated with EPIC Name. Is there any macro/setting needs to configured in project for EPIC Name to populate as expected. Please provide any tips/feedback.
Mythreyi Vattikuti
added a comment - This is still not resolved. In Screen Shots attached on this ticket it shows the EPIC Name, but it is not working like this in our queries. EPIC Name is still coming empty in Confluence page. When I add EPIC Name column in the JIRA Query Results also EPIC Name is coming blank, However EPIC Link is populated with EPIC Name. Is there any macro/setting needs to configured in project for EPIC Name to populate as expected. Please provide any tips/feedback. 
This is ridiculous behavior. Why put a name in the field if it can't be used to reference the EPIC in a issue type? We can read it in Jira when it is assigned, why not allow it to be present when exported?
Who thought that showing the EPIC link was good enough? Business operations users and management should not have to be provided with some sort of translator to know the name of something that is already there.