Incorrect Association of Predefined Tasks and Associated Elements During Ticket Creation (Issue Reopening)

[jussara-ti]

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

Version

10.0.11

Bug description

Hello, I have found a bug in ticket creation.

On the ticket creation screen, if I mistakenly select a category [1] that has a predefined task and/or associated element, and then change it to the correct category [2], the ticket will be created in the last selected category [2] as expected.

However, if this category [2] does not have a predefined task and/or associated element, the ticket will be opened with the predefined task and/or associated element from the first selected category [1].

Relevant log output

No response

Page URL

No response

Steps To reproduce

1. Create a ticket template [1] linked to a ITIL category that has a predefined task and/or associated element.
2. Create a ticket template [2] linked to a ITIL category that does NOT have a predefined task and/or associated element.
3. On the ticket creation screen, select the first category [1], wait for the page to reload, and then change it to the second category [2].
4. Complete the ticket creation process.

Your GLPI setup information

Installation mode: TARBALL

Operating system: Linux GLPI 6.1.0-13-amd64 #​1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64
PHP 8.2.7 apache2handler (Core, FFI, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, apcu, bcmath, bz2,
calendar, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, igbinary, imagick, imap, intl, json,
ldap, libxml, mbstring, memcache, mysqli, mysqlnd, openssl, pcre, pdo_mysql, posix, random, readline, redis, session, shmop,
soap, sockets, sodium, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib)
Setup: max_execution_time="30" memory_limit="512M" post_max_size="8M" safe_mode="" session.save_handler="files"
upload_max_filesize="2M"
disable_functions="pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,"

Software: Apache/2.4.57 (Debian) (Apache/2.4.57 (Debian) Server at glpi.xxxxxx.com Port 443
)

Anything else?

The bug started in the version 10.0.5.
The previous issue got stale, so I reopened it.

[github-actions]

There has been no activity on this issue for some time and therefore it is considered stale and will be closed automatically in 10 days.

If this issue is related to a bug, please try to reproduce on latest release. If the problem persist, feel free to add a comment to revive this issue.
If it is related to a new feature, please open a topic to discuss with community about this enhancement on suggestion website.

You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly.

[jussara-ti]

The error still happening