# data[].attributes.body
is a super pig

# data[].attributes.body
It's been a long time, it's almost there :)

# data[].attributes.body
Taking shape and becoming more solid

# data[].attributes.body
The application is not covered 100% so after QA's detects an error I create a test.

# data[].attributes.body
Always need assistance, poor documentation and unstable environment

# data[].attributes.body
we handled them pretty fast once their appeared

# data[].attributes.body
Everyone is always genuinely involved and willing

# data[].attributes.body
backups and restore staging take so much space and time

# data[].attributes.body
update in comments a re pretty clear but not always updated in the description

# data[].attributes.body
Hard to tell if it's false alarm or really propositions are not being processed correctly

# data[].attributes.body
Going deep into reasons. Maybe a distribution of major causes of issues?

# data[].attributes.body
Some tickets the logic is not well defined

# data[].attributes.headline
QA HFCM user Interface test battery (user side) 

# data[].attributes.subject
QA HFCM user Interface test battery (user side) 

# data[].attributes.body
Really time consuming, it has to be done, but i think it could be optimized

# data[].attributes.headline
A lot of the sprint dedicated to one project (PWC)

# data[].attributes.subject
A lot of the sprint dedicated to one project (PWC)

# data[].attributes.body
Sticks converting to bricks (and may be concrete later)

# data[].attributes.body
API is strange. Old doc and not very smart

# data[].attributes.body
Update Rails Ticket battery of tests is updated and will be used for other QA analysis

# data[].attributes.body
Not enough QA analysis during the sprint retro

# data[].attributes.body
Lot's of tickets without estimation > hard to have a precise idea of amount of work left or done