0effe3c2ae
Review catch. GenericAssetEndpoint.post deduplicates on workspace + external_source + external_id with no project scoping, and answers a match with 409 carrying asset_id and asset_url. For an attachment, asset_url also embeds the owning project and issue ids. When the body omits project_id the create-path validation is skipped entirely, so this branch is the only gate. Knowing the asset UUID is the precondition for every asset-scoped attack on this surface, so the preceding commit closed the routes that consume a foreign id while leaving the path that hands it out -- in the same handler. Two of the reports this branch addresses name this echo as their id-recovery step. Answer 404 when the matched asset's project is not accessible, and keep the 409 echo for a match the caller can reach. 404 rather than 403 deliberately: a 403 would still confirm that some asset holds this external id pair in this workspace, turning the pair into an existence oracle. The 403 used elsewhere in this branch is fine on routes where the caller already named an asset id; here they named only an external id, so a match is new information. The cost is that a caller who guesses a pair held by a project they cannot see cannot create their own asset under it -- the right trade, since real integrations mint ids per source and run as a member of the target project. Contract tests: disclosure with project_id supplied, disclosure with project_id omitted, and two controls proving dedup still echoes for a project member and for a workspace-level asset whose project_id is NULL. Verified fail-before against the previous commit -- the negative case returned 409 with the foreign asset id and its project id in asset_url. Co-authored-by: Plane AI <noreply@plane.so>
Modern project management for all teams
Website • Forum • X • Documentation
Meet Plane, an open-source project management tool to track issues, run sprints cycles, and manage product roadmaps without the chaos of managing the tool itself. 🧘♀️
Plane is evolving every day. Your suggestions, ideas, and reported bugs help us immensely. Do not hesitate to join in the conversation on Forum or raise a GitHub issue. We read everything and respond to most.
🚀 Installation
Getting started with Plane is simple. Choose the setup that works best for you:
-
Plane Cloud Sign up for a free account on Plane Cloud—it's the fastest way to get up and running without worrying about infrastructure.
-
Self-host Plane Prefer full control over your data and infrastructure? Install and run Plane on your own servers. Follow our detailed deployment guides to get started.
| Installation methods | Docs link |
|---|---|
| Docker |  |
| Kubernetes |  |
| Managed hosting |  |
Instance admins can configure instance settings with God mode.
🌟 Features
-
Work Items Efficiently create and manage tasks with a robust rich text editor that supports file uploads. Enhance organization and tracking by adding sub-properties and referencing related issues.
-
Cycles Maintain your team’s momentum with Cycles. Track progress effortlessly using burn-down charts and other insightful tools.
-
Modules Simplify complex projects by dividing them into smaller, manageable modules.
-
Views Customize your workflow by creating filters to display only the most relevant issues. Save and share these views with ease.
-
Pages Capture and organize ideas using Plane Pages, complete with AI capabilities and a rich text editor. Format text, insert images, add hyperlinks, or convert your notes into actionable items.
-
Analytics Access real-time insights across all your Plane data. Visualize trends, remove blockers, and keep your projects moving forward.
🛠️ Local development
See CONTRIBUTING
⚙️ Built with
📸 Screenshots
📝 Documentation
Explore Plane's product documentation and developer documentation to learn about features, setup, and usage.
❤️ Community
Join the Plane community on GitHub Discussions and our Forum. We follow a Code of conduct in all our community channels.
Feel free to ask questions, report bugs, participate in discussions, share ideas, request features, or showcase your projects. We’d love to hear from you!
🛡️ Security
If you discover a security vulnerability in Plane, please report it responsibly instead of opening a public issue. We take all legitimate reports seriously and will investigate them promptly. See Security policy for more info.
To disclose any security issues, please email us at security@plane.so.
🤝 Contributing
There are many ways you can contribute to Plane:
- Report bugs or submit feature requests.
- Review the documentation and submit pull requests to improve it—whether it's fixing typos or adding new content.
- Talk or write about Plane or any other ecosystem integration and let us know!
- Show your support by upvoting popular feature requests.
Please read CONTRIBUTING.md for details on the process for submitting pull requests to us.
Repo activity
We couldn't have done this without you.
License
This project is licensed under the GNU Affero General Public License v3.0.