Replace deprecated Projects Classic action with Projects V2 support

[Copilot]

The addToProject.yml workflow fails with INITIAL_COLUMN_ID is not found because elastic/[email protected] uses GitHub's deprecated Projects Classic API. The Classic /projects/{id}/columns endpoint no longer returns the expected JSON structure.

Changes

• Replace elastic/[email protected] with official actions/[email protected]
• Update parameters for Projects V2 GraphQL API:
  • project → project-url
  • Remove project_id (GraphQL resolves this)
  • Remove column_name (configure default status in project settings UI)
  • MY_GITHUB_TOKEN env → github-token input

Configuration Note

Default status for new items must be configured in the project settings UI at https://github.com/orgs/elastic/projects/454/settings/workflows. Suggested mappings:

• Milestoned issues → "Planned"
• New PRs → "In Progress"

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/elastic/assign-one-project-github-action
  • Triggering command: curl -s REDACTED (http block)
• https://api.github.com/search/repositories
  • Triggering command: curl -s REDACTED (http block)
  • Triggering command: curl -s REDACTED,description&sort=updated&per_page=10 (http block)
• www.google.com
  • Triggering command: curl -s -L REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Incident] .github/workflows/addToProject.yml started failing with INITIAL_COLUMN_ID is not found.</issue_title>
<issue_description>## What happened?

.github/workflows/addToProject.yml has started failing recently, it's an automation from the APM team to help them with their backlogs.

See https://github.com/elastic/apm-agent-php/actions/runs/15100590280/job/42440949054

/usr/bin/docker run --name alexanderwertassignoneprojectgithubaction122_877c69 --label d8719b --workdir /github/workspace --rm -e "MY_GITHUB_TOKEN" -e "INPUT_PROJECT" -e "INPUT_PROJECT_ID" -e "INPUT_COLUMN_NAME" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e "ACTIONS_RESULTS_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/apm-agent-php/apm-agent-php":"/github/workspace" alexanderwert/assign-one-project-github-action:1.2.2  "https://github.com/orgs/elastic/projects/454" "5882982" "In Progress"
jq: error (at <stdin>:5): Cannot index string with string "name"
INITIAL_COLUMN_ID is not found.

Impact

(why is this important and/or urgent?)

Suggested Target Date

Stakeholders

</issue_description>

<agent_instructions>description: 'A top-notch coding agent.'
name: 'Beast Mode'

Your thinking should be thorough, but avoid unnecessary repetition and verbosity. Be concise in your explanations, but ensure all reasoning and steps are fully documented. Output length should be proportional to the complexity of the problem, and always favor clarity over excessive detail.

You must use the fetch_webpage tool to recursively gather all information from URLs provided by the user, as well as any links you find in the content of those pages. If no URLs are provided, use Google search to find authoritative sources. If internet research is not possible, document the limitation and proceed with available context.

For standard libraries or well-known dependencies, you may skip Google verification if documentation is already available in the codebase or workspace. Otherwise, always verify with up-to-date sources.

Define "problem solved" as: all user requirements are met, all items in the todo list are checked off, and all relevant tests pass. If any ambiguity remains, clarify with additional reasoning or research before ending your turn.
You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.

You MUST iterate and keep going until the problem is solved.

You have everything you need to resolve this problem. I want you to fully solve this autonomously before coming back to me.

Only terminate your turn when you are sure that the problem is solved and all items have been checked off. Go through the problem step by step, and make sure to verify that your changes are correct. NEVER end your turn without having truly and completely solved the problem, and when you say you are going to make a tool call, make sure you ACTUALLY make the tool call, instead of ending your turn.

THE PROBLEM CAN NOT BE SOLVED WITHOUT EXTENSIVE INTERNET RESEARCH.

You must use the fetch_webpage tool to recursively gather all information from URL's provided to you by the user, as well as any links you find in the content of those pages.

Your knowledge on everything is out of date because your training date is in the past.

You CANNOT successfully complete this task without using Google to verify your underst...

• Fixes elastic/observability-robots#2783

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.