An issue becomes a chat, a terminal session, and another message asking what happened.
The request has a task, an assigned agent, and a reviewable run.
A ticket is a starting point, not always a complete brief
“Fix the export” may identify a customer problem without explaining the expected format, constraints, or acceptance checks. Keep the original issue context and add the missing information before execution.
Norc can use linked issue context in a run. Configured context gates can send a thin brief back for clarification rather than treating an ambiguous request as ready work.
Coordinate the implementation around the request
Use a task for investigation when the issue needs diagnosis, then connect implementation and documentation tasks as dependencies. Assign the work or use configured routing to choose an eligible agent.
For coding runs, review the resulting changes, checks, and branch or pull-request evidence. An issue state alone does not tell you whether the change solves the customer’s problem.
Use the board that fits the project
Norc has a native Mission Board, so an external issue tracker is not required to coordinate tasks. Connect GitHub or Linear where it helps preserve your existing intake workflow.
Check connector permissions and project settings before bringing in real work. The useful first test is one well-scoped issue with a clear reviewer, not an entire backlog assigned at once.
Practical questions.
Is Notion required?
No. Norc has its own Mission Board. Notion is an optional integration rather than a prerequisite for managing tasks.
Will connecting a tracker automatically solve every issue?
No. Work needs appropriate scope, agent access, routing and execution settings, and review. Start with one issue and verify the complete workflow.
By the Norc team · Product details checked against the Norc project documentation. View the project