|
Mobile: |
Tablet: |
Desktop (macOS): |
Desktop (Windows): |
|---|---|---|---|
|
Android: |
Android: |
|
|
|
|
||
|
iOS: |
iOS: |
||
|
|
||
|
|
|
|
|
|
|
|
|
|
Mobile: |
Tablet: |
Desktop (macOS): |
Desktop (Windows): |
|---|---|---|---|
|
Android: |
Android: |
|
|
|
|
||
|
iOS: |
iOS: |
||
|
|
||
|
|
|
|
|
|
|
|
|
|
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 |
Stingray |
|
Issue type |
Bug |
|
Summary |
A brief one-line summary of the issue. |
|
Description |
Description field should be filled as in following template: Preconditions: 1…. 2… Steps to reproduce:
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 |
|
Attachment |
If you can supplement your bug report with a picture that shows the |
|
Linked Issues |
<link to the related issue> |
|
Assignee |
The person whom the bug is assigned to (backend issues – BE/Dev Lead, |
|
QA Scope |
<testing scope> |
|
|
|
|---|---|
|
Passed |
Verification status: Device/Browser: Win10 + Chrome (the latest) – if actual Comment: describe the actual result Screenshot(s): <screenshot> |
|
Reopened |
Verification status: Device/Browser: iPhone 13 Pro Max (the latest iOS + Safari) Actual result: <Actual result> Screenshot(s): <screenshot> Expected result: <Expected result> |
|
Blocked |
Verification status: Device/Browser: Samsung Galaxy S22 Ultra (the latest Android + Chrome) Screenshot(s): <screenshot> Comment: <Additional info about blocking issue> |
All team members should provide their priorities, progress, and problems each day in this report.
|
Team name |
Dream team |
|---|---|
|
Direct supervisor |
|
|
Table of contents |
|
Name |
Priorities |
Progress |
Problems |
|
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 |
|
Name |
Priorities |
Progress |
Problems |
|
|---|---|---|---|---|
| 1 |
Dima |
CR and QA fixes |
In process |
|
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 |
|
Name |
Priorities |
Progress |
Problems |
|
|---|---|---|---|---|
| 1 |
Ihor |
QA issues |
Should finish today |
- |
| 2 |
Dima |
Fixes after code review |
Will start |
|
| 3 | ||||
| 4 | ||||
| 5 |
|
Name |
Priorities |
Progress |
Problems |
|
|---|---|---|---|---|
| 1 |
Ihor |
Finish contact us page |
Halfway |
- |
| 2 |
Dima |
Fix QA issues |
||
| 3 | ||||
| 4 | ||||
| 5 |
|
Name |
Priorities |
Progress |
Problems |
|
|---|---|---|---|---|
| 1 |
Ihor |
Work on contact us page (FE) |
Just started |
- |
| 2 |
Dima |
Add all secondary blocks to Technology page |
- |
- |
| 3 | ||||
| 4 | ||||
| 5 |
|
Project Name / Client |
Stingray / Kind |
|---|---|
|
Phase |
IN DEVELOPMENT |
|
Scope |
Resesign of the website |
|
Tech Stack |
WP |
|
Initial Estimate |
325 – https://docs.google.com/spreadsheets/d/1H4KOvwHXf89FTWqU9lf8aes2PiSbFeaXhoVWnlsW8sM/edit?usp=sharing |
|
Project’s Start Date |
23.01.2022 |
|
Target release |
10.03.2022 |
|
Time Tracking Tool |
Timedoctor – Stingray |
|
Invoicing Type |
SOW for KIND – end of each month |
|
PM |
Ruslan Bokach |
|---|---|
|
Designer |
– |
|
Developer |
Dmytro Melnyk, Artem Symonchuk, Ihor Havrylenko |
|
QA |
Viktoriia Malysh |
An informational website that highlights Stingray’s product. Just info pages and one contact form. Good quality animations are described in the design.
KIND contact persons:
1) Marianne Erdal ( marianne@kindworldwide.com ) – Key Account manager and responsible person from KIND’s side
2) Emil Olsen ( emil@kindworldwide.com ) – Designer of the project
🔗 Accesses & Useful links
|
Design |
https://xd.adobe.com/view/37d711b3-d697-45c0-8fc8-1f058ce9a087-6284/grid Upd (06.10.2023) – https://xd.adobe.com/view/234a6d7f-87dc-42cf-9145-0a7f5a2d8641-7619/grid/ |
|---|---|
|
Stage dev |
stingray.dev.cheitgroup.com |
|
Stage admin |
stingray-admin |
|
FTP |
HOST => 159.69.126.101 |
|
Database |
DB_NAME => stingray_db |
|
GIT |
https://gitlab.cheitgroup.com/cheitgroup/developing/wordpress/stingray |
|
Page |
Functionality |
Notes |
|---|---|---|
|
Question |
Answer |
Answered by |
Date Answered |
|---|---|---|---|
|
Name |
Date Requested |
Estimate |
Status |
|---|---|---|---|
|
IN PROGRESS DONE |
|||
|
DECLINED |
Use it to create something wonderful.
To start, you might want to:
Customise this overview using the edit icon at the top right of this page.
Create a new page by clicking the + in the space sidebar, then go ahead and fill it with plans, ideas, or anything else your heart desires.
Get a quick intro into what spaces are, and how to best use them at Confluence 101: organize your work in spaces.
Check out our guide for ideas on how to set up your space overview.
If starting from a blank space is daunting, try using one of the space templates instead.