Request tracker to Zammad migration scripts
Find a file
Michal Čihař af589b77f2 Document notifications
Signed-off-by: Michal Čihař <michal@cihar.com>
2019-05-27 21:20:26 +02:00
.gitignore Download and cache rt data 2019-05-25 11:01:10 +02:00
LICENSE Initial commit 2019-05-25 10:07:42 +02:00
README.md Document notifications 2019-05-27 21:20:26 +02:00
requirements.txt Remove not needed dependency 2019-05-27 12:05:42 +02:00
rt2zammad.py Remove not needed attribute 2019-05-27 13:19:28 +02:00

rt2zammad

Request tracker to Zammad migration script. This is not an out of box solution for everybody, you will probably have to customize it.

Known issues:

  • Comments on issues from non creators are rejected by Zammad. This can be workarounded by creating appropriate organizations in Zammad manually or temporarily grainting Users group agent privilege.
  • Disabled users from RT can not be accessed by API, thus will lack email address and will fail to be created. Enable all users prior to the migration.
  • Timestamps are not preserved. The Zammad API doesn't seem to allow this.
  • Zammad will send notification for all actions, you probably want to disable outgoing mail for time of import.