Connection
Connects in a few lines.
Create an access token in your profile and add it to your tool.
Orciss brings boards, sprints, timelines, testing, goals and a service desk into one product. You start with three columns on day one; approvals, rules and automation arrive when you switch them on.
Nothing to install. Runs in your browser.
Search| Key | Title | Status | Due |
|---|
No rules, no schemes, no admin. Turn the depth switch and the same board gains layers.
Issues and figures in these windows are sample data.
Why a new tool
These aren’t edge cases. They’re things teams need every day and have been voting for year after year.
2,800 votes, open since 2004. In Orciss every field can have a default.
Votes for five features that tool’s simple project type lacks. Orciss has a single project type.
Three of its seven top-selling add-ons are for test management. In Orciss, testing is built in.
| Request | Votes | Open for | Orciss |
|---|
Figures were read on 11 November 2026 from the public request tracker and add-on marketplace of the industry’s most widely used issue tracker; they may have changed. The vote count in the last row is low because duplicate requests were merged.
Features
Everything below runs in one product, under one permission model.
AI
Orciss doesn’t put an assistant button in every corner. You connect the tool you already use over MCP; it reads and updates issues with exactly your permissions.
Connection
Create an access token in your profile and add it to your tool.
Permissions
The agent can do whatever the token’s owner can do in their role. Nothing more.
Code
Branches, PRs and commits show on the issue; when the PR merges, the status moves on its own.
The command shown is illustrative; current connection steps are in the app under Profile → API and MCP.
Modules
Timeline, milestones, releases and per-person capacity.
instead of roadmap and capacity add-onsBranches, PRs and commits show on the issue. When the PR merges, the status moves on.
instead of updating status by handTest cases, test cycles and a requirements traceability matrix.
instead of a test management add-onOKRs at company, team and personal level. A key result can be tied to a query.
instead of a separate OKR toolCustomer portal, request forms and an SLA queue. A request becomes an issue.
instead of a separate service deskOur principles
An issue stays an issue, a project stays a project. You won’t wake up to a different word.
Major interface changes take effect when the workspace admin decides.
There’s no button in the interface you’ll have to turn off.
Download all your issues as CSV and JSON whenever you like.
Enterprise
Security and administration aren’t a layer added later; every action goes through the same permission check.
Migration
Export your issues as CSV from your current tool.
The Summary, Status, Assignee, Labels and Story Points columns are mapped automatically.
Check the preview, adjust the mapping if needed, then import.
Workflow and permission schemes are set up by hand for now.
FAQ
Teams that build software. A small team starts with a three-column board on day one and, as it grows, switches on rules, approvals and reports in the same project.
The Orciss query language resembles the one you’re used to but isn’t fully compatible. You’ll need to rewrite your filters; common expressions such as status, assignee, label, date and sorting have direct equivalents.
Both. You choose per project and can change it later. Sprints, backlog and WIP limits are ready to use.
No. Orciss focuses on issue tracking; your documents and chat stay in the tools you already use.