@julian TBH I really like that they finally added these, as previously we worked around such things with labels. But with these explicit fields we don’t need the labels anymore and can potentially filter better. Also as I'm maintainer or co-maintainer in several big repos, I like that things get standardized and don’t need anymore custom decisions and setups.

@shini92@mas.to hah that's fair, different use cases for different people. I suppose many would find it beneficial.

For me running a smaller project, this stuff is overkill. I wonder if there's a toggle to turn it off.

@julian

One story point equals one unit of effort, remember?

(Micro-managers are killing us all…)

@airwhale@beige.party I was contractor to a team where we had to assign story points based on vibes.

The PM took great pains to tell us story points are unitless and did not have parallels to effort, hours, etc. It was... something.

@julian

My point is that, if using Story Points, they should be a team internal value, not an external metric. I do agree they should take complexity and uncertainty into consideration, but again, this needs to be agreed in each team/squad using them. Considerations local to the system and its context are at play here. Also, they are NOT comparable across teams (which managers just LOVE to be able to do). IMHO.