- Issue created by @bkline
- Status changed to Closed: works as designed
over 1 year ago 7:12pm 31 July 2023 - ๐บ๐ธUnited States drumm NY, US
This is a side effect of the bulk updates for the following comment changing the Version and how Drupal keeps track of revisions. Notice https://www.drupal.org/node/2971390/revisions/view/11380013/11380027 โ also includes that version change. Those bulk updates are run via a drush script which is operating as the anonymous Drupal user. That bulk update probably should have used
$issue_node->revision = TRUE;
With #3265096: Move issues from www.drupal.org to git.drupalcode.org โ upcoming, I donโt think GitLab provides a way to view issue summary revisions, so we won't have to worry about migrating this type of non-ideal data. And correcting it in the meantime would be more trouble than its worth, since weโd have to back-fill more revisions.
- Status changed to Closed: won't fix
over 1 year ago 9:26pm 31 July 2023 - ๐บ๐ธUnited States bkline Virginia
I get the argument that it's not worth fixing, but unless someone can point to documentation which explicitly states that the tracker system was intentionally designed to behave this way, I think "Closed (won't fix)" is a more appropriate status for this issue.