As of D21188, inlines have these remaining weird behaviors:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 30 2020
Apr 29 2020
In the DOM, inline comments are currently structured as a "comment row", followed by zero or more related rows (which may contain the editor UI or the undo UI).
Apr 28 2020
OKAY SO
I'm having trouble reproducing figuring out how to reproduce this locally.
Apr 27 2020
These issues are somewhat complicated because changesets currently have a single changeType attribute and a single fileType attribute, and a lot of rendering logic depends on these attributes. This model isn't correct in the general case.
This seems to be fixed and has deployed to the cluster.
This appears to be an issue with synthetic lint messages from Harbormaster that do not specify a line number. We reach this section of the code:
- Followups on "Hidden" logic have moved to T13519.
Apr 26 2020
With PHP 7.4, it seems OpenSSL (and various other libraries) have moved to pkg-config, which is a tool that uses the PKG_CONFIG_PATH environmental variable to locate packages. This impacts OpenSSL and libxml2.
Apr 25 2020
At time of writing, calls to rest/api/3/myself now return this:
At time of writing, calls to rest/auth/1/session return a result like this:
I believe D21167 fixed this.
The request sequence here is:
Apr 24 2020
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-.
Apr 23 2020
Apr 22 2020
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).