Bug report instructions

Title should be self-descriptive ("What?" "How behaves?" "While what conditions?").

[Vacancies]. Error page is displayed after visiting the Vacancy page and changing its status.

Bug specific should be stated on first place (ex.: reproducible only on some device type, intermittent issue, environment specific, any other unique attribute).

[Tablet] [Mobile] [RT]. Profile page is not adapting to the new layout after rotating the device.
[Intermittent] [PROD] [Companies]. Updates are not displayed on the company preview page after clicking the “Vorchau“ button.

Component name should be stated at the beginning of the title.

[Applicants]. User is not shown in the Applicants tab after applying on the publication.

Avoid using not exact phrases such as "working not appropriately", "not proper way","not per design". Try to be as specific as possible.

[PaaS]. Report is downloaded in a not proper format.

Project

<Project Name>

Issue type

Bug / CB - client issue

Summary

A brief one-line summary of the issue.
Summary field name should be filled according template:
[Area name] <Problem short and concrete description>

Component

<Component's name> select from the dropdown. For each project, the list of components is specific.

Description

Description field should be filled as in following template:

Preconditions:

REPLACE the TEXT with needed configuration, if applicable.

Steps to reproduce:

1. Step_1.

2. Step_2.

3. 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.

Labels

Choose from the drop down. The label indicates the bug is related to some component. For each project, the list of labels is specific.

Environment

one of the (DEV, STG, PROD)

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)

Epic Link

Contains a link to Epic in accordance with overall structure of epics on the
project.

Severity

The degree of impact that a defect has on the functionality of the tested component or system.

Please, find the additional info here

Sprint

<sprint>

QA Scope

<testing scope>

Passed

Verification status: Passed

Environment: <link>

Device/Browser: Win10 + Chrome (the latest)

Screenshot(s): <screenshot>

 Reopened

Verification status: Reopened

Environment: <link>

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

Environment: <link>

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

Screenshot(s): <screenshot>

Comment: <Additional info about blocking issue>