I think it’s fixed, so I’ll mark it as done. If it comes back I guess I can “do this again”... Daniel explained it pretty well.
To get into the technical details, when a Person joins a Goal, the Person has a TeamMember, which belongs to a Team. Both the Team and TeamMember point to the Goal (for performance reasons). This can cause problems when something bad happens and the Team and TeamMember point to different goals (which was happening when a big goal rename crashed while moving the team to the new goal).
To sort the messed up TeamMembers out I wrote a script that made all the TeamMembers point to the same Goals as the Teams they were on, and made sure people weren’t on the same goal twice. Unfortunately the script isn’t smart enough to figure out which goal people actually wanted to be on. So some people who were affected might find themselves unexpectedly on an old goal, and some people with duplicate stuck goals might find their entries on a different goal than they were expecting. But all of their goals should be unstuck, so they should be able to post entries, complete, delete, etc. them. 7 years ago
Here’s what I understand to be happening with this highly annoying bug. Someone creates a goal, then invites people as a “team”. But not just a few people … a lot of people. What happens next is where things go wonky. Someone on that team will edit the goal name. That essentially creates a new goal with the corrected spelling or adjusted wording … which in turn tries to drag all the other team members over to the newly named goal. In goals with not too many team members this works fine. But when there are a lot of team members and/or content associated with the original goal name the script which drags over your entries, comments and cheers crashes at some point. This results in a divided team and also in having a “completed” goal that remains on your list. Since it’s completed you can’t remove it—which is frustrating as all get out!
With much talking between Robots … and new Robot Laurel asking some important questions we came to a 3-pronged solution. We’re going to locate all the current corrupt goals, fix corrupted goals and also disallow the ability to change a goal name for future team goals. This should prevent the issue in the future. However, once you create a goal and invite people as team members you won’t be able to change the goal name any longer. That’s the trade-off. But a good one in my opinion.
Keep your fingers crossed and we’ll see if this all works in the coming days. Here’s a sketch of the conversation and the data model that we’re untangling. 7 years ago
I rejoined this newly named goal. Can I write an entry? 7 years ago
I’m writing an entry. 7 years ago
Users (thanks to all of you) have been reporting a mysterious teams bug whereby people create teams, rename the goal and find out that some of their teamates get left in the dust. When they reinvite some of the people they either can’t join the new goal or can’t post to the new goal. Or the goal they have on their list doesn’t match the goal page.
At any rate, you can see how damn complicated it gets as there doesn’t seem to be any consistency in the bug activity—but I know there’s a dirty bug hidden way deep down. Somwhere below the crust. Below the asthenosphere. Way past the upper and lower mantle. Perhaps in the liquid iron core. Or maybe … just maybe in the solid iron core.
This team goal (which I’ve invited Robots to) is my attempt to unravel this mystery and kick it to the curb once and for all. 7 years ago