Merged Startgroups: Not all entered times are shown in the time table

0 votes
asked Apr 13, 2016 in Feature requests by Wedstrijdsecretaris Hellas Utrecht
edited Apr 19, 2016 by Athletics.app Customer Service
I am an organizer at a pupil competition, in all categories we work with 2 or 3 groups, I have entered the timetable for all groups by startgroups. But when I look under the timetable button, not all times show up. Under the button "per group" it doesn't even show anything at all.

Am I doing something wrong ? And if so, how can I solve this.



Petra Das - Hellas Utrecht

This has been automatically translated into English

commented Apr 14, 2016 by Wedstrijdsecretaris Hellas Utrecht
I have since found out that this is about group 2 and group 3 running parts. For running components, our competitions have group 1 through 3 combined within a category, so are all in group 1 for that.

This has been automatically translated into English

1 Answer

0 votes
answered Apr 19, 2016 by Aron Hemel
I emailed last week with the same kind of question. I now read that there has been an update. I just don't see a difference yet. in my case it is also about merging e.g. a sprint number me different startgroups.

This has been automatically translated into English

commented Apr 19, 2016 by Jesper Haverkamp

I am experiencing the same thing. See the screenshot below. The groups where hurdling has been merged now have a gap in their schedule. For example group 1, 2, 3 and 4 together; then it remains visible only in group 1. The same happens with the 600 meters.

 

This has been automatically translated into English

commented Apr 19, 2016 by Athletics.app Customer Service
Ah, the update did not include this. Because this is a relatively new option (only a few months old) there are still some bugs in it.

Events were sometimes displayed for merged groups that were not available at all for that merged group, polluting the schedule. So there was just too much displayed there.

It looks like there is just too little displayed here. I'll put it on our to-do list and try to include this in a future update. This is a relatively difficult problem, so it may take some time to fix.

This has been automatically translated into English

...