Thomas Knops
My feedback
23 results found
-
1 voteThomas Knops
shared this idea
·
-
2 votesThomas Knops
shared this idea
·
-
12 votes
An error occurred while saving the comment Thomas Knops
supported this idea
·
-
16 votes
An error occurred while saving the comment Thomas Knops
commented
Currently, a user whose booking is cancelled due to a desk closure does not receive any further information on why the desk was closed, leading to confusion and follow-up questions (e.g. with floor managers, personal assistants, group admins etc.).
As a reason must be provided to perform a closure anyways, it would be good to include this reason in the respective booking cancellation mail. This would lead to more transparency and less confusion with the users.
Thomas Knops
supported this idea
·
-
17 votes
An error occurred while saving the comment Thomas Knops
commented
One additional thought / suggestion from UI/UX perspective.
The recently introduced feature of colored initials on the floor plan view would make more sense if each of the colors would represent one custom team.
Currently, the colors are apparently applied in a completely random way to the members within "My team" which leads a) to confusion as soon as the team gets too big to remember which member has which color and b) to false "connection indications" if two members coincidently have the same color, although they have nothing to do which each other work-wise (which is one of the reason to introduce "custom teams" in the first place).
If this is not possible though, users should at least be able to customize the color per team member (although I think this is an even bigger effort from programming perspective).
An error occurred while saving the comment Thomas Knops
commented
To be precise: I'm talking about multiple 'custom' teams rather than pre-created teams (e.g. based on Active Directory information or by creation by admins).
Thomas Knops
shared this idea
·
-
2 votes
An error occurred while saving the comment Thomas Knops
commented
Further information: https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-for-office-365-proplus-v1908-sept-2019-final/ba-p/873084
"One of the threats of these old binary file formats is that their inherent complexity too often led to exploitable bugs in their parsers. The bigger threat is that many of these formats can include macros or other executable instructions that are easily abused."
Thomas Knops
shared this idea
·
-
5 votesThomas Knops
supported this idea
·
-
6 votesThomas Knops
shared this idea
·
-
67 votesThomas Knops
supported this idea
·
-
5 votesThomas Knops
supported this idea
·
-
9 votesThomas Knops
supported this idea
·
-
19 votesThomas Knops
supported this idea
·
-
32 votes
An error occurred while saving the comment Thomas Knops
commented
Currently, some email templates (e.g. booking confirmation / cancellation) can be adjusted in the web application, while others (e.g. bump reminder / bump confirmation) can only be adjusted via ticket.
Also, both ways seem to support different default fields (e.g. "<bumptime>" is available for the bump reminder template, but not for the booking confirmation template).
It would be beneficial if a customer could change all templates by himself and if he would have access to all available default fields.
Thomas Knops
supported this idea
·
-
54 votesThomas Knops
supported this idea
·
-
5 votesThomas Knops
supported this idea
·
-
1 vote
We will add a red asterix to the floor field, we've added this item to our UI backlog
Thomas Knops
shared this idea
·
-
1 vote
Moving this item back to 'Under consideration' as this is part of our roadmap 'backlog'. I do not have an ETA for this at the current time however.
Thomas Knops
shared this idea
·
-
75 votes
An error occurred while saving the comment Thomas Knops
commented
I would not necessarily restrict that to bookings. 'Actions of admin users' can also include changes to a user or its permissions. The current log of this is only available at each user's profile ('View history'), but neither is there an overview available of these information, nor are they meaningful at all because it just says 'Account updated by [user]' instead of stating what exactly has been updated.
Thomas Knops
supported this idea
·
-
73 votesThomas Knops
supported this idea
·
-
6 votesThomas Knops
shared this idea
·
Currently in the "Book a personal space" feature, the "Booking for someone else?" area (checkbox and search box) is placed BELOW the booking calendar.
This leads to the behaviour that when booking for someone else, users usually first select a group, then a date and then check the box to book for someone else to enter the affected user's details. However after selecting the user, the previously selected date is discarded (as the screen reloads, e.g. to apply the permissions of the selected user) and must be selected again.
From user experience perspective, it would be more sensible to put the "Booking for someone else?" area ABOVE the calendar, so that the user first selects the group / floor, than the affected user (if applicable) and only then the date.
This way, the user does not have to re-select a date after selecting a user.