# data[].attributes.headline
limited release windows and approval needed

# data[].attributes.subject
limited release windows and approval needed

# data[].attributes.body
I understand where it is coming from, but it still added overhead to the process and pressure

# data[].attributes.body
Nobody knows what caused today's IM. Also in general, takes too long to find the root cause

# data[].attributes.body
Pappy documentation seems lacking, I've run into blockers on how to do some basic things. It's possible that it exists but CorpWiki search is simply inadequate.

# data[].attributes.body
The endpoint is working, however it is not returning a list of tasks for employees who have more than one task. It only returns a single task.

# data[].attributes.body
Too many channels, and channels with similar names, in Slack

# data[].attributes.body
Asad wrapping up onboarding and API exercise

# data[].attributes.body
Should do more, very effective

# data[].attributes.body
It's super helpful when people '@' the channel to mention we have a new autoenv

# data[].attributes.body
All bugs related to IO, LI or Campaigns are routed to our team by default

# data[].attributes.body
Still not working. Makes it hard to do local development

# data[].attributes.body
Since UI is where people notice problem, we get to be woken up first and help triage. If we continue need to do that, It would be nice to get more knowledge transferred or have some runbook shared with us

# data[].attributes.headline
late-stage product/UX discussions for UIT 

# data[].attributes.subject
late-stage product/UX discussions for UIT 

# data[].attributes.body
understandable, so only a
minor concern

# data[].attributes.body
were both stable and available the second half of the week

# data[].attributes.body
Help from Jeremy for pappy with GDLI bugs and freq capping helps a lot

# data[].attributes.body
Shoutout for being very helpful this week

# data[].attributes.body
This is specific to my effort on the GDLI refactor. The original thought was that since the workflow would be blocked in the UI due to the line item type selector being disabled, it might be okay to merge bits of work into master instead of keeping a "long running" feature branch around. I think it's less risky to keep the feature branch approach around, though, since it prevents problems introduced into master that would prevent master from being "releasable" from occurring during the development process... better to just keep these isolated on a separate branch until everything's ready to go.

# data[].attributes.body
Short release window with exceptions being made only for specific items means frequent reverts to master

# data[].attributes.body
Running Functional Tests help getting confidence before releases 👍

# data[].attributes.headline
More engineers can run functional tests locally

# data[].attributes.subject
More engineers can run functional tests locally

# data[].attributes.body
Reviews and feedback come pretty quickly from people on the team

# data[].attributes.body
Were broken for a few days, blocking releases

# data[].attributes.body
tickets stay in testing status for a while, a bit challenging to track all the tickets and switch back to context

# data[].attributes.headline
Merging stuff in tools_ftf-tests is slow

# data[].attributes.subject
Merging stuff in tools_ftf-tests is slow

# data[].attributes.body
- Sometimes autoenv fail, etc.
- Builds take time to run, specially when there are a lot of builds queued.
- Code reviews are slow and is not clear if test code style should be enforced or not in some cases. Some criticism looks like code style preference and it's a blocker for merging.