Add visible fields to project views - #2988
Open
zwick wants to merge 2 commits into
Open
Conversation
zwick
force-pushed
the
zwick-add-project-view-visible-fields
branch
from
August 7, 2026 01:56
d7db5ca to
bbf2398
Compare
zwick
force-pushed
the
zwick-add-project-view-visible-fields
branch
from
August 7, 2026 12:44
bbf2398 to
5b75042
Compare
zwick
marked this pull request as draft
August 7, 2026 13:16
zwick
force-pushed
the
zwick-add-project-view-visible-fields
branch
from
August 7, 2026 13:35
5b75042 to
8d0f208
Compare
zwick
marked this pull request as ready for review
August 7, 2026 13:58
tommaso-moro
previously approved these changes
Aug 7, 2026
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 1421a5d5-fdce-4c0e-9528-56d555ec30d4
Reject roadmap layouts before enumerating project fields in both the create and update paths, and verify view ownership before resolving visible fields on update, so rejected requests no longer pay for a paginated field listing. Skip the follow-up filter mutation when the filter is explicitly null, since a new view has no filter to clear, and include the created view ID when cleanup after a failed filter mutation also fails so the caller can recover the orphaned view. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
zwick
force-pushed
the
zwick-add-project-view-visible-fields
branch
from
August 7, 2026 17:37
8d0f208 to
45526bd
Compare
Contributor
Author
|
Rebased against the changed PR in this stack |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds ordered visible-field configuration to Project view create/update and read-back. This PR is stacked on #2961 and is blocked on that PR.
Why
The stable GraphQL API now supports view
configuration.visibleFieldIdswithout preview headers.What changed
MCP impact
projects_writegrew by 202 bytes / 48 tokens (o200k_base); no parameters were added.Prompts tested (tool changes only)
Security / limits
Uses existing Projects permissions and returns only field database IDs already exposed by Projects tools.
Tool renaming
deprecated_tool_aliases.goLint & tests
./script/lint./script/testAlso passed toolsnap and docs generation checks. Live disposable-resource dogfood covered create/get/list, specialized multi-select resolution, reorder, omission preservation, reset, and verified cleanup without preview headers.
Docs