-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1000.34.0, 6.3.4
-
12
-
Severity 3 - Minor
-
1
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Summary
If your Page Properties Macro contains pagination, the pagination will not load when inside the macro body of Page Properities contains JIRA Issue Macro value.
Steps to Reproduce
- Add Page Properities Macro Report to a page (set the number of items to display to 2)
- Add Page Properties Macro to two pages (without JIRA Issue Macro to the Value)
- Add Page Properties Macro to one page (add JIRA Issue Macro to the Value)
- Reload the page containing the Page Properties Report Macro
- Use the Pagination to navigate to 2
- Then back to 1
Expected Results
- Page Properties Report Macro pagination should load the table when a Page Properties includes JIRA Issue Macro value
Actual Results
- Page Properties Report Macro pagination breaks when a Page Properties includes JIRA Issue Macro value
Workaround
- Reload the page containing the Page Properties Report Macro and the table will reload.
- is incorporated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned in
-
![[Confluence] Page](/images/icons/generic_link_16.png "[Confluence] Page")
Page
No Confluence page found with the given URL.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-41462] Page Properties Report Macro pagination breaks when a Page Properties includes JIRA Issue Macro value
Hi
We are planning an upgrade and this issue, (which is not a minor) is holding us back as we would have to remove the column that has the JIRA macro so as not to affect all the pages. Then when you do finally fix it we will have to go back in and add the columns again.
The workaround doesn't work.
Can we pls have this fixed?
Conor
Conor Harte
added a comment - - edited Hi
We are planning an upgrade and this issue, (which is not a minor) is holding us back as we would have to remove the column that has the JIRA macro so as not to affect all the pages. Then when you do finally fix it we will have to go back in and add the columns again.
The workaround doesn't work.
Can we pls have this fixed?
Conor 
SysAdmins
added a comment - This is also not a minor issue here. We have about 30 or so pages that pull over 30 results so we need them all to work correctly.
SysAdmins
added a comment - This is also not a minor issue here. We have about 30 or so pages that pull over 30 results so we need them all to work correctly. We have this problem too.
I don't think it's a "minor" issue.
Your workaround does not work. And always if I use have a page property with JIRA macro, the "Number of items to display" will not be respected.
-> I have 50 pages with page properties, one of them uses JIRA macro. One page with the report with max shown items = 100 will just show me 30 items and a page two which I can never see.
So it's a big impact to users with Page Properties and JIRA.
For me, this isn't an actual "real" workaround.
When you reload the page, when you're on the second page of the Page Properties Report Macro,
not the second page reloads, but you're redirected to the first page of the Page Properties Report Macro.
So this workaround only applies if you have a Page Properties Macro with ONE page... If you have more than one page, you have no chance to reload the second one.
In my opinion the workaround in the bug description is not completely correct.
Paul Auerbach
added a comment - - edited For me, this isn't an actual "real" workaround.
When you reload the page, when you're on the second page of the Page Properties Report Macro,
not the second page reloads, but you're redirected to the first page of the Page Properties Report Macro.
So this workaround only applies if you have a Page Properties Macro with ONE page... If you have more than one page, you have no chance to reload the second one.
In my opinion the workaround in the bug description is not completely correct. Does also appear within Confluence 5.9.9. Breaks the properties report and make it a useless feature.
Our customers are highly interested in this type of reporting. Please update this issue.
For us, the workaround does not work. Even if we reload the page. The macro becomes broken while changing the pages.
Best regards
Andreas Morgner
Andreas Morgner (Scandio)
added a comment - - edited Does also appear within Confluence 5.9.9. Breaks the properties report and make it a useless feature.
Our customers are highly interested in this type of reporting. Please update this issue.
For us, the workaround does not work. Even if we reload the page. The macro becomes broken while changing the pages.
Best regards
Andreas Morgner
Hi, we have the same problem.
Confluence 6.3.4.
Jira 7.2.7