I got started with migrating these customizations to 5.x and give them a repository. This is the first time I actually used the OTRS-Build function as well as github. If anything doesn't match "best practices" please let me know.
This addon shows a small widget on the dashboard with CIs that are in incident.
The analyze run is an automated job, that gets all information from the package (vendor, framework version, requirements, ...) and it analyzes the files. The long term goal is to give the author an automated feedback about the "code quality" (with regards to the OTRS standards).
just tried again on a 5.0.14 and for me at least it works right away. Could you please attach the apache or otrs log while you access/refresh the dashboard? That would help alot. I will also push an update the coming days, found some things in the source that I don't like
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
The user rstraub is primary maintainer for the namespace TTO-CIsInIncident.
But OPAR couldn't get the name from the file. Can you upload the file with the webdeveloper tools enabled? Can you send me the logs (with removed password)?
