Lavagna VS Trac

Lavagna - Java is bad, looks updated recently, no demo, not better than OP

For instance, when I enter Trac-2345, logseq knows that it must be replaced by a link to the ticket number 2345 in my Trac ticket system.

Before there was Github, I used this software called Trac since it worked with subversion. It was so cool to be able to view source code and commits on the web. Then around 2007 or so I started using git and then in 2009 I created a Github account...so proud of Github and Rails. Thanks for the writeup!

Trac. https://github.com/edgewall/trac

For my documentation : Trac

Try Trac, I've used it before without issues.

Trac - SQL based (literally in the GUI) issue tracker & documentation, not bad, not for me

While many projects these days choose to take reports of issues alongside where their code is hosted, some prefer to use an open source or third-party solution, such as Bugzilla or Trac. Wherever a project takes reports of issues and discusses them, making it very clear where community members should report current issues makes it an easier experience for them. As a side benefit, it lowers costs for maintainers by reducing the amount of redirection they need to do.

Trac Project - Free, Open Source, Self-hosted. Provides issue management, source control integration, wiki etc.

In github, you can link to an issue just by typing #500. Trac had similar auto-link types for linking to source code lines, issues, etc.

I really like this idea and wish all project management tools included it by default. Fwiw Fogbugz has been using it for over a decade, called Evidence Based Scheduling:

- https://www.joelonsoftware.com/2007/10/26/evidence-based-sch...

- https://support.fogbugz.com/hc/en-us/articles/360011258994-E...

- https://blog.fogbugz.com/evidence-based-scheduling

There’s at least one Jira app for it:

- https://github.com/handshake/pystradamus

And Trac also used to have EBS but I’m not sure if it still does, can’t find it atm:

- https://trac.edgewall.org/