Where should a tick be submitted? - briefly
Submit the tick to the project's official issue‑tracking system, such as its bug‑tracker or support portal. Follow the provided submission guidelines for format and required details.
Where should a tick be submitted? - in detail
When you need to record a tick, direct it to the system that is designed to capture and process such items. For software projects, the appropriate destination is the project's issue‑tracking platform (e.g., GitHub Issues, GitLab, Jira). The submission should contain:
- A concise title that identifies the problem.
- A clear description of the observed behavior.
- Steps to reproduce, including input data and environment details.
- Expected outcome versus actual outcome.
- Relevant logs, screenshots, or error codes.
If the tick concerns hardware or a physical device, send it to the manufacturer’s support portal or authorized service center. Include the serial number, purchase date, and a description of the fault.
For biological ticks (parasites) collected for identification, forward the specimen to a certified public‑health laboratory or university entomology department. Provide collection date, location, host information, and preservation method.
In all cases, use the official submission channel rather than informal discussion boards, ensuring the tick enters the workflow that triggers tracking, assignment, and resolution.