I moved most tasks from the cloud-services-team (Kanban) milestone board to the cloud-services-team project board. Columns have retained the same names, but there is a new column "FY2022/2023-Q3" that is displayed automatically because a new milestone has been created with that name.

Clicking on the title of that column will take you to a new board that is a "zoomed-in" view, showing the same tasks that are in the "Q3" column of the main board, divided into 4 columns: Backlog, In progress, Blocked and Done.

I went through the tasks that were in the "Doing" column of the old kanban board, moved the ones that had recent activity to "In progress" in the Q3 board, and moved back to "Inbox" the tasks that didn't seem to have any recent activity. Feel free to move tasks to a more appropriate column if you're planning to work on them soon.

This isn't likely to be the final state of the boards, but I hope that iterating on their shape will lead us to a place where the boards are more useful for people inside and outside of the team.

If you have any comments or concerns, please leave a comment below!

In T327309#8540533, @fnegri wrote:

I moved most tasks from the cloud-services-team (Kanban) milestone board to the cloud-services-team project board.

I have disabled {H356} which was likely fighting against this change for new tasks. It might not be a bad idea to setup an inverse rule to help with muscle memory of tagging things with cloud-services-team (Kanban).

Thanks @bd808 -- I like the idea of the reverse rule, I've added it as a suggestion in T327407.

I also noticed that the Phaultfinder bot is using the old tag, see for example T327375. The reverse rule would fix it, but maybe it's worth updating the bot as well.

One more thing: I noticed that for quite a few tasks that were in the old "Doing" column, you had moved them from "Inbox" to "Doing" in Sep 2022. They didn't seem really active, was it a way to "highlight" them in some way? I have moved them back to "Inbox", I hope I didn't "erase" any useful info about those tasks.

In T327309#8541285, @fnegri wrote:

Thanks @bd808 -- I like the idea of the reverse rule, I've added it as a suggestion in T327407.

I can make us one. I'll follow up on the linked task.

I also noticed that the Phaultfinder bot is using the old tag, see for example T327375. The reverse rule would fix it, but maybe it's worth updating the bot as well.

Per the description at @phaultfinder, @fgiunchedi is probably the right person to ask about doing that.

One more thing: I noticed that for quite a few tasks that were in the old "Doing" column, you had moved them from "Inbox" to "Doing" in Sep 2022. They didn't seem really active, was it a way to "highlight" them in some way? I have moved them back to "Inbox", I hope I didn't "erase" any useful info about those tasks.

I think I moved a bunch of things to Doing because they had folks assigned to them. A historical assumption was that folks would not lick the cookie by taking ownership of a task unless they were actually working on the task.

In T327309#8542168, @bd808 wrote:

In T327309#8541285, @fnegri wrote:

Thanks @bd808 -- I like the idea of the reverse rule, I've added it as a suggestion in T327407.

I can make us one. I'll follow up on the linked task.

I also noticed that the Phaultfinder bot is using the old tag, see for example T327375. The reverse rule would fix it, but maybe it's worth updating the bot as well.

Per the description at @phaultfinder, @fgiunchedi is probably the right person to ask about doing that.

Essentially the alertmanager configuration at modules/alertmanager/templates/alertmanager.yml.erb needs updating with the new PHID to use when opening tasks. The relevant lines are the ones with a webhook config talking to localhost:8292, IOW:

  - name: 'wmcs-pagetaskircmail'
    victorops_configs:
      - routing_key: 'wmcs'
    webhook_configs:
      # #wmcs tag, cloud-services-team is deprecated in favor of this one
      - url: 'http://localhost:8292/alerts?phid=PHID-PROJ-7sul7hj32btacinsnubq'
        send_resolved: false
      - url: 'http://<%= @active_host %>:19190/wikimedia-cloud-feed'
>>  email_configs:
      - to: 'cloud-admin-feed@<%= @facts["networking"]["domain"] %>'

  - name: 'wmcs-taskircmail'
    webhook_configs:
      # #wmcs tag, cloud-services-team is deprecated in favor of this one
      # title={{groupLabels.alertname}} {{groupLabels.instance}} {{commonAnnotations.description}}
      - url: 'http://localhost:8292/alerts?phid=PHID-PROJ-7sul7hj32btacinsnubq&title=%7B%7BgroupLabels.alertname%7D%7D%20%7B%7BgroupLabels.instance%7D%7D%20%7B%7BcommonAnnotations.description%7D%7D'
        send_resolved: false
      - url: 'http://<%= @active_host %>:19190/wikimedia-cloud-feed'
>>  email_configs:
      - to: 'cloud-admin-feed@<%= @facts["networking"]["domain"] %>'

HTH!

@fnegri I have added the "hash" wmcs-current for the latest milestone, we can move that one every time we create a new one, that way there's a static name for the current milestone we can use in places like that (and my own scripts xd)

@dcaro thanks, that sounds like a good idea!