toodles vs SIT

Our great sponsors

InfluxDB - Power Real-Time Data Analytics at Scale

WorkOS - The modern identity platform for B2B SaaS

SaaSHub - Software Alternatives and Reviews

Our great sponsors

toodles		SIT
	Project
2	Mentions	1
966	Stars	557
-	Growth	0.4%
1.8	Activity	0.0
about 1 year ago	Latest Commit	over 5 years ago
Haskell	Language	Rust
MIT License	License	Apache License 2.0

The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

toodles

Posts with mentions or reviews of toodles. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-09-05.

Project Management from TODOs in Codebase
1 project | news.ycombinator.com | 5 Sep 2021
todo-or-die – TODOs you cannot forget!
6 projects | news.ycombinator.com | 5 Sep 2021

This reminded me of toodles[0], a nice project you can use to visualize TODO comments as issues. I didn't have the chance to try it, but I'm looking forward it for my next project
[0] https://github.com/aviaviavi/toodles

SIT

Posts with mentions or reviews of SIT. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-09-05.

todo-or-die – TODOs you cannot forget!
6 projects | news.ycombinator.com | 5 Sep 2021

I want the opposite - tickets-as-code part of the git repo. Something like SIT[1]. Fossil has it, but today's standard DVCS is git.
There are 2 trends here:
1. Everything-as-a-code stored in the git repo in a text format, close to the actual source code. If you store documention-as-a-code, diagrams-as-a-code, IaaC, tests-as-a-code, loadtesting-as-a-code, etc. - then why not issues/tickets as code also?
2. Reduce number of tools/service you use in order to eliminate impedance mismatch and simplify workflows, and remove barriers to collaboration. For example if you standardize on Github, then you can use Guthub Issues, Projects, Packages, Actions, Codespaces, etc. And most developers are already having Github a/c.
[1] https://github.com/sit-fyi/sit

What are some alternatives?

When comparing toodles and SIT you can also consider the following projects:

todo-or-die - TODOs you cannot forget!

Erxes - Source available experience management infrastructure. Pioneering the future of experiences with XOS (Experience Operating System). Hubspot + Qualtrics alternative

todo_or_die - Write TODOs in code that ensure you actually do them

OTRS - ((OTRS)) Community Edition is one of the most flexible web-based ticketing systems used for Customer Service, Help Desk, IT Service Management. Please note that ((OTRS)) Community Edition offers limited OTRS functionality.

spiros - my custom prelude

MantisBT - Mantis Bug Tracker (MantisBT)

enumerate-function

Zammad - Zammad is a web based open source helpdesk/customer support system

django-todo - A multi-user, multi-group todo/ticketing system for Django projects. Includes CSV import and integrated mail tracking.

GLPI - GLPI is a Free Asset and IT Management Software package, Data center management, ITIL Service Desk, licenses tracking and software auditing.

osTicket - The osTicket open source ticketing system official project repository, for versions 1.8 and later

HuBoard - Kanban board for github issues