yet another ticketing system
Clone or download
Henner + § for docids
= redisign doc template
Latest commit 90a34dc Jan 14, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin +-= initiale ignition Jun 18, 2014
build +-= initiale ignition Jun 18, 2014
debian/scripte + djradicale & radicael Aug 22, 2018
modules + § for docids Jan 14, 2019
sites + fix static on 500er errors Oct 16, 2018
test + fileupload test Sep 3, 2018
vagrant = setup Sep 20, 2018
.gitignore + ignore vagrant running stuff... Jul 26, 2014
LICENSE + mit license Oct 25, 2017
README.md + more feature Aug 30, 2018
build.xml +-= cur ver Oct 16, 2018
help.txt +-= cur ver Aug 7, 2018
todo.txt + show_start Nov 5, 2018

README.md

YATS

license GitHub issues GitHub pull requests GitHub contributors GitHub forks GitHub stars

DEMO

https://yats.mediafactory.de

Staff User:
Login: staff.user
Password: qwertz

Customer User:
Login: customer.user
Password: qwertz

Or use vagrant!

VAGRANT

howto:

$ cd vagrant
$ vagrant up

Wait! :-) Point your browser at: http://192.168.33.11 or for admin interface: http://192.168.33.11/admin

Staff User:
Login: admin
Password: admin

WHY JUST ANOTHER?

We used to use TRAC for a long time and were quiet happy. But every time, we wanted to customize it, it took us a long to rethink the way, trac was developed or find a plugin working with our version.
Today all our web projects are build on top of django. So it is much easier to change YATS and we are faster in adding new feateures. We think, we kept it simple in the backend, so it is still easy to modifie for people not familiar with the YATS source (as long as you know django).

KEY FEATURES

  • CalDAV support - reports are populated as todo lists in external ToDo Tools
  • custom fields (mandatory fields and default values configurable)
  • different view of tickets for customers - fields hideable from customers (even in emails)
  • mails for ticket changes, comments, close, reopen, reassign
  • searchable fields configurable
  • searches saveable as reports
  • nice visual for complex search supporting AND and OR in groups
  • ticket history and general logs of what you have done
  • ticket references (including back references)
  • complex workflows (create the workflow you need)
  • multiple kanban boards with columns saved from searches
  • file attachments with drag/drop (optionally virus scanned)
  • preview of all uploaded files
  • twitter bootstrapp 2 - responsive layout
  • git TAGS from Github as versions example
  • XML-RPC API
  • compatible with tracker (see https://github.com/mediafactory/tracker)
  • simple, but yet powerful! No real magic :-) 2 sourcefiles besides the django stuff (tickets.py and shortcuts.py)
  • SSO (single sign on), if you are using multiple YATS and YATSE (but you or your customers can still login locally)
  • Simple-Mode for using YATS as a simple task manager
  • Github-Style ToDo list inside tickets
[ ] my first ToDo
[ ] my second ToDo
[X] third ToDo
[ ] 4. ToDo

INSTALLATION

no pypi package yet!

needs: see requirements.txt AND all modules from modules folder

should need:
pyclamd (add TCPSocket 3310 and TCPAddr 127.0.0.1 to its config and restart)
memcache

There is a debian package which includes parts of all, but is very special designed for our usecase as we make no use of pip.

settings.py reads part of its config data from an inifile (see top of settings.py).

The project is splited into 2 parts:

  • the app (yats)
  • the web, using the app (web)

Customization is done in the web module - e.g. add more ticket fields (models.py in web) besides the settings itself (settings.py and ini file). So far the app needs 2 folders (for logging and attachments as defined in the inifile). Make sure the webserver has write access to those folders.

ALTERNATIVE PACKAGES

https://www.djangopackages.com/grids/g/ticketing/