We currently have 3 methods for displaying reports:
Android – inline HTML
Android – pdfjs for PDF
All Others – Iframe with Blobs
These are currently all encapsulated with branching logic inside the attachment binding. This should be split into 2 or 3 bindings and separated from the bindings/report module. We should also consider reusability when working through the binding to determine the best interface.
Acceptance Criteria
This should pass all selenium tests.
Analysis
Related Stories
This was split from #5025.
Tasks
{{ table query: SELECT Number, Name, Owner, 'Task Status' WHERE Type = Task and Story = THIS CARD ORDER BY Status }}
Defects
{{ table query: SELECT Number, Name, Owner, 'Status' WHERE Type = Defect and 'Related Story' = THIS CARD }}
Mingle Card: 5044 Description
We currently have 3 methods for displaying reports:
These are currently all encapsulated with branching logic inside the attachment binding. This should be split into 2 or 3 bindings and separated from the bindings/report module. We should also consider reusability when working through the binding to determine the best interface.
Acceptance Criteria
This should pass all selenium tests.
Analysis
Related Stories
This was split from #5025.
Tasks
{{ table query: SELECT Number, Name, Owner, 'Task Status' WHERE Type = Task and Story = THIS CARD ORDER BY Status }}
Defects
{{ table query: SELECT Number, Name, Owner, 'Status' WHERE Type = Defect and 'Related Story' = THIS CARD }}
Test Plan