We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User wants to capture effort spent to solve a particular issue. HD Ticket doctype extended with a custom field of field type "duration".
In Frappe Helpdesk effort can not be entered correctly and if its updated in backend in desk, on helpdesk it appears as numeric value as shown here.
In back end it appears correctly as follows.
Request is to support duration field type in frappe help desk, which can be updated and displayed properly in frappe helpdesk.
Request is to support duration field type in frappe help desk, which can be updated and displayed properly in frappe helpdesk like it works in desk.
No response
The text was updated successfully, but these errors were encountered:
Could you please tell me more about this field, what is this customization, shall this be added in the core itself?
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem? Please describe.
User wants to capture effort spent to solve a particular issue. HD Ticket doctype extended with a custom field of field type "duration".
In Frappe Helpdesk effort can not be entered correctly and if its updated in backend in desk, on helpdesk it appears as numeric value as shown here.
In back end it appears correctly as follows.
Request is to support duration field type in frappe help desk, which can be updated and displayed properly in frappe helpdesk.
Describe the solution you'd like
Request is to support duration field type in frappe help desk, which can be updated and displayed properly in frappe helpdesk like it works in desk.
Describe the alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: