Creating new issue format

1) Issues found while testing:

Issue Type: Bug – If it is an issue. Improvement – If it is suggestion.

Summary: Summary of the issue

Attachment: Screenshot and video

Description: URL / Credential / Pre condition / Steps/ Actual result /Expected result/ Device or
platform info / App version.

Assignee: Assign to the relevant developer if applicable.

Priority: Put the priority on how fast developers need to fix it.

Linked Issue: Link the related issue or story if applicable.

Examples:

Web: https://kametventures.atlassian.net/browse/BM-953

Mobile: https://kametventures.atlassian.net/browse/ZEN-1702

2) Issues found while validating story/feature:

Issue Type: Bug – If it is an issue. Improvement – If it is suggestion.

Summary: Summary of the issue

Attachment: Screenshot and video

Description: URL / Credential / Pre condition / Steps/ Actual result /Expected result/ Device or
platform info / App version / Environment.

Assignee: Assign to the relevant developer if applicable.

Priority: Put the priority on how fast developers need to fix it.

Linked Issue: Link the related issue or story if applicable.

 Validating Tickets which are in ‘IN QA’ / ‘QA’
column

1) Validating the Story/Improvement/Sub-Task:

* Issues to be validated for mobile app will appear in ‘IN QA’ column of Brightmile Android JIRA
board.

* Issues to be validation for Web app will appear in ‘QA’ column of BM board JIRA board.

* Validate the story/improvement/sub-task only if the story/bug is in ‘IN QA’ OR ‘QA’ column with
‘QA’ label - Raise issue if any issues found while validating.

* Commenting after validation for mobile:

Tag relevant developer to whom the story/bug is assigned or who has created the story.

Write appropriate comments:

* Issue is closed for fixed.

* Issue still exists and steps to reproduce it(Incase approach is different).

Video/Screenshot if any (Let video contain app version)

Device: Android

App version: 0.15.0(100)

* Commenting after validation for web:

Tag relevant developer to whom the story is assigned or who has created the story.

Write appropriate comments:

* Issue is closed for fixed.

* Issue still exists and steps to reproduce it(Incase approach is different).

Video/Screenshot if any

OS: Windows/Mac

Browser: Chrome/Firefox/Edge.

Environment: QA

* Moving story after validation:

 Move the Story to ‘Done’ (Select from ‘Workflow drop’ down), IF it is working fine.
 Move the Story to ‘Blocked’ (Select from ‘Workflow drop’ down), IF it is NOT working fine.
 If the story is linked to any bugs then move Story to ‘Blocked’ and linked bug to ‘Ready
for Development’.
2) Validating the Bug:
* Validate the bug- Raise issue if you have found any other issue from this bug (Regression Test).

* Commenting after validation for mobile:

Tag relevant developer to whom the bug is assigned (If none, check ‘Activity’ and tag the developer
who is in loop).

Write appropriate comments:

* Issue is Closed for fixed.

* Issue still exists and steps to reproduce it(Incase approach is different).

Video/Screenshot if any (Let video contain app version)

Device: Android

App version: 0.15.0(100)

* Commenting after validation for web:

Tag relevant developer to whom the bug is assigned (If none, check ‘Activity’ and tag the developer
who is in loop).

Write appropriate comments:

* Issue is Closed for fixed.

* Issue still exists and steps to reproduce it(Incase approach is different).

Video/Screenshot if any

OS: Windows/Mac

Browser: Chrome/Firefox/Edge.

Environment: QA

* Moving bug after validation:

 Move the bug to ‘Done’ (Select from ‘Workflow drop’ down), IF it is working fine. It will
appear in ‘Passed QA’.
 Move the bug to ‘Ready for Development’ (Select from ‘Workflow drop’ down), IF it is
NOT working fine.
 If the bug is linked to any story then move Story to ‘Blocked’ and linked bug to ‘Ready
for Development’.

Note: If there is any doubt regarding ticket validation please refer ‘Ticket Validation’ sheet in the
drive.