π Projects
Create, configure, and manage the projects that organize your defect tracking, feedback collection, and error monitoring workflows.
π Overview#
A project in Sniffer is the central workspace for tracking bugs, collecting feedback, and monitoring errors. Each project has its own π Task Board, π Sprints, π¬ Feedback pipeline, π‘ Live Logs, π Integrations, and team roster. You can create separate projects for different products, teams, or clients.
Projects are created using a guided onboarding wizard and appear on your Projects Dashboard where you can access, edit, or archive them.
π Projects Dashboard#
Your landing page after login. Displays all projects in a card layout.
π Project Card Details#
Each card shows:
-
Project Name and color icon
-
Project Key β short identifier used in issue keys (e.g.,
SNF-101) -
Team Members β avatars of assigned members
-
Open Issues β count of unresolved bugs and tasks
-
Last Activity β timestamp of most recent update
π My Tasks#
Access My Tasks from the sidebar to see all issues assigned to you across every project.
β Create Project Wizard#
Click Create New Project to launch the guided wizard. The URL includes the organization type: ?org=SUPPORT, ?org=ENGINEERING, or ?org=MARKETING.
Step 1: π Welcome#
An introduction screen explaining what Sniffer does. Click Get Started to proceed.
Step 2: π Project Details#
Step 3: π‘ Channel Selection#
Choose how bugs and feedback will reach your project:
Tip: βCustomer Feedback Buttonβ is recommended for most teams. If selected, a Widget Customization panel appears with these options:
See π¬ Feedback β for full widget documentation.
Step 4: π§ Connect Your Tools & Set Routing#
A grid of tool groups. For Support projects, the Project Management group is hidden (Support uses Helpdesk tools). For Engineering projects, all three groups appear.
Clicking any tool opens a configuration modal showing:
-
Connection status chip (Connected / Not Connected)
-
If company-level credentials exist: a toggle switch to connect this project
-
If not configured: a βConfigure [Tool]β button navigating to Company Settings
Below the tool groups, a Category Routing matrix appears:
See π Integrations β for detailed setup instructions.
Step 5: π‘οΈ Error Monitoring#
A yes/no choice: βWant to Catch Errors Before Customers Notice?β
If Yes is selected, a configuration panel appears:
If No, error monitoring can be enabled later from βοΈ Settings.
See π‘ Live Logs β for full error monitoring documentation.
Step 6: β Done#
Project is created. You are redirected to the new projectβs π Task Board. A Getting Started Checklist appears in the sidebar showing remaining setup steps.
π± Applications#
Each project can contain multiple Applications β sub-modules representing different parts of your product (e.g., βWeb Frontendβ, βAPI Serverβ, βMobile Appβ).
Navigate to Project β Applications to manage them.
Note: You can register multiple applications under a single project for different environments (staging, production) or multiple domains.
π§ Managing Existing Projects#
βοΈ Edit Settings#
Navigate to Settings from the project sidebar to modify project name, description, icon color, integrations, statuses, and more. See βοΈ Settings & Permissions β.
π¦ Archive#
Deactivate a project while preserving all data. Archived projects can be restored at any time.
ποΈ Delete#
Navigate to Settings β Danger Zone and click Delete Project.
-
A confirmation dialog appears
-
Type the project name to confirm
-
Click Delete to permanently remove all data
β οΈ Warning: Deleting a project is irreversible. All tasks, sprints, feedback, attachments, and settings will be permanently removed. Existing Jira tickets created by Sniffer will remain in Jira but will no longer sync.
π Permissions#
See βοΈ Settings & Permissions β for role details.