Bug report instructions

Rule	Example
Title should be self-descriptive ("What?" "How behaves?" "While what conditions?").	[Home page] The links are not added to the social icons in the Footer.
Bug specific should be stated on first place (ex.: reproducible only on some device type, intermittent issue, environment specific, any other unique attribute).	[Home page] [Footer] [Devices] The lines are not centered in the footer-bottom section.
Avoid using not exact phrases such as "working not appropriately", "not proper way","not per design". Try to be as specific as possible.	The white space is shown under the Header.

Steps should be as specific as possible;
Examples of pages, profiles, vacancies, etc. that could be used for easier bug reproducing should be provided in any suitable form (URL, ID, etc.);
Actual and Expected results should be provided with appropriate screenshots, whenever applicable;
During bug creation, separate critical/major/minor bugs and create a separate bug for each issue;
You can combine the bugs if they have the same priority. But if the priority is different – please create 2 or more bugs.
If during retesting the bug, the issues described initially are fixed, close the bug, and for all new issues that appeared after the fix and weren’t described in the bug initially create a NEW bug.

Filed	What to fill
Project	Easol: Marnie Rays
Issue type	Bug
Summary	A brief one-line summary of the issue. Summary field name should be filled according template: [Page] [Area name] <Problem short and concrete description>
Description	Description field should be filled as in following template: Preconditions: 1…. 2… Steps to reproduce: Step_1. Step_2. Step_3. Actual result: Clear description of what actually happened. See attached screenshot for more details. <Screenshot> Expected result: Clear description of what should have been happened. See attached design for more details. <Screenshot> / <link to the design> Additional information: REPLACE the TEXT with Additional information, if applicable.
Priority	The degree of importance for the business to resolve the defect. It is driven by business value and indicates how soon the defect should be fixed.
Attachment	If you can supplement your bug report with a picture that shows the problem, or a score that helps others reproduce, fix and verify the problem quickly, attach these files to the bug report. The attached files can be as follows: pictures, video-recording, other files types, if needed.
Linked Issues	<link to the related issue>
Assignee	The person whom the bug is assigned to (backend issues – BE/Dev Lead, Frontend issues – FE Lead)
QA Scope	<testing scope>

Verification statuses templates


Passed	Verification status: Passed Device/Browser: Win10 + Chrome (the latest) – if actual Comment: describe the actual result Screenshot(s): <screenshot>
Reopened	Verification status: Reopened Device/Browser: iPhone 13 Pro Max (the latest iOS + Safari) Actual result: <Actual result> Screenshot(s): <screenshot> Expected result: <Expected result>
Blocked	Verification status: Blocked Device/Browser: Samsung Galaxy S22 Ultra (the latest Android + Chrome) Screenshot(s): <screenshot> Comment: <Additional info about blocking issue>

Passed

Verification status: Passed

Device/Browser: Win10 + Chrome (the latest) – if actual

Comment: describe the actual result

Screenshot(s): <screenshot>

Reopened

Verification status: Reopened

Device/Browser: iPhone 13 Pro Max (the latest iOS + Safari)

Actual result: <Actual result>

Screenshot(s): <screenshot>

Expected result: <Expected result>

Blocked

Verification status: Blocked

Device/Browser: Samsung Galaxy S22 Ultra (the latest Android + Chrome)

Screenshot(s): <screenshot>

Comment: <Additional info about blocking issue>