Tue, Nov 15
Oct 11 2022
Aug 10 2022
@ldelench_wmf to confirm stakeholders and stewardship for this to determine if it is still relevant
Aug 3 2022
Aug 1 2022
Update after meeting with Desiree!
Jul 20 2022
@MaryMunyoki Hi! Just want to make sure you're aware of this. Please let me know if you have questions. :)
Jun 30 2022
@Aklapper Thanks for the reminder! We do have mechanisms for updating elapsed Due Dates but neglected this one.
Jun 29 2022
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.
Jun 22 2022
Thanks, @brennen ! I know you folks have a lot going on and really appreciate your attention on this. :)
Jun 15 2022
From Desiree, after I reached out to sync:
Jun 8 2022
Jun 7 2022
@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
Jun 3 2022
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
Jun 2 2022
Adding @LGoto as an interested party.
Apr 28 2022
Apr 25 2022
Apr 20 2022
Apr 14 2022
Mar 31 2022
Mar 9 2022
@ggellerman to reach out to non-TPgM team folks about status
Mar 4 2022
Mar 1 2022
Feb 24 2022
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.
Feb 23 2022
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.
Feb 21 2022
Feb 19 2022
Feb 18 2022
Feb 17 2022
Feb 2 2022
Shifted task visibility deliberately :)
Regarding Due Date stamp not showing on this task:
Jan 19 2022
Jan 7 2022
Dec 22 2021
Dec 15 2021
Dec 14 2021
Hmm. FWIW, I see that and think "I don't have some emoji coded properly"
Dec 13 2021
Dec 9 2021
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.
Dec 7 2021
Nov 23 2021
Nov 22 2021
Nov 19 2021
Word. By all means, change it if that's generally accepted :)
Good question! I am a dinosaur when it comes to the naming/coloring/icon conventions established early on in WMF's use of Phab, and though I know some constraints have lessened more recently, I still shy away from things like "use the global tag icon and color" when making these sorts of things. If folks like you and @Aklapper don't mind, neither do I. :)
All my tasks are tagged with 1 team (cloud services), so you could say it's limited to 1. They might have other team tags too, though I don't usually manage/take care of those. There's many project tags too, that I do care, but there's only one team tag that I care of.
Nov 18 2021
FWIW, I think that this approach isn't exclusive of personal tasks or otherwise. You could, for example, have "SRE-origin-user" and track that on your own board. In fact, that would add a layer of tracking in the event that you had multiple teams.
Right, sorry, lemme re-rephrase: I'm assuming that you are tracking on behalf of one team or more (SRE?). Even if the data is just for your use right now, "SRE-origin-user" fits more neatly with existing naming conventions, and also lends itself to being picked up by others on that team in the event that it's a brilliant system but you've struck it rich and have left to live on your Caribbean island. :)
Nov 17 2021
While investigating Hatjitsu generally, I came upon some alternatives (via https://trello.com/b/2Fggyc6X/remote-team-tools) that may help in the interim:
(Also worth noting that while http://hatjitsu.herokuapp.com/ still exists as a replacement, some folks don't use it because the spinning feature that is present on that instance makes some people nauseous. It's also not clear to me if that instance suffers the same issue, but I assume no).