BUG: Case Caption Information Printing as Black Text

Question

BUG: Case Caption Information Printing as Black Text

Closed this issue a month ago · 0 comments

Describe the Bug
When attempting to print the browser page in DAWSON, the case docket number and caption information is displaying as printing as black text, even though the display on the screen view is the standard white text.

This occurs in Edge, Chrome, and Firefox (and probably Safari).

Business Impact/Reason for Severity
Case info is not readable in printed view

In which environment did you see this bug?
PROD, TEST

Who were you logged in as?
CA

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
Attempting to print party information for a case

To Reproduce
Steps to reproduce the behavior:

Go to a Case
Right click on the screen and select "Print"
Note the displayed image for printing

Expected Behavior
Case caption info displays and prints as white as seen on the screen

Actual Behavior
Case caption info displays and prints as black text

Screenshots
Print view:

Printed view:

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Cause of Bug, If Known

Process for Logging a Bug:

Complete the above information
Add a severity tag (Critical, High Severity, Medium Severity or Low Severity). See below for priority definition.

Severity Definition:

Critical Defect
Blocks entire system's or module’s functionality
No workarounds available
Testing cannot proceed further without bug being fixed.
High-severity Defect
Affects key functionality of an application
There's a workaround, but not obvious or easy
App behaves in a way that is strongly different from the one stated in the requirements
Medium-severity Defect
A minor function does not behave in a way stated in the requirements.
Workaround is available and easy
Low-severity Defect
Mostly related to an application’s UI
Doesn't need a workaround, because it doesn't impact functionality

Definition of Ready for Bugs(Created 10-4-21)

Definition used: A failure or flaw in the system which produces an incorrect or undesired result that deviates from the expected result or behavior. (Note: Expected results are use cases that have been documented in past user stories as acceptance criteria and test cases, and do not include strange behavior unrelated to use cases.)

The following criteria must be met in order for the development team to begin work on the bug.

The bug must:

Be focused on solving a user problem
Contain data for all fields in the bug template, so the team can pick it up and begin working immediately

Process: If the unexpected results are new use cases that have been identified, but not yet built, new acceptance criteria and test cases should be captured in a new user story and prioritized by the product owner.

If the Court is not able to reproduce the bug, add the “Unable to reproduce” tag. This will provide visibility into the type of support that may be needed by the Court. In the event that the Court cannot reproduce the bug, the Court will work with Flexion to communicate what type of troubleshooting help may be needed.

Definition of Done (Updated 4-14-21)

Product Owner

Bug fix has been validated in the Court's test environment

Engineering