-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
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
Custom fields proposed improvements #253
Comments
I strongly support it, especially also the parts, you classified as "nice to have": |
You gotta wait for at least Mellifera 13 (fall 2017). The statistics and
filtering/search will, among other things, get a serious facelift.
|
Can the custom field types be expanded to include a multi-line text box? An example custom field would be SMTP Header, which can be many separate lines. |
The following Custom Fields would be helpful to build robust Case templates.
In addition, it would be ideal to be able to set the Required Field flag on the custom field to ensure that, if the field has been added to the case, that the field is populated prior to closing. |
Hi :-) Is there any way to delete a previously created custom field? Regards |
Also wondering about deleting a custom field. |
We'll try to tackle this in Cerana 1 or 2. |
Any update on if these enhancements are going to make 3.1.0? Just installed RC1 and noticed that they were not in there. "Can the custom field types be expanded to include a multi-line text box? An example custom field would be SMTP Header, which can be many separate lines." from July 2017 -- was added to the 3.1 milestone. |
@airlinedev it's highly likely they are not going to make it to 3.1. But if anyone wants to step up and help us, please go ahead and create a PR. |
So - any news about the proposed improvements? We could really use this... |
bump |
Bump- and does anyone know of any plugins/etc that allow custom multi-line text fields? |
Filtering by custom fields in TH4? Planned to be added? |
Request Type
Feature Request
Problem Description
#12 is great improvement for our preferred workflow, however, few things can be improved:
The text was updated successfully, but these errors were encountered: