# data[].attributes.body
Needed to be done, is better now

# data[].attributes.body
Did not actually technically finish it

# data[].attributes.headline
Front-end work pulled in by back-end without assessing how much effort involved

# data[].attributes.subject
Front-end work pulled in by back-end without assessing how much effort involved

# data[].attributes.body
Pulled in two tickets and did prep work for another three.

# data[].attributes.body
Acceptance criteria needs to be updated if changes are made to the ticket later. Maybe a comment might be helpful

# data[].attributes.headline
Front-end work for the Grid poorly scoped

# data[].attributes.subject
Front-end work for the Grid poorly scoped

# data[].attributes.body
and only slightly offended that you only miss Luke...!

# data[].attributes.headline
I had stuff to do because Luke was working elsewhere

# data[].attributes.subject
I had stuff to do because Luke was working elsewhere

# data[].attributes.headline
Got a lot of work done for plant records - jh

# data[].attributes.subject
Got a lot of work done for plant records - jh

# data[].attributes.headline
Our PHP code is slowing being standardised

# data[].attributes.subject
Our PHP code is slowing being standardised

# data[].attributes.body
yay!

# data[].attributes.headline
Front-end work in the admin is not being taken seriously enough by the business.

# data[].attributes.subject
Front-end work in the admin is not being taken seriously enough by the business.

# data[].attributes.body
IMFestival was fun

# data[].attributes.headline
Re-visit the deployment and utilisation of resources: Front end resources - Where should effort go if not enough work for front end.

# data[].attributes.subject
Re-visit the deployment and utilisation of resources: Front end resources - Where should effort go if not enough work for front end.

# data[].attributes.headline
In Shaping - if any unknowns, take a quick look at the code to figure out roughly how long or difficult  a task is

# data[].attributes.subject
In Shaping - if any unknowns, take a quick look at the code to figure out roughly how long or difficult  a task is

# data[].attributes.headline
When injecting a a new ticket mid sprint - discuss with team and ensure we have capacity (front, back, QA)

# data[].attributes.subject
When injecting a a new ticket mid sprint - discuss with team and ensure we have capacity (front, back, QA)

# data[].attributes.headline
If offline discussions are being had about tickets, make sure to update the AC in Jira (or note in the ticket)

# data[].attributes.subject
If offline discussions are being had about tickets, make sure to update the AC in Jira (or note in the ticket)

# data[].attributes.headline
In the retro - go through tickets to see if any need to be re-sized, use conversations to improve.

# data[].attributes.subject
In the retro - go through tickets to see if any need to be re-sized, use conversations to improve.

# data[].attributes.headline
Better standards for Javascript in the Admin - Re-iterate to Steve G.  This is not getting the attention it needs. Paul to touchbase with Annabel also.

# data[].attributes.subject
Better standards for Javascript in the Admin - Re-iterate to Steve G.  This is not getting the attention it needs. Paul to touchbase with Annabel also.

# data[].attributes.headline
Performance - need better analysis tools. Dennis has reached out to New Relic Pro

# data[].attributes.subject
Performance - need better analysis tools. Dennis has reached out to New Relic Pro