See private correspondence ("Re: Contributing / Jira Oauth Patch"), which suggests the call to rest/auth/1/session should be (and may urgently need to be) replaced with a call to rest/api/2/myself. See also https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/#which-apis-and-methods-will-be-restricted-.

This is quite old and I'm not sure it's particularly relevant anymore. T13516 has made some related changes.

Currently, I also think no part of this pipeline can actually tell if changeset X changed at diff Y or not, but this isn't conceptually hard to get right most of the time.

I'm not aware of any current customer interest in improving this behavior, and it's likely a lot of work to improve what is largely a moot case (there's usually no value in reviewing individual file-level changes in a "create a new branch X" commit) that only affects Subversion.

Filetree stuff is now in T13516: Remove the "filetree" setting (so it's always enabled for everyone).

Pretty much ready to ship:

To save this setting, the shortest path is to just reload the change with an option like justSaveViewStateDoNotActuallyRenderAnything=true. But, since reloading changes is per-changeset, this is inefficient if filetree changes out of T13516 support collapsing multiple files at once.

Updating renderer is a big oof. The value sometimes depends on the window dimensions on the client.

There is currently no storage unique to a <user, changeset> pair, or a <user, diff> pair, or a <user, revision> pair.

keyboard shortcut for "Open in Editor".

I think I'm just going to no-op this migration.

This is now possible.

This is now supported.

These field functions have somewhat-weird scopes/context.