Skip to content

Post PBB migration: Refactor "Issue Trigger"  #7075

@t-will-gillis

Description

@t-will-gillis

Overview

The new Projects Beta is structured a little differently from Projects (classic). During to our recent migration from Projects (classic) to Projects Beta, we scrubbed our workflows and removed all functionality that referenced 'columns' as this term is no longer used. We need to refactor our post migration workflows so that they have similar functionality as previously.

Details

Prior to the migration to Projects Beta, preliminary-update-comment.js contained logic that un-assigned a member and posted a message if the member assigned themselves to an issue in the "New Issue Approval" column, and if that issue had neither a Complexity: Prework nor Draft label. This file's logic needs to be rewritten in terms of the 'status' field instead, using GraphQL.

Action Items

UPDATE: PR #6969 addresses the following Action Items:

  • This issue involves GithHub Actions and GraphQL. You will need the new Project Board Beta set up in your repo so that you are able to test and demonstrate your solution. Refer to the "Resources/Instructions" section below to get started, and be sure to let us know if you have questions.
  • In the same section below, see the "Previous (pre-migration) issues" that describe the previous functionality which needs to be emulated as closely as possible in the new projects. Additionally, refer to preliminary-update-comment.js, lines 54-90 +/-: This section is pre-migration code, and may be used as a rough guide for the functionality we want restored.
  • Using GraphQL, refactor this file to restore the previous functionality as noted above and on the previous issues linked below.
  • Note that the files 'draft-label-reminder.md' and 'unassign-from-NIA.md' already exist.

This additional step applies to a special case.

  • In the pre-migration issue-trigger.yml file (see PBB migration "Issue Trigger"  #7053) , line 13, an issue with the phrase "Hack for LA website bot" in its title was sorted to the "Questions/ In Review" column. For the new Projects Beta, if a newly created issue matches this criteria it should be sorted to the "Questions/ In Review" status, which will need to be done in GraphQL

Merge Team

Resources/Instructions

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions