List view
- Overdue by 6 year(s)•Due by May 31, 2019•10/10 issues closed
Required changes to testing framework to be clinically compliant
Overdue by 6 year(s)•Due by June 30, 2019•2/2 issues closed- Overdue by 6 year(s)•Due by May 10, 2019•37/37 issues closed
As Hornet team conducts their tests on Pipelines API v2, address the common errors they see and improve success rate from ~90% to 95%+.
Overdue by 6 year(s)•Due by June 1, 2019•3/5 issues closedP0 Achieve consistent > 99.9% uptime as measured by our site reliability metrics, including both status endpoint checks as well as critical user flows (canary workflows) [P1] Generate a long-term targeted technical plan on horizontally scaling Cromwell. [P1] When appropriate, the system should report a degraded status with an informative message so clients can potentially still use parts of the system when there are issues.
No due date•1/3 issues closed1. Implement cleanup of intermediate results (Cost Management Plan)
No due date•0/1 issues closedGeneral users want: - actionable failure messages - understand the root cause of a failure mode without having to learn what pipelines error codes mean
Overdue by 6 year(s)•Due by June 30, 2019•4/8 issues closed- No due date•27/32 issues closed
For tickets that are being worked on in our Bugs / Tech debt / User-driven tickets rotation
No due date•106/125 issues closed