Page MenuHomePhabricator
Create Task
Maniphest T141826

Update Collaboration team Herald rules
Closed, ResolvedPublic
Actions

Description

Please update the Collaboration team Herald rules as follows:

We're going to try to use milestones instead of the explicit excludes for future quarters, but for now the above should work (I don't think you can change an existing project into a milestone).

For history, see:

Related Objects

Event Timeline

• Mattflaschen-WMF created this task.Aug 1 2016, 10:41 PM
Restricted Application added subscribers: TerraCodes, Aklapper. · View Herald TranscriptAug 1 2016, 10:41 PM
• Mattflaschen-WMF changed the task status from Open to Stalled.EditedAug 1 2016, 11:09 PM

I want to check one thing before you make this change.

• Mattflaschen-WMF added a comment.Aug 1 2016, 11:22 PM

This is good to go as originally stated.

• Mattflaschen-WMF changed the task status from Stalled to Open.Aug 1 2016, 11:22 PM
Danny_B claimed this task.Aug 2 2016, 1:18 AM
Danny_B triaged this task as Medium priority.
Danny_B moved this task from To Triage to Herald rules on the Phabricator board.
Danny_B subscribed.

{H26} updated.

Danny_B added a comment.Aug 2 2016, 1:22 AM

{H180} created.

• Mattflaschen-WMF added a comment.EditedAug 2 2016, 1:23 AM

Please add back Collaboration-Team-Archive-2015-2016 to the "Projects do not include" list of H26.

Danny_B closed this task as Resolved.Aug 2 2016, 1:23 AM

I strongly encourage you to use subprojects and/or milestones instead of separate projects though.

• Mattflaschen-WMF reopened this task as Open.Aug 2 2016, 1:25 AM

Please see my comment above re H26.

We do plan to use milestones for future quarters (the Q1 board was created before we decided on this new/revised plan).

Danny_B added a comment.Aug 2 2016, 1:26 AM
In T141826#2513900, @Mattflaschen-WMF wrote:

Please add back Collaboration-Team-Archive-2015-2016 to the "Projects do not include" list of H26.

Done. The description was not unambiguous, sorry for noise.

Danny_B closed this task as Resolved.Aug 2 2016, 1:26 AM
• Mattflaschen-WMF reopened this task as Open.Aug 2 2016, 1:26 AM
• Mattflaschen-WMF updated the task description. (Show Details)
Danny_B added a comment.Aug 2 2016, 1:27 AM
In T141826#2513904, @Mattflaschen-WMF wrote:

Please see my comment above re H26.

We do plan to use milestones for future quarters (the Q1 board was created before we decided on this new/revised plan).

Phabricator does not notify users on "edit conflicts" and this was a clear example of it...

• Mattflaschen-WMF closed this task as Resolved.Aug 2 2016, 1:27 AM
Danny_B added a comment.Aug 2 2016, 1:30 AM
In T141826#2513904, @Mattflaschen-WMF wrote:

Please see my comment above re H26.

We do plan to use milestones for future quarters (the Q1 board was created before we decided on this new/revised plan).

It is possible to attach currently separate projects as subprojects or milestones with keeping their boards.

• Mattflaschen-WMF reopened this task as Open.Aug 2 2016, 1:32 AM

Sorry. This is my fault.

Can you also add Edit-Review-Improvements and Collab-Notifications-Page (it would be nice if that was automatic since it's part of Notifications , but evidently not per T141836) to the "Include any" of H26?

• Mattflaschen-WMF added a comment.Aug 2 2016, 1:38 AM
In T141826#2513913, @Danny_B wrote:

It is possible to attach currently separate projects as subprojects or milestones with keeping their boards.

How can I do that? I know about https://phabricator.wikimedia.org/project/subprojects/65/ , but I only see options to create projects.

Danny_B added a comment.Aug 2 2016, 1:40 AM
In T141826#2513930, @Mattflaschen-WMF wrote:

Sorry. This is my fault.

Can you also add Edit-Review-Improvements and Collab-Notifications-Page (it would be nice if that was automatic since it's part of Notifications , but evidently not per T141836) to the "Include any" of H26?

Done.

• Mattflaschen-WMF closed this task as Resolved.Aug 2 2016, 1:41 AM

Thanks, sorry about initially missing those projects, and the back and forth.

(Please do let me know about attaching existing boards as milestones, but that doesn't block resolving the task).

Danny_B added a comment.Aug 2 2016, 1:43 AM
In T141826#2513934, @Mattflaschen-WMF wrote:
In T141826#2513913, @Danny_B wrote:

It is possible to attach currently separate projects as subprojects or milestones with keeping their boards.

How can I do that? I know about https://phabricator.wikimedia.org/project/subprojects/65/ , but I only see options to create projects.

In T141826#2513936, @Mattflaschen-WMF wrote:

(Please do let me know about attaching existing boards as milestones, but that doesn't block resolving the task).

(For the record: communication followed on IRC, as the task is resolved and this would be different one.)

• Mattflaschen-WMF reopened this task as Open.Aug 2 2016, 2:07 AM

Really sorry to once again reopen this, but might as well keep it all in one place since it's tightly related:

I forgot that Collab-Team-Q1-July-Sep-2016 is a subproject of Collaboration-Team-Triage (which I think I did because the docs say "Sprint is for sub-projects of a team being worked on in a certain time frame"). So per https://secure.phabricator.com/book/phabricator/article/projects/#subprojects-and-mileston , "When a project tag is added that is the ancestor or descendant of one or more existing tags, the old tags are replaced" (this goes both ways).

So I don't think H180 has any effect, and it should be archived. Sorry.

Danny_B added a comment.Aug 2 2016, 2:13 AM

Correct.

I assumed it is separate project and didn't verify it is subproject.

The same will actually apply to {H26}, so I can modify that one too.

Danny_B added a comment.Aug 2 2016, 2:13 AM

{H180} archived.

Danny_B closed this task as Resolved.Aug 2 2016, 2:28 AM
In T141826#2514062, @Danny_B wrote:

The same will actually apply to {H26}, so I can modify that one too.

After clarification on IRC this has been found as not desired.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL