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

Hiding fields depending on category does not work #847

Open
2 tasks done
DaviidMM opened this issue Oct 15, 2024 · 0 comments
Open
2 tasks done

Hiding fields depending on category does not work #847

DaviidMM opened this issue Oct 15, 2024 · 0 comments

Comments

@DaviidMM
Copy link

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues

GLPI Version

10.0.15

Plugin version

1.21.15

Bug description

When I setup a block to be hidden depending on ticket category, block is not hidden in simplified interface. Haven't tried in standard interface since it does not meet our requirements.

Block configuration:

Block config 1

Block fields:

Block fields

Block hiding condition:

Block condition
Block condition 2

When a user begins to create a ticket, block is shown (which is expected to happen)

Ticket creation before setting category

But when the user sets the category by which the block has to be hidden, some erratic movement happens and the field is still shown with broken CSS, a.k.a. moved rightwards and wider.

Ticket creation after setting category

I've tried setting the condition to the ticket's title and this works correctly, block is successfully hidden and works like a charm.

Relevant log output

No response

Page URL

No response

Steps To reproduce

  1. Create a block and set it's type to "Insertion in the form (before save button)".
  2. Configure some fields in the block.
  3. Set a hiding conditional rule that depends on ticket's category.
  4. Test a ticket creation by setting the category specified on step 3 and block is still present.

Your GLPI setup information

No response

Anything else?

No response

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

No branches or pull requests

1 participant