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 field description #758
Conversation
No time for a deeper look or testing, but looks good at first sight. Missing documentation, e.g. https://www.mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.pages.manage.customfields |
i agree. I had opened #0020305 to open discuss possible solutions. |
fa42fed
to
7811c0a
Compare
Actually, current documentation for CF was quite outdated. |
@@ -865,6 +865,10 @@ | |||
# Enable gravatar plugin if avatars are enabled | |||
$g_upgrade[205] = array( 'UpdateFunction', 'gravatar_plugin', array() ); | |||
|
|||
# Add description field to custom field definition | |||
$g_upgrade[206] = array( 'AddColumnSQL', array( db_get_table( 'custom_field' ), " | |||
description XL NULL DEFAULT NULL" ) ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to support long descriptions here? Should we use a one line for description? That would reflect on the db schema and UI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not default to empty string rather than null?
I see the use case for multi-line. Usually you wont need more that 2 or 3 lines, but the option is ther if needed.
I'm neutral on that. I replicated the description field from project table |
👍 -- I'll leave it to @dregad to comment on the schema. I personally prefer empty over null. |
In terms of UI consistency, I'm wondering why the CF's description is sometimes displayed, and sometimes not. Currently, it's shown when
It's missing when
Haven't had time to review the doc yet. |
For the missing description:
The table based layout is not easy to accommodate the description in those pages.
That can be done with the current layout. I will review this. |
@dregad, updated the actiongroup page. |
I found the use case for custom fields that may have some restrictions, like min/max lenght, or regexp. Using this description to explain the field restrictions can be a solution. |
Add management for custom fields description attribute
Add custom field description text of form input labels
Whitespace and minor formatting changes
Revision for Custom Fields documentation, up to v1.3.0-rc1 - Remove duplicate information across different sections - Remove obsolete information - Add new functionality for current version
Add documentation for new custom field attribute 'description'.
Do not print HTML markup for Custom Fields description on labels, if the description is empty.
5c80864
to
9ca6f2b
Compare
|
outdated & no progress |
Add description text attribute for custom field definition, and show this description on labels for form inputs.
Fixes #03433