---
last_updated: 2025-07-15
tags: [workflow, qa-process, jira, yara724]
source: import-knowledge
---

# Current QA Workflows — Yara724

## Daily Workflow

```
CEO Request
        ↓
Requirement Analysis
        ↓
Convert Requirement into Jira Task
        ↓
Write Documentation
        ↓
Create Mockups / Annotated Screenshots
        ↓
Describe Backend Changes
        ↓
Developers Implement
        ↓
QA Testing
        ↓
Bug Investigation
        ↓
Frontend / Backend Root Cause Analysis
        ↓
Retest
```

## Requirement Intake

Requirements do not follow a standardized process. Typical characteristics:

- Received from different stakeholders.
- Usually communicated verbally or as short informal messages.
- Often consist of only one sentence or a rough idea.
- Frequently marked as urgent.
- Sometimes conflict with existing business workflows.
- Require additional clarification before implementation.

## Requirement Analysis — Clear Requirements

```
Receive Request
        ↓
Open Jira
        ↓
Navigate the current flow
        ↓
Capture screenshots
        ↓
Document the requirement
        ↓
Use ChatGPT with a predefined Jira template
        ↓
Review
        ↓
Publish Jira Task
```

## Requirement Analysis — Ambiguous / Larger Requirements

```
Receive Request
        ↓
Analyze current workflow
        ↓
Discuss with Frontend / Backend
        ↓
Reach verbal agreement
        ↓
Create Jira Task
```

## Jira Ticket Creation Process

A significant portion of working time is spent creating high-quality Jira tasks:

- Writing a meaningful title
- Writing a detailed description
- Explaining the business requirement
- Specifying affected URLs and pages
- Attaching and annotating screenshots (using Paint)
- Highlighting UI elements
- Explaining expected behavior
- Writing backend expectations
- Specifying API modifications
- Explaining request body / response model changes
- Describing validation rules

Sometimes also specifying:
- Which API should be used
- Which fields are missing
- Which response properties should be added
- Which endpoint should be modified
- How the frontend expects the backend response

## Bug Investigation Workflow

```
UI
  ↓
Browser DevTools
  ↓
Network Request
  ↓
Swagger
  ↓
Backend Response
  ↓
Compare with Frontend Expectations
  ↓
Determine Root Cause
```

Possible outcomes:
- Frontend bug
- Backend bug
- Wrong API called
- Missing request parameter
- Incorrect request body
- Missing response field
- Validation issue
- Business logic issue

For some bugs, QA reads frontend/backend code to explain why a condition or logic is wrong.

## AI-Assisted Workflow (Current)

```
Raw Requirement
        ↓
ChatGPT
        ↓
Structured Jira Ticket
        ↓
Manual Review
        ↓
Publish to Jira
```

ChatGPT is used to convert raw requirements into structured Jira tickets. Improvement on ticket quality noted. Also used for wording and organizing documentation.

## Investigation Workflow (with MongoDB)

```
UI
        ↓
Browser DevTools
        ↓
Network Requests
        ↓
Swagger
        ↓
MongoDB
        ↓
Root Cause Analysis
```