FYI, I think @gpaumier has a plan for this in the coming quarters, to coincide with the Product and Technology departments being merged. :)

I can report today that while the site is still slower than I'd expect, there was a marked improvement. OK to close this for now and re-open, as needed (or as I can replicate better).

@ldelench_wmf to confirm stakeholders and stewardship for this to determine if it is still relevant

Update after meeting with Desiree!

@MaryMunyoki Hi! Just want to make sure you're aware of this. Please let me know if you have questions. :)

@Aklapper Thanks for the reminder! We do have mechanisms for updating elapsed Due Dates but neglected this one.

Ah, OK, great, thanks for the clarification. I'll keep an eye out.

Thanks, @matmarex . If I'm understanding correctly, restoring the original functionality is not possible due to Phab's new model for attachments. If that's the case, while documenting how-to is important, I think it's more important for the Phab UI to give instructions. The issue I'm hearing from folks is not that they don't know how to fix the issue, but that they forget (or, in the case of bug reporters, don't realize), because it's not intuitive.

Thanks, @brennen ! I know you folks have a lot going on and really appreciate your attention on this. :)

From Desiree, after I reached out to sync:

@Aklapper Here we go: https://phabricator.wikimedia.org/T310188

@Aklapper Thanks for the reminder about the Due Date. For some reason, this task does not show the Due Date stamp on the board view, so it's often overlooked. If that's causing problems, we could probably just clear that field. We think it might be a bug related to the form (perhaps being changed midway?) but we're not sure. See https://phabricator.wikimedia.org/T279593#7672410

In the meantime, I wonder how hard it would be to replace our Phab instance functionality with this one. Standard caveats apply, of course (it's probably not as easy as I think, and there might be more than the zero people I see using the existing functionality). Having said that, my ignorant observation is that we could swap which number in the column is targeted (from points to count). I imagine a small UI tweak would be needed, too, so that the visual is on the right numbers.

Added a ticket: https://we.phorge.it/T15100

Adding @LGoto as an interested party.

@ggellerman to reach out to non-TPgM team folks about status

I filed a task for improving the UX in the current setup (regardless of what we decide): T302525: When a project is not public, it appears to users outside "Visible To" criteria as "Unknown Object", which is confusing

I also re-read your comment and realize that you already showed which task you screenshotted in T302441: Create a Wiki page describing the virtual bonfire - somewhere, so apologies for missing that and asking about it. It also helps me understand the problem a little more, which seems to be that the projects are private. I appreciate your patience as I digest. :)

Thanks for flagging this again. I agree that the UI in these circumstances is unfortunate and confusing, and that public-by-default is generally valuable, values-friendly, and eases these UI edge cases.

Update the acceptance criteria for this ticket: focus on the team's skills rather than individual (individual assessment, but output reflects the team). If a team has already completed this on the individual level, help teams convert that to a team-level assessment.

Shifted task visibility deliberately :)

Regarding Due Date stamp not showing on this task:

@ggellerman to chat with @ldelench_wmf about a good starting point for the artefact.

Hmm. FWIW, I see that and think "I don't have some emoji coded properly"

Barring an alternative icon that universally conveys "open" I feel similarly, though that may be simply what I am used to since the icons are new.