The schedule app is a constant work in progress and we welcome all constructive feedback and bug reports. Read how to behave according to the error you encountered.

Critical issue

If you have encountered an error that disables the basic functionality of the schedule (e.g. no items on schedule, page crashes while loading, …) please write to kontakt.afurnik@aflabs.si. We will do our best to fix the error as soon as possible. Please describe in detail, what did you do on the page, what did you expect to happen and whathappened. If possible, include a screenshot and copy the text possible mistakes and tell us how to repeat the mistake, because it will allow us to fix it easier and faster.

Error in the operation of the page (technical error)

If you encountered a technical irregularity on the page (e.g. overlapping data, poor readability, you can't click on some button, reservations sort wrong, …) please write to kontakt.afurnik@aflabs.si. As in the case of a critical error, please describe in detail, what did you do on the page, what did you expect to happen and whathappened. If possible, include a screenshot and copy the text possible mistakes and tell us how to repeat the mistake, because it will allow us to fix it easier and faster.

Error in schedule data (content error)

If you encountered a content error (e.g. your reservation is not listed), the subject you are doing is not on the timetable, or it is in the wrong oneclassroom/term, …) contact the responsible person at your faculty (kontakt.afurnik@aflabs.si), or, in the case of reservations, to the corresponding report. If you are a student, write to the course instructor with whom there is a problem.

Desire for additional functionality

We want the app to be as useful as possible, so we welcome new suggestions from users. The schedule is simple and does not support:

If you have a suggestion for functionality that would improve the usability of the schedule for as many people as possible, you can write to kontakt.afurnik@aflabs.si. New functionalities will be implemented when the opportunity arises, in the order chosen by the developers.