Change Details

See PHI854, which would like better behavior for dashboard panels with more results than are visible. This may be easy, or may get rescheduled into T13083. See also T9903. See PHI853 and D19628. It appears that JIRA has begun responding `HTTP/1.0 200` instead of `HTTP/1.0 200 OK`. This is apparently legal, just unusual. See PHI852, which is equivalent to T8573 and I expect to resolve as "the author can mark inlines done". See PHI851. `diffusion.commit.search` should accept string constants (not numeric constants) for the `statuses` constraint.

See PHI854, which would like better behavior for dashboard panels with more results than are visible. This may be easy, or may get rescheduled into T13083. See also T9903. See PHI853 and D19628. It appears that JIRA has begun responding `HTTP/1.0 200` instead of `HTTP/1.0 200 OK`. This is apparently legal, just unusual. See PHI852, which is equivalent to T8573 and I expect to resolve as "the author can mark inlines done". See PHI851. `diffusion.commit.search` should accept string constants (not numeric constants) for the `statuses` constraint. See PHI847, which requests better logging from `RepositoryOperation`. A `RepositoryOperationLog` is likely reasonable.

See PHI854, which would like better behavior for dashboard panels with more results than are visible. This may be easy, or may get rescheduled into T13083. See also T9903. See PHI853 and D19628. It appears that JIRA has begun responding `HTTP/1.0 200` instead of `HTTP/1.0 200 OK`. This is apparently legal, just unusual. See PHI852, which is equivalent to T8573 and I expect to resolve as "the author can mark inlines done". See PHI851. `diffusion.commit.search` should accept string constants (not numeric constants) for the `statuses` constraint. See PHI847, which requests better logging from `RepositoryOperation`. A `RepositoryOperationLog` is likely reasonable.