Provide permalink for the revision which is the current revision

Problem/Motivation

If I display a list of revisions, the link to the current revision (let's call it revision A) goes to the friendly URL of the page, not to a revision link. If the page is subsequently revised, such that a different revision (let's call it revision B) becomes the current revision, the link for revision A replaced by a revision link.

The problem is that if I both want to report an issue with revision A rendering to the development team and I want to report to the content editor that I want them to make a change to the page content, then if the editor removes the problematic content, the link that I give to the developers will no longer display the problem that I am reporting in our issue tracker. I still want the issue fixed, because it could occur on other pages in which the same formatting would be appropriate.

If I wait until the content editor fixes the problem so that I do have a stable link to give to the developers, that increases my cognitive load as it is one more thing for me to have to keep track of. It also increases my workload because I have to keep track of whether or not the editor has fixed the content issue.

It would be ideal if the list of revisions row for the current revision (revision A) also contained a permalink to the revision which I could then put in the issue tracker.

Steps to reproduce

1. Log into a website as a user who has permission to view revisions.
2. Go to https://[site domain]/node/[node number]/revisions

Desired result:

• The current revision links to the friendly URL.
• In the same row, there is the text Permalink which links to the revision in the form /node/[node number]/revisions/[revision number]/view.
• All remaining revisions link to their corresponding revision in the form /node/[node number]/revisions/[revision number]/view.

Current result:

• The current revision links to the friendly URL.
• All remaining revisions link to their corresponding revision in the form /node/[node number]/revisions/[revision number]/view.

Workaround:

1. Create draft.
2. Save and publish draft.

The revision which I want to report to the developers now links to the revision rather than to the friendly URL.

However, there are two disadvantages to this workaround:

• If the retention being saved contains something which was not previously being flagged as an error but is now being flagged as an error, I will get an error message and have to resolve it, which interrupts my workflow and takes additional time that is properly assigned to the content editor.
• If there is an outstanding draft, I can't use this workflow without disturbing the current draft status.

Proposed resolution

On the list of revisions for a node, add a permalink to the current revision which links to the current revision using a revision URL.

Remaining tasks

User interface changes

On the list of revisions for a node, add the word Permalink to the row containing the current rev

API changes

Data model changes

Release notes snippet