Hi,

This bug has a wider affected area than described and is affects our workflow a lot. It makes it impossible to get a table overview from Confluence of statuses in Jira, since at any time a page in Confluence is edited, all smart links to Jira in the page properties report are lost.

Summarize

Any edit to a page which contains links in page properties to any Jira issue, will cause the link to be displayed as regular URL, not as a smart link. 

Steps to Reproduce

1. Create page A and add page properties macro on the page and insert links to Jira issues.
   The link to Jira can be inserted by copy and paste or by the Jira issue macro, does not matter.
   
2. Publish page A.

1. Create page B and insert page properties report macro.
2. Publish page B.
   Links to Jira show as smart links with Jira Issue type, Summary, Status.
   
3. Make any edit on page A and publish the page.
4. Refresh page B.
   All smart links are replaced with regular URLs, Issue type, Summary, Status don't show any more.
   

Expected Results

Page properties report macro should show the smart links of Jira issues.

Actual Results

All smart links are replaced by normal links/url in page properties report macro after the page containing links has been edited.

Workaround

The workaround to add all Jira links last is not practical. 

It also affects very long links that are displayed on the subpage in the page properties as smart links and then in the page properties report as a very long link instead of a smart link. Which stretches the page properties report table way too wide.

+1

+1

Peter Mills, images cannot be added by issue commenters. However, you could upload the images to a service such as img.ur and paste the links instead. 

I tried editing my comment, but I'm getting a permissions error

"You do not have permission to create attachments for this issue"

The images are missed. Please fix it

Hi Atlassian, 

I note that the bug https://jira.atlassian.com/browse/CONFCLOUD-54631 was fixed recently, addressing the problem of multiple Jira tickets not rendering correctly.

Unfortunately the Page Properties Report  ("PPR") macro is still not completely fixed wrt rendering single Jira tickets correctly.  Although the problem with the infinite 'spinner' has gone, single Jira tickets still render as plain text hyperlinks, not Smart links.

To summarise, the Jira ticket when rendered inside the PPR macro should look like this 

But instead it looks like this

The only time the single Jira ticket renders correctly is after the Jira macro has been inserted for the first time into the Page Properties macro on the child page and the child page published.  ANY subsequent edits to the child page will result in the PPR macro reverting to displaying the plain text hyperlink.  

Interestingly, with the recent bug fix https://jira.atlassian.com/browse/CONFCLOUD-54631 I note that the Jira ticket rendering problem only occurs for the "Single Issue" display option.  When I choose the "Table" display option, the Jira ticket always renders as expected - but being a table layout  it is not very easy on the eye - it looks like this 

Any chance of fixing the issue with single Jira ticket rendering in the PPR macro?

Cheers

Peter

Would appreciate this issue being addressed. My team gathers lots of details and we use page properties to report to our customers what action they need take in Confluence. Having them click through loads of hyperlinks to get to a ticket to see a status is very unhelpful.

This bug is terrible because project reports for Stakeholders look not good. Too much manual work is needed every week to make reports readable. Is this possible to increase bug priority? please!

I've you already clicked it, it will say 'remove my report'.

https://imgur.com/a/87ZE3XL 

Otherwise it will say 'This affects my team'

https://imgur.com/a/eiRh6AI 

@Pieter Helsen
I do not see any such button - can you please share a screenshot?

Everyone, please make sure to not only add a comment, but also click the 'this effects my team' button in the right-hand information pane on the website.

This is what influences whether Atlassian will prioritize this issue or not. 

This functionality may as well not be there if it doesn't work. A week ago I had a page full of links that was fully supporting my team in their work. I have looked this morning and practically every link is now not showing. the result being that  every link now has to be visited to see the status information that the link was providing.

Ugh, are we still in the "Gathering Impact" phase with this bug? 

Man, I understand that Atlassian can't just work on everything, that is broken, at once.

But I sure hope that I'll live to see the day, when this bug finally gets fixed.

Up-voting all these comments - Experiencing this bug myself and it's SUPER frustrating! 

It is a horrible bug for me that mainly ruined my work. Indeed, I can't believe that this bug still is there.

I can't believe this bug still is there, It's affecting all of our teams globally using the product. This together with the broken create Jira issue from confluence bug is getting embarrassing, when we are trying to promote this within our company, and then we see the engineering team spend their time on adding the ability to add a banner image to a page, something we can all do anyway, wow, just wow

This is a really bad bug that makes the Properties report pretty useless if you use Smart links to Jira. The workaround to re-create the the link to Jira every time you change anything in the table is not a good solution since it takes a lot of unnecessary time for administration.

I reported this to Atlassian in may 2020 and it still is in status "Gathering Impact". Clearly it affects everyone using the macro and isn't a corner case using Confluence at the edge of it's capacity. 

@Alassian, please prioritize this!

Hi @Atlassian, can you please fix this bug!!  We have to stop using the page properties report macro and instead create a regular table with the Jira tickets inserted one at a time, plus copying the other page properties values from the child pages - terrible for productivity and for keeping the content in sync.  

HELP!!

Cheers Peter

This issue is also causing us problems, as we're relying on the visual cue of the page properties report to see the status of the linked issues. 

We're obliged to go back to the page, remove the link, and put in the /Jira macro again to have it work.  As soon as you go back to EDIT the page, it converts the /Jira macro to a regular link, which breaks the page properties report.

Please increase the severity of this, as it is causing us an undue amount of work (wasted productivity) using a tool that should be saving us time (which it usually does).

Thank you!

As described here this issue also affects the formatting without any @mention stuff going on.

Simply have an Old page and New Editor page and paste a Jira link into the pages and save.

Then on a page with a properties report setup, the old page values show the rendered view, new page shows a raw link (despite the page itself showing the rendered view).

Its frankly a real pain as it means (as David above says) our project/product team cannot use the Jira status on tickets to quickly identify the status of initiatives and actions based on Jira and have to click through.

Also; as urls don't include the summary, a wall of tickets becomes as useful as a spreadsheet for project management as theres no title to understand what the action is.

This is a pretty big deal for our Product team. All our req. gathering / design happens in Confluence and are linked through to issues (stories) in Jira, they like to see the status of the issues as the work progresses from inside Confluence (the tool they use everyday)...

I would really appreciate a uplift in the severity on this one...

(needless to say I am catching a lot of flack on this one daily...)