# data[].attributes.headline
Fixed improperly is forgotten, Tickets are left there for days

# data[].attributes.subject
Fixed improperly is forgotten, Tickets are left there for days

# data[].attributes.body
* Add to priority schema,
* communicate to everybody
* Yassen has reported how many are assigned to each person daily

Why this happen?
Lack of Documentation. Guessing.
Our current rate is 20%~

# data[].attributes.headline
[Documentation] Some bugs are not informative enough, make it harder to understand for devs, takes more time to reproduce. And is hard to resolve bugs faster.

# data[].attributes.subject
[Documentation] Some bugs are not informative enough, make it harder to understand for devs, takes more time to reproduce. And is hard to resolve bugs faster.

# data[].attributes.body
* More descriptive reproduction steps.
*  talk with all the CS team.
* VIdeo on LOOM with voice/
* QA check some bugs prior devs reproducing, enriching information, clearing out doubts, etc
* Meeting ( 9:15 )
* QA could anticipate what test will cover.
* Evaluate documentation platform. -> I will record a video with alternatives (this week).

Why?
* We dont always understand how feature should work?

# data[].attributes.headline
Messages on teams are just an URL with no context

# data[].attributes.subject
Messages on teams are just an URL with no context

# data[].attributes.body
Template to talk about issues on Ms TEAMS. Developers now will include PR, explain what was the issue and how it was solved.

Title
Ticket URL
PR* (in case job is finished)
Summary of update

This allows us to understand all the context instead of just an URL without any information

# data[].attributes.headline
Not clear what is in progress and developers switching focus frecuently

# data[].attributes.subject
Not clear what is in progress and developers switching focus frecuently

# data[].attributes.body
Added a In progress section, with limit of 2 per person. When developers start working on a ticket they must move to this section.

Increase focus

Give clarity on whats being worked on

➡ to mark next tasks to work on. Maximum 4 in the whole board

# data[].attributes.headline
Overwhelmed - Too many bugs, always in rush, increasing amount of bugs without resolution, Rushing leads to wrong quality, bugs.

# data[].attributes.subject
Overwhelmed - Too many bugs, always in rush, increasing amount of bugs without resolution, Rushing leads to wrong quality, bugs.

# data[].attributes.body
Bring new dev.
Ask Jeff
Move temporary All dev team

# data[].attributes.headline
[Clarity] The process is complex and doesn't bring clarity

# data[].attributes.subject
[Clarity] The process is complex and doesn't bring clarity

# data[].attributes.headline
[Priorization] It's hard knowing what to work on, too much tasks, too many critical priorities.

# data[].attributes.subject
[Priorization] It's hard knowing what to work on, too much tasks, too many critical priorities.

# data[].attributes.headline
[Process] Hard to know if bug is being worked on, gathering information, stucked, etc

# data[].attributes.subject
[Process] Hard to know if bug is being worked on, gathering information, stucked, etc

# data[].attributes.headline
[Process and clarity] We dont know when QA step into, if we hotfix smthing but still working on the root cause

# data[].attributes.subject
[Process and clarity] We dont know when QA step into, if we hotfix smthing but still working on the root cause

# data[].attributes.body
items are handled in multiple bugs and is hard to track.

# data[].attributes.headline
[Flow] Lack of capacity, consistent hours and time spent working on bugs

# data[].attributes.subject
[Flow] Lack of capacity, consistent hours and time spent working on bugs

# data[].attributes.headline
Duplicated tickets makes risk of do work twice by different people and adds noise. We dont have a way to handle duplicated issues

# data[].attributes.subject
Duplicated tickets makes risk of do work twice by different people and adds noise. We dont have a way to handle duplicated issues

# data[].attributes.body
Bundles case. We create a DEV parent task and log all issues there as subtasks. Both CS bug and DEV bug have to be referenced

# data[].attributes.headline
Bugs are stuck on fixed improperly and Notify Client

# data[].attributes.subject
Bugs are stuck on fixed improperly and Notify Client

# data[].attributes.body
Why we are rushing to fix loads of things but when we fix them, issues stay in this list for days? We maybe are investing our effort in things that are not the priority? I would expect that if we work in the right, critical think this list will be empty super fast.

# data[].attributes.headline
We don't know what kind of solution we applied 

# data[].attributes.subject
We don't know what kind of solution we applied 

# data[].attributes.body
fixed the root cause, patch, fix to data.

# data[].attributes.headline
The unsorted list is too big, hard to know focus

# data[].attributes.subject
The unsorted list is too big, hard to know focus

# data[].attributes.body
Huge Unsorted list splited into Customer Detected and Detected -> Give us clarity on what should be attended first (customer reported)

# data[].attributes.body
Add a column for client and remove from title

# data[].attributes.headline
Not knowing what is our performance, how much a bug take to complete, what is our capacity

# data[].attributes.subject
Not knowing what is our performance, how much a bug take to complete, what is our capacity

# data[].attributes.body
add a column with resolution date, manually set on last step and register it with weekly basis

# data[].attributes.headline
[Testing, QA] We are skipping merging into stage, which causes not automated tests run

# data[].attributes.subject
[Testing, QA] We are skipping merging into stage, which causes not automated tests run

# data[].attributes.headline
[QA, Testing] We do not run test automatically on PR and we don't know results

# data[].attributes.subject
[QA, Testing] We do not run test automatically on PR and we don't know results

# data[].attributes.body
* Jenkin box will test.

# data[].attributes.headline
🔶 Our Fixed improperly (bounces) rate is high

# data[].attributes.subject
🔶 Our Fixed improperly (bounces) rate is high

# data[].attributes.headline
[Prioritization, speed] Slow updates, bugs takes longer than expected, not as prompty as it could be 

# data[].attributes.subject
[Prioritization, speed] Slow updates, bugs takes longer than expected, not as prompty as it could be 

# data[].attributes.body
Often times there is a lack of intended functionality of existing features. How should it be working? How was it developed? Is it working correctly? Was it a miss when originally developed? All lead to difficulty in fixes.

# data[].attributes.headline
Deploys    - Stressful    - high risk    - didnt follow schedule, posponed, failed

# data[].attributes.subject
Deploys    - Stressful    - high risk    - didnt follow schedule, posponed, failed

# data[].attributes.headline
[Metrics] We don't know our full capacity + focus factor, reducing the capacity to estimate how much we can improve by limiting the work in progress + increasing focus.

# data[].attributes.subject
[Metrics] We don't know our full capacity + focus factor, reducing the capacity to estimate how much we can improve by limiting the work in progress + increasing focus.

# data[].attributes.body
not enought information