Projects: group work, link a repository, track progress
A project groups tickets that belong together: a product, a customer engagement, a launch. It also carries the one thing Starko AI needs to write code, a link to a repository. Open Projects from the sidebar.
projects list
The projects list
Projects are grouped by status (Backlog, Open, In progress, Done). Each row shows priority, icon and name, progress as closed tickets over all tickets, and the lead. Filter by tenant, company or client to see the projects for one customer. ⌘F focuses the search.
Creating a project
Press Create project at the top of any status group.
project create
Name is the only required field. Add an emoji icon to make it easy to spot in the sidebar.
Description, start and target dates, priority, status and lead are optional.
Tenant, company and client link the project to a customer in the CRM.
Template starts the project with a set of tickets. Browse templates with Use a template, including public ones from other workspaces.
Inside a project
project detail
The project page shows its tickets as a board, list, chart or timeline, the same layouts as the Tickets page, filtered to the project. The header holds the repository link, the project lead and the status. From the header you reach:
Starko AI settings (the gear next to the repository): agent instructions, project context, repo learnings, autonomy, commands, sandbox variables and the warm sandbox. Described in Starko AI, your coding teammate for support tickets.
Share: a read-only link to the board for people outside the workspace.
Slack: a channel to post ticket and pull request updates to.
Pin: pinned projects appear in the sidebar with their active Starko AI sessions underneath.
Linking a repository
Open the project's settings and choose a repository from the GitHub accounts you installed the Starko GitHub App on. You can also create a new repository from the picker. Once linked, every ticket in the project can be handed to Starko AI, and pull requests show on tickets and in the Inbox. See Connect GitHub and set up a repository.
Sub-tickets and relations
Tickets inside a project can have sub-tickets and relations (blocks, blocked by, relates to). The timeline layout draws dependencies between them.
Tips
One project per repository keeps Starko AI's context clean.
Put customer engagements in their own projects and link the company, so Reporting can show work per customer.
Use a template for recurring engagements such as onboarding.
Did this answer your question?