Hiding fields depending on category does not work
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Reproduce ticket creation in the simplified interface using a block with fields and a hiding condition based on ticket category, then inspect the plugin code handling conditional block visibility and form layout updates. Compare the category condition with the working title condition; done means the block hides when the specified category is selected without layout or CSS breakage.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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 fields:
Block hiding condition:
When a user begins to create a ticket, block is shown (which is expected to happen)
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.
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
- Create a block and set it's type to "Insertion in the form (before save button)".
- Configure some fields in the block.
- Set a hiding conditional rule that depends on ticket's category.
- Test a ticket creation by setting the category specified on step
3and block is still present.
Your GLPI setup information
No response
Anything else?
No response
- Lenguaje dominante
- PHP
- Estrellas
- 115
- Forks
- 82
- Merge medio
- 3 d 5 h
- PR fusionados (30 d)
- 12
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pluginsGLPI/fields
-
Dificultad 3/5 1-2 días Aptitud para principiantes 66/100
pluginsGLPI/fields#1270 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
pluginsGLPI/fields#1245 · 4 comentarios ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 30/100
pluginsGLPI/fields#1015 ·
Todos los issues de pluginsGLPI/fields
Issues similares
-
tooling
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
UX
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
ProfessionalWiki/NeoWiki#1525 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
bug customer-reported
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
MagnaCapax/PMSS#949 ·
-
responsive-media kses allow-list strips clipPathUnits, collapsing objectBoundingBox clip paths Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Automattic/static-site-importer#1829 ·