Skip to content
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

'Classify Content' Setting Checkbox Behavior Changes #643

Closed
1 task done
ankitguptaindia opened this issue Dec 20, 2023 · 1 comment · Fixed by #824
Closed
1 task done

'Classify Content' Setting Checkbox Behavior Changes #643

ankitguptaindia opened this issue Dec 20, 2023 · 1 comment · Fixed by #824
Assignees
Milestone

Comments

@ankitguptaindia
Copy link
Member

ankitguptaindia commented Dec 20, 2023

Is your enhancement related to a problem? Please describe.

The current behavior of the 'Classify Content' setting is to enable/disable all settings related to IBM Watson NLU features. Upon further investigation, I observed that when this checkbox is disabled, the settings below it remain visible but non-functional. To enhance user experience, it would be more intuitive to dynamically hide/show the settings below based on the state of the checkbox.

Proposed Changes:

  • When the 'Classify Content' checkbox is disabled, hide all settings below it.
  • When the checkbox is enabled, reveal and enable the settings for user interaction.

Screenshot 2023-12-20 at 3 00 15 PM

Benefits:

  • Improved User Experience: Dynamically adjusting the visibility of settings based on the checkbox state ensures that users see only relevant options.

  • Clarity in Configuration: Users will have a clear visual indication of which settings are applicable, reducing confusion and potential misconfigurations.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jeffpaul jeffpaul added this to the 3.0.0 milestone Dec 20, 2023
@jeffpaul jeffpaul moved this from Incoming to Backlog in Open Source Practice Dec 20, 2023
@dkotter dkotter modified the milestones: 3.0.0, 3.1.0 Feb 5, 2024
@dkotter dkotter modified the milestones: 3.1.0, 3.2.0 Jul 12, 2024
@iamdharmesh
Copy link
Member

With the updated settings UI in #824, users can visit the settings for enabled features only, which resolves this issue. Linking this issue to the PR so it will be closed upon the PR's merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants