Remove Type field details addition in sync-bug-triage-github-project-beta.sh

[Rajalakshmi-Girish]

What type of PR is this:

/kind cleanup

What this PR does / why we need it:

periodic-sync-bug-triage-github-project-beta-1-34
has been failing with below error:

Starting sync...
[INFO] Fetching the list of open issues and PRs from k/k under the current release milestone, v1.34
[INFO] Getting metadata for the Bug Triage GitHub Beta Project with ID: 80
[INFO] Feeding data from k/k issues into the GitHub Project Beta
gh: Could not resolve to a node with the global id of ''

The Bug Traige board does not need the information if the item is an issue/pr. The icon against each row indicated it's Type.

Special notes for your reviewer:

New changes in GH https://github.com/github/docs/commits/main/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Rajalakshmi-Girish
Once this PR has been reviewed and has the lgtm label, please assign fsmunoz for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• release-team/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wendy-ha18]

LGTM

[Priyankasaggu11929]

Folks, feel free to take the final call. 🙂

Just adding some context behind the original Type field with multi-value options (PR and Issue) — it was added to get a filtered view and a quick total count of Issue and PR items tracked by the bug triage team.

Example of such a filtered view:

---

I used the following patch to fix the script

(rename the field Type -> Tracking Type.
Found the Tracking Type field in the GH board template used by the Release Team)

diff --git a/release-team/hack/sync-bug-triage-github-project-beta.sh b/release-team/hack/sync-bug-triage-github-project-beta.sh
index 903d022b..dfdab0a0 100755
--- a/release-team/hack/sync-bug-triage-github-project-beta.sh
+++ b/release-team/hack/sync-bug-triage-github-project-beta.sh
@@ -54,13 +54,13 @@ function get_field_ids_from_github_beta_project() {
         query='.data.organization.projectV2.id'
     elif [ "$1" == "type-id" ]
     then
-        query='.data.organization.projectV2.fields.nodes[] | select(.name== "Type") | .id'
+        query='.data.organization.projectV2.fields.nodes[] | select(.name== "Tracking Type") | .id'
     elif [ "$1" == "issue-id" ]
     then
-        query='.data.organization.projectV2.fields.nodes[] | select(.name== "Type") | .options[] | select(.name== "Issue") | .id'
+        query='.data.organization.projectV2.fields.nodes[] | select(.name== "Tracking Type") | .options[] | select(.name== "Issue") | .id'
     # for "pr-id"
     else
-        query='.data.organization.projectV2.fields.nodes[] | select(.name== "Type") | .options[] | select(.name== "PR") | .id'
+        query='.data.organization.projectV2.fields.nodes[] | select(.name== "Tracking Type") | .options[] | select(.name== "PR") | .id'
     fi
 
     ID="$( gh api graphql -f query='

[Priyankasaggu11929]

Also, testing the PR changes locally. I'm getting following error:

❯ MILESTONE=1.34 GITHUB_TOKEN=<gh-PAT-token> PROJECT_NUMBER=219 ./sync-script-pr-2788.sh

Starting sync...
[INFO] Fetching the list of open issues and PRs from k/k under the current release milestone, 1.34
[INFO] Getting metadata for the Bug Triage GitHub Beta Project with ID: 219
[INFO] Feeding data from k/k issues into the GitHub Project Beta
gh: Argument 'fieldId' on InputObject 'UpdateProjectV2ItemFieldValueInput' is required. Expected type ID!
Argument 'value' on InputObject 'UpdateProjectV2ItemFieldValueInput' is required. Expected type ProjectV2FieldValue!

[Priyankasaggu11929]

/hold

[Rajalakshmi-Girish]

@Priyankasaggu11929, following your comment, renaming the field from Type to Tracking Type seems reasonable.

Would it be appropriate for me to go ahead and submit the changes you suggested in this PR?

@wendy-ha18 @Vyom-Yadav — I’d appreciate your input on whether this approach makes the most sense moving forward.

[wendy-ha18]

I also think using Tracking Type is better than removing it completely, at least for now. @Vyom-Yadav it's your call.