You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently custom fields can be added and a default value can be assigned to them, but there is no option to provide some kind of guidance to the user using the tool as to what kind of data has to be entered into the fields. What would be great, is if a help text of some sort can be added along with the field, either within the same entry filed form space itself or just near it.
Please find the attached screen shots which shows a kind of help text that is provided within a tool called Opnsense (opensource firewall). This kind of help text can be helpful to users. Thought I share this approach.
The text was updated successfully, but these errors were encountered:
Exactly. But no need to open an issue.
I was quicker and already added that feature, along with others.
Please have a look at the open PR in the plugin repository.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai.
lockbot
locked and limited conversation to collaborators
Nov 20, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently custom fields can be added and a default value can be assigned to them, but there is no option to provide some kind of guidance to the user using the tool as to what kind of data has to be entered into the fields. What would be great, is if a help text of some sort can be added along with the field, either within the same entry filed form space itself or just near it.
Please find the attached screen shots which shows a kind of help text that is provided within a tool called Opnsense (opensource firewall). This kind of help text can be helpful to users. Thought I share this approach.
The text was updated successfully, but these errors were encountered: