-
Bug
-
Resolution: Timed out
-
Low
-
None
-
3.1.1, 5.4.1, 5.5.3
-
Tomcat
-
1
-
Severity 3 - Minor
-
One of our users noticed that when he tried to delete a page, the confirmation message said there was an incoming link, but when he clicked on the message (which takes you to the info sheet for the page), no incoming links were shown. We think we've tracked down that this happens when a page that has been deleted had a link to the page you're trying to remove. It seems like the bug fixed (in 2.3) reported in CONF-4815 may have had this additional aspect that wasn't fixed. (That bug report is about the info sheet – the info sheet properly detects that the link no longer exists, but the remove message does not.)
[CONFSERVER-21517] Remove page confirmation message reports incoming links that no longer exist
Issue still present in 5.4.1. Verified by repeating the 'Steps to replicate' above.
Roy Hartono [Atlassian]
added a comment - Steps to replicate:
- Create two pages: A and B
- Create a link to B in A
- delete A
- delete B and you will see a warning about an incoming link from A
Roy Hartono [Atlassian]
added a comment - Steps to replicate:
Create two pages: A and B
Create a link to B in A
delete A
delete B and you will see a warning about an incoming link from A
Roy Hartono [Atlassian]
added a comment - Reopen.
This is a valid bug and also exists in Confluence 3.4.5
Roy Hartono [Atlassian]
added a comment - Reopen.
This is a valid bug and also exists in Confluence 3.4.5 
Patrick Gisbey
added a comment - Hi Jonathan,
I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket.
Please refer to the support ticket for any future correspondence relating to this issue.
In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in https://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you.
Regards
Atlassian Support Team.
Patrick Gisbey
added a comment - Hi Jonathan,
I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket.
Please refer to the support ticket for any future correspondence relating to this issue.
In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in https://support.atlassian.com , it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you.
Regards
Atlassian Support Team. 
Thank you for taking the time to raise, comment or vote on this Bug. We regret to inform you that due to a limited number of reports and based on our current backlog of higher impact issues that we are closing this issue as Timed Out.
If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue.
Thanks again.
Regards,
Confluence Development