Do you agree that products always have room for improvement?
"Every day there are little things in software that we find annoying. Some write books about it, like Annoyances.org, but I thought this site would be more constructive.
BetterSoftwareSuggestions.com is proudly maintained by myself and the developers at SSW."
I have had employees leave SSW and we have had little dramas later… this is when I discover that we have lost their forms. Has this happened to any of you?
Losing Microsoft Forms when employees leave your company can be avoided by making sure they share it to a team and not to one user.
Suggestion:
I would like a warning in the form that says this form is an orphan and is not shared to a team.
OR
…even better, have an admin portal that allows you to assign the missing form to a new owner.
What we want to see is the number of phone calls per recruiter – to track activity on candidates.
We can add tags to candidates within a project, but then we cannot report on it.
But in the custom reports, you can’t do anything with those tags:
Suggestion
What would be awesome is a custom report that shows, for each recruiter:
Username
InMail Sent
Phone Calls done (could be a tag)
Moved to xxx stage
Unfortunately no way to do that report ☹.
Another approach would be to have a custom stage in the pipeline like “Contacted on the phone” that we could move candidates to. Then report on that pipeline stage.
Unfortunately no way to report on this either (you can only report on the top level stage).
When I look at a list of closed Pull Requests, I can see easily see who created them, but not who approved them…
Currently, I need to click on each PR to see who approved them; or add a filter “reviewed-by:” if I want to see all items approved by a specific person…
One of the things I’ve learnt using Microsoft Forms is that employees want to get feedback on their feedback, otherwise they feel that their time went into a blackhole.
Therefore, after all the responses come in, I review the comments and I find I want to bold and highlight remarkable feedback.
Workaround – You cannot do this now, so we must copy the responses into a Word document and annotate it there. Then I record a video and send it to the staff, an example (of a public one) is below.
Suggestion:
Please allow Microsoft Forms responses to be annotated
Please allow an emoji to be given to a response
Please give us an extra “Notes” column after the “Responses” column
Please have the whole form have a “Notes” field too, so I can place comments there E.g. the URL of the feedback video
Tip:Camtasia 2021 is recommended because it vastly improves upon 2018 and 2019.
Just before you record, you might want to check small details in the background. One piece of pain is you can not see the full screen of your laptop’s camera in Camtasia.
The workaround was not easy enough to discover when you have 3 people standing around you.
Workaround Tip: To see the full screen, first turn off the camera in Camtasia, then open the Windows Camera App.
It would be great if Camtasia allowed a “preview” of the full camera. See the below screenshots for details.
If that cannot be done, please add a link “Preview Hack” that pops a message to turn off Camtasia’s camera… and once done, will launch the Windows Camera app.
This problem comes up every couple of weeks so I thought of 4 things that would help Power BI users.
See email of failed refresh below. I get this email periodically telling me of an error. Thank you.
When I look into the error… sometimes it has magically resolved itself and it was a waste of time me looking into it.
Here is an example…
Suggestion #1 – Emails
We currently get an email on refresh failure. We need one on the next success too (only after the last one failed). Please.
Suggestion #2 – UX
Please add a Duration column in the Refresh History table next to the End Time.
Suggestion #3 – UX
Please provide more flexibility with refresh timings by allowing users to pick the time rather than just 30-minute intervals (change from combo to textbox).
Suggestion #4 – Please provide more info
The details link unfortunately does not provide much detail apart from saying it was a timeout issue.
This report uses an SSW gateway and my best guess is that this was due to some issue connecting to the Gateway.
If that is the reason it would be helpful to provide that info.