Rename ‘Resolve issue’ button to ‘Acknowledge issue’ for clarity
S
Sjoerd de Vries
PROBLEM SUMMARY:
The button “Resolve issue” is misleading (see screenshot). Clicking it does not resolve anything — it only hides the item from the report. The blue checkmark icon reinforces the impression that the problem has been fixed, while in reality the underlying issue remains.
For example: if a person exists in the HR system, but has no AD/Entra account (while the Business Rules expect one), HelloID correctly signals a mismatch. Clicking “Resolve issue” hides this notification; the problem itself still exists, so nothing is resolved.
CONSULTANT’S PERSPECTIVE:
In a brief dialogue with a HelloID consultant, he explained that “Resolve issue” means you have already handled the problem outside HelloID, so you acknowledge it as resolved. If not, the issue will reappear in the next reconciliation report. To actually fix the issue in HelloID, you should use “Create account” or add the person to Exclusions.
SUGGESTION:
Rename the button from “Resolve issue” to “Acknowledge issue”.
This wording reflects the actual behavior: the issue is acknowledged and hidden from the report, but not technically resolved within HelloID.
Other options for renaming the button:
“Ignore issue”
“Hide from report”
R
Rick van den Dijssel
Hey Sjoerd de Vries, thanks for your feedback! I have a few more questions for you:
- What specific scenarios have you encountered where the current button label caused confusion?
- How frequently do you use the 'Resolve issue' button, and what is your typical workflow after clicking it?
- Are there any other areas in the interface where similar wording might cause confusion?
S
Sjoerd de Vries
Rick van den Dijssel it was noticed during our HelloID implementation project, not yet in a live/prd scenario. We go live in Nov. We spotted several language-related issues and agreed to raise Feedback cases for several of them.
Our expectation is that name of a button reflects its function, instead of the exact opposite (as in this case, where clicking the "resolve" button does several things, but the one thing it does NOT do is resolving anything).
What actually happens when clicking this button, is (1) acknowledging the issue and (2) hiding it from the list/report. Hence our suggestion to use one of these functions as name for the button.
To summarize, in response to you questions:
(1) None
(2) None yet
(3) No