Org Web Adapter

journals/2020_05_27.org

ID
d468b773-3a96-47ae-9874-769c17659311

2020-05-27 - Wednesday

Tasks

DONE Review Github and Jira notifications

CLOSED: SCHEDULED:

DONE Feed [[id:00b7467f-98cd-48a4-9a20-1389adfa4517][Chickens]] and move [[id:2b8f8b07-21a8-4837-8e9e-7058dddc2ff9][Goats]] [[id:cd0bca31-039c-4f2a-a6fc-d725d8afdc37][Animal Fencing]]

CLOSED: SCHEDULED:

- Note taken on

I fed the chickens and just put the goats back on the same piece of pasture

they were on yesterday. They’re such a small group that we can probably get

away with this more often. Looking at the last few days’ pastures I probably

could have left them there a little longer.

DONE [[id:abd31776-07d5-4991-b492-281fbf2ad91e][Pull Request]] reviews

CLOSED: SCHEDULED:

- Note taken on

Did not get more than a few perfunctory reviews done today. Need to find more

time tomorrow or later this evening.

DONE Clean up PR for Namely integration [[id:906e4b87-2a0f-44ad-9cdc-2700eec4d0a9][ENG-8856]]

CLOSED:

Meetings

DONE Stand-up with [[id:10b14f49-b275-45f5-b76b-fea159f0a75a][Andrii]]

CLOSED: SCHEDULED: <2020-05-27 Wed 8:00-8:10>

- Note taken on

Had nice conversation with Andrii this morning. He was lamenting out he only

really has two days of development time each week on Monday and Tuesday before

meetings kick in for the rest of the week – Manager’s Life :)

We also have a story inject in the sprint to redact attribute values from the

account when you login as a user. So we talked about that a bit.

DONE [[id:1a25c7bf-7040-4905-9075-2b12948b128f][Administrative Squad]] huddle

CLOSED: SCHEDULED: <2020-05-27 Wed 9:00-09:30>

ZOOM
https://zoom.us/j/8597441264

- Note taken on

Had a really long discussion about a bug with group permissions and features

where it was possible for a permission to be disabled in one big group and to

have a lot of users lose access to a given feature because the group

permission was XOR-ing the access, so one False caused the feature to be

unavailable.

We went around for a while about a robust solution before I called out that we

should probably just allow users to easily see what groups are providing or

prohibiting what permission. The root cause here was that Maru lost access to

something. When Priscilla went to fix it, she had to inspect 5+ groups to see

which one had disabled it. What if we made it so Maru could check group

permissions to a feature and/or her company admin?

We wouldn’t need to calcculate it for everyone, just the one person who’s work

is disrupted by this problem. This was related to ENG-9213

DONE [[id:c4cbb750-e46d-42be-ab60-c74e5f5f0cd6][Wednesday Boost]]

CLOSED: SCHEDULED:

ZOOM
https://zoom.us/j/647103643

- Note taken on

Milestones for PLG:

- Are managers actually signing up?

- Prove 25% of users have “ah ha” moment