Hello, and thank you for the Copilot app.

Hello, and thank you for the Copilot app. I have been using app sessions to automate repository setup from end to end, and I ran into one gap that I thought was worth reporting.

An agent can now do almost everything unattended: it creates a Projects v2 board, adds the Start date and Target date fields, and creates the Roadmap, Kanban, and Backlog views through createProjectV2View, which accepts a name and a layout. The one thing it cannot do is tell the Roadmap view which fields to use for its date axis. The configuration input on that mutation exposes only visibleFieldIds, and the read side is just as limited, since groupByFields, sortByFields, and filter can all be read but none of them can be written.

The practical effect is that automation stops one step short. After the agent finishes, a person still has to open the project in the browser and pick Start date and Target date by hand. It is a small step, but it is exactly the kind of step people forget, and until someone does it the Roadmap view looks empty, which makes the whole board seem broken to anyone opening it for the first time.

What would help most is being able to set the roadmap date fields, and ideally the grouping, by field ID when creating or updating a view. Inferring them from field names would be less reliable, since those names are chosen freely by each project.

Thank you for considering this, and for the work on the app so far.

---
| Field | Value |
| --- | --- |
| App version | 1.1.6 |
| OS | macOS 15.2.0 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 20 |

Start with the createProjectV2View mutation and its configuration input, especially visibleFieldIds, then compare the readable groupByFields, sortByFields, and filter fields. Done means an agent can set the Roadmap date fields by field ID when creating or updating a view, with grouping support if included; verify the resulting view through the read side.

Written by the indexing model from the issue text.