{ "version": "1.0", "generatedAt": "2026-07-22T19:06:23+00:00", "generatedFor": "Peppermint additive data expansion", "source": { "project": "glpi-project/glpi", "repositoryUrl": "https://github.com/glpi-project/glpi", "api": "GitHub REST API" }, "selection": { "tickets": 882, "comments": 1919, "anonymizedUsers": 96, "open": 364, "closed": 518, "originalPeppermintTicketsPreserved": true, "sourceContributors": 615 }, "users": [ { "name": "Avery Adler", "email": "avery.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-001", "logins": [ "00Venfan00", "bmarquinhoss", "Gbrl-BC", "Jose-Pachongo", "mciobanu1", "rbrannath", "tvanparys" ], "roles": [ "creator" ] } }, { "name": "Bailey Adler", "email": "bailey.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-002", "logins": [ "0xNath", "Chico0008", "geek95dg", "Julien-lgx", "meijin4", "richardlg-pro", "twmarcelo" ], "roles": [ "creator" ] } }, { "name": "Cameron Adler", "email": "cameron.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-003", "logins": [ "aayush1108", "CHRPAR", "Geo-Ron", "KamikX", "mepuerto", "Rico29", "vincenzopirozzideveloper" ], "roles": [ "creator" ] } }, { "name": "Casey Adler", "email": "casey.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-004", "logins": [ "abhi0698", "CireSacud26", "GerryCrooked", "ke029ke", "mgiguet", "RobyellMartins", "ViniciusgCaetano" ], "roles": [ "creator" ] } }, { "name": "Dakota Adler", "email": "dakota.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-005", "logins": [ "abhishek-rajput-44", "Claonilton", "Giorgio6846", "keguapo-cell", "mifimov345", "root-it74", "Vireth4114" ], "roles": [ "creator" ] } }, { "name": "Devon Adler", "email": "devon.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-006", "logins": [ "absita07", "CPMurilo87", "giovanny07", "Kentrier", "MKNRTV", "rootjog", "vishvas-u" ], "roles": [ "creator" ] } }, { "name": "Drew Adler", "email": "drew.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-007", "logins": [ "ahercon", "CsroDev", "github-actions[bot]", "KerieVelu", "montelocso", "RPGMais", "vpkleo" ], "roles": [ "creator" ] } }, { "name": "Elliot Adler", "email": "elliot.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-008", "logins": [ "almeidaddiego", "cuicui86", "GOAguiar99", "killerwanee", "mshishko82", "RRohi", "wc55" ], "roles": [ "creator" ] } }, { "name": "Emerson Adler", "email": "emerson.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-009", "logins": [ "AlvinChenC", "cyrakuse", "Goggin", "kodicd", "muzzol", "Russell-Jones-OxPhys", "Werneschoenholz" ], "roles": [ "creator" ] } }, { "name": "Finley Adler", "email": "finley.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-010", "logins": [ "AndiMb", "damien51", "gpiera", "kofe88", "NauGui", "SachaKeserovic", "whoiswhoami" ], "roles": [ "creator" ] } }, { "name": "Harper Adler", "email": "harper.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-011", "logins": [ "andreasmerkel", "DarknessOmbrage", "grandjeane", "kotkrsk", "Neu-Maximilian", "saz", "wisatan" ], "roles": [ "creator" ] } }, { "name": "Hayden Adler", "email": "hayden.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-012", "logins": [ "asscjr", "darthjuanan", "greatman", "krysleo", "nicoGri34", "schieffahrer", "xBounceIT" ], "roles": [ "creator" ] } }, { "name": "Jamie Adler", "email": "jamie.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-013", "logins": [ "AstroWorld95", "deguiremathieu", "GSGustavo", "ladenree76000", "OldmanTrenton", "scmilhon", "Xlebati" ], "roles": [ "creator" ] } }, { "name": "Jesse Adler", "email": "jesse.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-014", "logins": [ "astwinioenergy", "Dercni", "hagianghi", "laurentbarre1985", "PacGyver", "sercasbh", "yajih" ], "roles": [ "creator" ] } }, { "name": "Jordan Adler", "email": "jordan.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-015", "logins": [ "aumongplf", "Dheemant6", "hakd0c", "lcoria", "paidge", "shanel-svi", "yassinedamir" ], "roles": [ "creator" ] } }, { "name": "Kai Adler", "email": "kai.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-016", "logins": [ "Axel35000-tech", "dhrzic", "HyunahJang", "leon9neun", "pboosten", "shivamtestc2-sudo", "yberteaux" ], "roles": [ "creator" ] } }, { "name": "Kendall Adler", "email": "kendall.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-017", "logins": [ "b-o-r-i-s975", "dk381", "iambucketdotcom", "Lmaquaire92", "perplexityjeff", "sidneyveroneze", "Yohan-Baret-st" ], "roles": [ "creator" ] } }, { "name": "Lane Adler", "email": "lane.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-018", "logins": [ "BadgerDwarf", "dkurzelewski", "ichatenet", "logann-sys", "phamorais", "sis68" ], "roles": [ "creator" ] } }, { "name": "Logan Adler", "email": "logan.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-019", "logins": [ "balyasbob", "Dmtrkozl", "informatiquemagny78114-sys", "Loiseau2nuit", "pheamakara", "smccloud" ], "roles": [ "creator" ] } }, { "name": "Micah Adler", "email": "micah.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-020", "logins": [ "bapt1508", "dsiens", "jairockman", "LordVader4711", "PierreTeclib", "ssegard" ], "roles": [ "creator" ] } }, { "name": "Morgan Adler", "email": "morgan.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-021", "logins": [ "bastien33260", "dygland", "jcouallier", "loulouontop", "pieter-liekens", "sspoiden" ], "roles": [ "creator" ] } }, { "name": "Noel Adler", "email": "noel.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-022", "logins": [ "bcervinho", "efazenda", "jcusto-acores", "lpgab", "pisarz77", "sta-zot" ], "roles": [ "creator" ] } }, { "name": "Parker Adler", "email": "parker.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-023", "logins": [ "bcnan", "elidjah", "jeremypgn", "lscotte", "plburguet", "StbanMc" ], "roles": [ "creator" ] } }, { "name": "Quinn Adler", "email": "quinn.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-024", "logins": [ "Bellegund", "EmilieBy", "jeromeroseaueslc", "Lucitiana", "po1vo", "stefjes" ], "roles": [ "creator" ] } }, { "name": "Reese Adler", "email": "reese.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-025", "logins": [ "bessantoy", "flagoda", "jglavas-getim", "luisjosemachado", "pplaniol", "stevanborges" ], "roles": [ "creator" ] } }, { "name": "Remy Adler", "email": "remy.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-026", "logins": [ "BioulacJe", "fralla2", "jhermsen", "MadBeango", "PSGCV85", "supermozzi" ], "roles": [ "creator" ] } }, { "name": "Riley Adler", "email": "riley.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-027", "logins": [ "blackxthink", "ftoledo-opensa", "JMICob", "MarcSamD", "racingfoss", "sylvainblanchouin" ], "roles": [ "creator" ] } }, { "name": "Robin Adler", "email": "robin.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-028", "logins": [ "Blank-Vcf", "Gabri374", "joao-panao", "masakazuwatanabe", "raregtp", "TheLaskY" ], "roles": [ "creator" ] } }, { "name": "Rowan Adler", "email": "rowan.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-029", "logins": [ "blippercop", "gabrielgbs97", "jon-nfc", "Maximjke", "raulFeitosa", "TheRoby" ], "roles": [ "creator" ] } }, { "name": "Sage Adler", "email": "sage.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-030", "logins": [ "RomainLvr" ], "roles": [ "creator", "assignee" ] } }, { "name": "Skyler Adler", "email": "skyler.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-031", "logins": [ "AdrienClairembault", "btry", "cedric-anne", "eduardomozart", "HLeithner", "Otijom", "stonebuzz", "trasher" ], "roles": [ "creator", "assignee", "commenter" ] } }, { "name": "Taylor Adler", "email": "taylor.adler@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-032", "logins": [ "akstis-typer", "cconard96", "danicouso", "froozeify", "orthagh", "SebSept", "tograss" ], "roles": [ "creator", "assignee", "commenter" ] } }, { "name": "Avery Bennett", "email": "avery.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-033", "logins": [ "0nelight", "C-Duv", "FelipeBasilio1991", "jtfeatures", "nobrupinto", "Sevengroup-IT", "viktor-sc" ], "roles": [ "creator", "commenter" ] } }, { "name": "Bailey Bennett", "email": "bailey.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-034", "logins": [ "A-Loong", "candaes", "femachado", "kabassanov", "NoxWorld2660", "SilvaFernando", "vincentguajioty" ], "roles": [ "creator", "commenter" ] } }, { "name": "Cameron Bennett", "email": "cameron.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-035", "logins": [ "AAponciano", "Caseum96", "flegastelois", "kazishakilahmed", "Omareladawy", "silvasocrates", "VinnyOF1912" ], "roles": [ "creator", "commenter" ] } }, { "name": "Casey Bennett", "email": "casey.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-036", "logins": [ "acopernic", "cdbaq", "FMG-Jay", "keguira", "oneill2john", "SimonTheIman", "virt1122" ], "roles": [ "creator", "commenter" ] } }, { "name": "Dakota Bennett", "email": "dakota.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-037", "logins": [ "adamcios", "cfuchs-mpi", "FrancisTicgal", "kevin-m87", "OteJlo", "sl077", "vitalev" ], "roles": [ "creator", "commenter" ] } }, { "name": "Devon Bennett", "email": "devon.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-038", "logins": [ "afpes", "ChandlerBing82", "FreeMacs", "Killian-Aidalinfo", "OxydeBots", "Smiley-k", "VladoTTX" ], "roles": [ "creator", "commenter" ] } }, { "name": "Drew Bennett", "email": "drew.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-039", "logins": [ "agnesmorin-itgouv", "chguigoz59", "ftoledo", "Killink61", "pedroalves5770", "sothmani", "wastn" ], "roles": [ "creator", "commenter" ] } }, { "name": "Elliot Bennett", "email": "elliot.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-040", "logins": [ "AHTW4051", "chiwbicka1", "g-bougard", "kimi1983", "pete1854", "Sousou-cloud", "WBergeron" ], "roles": [ "creator", "commenter" ] } }, { "name": "Emerson Bennett", "email": "emerson.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-041", "logins": [ "ak47d", "Christof48", "Gabo700", "KirillLd", "picinformatique", "sr-it1", "wctrjunior" ], "roles": [ "creator", "commenter" ] } }, { "name": "Finley Bennett", "email": "finley.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-042", "logins": [ "akindemirci", "citygabor", "GamingRB", "KissWam", "pierregager-design", "SRDEYV", "werewolf004" ], "roles": [ "creator", "commenter" ] } }, { "name": "Harper Bennett", "email": "harper.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-043", "logins": [ "akuv-20", "clemmsy", "gdavidlt", "kranack", "Pixels-IT", "SruiSan", "wesleipedroza" ], "roles": [ "creator", "commenter" ] } }, { "name": "Hayden Bennett", "email": "hayden.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-044", "logins": [ "albertogalisteo", "coca-mann", "german-giraldom", "Krovyakov-Ivan", "PorteBannana", "stcithelpdesk", "wfort-GRADeS-CVL" ], "roles": [ "creator", "commenter" ] } }, { "name": "Jamie Bennett", "email": "jamie.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-045", "logins": [ "AldarisPale", "Code-Near", "ghost", "labiloute", "PowerMike-BZH", "SteadEXE", "wgondzik" ], "roles": [ "creator", "commenter" ] } }, { "name": "Jesse Bennett", "email": "jesse.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-046", "logins": [ "alexandre3685", "cofig", "Gizmodo", "landure", "prbt2016", "steph461", "wjqwh" ], "roles": [ "creator", "commenter" ] } }, { "name": "Jordan Bennett", "email": "jordan.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-047", "logins": [ "AlexisCay", "CoRpO", "glpi123", "Laurynas871", "PTG85", "steve-hbt", "wojtek19022" ], "roles": [ "creator", "commenter" ] } }, { "name": "Kai Bennett", "email": "kai.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-048", "logins": [ "alfredit", "Csabence92", "gonzaleztroyano", "lchanouha", "pvasener", "stwartelearte", "Wolvverine" ], "roles": [ "creator", "commenter" ] } }, { "name": "Kendall Bennett", "email": "kendall.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-049", "logins": [ "alfredudu", "Cyanur", "Gor3pig", "LeoDef", "pypetrov", "subdriver", "xiahan0406-han" ], "roles": [ "creator", "commenter" ] } }, { "name": "Lane Bennett", "email": "lane.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-050", "logins": [ "AlthausOV", "CYAsistemas", "GuidoWilden", "LeoEvaldt", "QuantumNomad26", "Supersonic431", "xseth03" ], "roles": [ "creator", "commenter" ] } }, { "name": "Logan Bennett", "email": "logan.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-051", "logins": [ "andreantunes2602", "Cyril6789", "gutsu77", "lotusflowr", "r59g7z9yt7-ux", "sy-l20", "xtrem57" ], "roles": [ "creator", "commenter" ] } }, { "name": "Micah Bennett", "email": "micah.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-052", "logins": [ "andreiIncifra", "CyrilVanErsche", "H4rDBuG", "lucaslevi-consultor-glpi", "rafaelse", "Tarru", "Yann843" ], "roles": [ "creator", "commenter" ] } }, { "name": "Morgan Bennett", "email": "morgan.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-053", "logins": [ "andrewc-ui", "Czaraoth", "hakimbedja", "magheinz", "RaivoMahnovs", "tattami", "YannickBarone" ], "roles": [ "creator", "commenter" ] } }, { "name": "Noel Bennett", "email": "noel.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-054", "logins": [ "anthonymontebrun", "dani", "hamx01", "Manu-emn", "RandomFrenchAdmin", "tc-jfoucault", "yild" ], "roles": [ "creator", "commenter" ] } }, { "name": "Parker Bennett", "email": "parker.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-055", "logins": [ "antoniotvr", "danyalberchtoldlf", "helpdesklypogroup", "marceloprado93", "raudouxe", "Techal62", "zekuraz" ], "roles": [ "creator", "commenter" ] } }, { "name": "Quinn Bennett", "email": "quinn.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-056", "logins": [ "Apashh", "dbremaudcerfrance", "HiopsNerevar", "marwajeljli-cyber", "raultak", "tguichard25" ], "roles": [ "creator", "commenter" ] } }, { "name": "Reese Bennett", "email": "reese.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-057", "logins": [ "apohutenumera", "dcrst7575", "hoaitran0429", "mat44444-us", "raymaill86", "this-is-boris" ], "roles": [ "creator", "commenter" ] } }, { "name": "Remy Bennett", "email": "remy.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-058", "logins": [ "arb103", "dersonbsb2022", "homebrewtainy", "Mateusz-Szczykutowicz-sokol-it", "rean1mat0r", "tizianosartori" ], "roles": [ "creator", "commenter" ] } }, { "name": "Riley Bennett", "email": "riley.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-059", "logins": [ "Arkham1997", "desrimaisd", "husisusi", "Math6768", "redddcyclone", "tojeroman" ], "roles": [ "creator", "commenter" ] } }, { "name": "Robin Bennett", "email": "robin.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-060", "logins": [ "arthurrschaefer", "DevDorrejo", "infime-it", "MathisLXE", "remuseu", "TOMAGITINT" ], "roles": [ "creator", "commenter" ] } }, { "name": "Rowan Bennett", "email": "rowan.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-061", "logins": [ "Aruileen85", "dioig0", "InformatiqueOLLN", "maxhinostrozaarias-lang", "ReskPP", "tomamplius" ], "roles": [ "creator", "commenter" ] } }, { "name": "Sage Bennett", "email": "sage.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-062", "logins": [ "aslushnikov", "Disinterpreter", "infraoderco", "Megachip", "RobertoMarcelino", "Toyama007" ], "roles": [ "creator", "commenter" ] } }, { "name": "Skyler Bennett", "email": "skyler.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-063", "logins": [ "Asmitta-01", "dmcoelho", "IP-V15", "mentaloverflow", "Robyell", "trenta" ], "roles": [ "creator", "commenter" ] } }, { "name": "Taylor Bennett", "email": "taylor.bennett@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-064", "logins": [ "ayygurl", "DonutsNL", "Izanagi52", "michaelmartinez-sistemasentry", "rol4nd", "trisosamu" ], "roles": [ "creator", "commenter" ] } }, { "name": "Avery Blair", "email": "avery.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-065", "logins": [ "Azgar1998", "dudkitt", "Izzaya0212", "michal1298", "romvek", "tristangallet" ], "roles": [ "creator", "commenter" ] } }, { "name": "Bailey Blair", "email": "bailey.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-066", "logins": [ "AziocNEU", "DWXXX", "J-C-P", "Mikhail-D", "roshanroche", "troloff" ], "roles": [ "creator", "commenter" ] } }, { "name": "Cameron Blair", "email": "cameron.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-067", "logins": [ "b1llyshears", "ebourgui", "j-guevara-m", "Minikea", "rrintoulsrsd", "troncoli" ], "roles": [ "creator", "commenter" ] } }, { "name": "Casey Blair", "email": "casey.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-068", "logins": [ "Balots", "EC2311", "Jacques-Laniado", "misterjmw", "RuanBojarski", "tsmr" ], "roles": [ "creator", "commenter" ] } }, { "name": "Dakota Blair", "email": "dakota.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-069", "logins": [ "barte91", "efpbe", "jamorrisacc1", "MNSPJack", "RuarriS", "tst-plutex" ], "roles": [ "creator", "commenter" ] } }, { "name": "Devon Blair", "email": "devon.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-070", "logins": [ "bchandra369", "ElanOD78", "jardeljsv", "mo-wcma", "rusakkl", "TxX8N8LN" ], "roles": [ "creator", "commenter" ] } }, { "name": "Drew Blair", "email": "drew.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-071", "logins": [ "BENZOOgataga", "emitlinks", "jcamargo-teclib", "monta990", "sam-markham", "Ujebhopshealthcare" ], "roles": [ "creator", "commenter" ] } }, { "name": "Elliot Blair", "email": "elliot.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-072", "logins": [ "Berlinst", "emptipat", "JeremieMercier", "mserramanxa", "SamuelMTeixeira", "valentin-ibc" ], "roles": [ "creator", "commenter" ] } }, { "name": "Emerson Blair", "email": "emerson.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-073", "logins": [ "Bigthibo", "eran113", "jerry-ne", "murilo-hyper", "sard1091", "valentindragan" ], "roles": [ "creator", "commenter" ] } }, { "name": "Finley Blair", "email": "finley.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-074", "logins": [ "blainvillem", "erique-souza", "jfoucher", "Mystikal57", "sazanof", "vboucard" ], "roles": [ "creator", "commenter" ] } }, { "name": "Harper Blair", "email": "harper.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-075", "logins": [ "brusilva84", "ewertonmuller", "jluis144", "n0womann0cry", "SebastianUDI", "verdanatech-marcio" ], "roles": [ "creator", "commenter" ] } }, { "name": "Hayden Blair", "email": "hayden.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-076", "logins": [ "bturnbough81", "ewilli", "jobercavalcante", "namtarkur", "Senninha1974", "VF404" ], "roles": [ "creator", "commenter" ] } }, { "name": "Jamie Blair", "email": "jamie.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-077", "logins": [ "bwutsa", "felag", "Jonathan-R23", "netsysspecialist-boop", "serviceticst", "vi-lgtm" ], "roles": [ "creator", "commenter" ] } }, { "name": "Jesse Blair", "email": "jesse.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-078", "logins": [ "Herafia", "Lainow", "MyvTsv" ], "roles": [ "assignee" ] } }, { "name": "Jordan Blair", "email": "jordan.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-079", "logins": [ "ccailly", "f2cmb", "felipee-monteiro", "Rom1-B" ], "roles": [ "assignee", "commenter" ] } }, { "name": "Kai Blair", "email": "kai.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-080", "logins": [ "AbyssMoon", "DamienGombaultRecia", "hpk-lentia", "makiaveliko92", "OscarBeiro", "squale323", "wandersilva-code" ], "roles": [ "commenter" ] } }, { "name": "Kendall Blair", "email": "kendall.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-081", "logins": [ "Alabaster12", "doumhfr", "igorvisi", "marcoabgm", "overag3", "stachu359", "WAV-mst" ], "roles": [ "commenter" ] } }, { "name": "Lane Blair", "email": "lane.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-082", "logins": [ "Aleko-SaR", "drumofragnarock", "igwtsw", "martinaluna", "ozit", "Steamera", "we-sell-bags" ], "roles": [ "commenter" ] } }, { "name": "Logan Blair", "email": "logan.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-083", "logins": [ "alesnav", "DwayneSamuels", "indrekteppan", "mateuszkruczek", "Pasdian", "tdozbun-reno", "wildangunawan" ], "roles": [ "commenter" ] } }, { "name": "Micah Blair", "email": "micah.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-084", "logins": [ "anirban6996", "ericgaspar", "iohann95", "mathiashabellis", "Phorms", "teopost", "willysaurio" ], "roles": [ "commenter" ] } }, { "name": "Morgan Blair", "email": "morgan.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-085", "logins": [ "AungShwe2002", "errror", "Ivanhoe81", "MeskitaNetzarim", "pinciu-sebastian", "tfdasilva", "xrcam" ], "roles": [ "commenter" ] } }, { "name": "Noel Blair", "email": "noel.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-086", "logins": [ "AurelienFroment", "fab44240", "JamesM-echo-9", "mikeheisenberg70", "plutoflyby", "thomassmithpchasorg" ], "roles": [ "commenter" ] } }, { "name": "Parker Blair", "email": "parker.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-087", "logins": [ "benoooo85", "flex-pgum", "jbonor", "Mirkk", "Pyroteknix25", "TiboulVinci" ], "roles": [ "commenter" ] } }, { "name": "Quinn Blair", "email": "quinn.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-088", "logins": [ "Bohoaush", "FlorianV54", "jerrylu2008", "mogzmogz", "pzbdkp", "TIITANIC1912" ], "roles": [ "commenter" ] } }, { "name": "Reese Blair", "email": "reese.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-089", "logins": [ "boraergul", "Fortis007", "jmechnich", "Mpic", "RegiloDeLaVega", "tilkov" ], "roles": [ "commenter" ] } }, { "name": "Remy Blair", "email": "remy.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-090", "logins": [ "CHCH069", "FranckAudebrand", "jussara-ti", "MrYamous", "rjmontenegro", "tmartincpp" ], "roles": [ "commenter" ] } }, { "name": "Riley Blair", "email": "riley.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-091", "logins": [ "ChrisGralike", "GeistFighter", "jvergacas", "msodrep", "RogueSnipa", "Tony710" ], "roles": [ "commenter" ] } }, { "name": "Robin Blair", "email": "robin.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-092", "logins": [ "CiaranHagen", "gituser-bit1", "Karmadibsa", "nhulot-a11y", "SANSY-KABA", "ToxicSmasher" ], "roles": [ "commenter" ] } }, { "name": "Rowan Blair", "email": "rowan.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-093", "logins": [ "cihlmi", "Giudy", "kmpm", "Niko-F", "SeBytev3", "ValFran99" ], "roles": [ "commenter" ] } }, { "name": "Sage Blair", "email": "sage.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-094", "logins": [ "cjdrilling29", "gon-AndreZielinski", "krishnaavril", "NWCRES-tech", "Simeonov98", "vandijkstef" ], "roles": [ "commenter" ] } }, { "name": "Skyler Blair", "email": "skyler.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-095", "logins": [ "cosmedd", "greglg45", "Kuba-Pawlak", "objectprogr", "slytara", "veieras" ], "roles": [ "commenter" ] } }, { "name": "Taylor Blair", "email": "taylor.blair@peppermint.local", "password": "Password1!", "admin": false, "source": { "project": "glpi-project/glpi", "personaId": "persona-096", "logins": [ "cyab-ux", "gromka", "lameslime", "ojeaaan", "soporteitsoliss", "vnirocha" ], "roles": [ "commenter" ] } } ], "tickets": [ { "title": "Very slow first load of /front/ticket.php after Central page in GLPI 11 (not in 10.0.20)", "detail": "Affected version:\n11.0.1 and 11.0.2\n\nIssue description:\nOn GLPI 11.0.1 and 11.0.2 (Docker official image), the very first load of the ticket list /front/ticket.php right after visiting the Central page (/front/central.php) is very slow: about 11–13 seconds of backend time.\n\nKey points:\n\n- The issue happens only on the first /front/ticket.php after going through the Central page.\n- If I wait for the Central page to fully finish loading and all background work to complete, then go to the ticket list, /front/ticket.php is fast.\n- Once this first slow request is done, navigating between ticket pages or returning to /front/ticket.php with the same default search is fast.\n- The slowness appears again only after I visit the Central page and quickly go back to the ticket list.\n\nAccording to the Symfony profiler:\n\n- The slow /front/ticket.php request shows ~11–13 seconds in SessionStart::execute.\n- Total SQL time is only ~76 ms for 242 queries.\n- A standalone session_start() using GLPI's GLPI_SESSION_DIR is extremely fast (~0.0002 s), so it does not look like a filesystem or session handler issue.\n\nI have tested with:\n\n- all plugins disabled,\n- automatic actions disabled / moved to CLI,\n- dashboards removed (Central, Assets, Assistance),\n- GLPI_AJAX_DASHBOARD=0,\n\nand the behavior is still the same.\n\nOn the same environment and database with GLPI 10.0.20, this problem does not occur with a similar dashboard configuration.\n\nFrom my point of view, this looks like a performance regression in GLPI 11 around the initialization of the session/user/context when coming from the Central page before the first ticket list load.\n\nReproduction steps:\n1. Install GLPI 11.0.1 or 11.0.2 using the official Docker image (glpi/glpi:11.0.x), with a real dataset (many tickets), and configure it normally.\n2. Log in and you arrive on the Central page (/front/central.php).\n3. Immediately click on the Tickets menu to open /front/ticket.php (do not wait for the central page to fully finish loading).\n4. Observe the backend duration of the /front/ticket.php request (using Symfony profiler or browser DevTools): it takes about 11–13 seconds.\n\n[Image omitted]\n\n5. Then go back to the Central page again.\n- This time, wait until the central page has fully finished loading (no more XHR / background requests in the browser network tab).\n- Click on Tickets again.\n6. Now the /front/ticket.php request is fast (normal response time).\n\n[Image omitted]\n\n7. Repeat the scenario and observe that the slow behavior only appears when navigating to the ticket list while the Central page is still doing background work.", "priority": "high", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Are there any slow network requests on the Central page? A lot of background requests in GLPI may not close the session immediately so the session file is locked until the request completes. This causes requests to wait for previous ones to finish even if they are asynchronous.\n\nOriginal response date: 2025-11-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3508327615, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21867#issuecomment-3508327615", "createdAt": "2025-11-09T13:38:17Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Are there any slow network requests on the Central page? A lot of background requests in GLPI may not close the session immediately so the session file is locked until the request completes. This causes requests to wait for previous ones to finish even if they are asynchronous.\n\nHi Taylor Adler, yes, I’ve done some more tests and I can confirm there are slow background requests on the Central page, and they are linked to the Planning.\n\nOn the Central page, the slow background requests I see are mainly :\n\n- common.tabs.php?_glpi_tab=Central$0&_target=central.php (XHR, html) => about 8621 ms\n- planning.php?action=get_events&view_name=... (XHR, json, triggered by fullcalendar.js) => about 13389 ms\n- planning.php (XHR POST) => about 14173 ms\n\n[Image omitted]\n\nI went to the Planning page and noticed that I had several plannings checked/visible (my own planning + other users).\n\nThen I tried :\n\n1. On the Planning page, I unchecked all plannings and left only my own planning visible.\n2. I went back to the Central page and repeated the test:\n - Login => Central => immediately click on Tickets.\n\nResult:\n\n- The planning.php?action=get_events... XHRs on the Central page are now much faster.\n- /front/ticket.php no longer shows the 11–13 seconds delay.\n- The slowness completely disappears in this scenario.\n\n[Image omitted]\n\nIf I re-enable multiple plannings (several calendars checked/visible), then:\n\n- planning.php?action=get_events... on Central becomes slow again (up to 13–14 seconds),\n- and the first /front/ticket.php after Central is again very slow.\n\nOn the same data and with the same number of plannings visible in GLPI 10.0.20, I do not have this problem.\n\nOriginal response date: 2025-11-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3508411221, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21867#issuecomment-3508411221", "createdAt": "2025-11-09T14:31:46Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Hi Elliot Blair , can you also check the performance within the ticket? What you mentioned about it being slow the first time seems very similar to what I’m experiencing in this issue #21115 — in the ticket handling area, but there it’s not just the first time; every time I hit F5, the slowdown is the same.\n\nOriginal response date: 2025-11-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3508466730, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21867#issuecomment-3508466730", "createdAt": "2025-11-09T15:46:51Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Hi Elliot Blair , can you also check the performance within the ticket? What you mentioned about it being slow the first time seems very similar to what I’m experiencing in this issue #21115 — in the ticket handling area, but there it’s not just the first time; every time I hit F5, the slowdown is the same.\n\nHi Micah Bennett,\n\nI’ve just done a few more checks.\n\nIn my case, I do not see the same behavior as in #21115 on the ticket handling page itself :\n\n- Opening a single ticket is normal.\n- Pressing F5 on the ticket page is also fast on my test instance.\n- I don’t have a persistent slowdown every time I reload a ticket.\n\nThe slowdown I reported happens in a very specific scenario :\n\n1. Go to the Central page.\n2. While the Central page is still doing background work\n3. Immediately go to the ticket list (/front/ticket.php).\n\nOnly the first /front/ticket.php after Central is slow (it waits for the slow planning.php calls).\nOnce that first request is done:\n\n- the ticket list is fast,\n- refreshing the list or a ticket with F5 is fast as well,\n- until I go back to Central with multiple plannings checked.\n\nSo it looks like my issue is more about Planning + Central + ticket list interaction (session lock while loading planning events), whereas your issue in #21115 is about slowness directly in the ticket handling area on every reload.\n\nI dont reproduce the behavior you describe inside the ticket itself on my side.\n\nOriginal response date: 2025-11-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3508654201, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21867#issuecomment-3508654201", "createdAt": "2025-11-09T18:17:31Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Elliot Blair Yes, unfortunately I've been having this problem since the alpha version, which is why that issue has been open for a while. According to comments from my teammate, some changes have been made that are affecting the overall performance of the system.\n\nOut of curiosity, which browser do you use to access GLPI? And what is the configuration of your GLPI Linux server? Apache, memory, CPU, etc.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3509026110, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21867#issuecomment-3509026110", "createdAt": "2025-11-10T00:39:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21867, "url": "https://github.com/glpi-project/glpi/issues/21867", "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "open", "stateReason": null, "createdAt": "2025-11-09T13:28:09Z", "updatedAt": "2026-04-13T17:21:35Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "General slowness in cards (responding, solution, etc.) when accessing the open ticket, only the first time GLPI 11 Rc5", "detail": "Affected version:\nGLPI 11 rc5\n\nIssue description:\nGuys, I noticed this during service tests related to overall performance:\n\nAs you may have noticed, when you click on “answer call” or “validate” for the first time, it causes this slowdown, but from then on, the speed returns to normal. If I refresh the page or have just entered the call, the first click on the card causes this slowdown.\n\nGlpi 11 Rc5", "priority": "high", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Do you see any network requests in the browser console during these times of slowness?\n\nOriginal response date: 2025-09-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3326062550, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21115#issuecomment-3326062550", "createdAt": "2025-09-24T01:07:32Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Taylor Adler If I use Chrome's F12 console, I only see traffic when refreshing the page. After refreshing, when I click on the card, it does not generate new traffic.\n\nOriginal response date: 2025-09-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3326171498, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21115#issuecomment-3326171498", "createdAt": "2025-09-24T02:00:39Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "This performance issue seems similar to what happens in form management when you go to the create questions tab; it takes a long time to load the sections, etc. There were even discussions here about performance from the first alpha to this one (taking the opportunity to comment).\n\nOriginal response date: 2025-09-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3326173922, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21115#issuecomment-3326173922", "createdAt": "2025-09-24T02:02:19Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Taylor Adler\nNow that I've noticed it better, the slowness is on the call page itself, not exactly related only to the buttons. Look how it freezes when trying to scroll up and down the timeline and on the right side as well to load the information. When I perform the same operations in the current version 10 with the same number of follow-ups, validations, etc., it works normally.\n\nThis is concerning if the final version is released like this, mainly because when it comes to calls, perhaps not the requester, but the technicians spend most of their time in this view.\n\nOriginal response date: 2025-09-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3326201467, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21115#issuecomment-3326201467", "createdAt": "2025-09-24T02:20:57Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Guys, with the release of the new version 11.0.0, I can confirm that the slowness and lack of performance/delay in loading remains the same when viewing within the call (same as in the video).\n\nThe test I will do is to update version 10 again to the latest version of 11 to see if there will be any different behavior.\n\nOriginal response date: 2025-10-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3356887459, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21115#issuecomment-3356887459", "createdAt": "2025-10-01T15:07:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21115, "url": "https://github.com/glpi-project/glpi/issues/21115", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "open", "stateReason": "reopened", "createdAt": "2025-09-23T22:58:16Z", "updatedAt": "2025-12-09T15:16:53Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Native form submission fails after ticket creation and causes duplicate tickets", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.6.0\n\nIssue description:\nWe are experiencing an intermittent issue with native forms in GLPI 11.0.6.\n\nWhen a user submits the native form \"Request a service\" / \"Demander un service\", GLPI sometimes displays a form submission failure message. However, the ticket is already created successfully in the database.\n\nBecause the user sees a failure message, they click the submit button again, which creates a duplicate ticket.\n\nIn our case, the first ticket was created successfully, then GLPI logged the following error during the same submission flow:\n\nMySQL query error: SAVEPOINT savepoint_0 does not exist (1305) in SQL query \"ROLLBACK TO savepoint_0\".\n\nThis suggests that the ticket creation succeeds, but the native form submission workflow fails afterward, causing a false failure message and leading users to create duplicates.\n\nAffected page:\nPOST /Form/SubmitAnswers\n\nReproduction steps:\n1. Open the native form \"Demander un service\" / \"Request a service\"\n2. Fill in the form and submit it once\n3. Sometimes the ticket is created successfully, but GLPI displays a form submission error\n4. The user clicks submit again because the UI indicates failure\n5. A duplicate ticket is created\n\nEnvironment details:\nGLPI version: 11.0.6\nPHP version: 8.3.6\nMariaDB version: 10.11.14\nOS: Ubuntu Linux\n\nDatabase checks already performed:\n\nphp bin/console system:status --private --allow-superuser => OK\nphp bin/console db:check --check-all-migrations --allow-superuser => OK\nphp bin/console db:check --check-innodb-migration --allow-superuser => OK\n\nAdditional database checks:\n\nno non-InnoDB tables found\nno triggers found in the GLPI database\nno stored procedures / routines found in the GLPI database\n\nAdditional context:\nWe confirmed that the first ticket is actually created before the error is shown.\n\nExample from our production instance:\n\nTicket 2026041401 — Demande d'accès — created at 2026-04-14 08:18:48\nTicket 2026041402 — Demande d'accès — created at 2026-04-14 08:19:06\n\nSame requester:\n\nusers_id_recipient = 320\n\nThis proves the following behavior:\n\n1. user clicks submit\n2. ticket is created successfully\n3. native form submission fails with SAVEPOINT savepoint_0 does not exist\n4. UI shows a failure message\n5. user clicks again\n6. duplicate ticket is created", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "micah.blair@peppermint.local", "text": "Hello,\n\nWe are experiencing the same issue.\nAfter checking, it seems to occur with the first ticket of the day. Seeing the ticket you mentioned, I’m wondering if you are observing the same behavior on your side.\nWe have not been able to reproduce this issue in the IT department so far.\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4250249732, "author": "mathiashabellis", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23861#issuecomment-4250249732", "createdAt": "2026-04-15T07:57:31Z" } }, { "userEmail": "sage.blair@peppermint.local", "text": "I am observing the same issue. Can also reproduce this just once and not a second time the same day or at least in the same session.\n\nOriginal response date: 2026-04-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4320617452, "author": "gon-AndreZielinski", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23861#issuecomment-4320617452", "createdAt": "2026-04-25T21:38:31Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "Micah Blair Sage Blair Can you tell me which ticket-related plugins you use? I’m wondering whether the issue might be caused by one of those plugins. I use Advanced forms and more tickets .\n\nOriginal response date: 2026-05-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4371200927, "author": "raudouxe", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23861#issuecomment-4371200927", "createdAt": "2026-05-04T12:53:46Z" } }, { "userEmail": "lane.blair@peppermint.local", "text": "Hello,\n\nSame issue.\n\nGLPI version: 11.0.6\nPHP version: 8.5.5\nMariaDB version: 12.3.1\nOS: Debian 12\n\nThe problem occur with the first ticket of the day too.\nWe don't have Advanced forms and More tickets plugins installed.\n\nThx\n\nOriginal response date: 2026-05-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4386919822, "author": "Steamera", "anonymizedAuthorEmail": "lane.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23861#issuecomment-4386919822", "createdAt": "2026-05-06T09:57:31Z" } }, { "userEmail": "sage.blair@peppermint.local", "text": "On our side it's: saml2sso, behaviours and More Reporting which are active.\n\nOriginal response date: 2026-05-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4394830400, "author": "gon-AndreZielinski", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23861#issuecomment-4394830400", "createdAt": "2026-05-07T07:00:07Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23861, "url": "https://github.com/glpi-project/glpi/issues/23861", "author": "raudouxe", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-14T11:13:46Z", "updatedAt": "2026-06-11T07:22:03Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "All Dashboard option not available on the profile Setup tab GLPI 11.0.1", "detail": "Issue description:\nDear all,\n\nAfter upgrading GLPI to the latest version 11.0.1, we want to give self service profile the right to display dashboards. By default, the dashboard display is restricted for this profile as shown on the capture :\n\n[Image omitted]\n\nWhen we go the profile settings under Administration -> Profil -> Setup, the \"All dashboard\" option is not available.\n\n[Image omitted]\n\n[Image omitted]\n\nWe want to know if it is a bug or we have something wrong in our installation", "priority": "medium", "type": "support", "createdByEmail": "quinn.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Not a bug. Only profiles with the standard interface have access to dashboards.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3470715348, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21716#issuecomment-3470715348", "createdAt": "2025-10-30T23:37:26Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "I'm afraid it is a bug about dashboard.\nyou maybe install formcreator befor.\nplease ref to this link and can be fix the problem.\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3472109120, "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21716#issuecomment-3472109120", "createdAt": "2025-10-31T09:29:40Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "Dear all,\n\nI want to note that we used the Formcreator plugin before upgrading to the latest version 11.0.1. So, when displaying the \"glpi_dashboards_dashboards\" table we noticed that there is \"plugin_formcreator_issue_counters\" exists and in the \"dhasboard_rights\" table the sef service profile has access only to this dhashboard.\n\nThe question now is how to deal with this issue of fromcreactor plugin ? since we didn't uninstall it before doing the upgrade ?\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3479290987, "author": "marwajeljli-cyber", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21716#issuecomment-3479290987", "createdAt": "2025-11-03T07:49:44Z" } }, { "userEmail": "parker.blair@peppermint.local", "text": "Taylor Adler Hi, in GLPI 11.0.1 I can't see the Dashboards option in any Profile, too. The screenshot above seems to be one of a normal user (just with the name \"Self Service\", the simplified interface has just one single line there.\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3479712177, "author": "Mirkk", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21716#issuecomment-3479712177", "createdAt": "2025-11-03T09:56:43Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "Not a bug. Only profiles with the standard interface have access to dashboards.\nWe are already working with the standard interface\n\n[Image omitted]\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3479942257, "author": "marwajeljli-cyber", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21716#issuecomment-3479942257", "createdAt": "2025-11-03T10:57:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21716, "url": "https://github.com/glpi-project/glpi/issues/21716", "author": "marwajeljli-cyber", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2025-10-30T13:46:14Z", "updatedAt": "2025-12-04T06:25:11Z", "closedAt": null } }, { "title": "Use a faster bundler than webpack", "detail": "Issue description:\nIt takes almost 30s locally (50s on the CI) to run the webpack build.\n\nIt is executed on each github runner so it waste at least 5/6 mins per commit.\nLocally it is also annoying as we rebuild dependencies often when changing branches.\n\nI have no idea what it implies to change this and if it is reasonable to do in a minor version but we should at least look into doing it for the next major release IMO.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I've been pushing for a switch to Vite. It aligns much better with our needs and future goals, like closer support for Vue and TypeScript, than webpack while being simpler and faster in most cases. In fact, I already dropped Webpack completely in favor of it in the plugin I am working on.\n\nWith Vite 8 coming soon with rolldown, I've found it to be even less complicated to configure and faster than before.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3637817664, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22330#issuecomment-3637817664", "createdAt": "2025-12-10T16:05:40Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "IMHO, the real solution is to replace bundling operations by basic copy operation of module files we need to import, and to use JS module imports everywhere.\n\nAnyway, if you find a better bundler for both GLPI 10 and 11, it is OK for me to with toit\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3637819490, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22330#issuecomment-3637819490", "createdAt": "2025-12-10T16:06:07Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I'm not a frontend expert, but IMO we do need a bundler (and a build step) even if we use JS modules. A bundler is far more efficient than sending the raw JS files to browsers.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3637854474, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22330#issuecomment-3637854474", "createdAt": "2025-12-10T16:12:18Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "~~We could try to migrate to RsPack, see\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3637857847, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22330#issuecomment-3637857847", "createdAt": "2025-12-10T16:13:00Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "We could try to migrate to RsPack, see\n\nI don't see the need (except maybe the config compatibility) since Vite 8's Rolldown is also developed in Rust, and we can stay within a large development ecosystem that has become the go-to for JS as opposed to a tool that didn't exist 2 years ago. It may gain popularity, but with many things relating to JavaScript it may just as easily die and be replaced with a different new shiny thing.\n\nOn a personal note, I have concerns about its creator ByteDance as well.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3637892033, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22330#issuecomment-3637892033", "createdAt": "2025-12-10T16:19:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22330, "url": "https://github.com/glpi-project/glpi/issues/22330", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-10T15:54:34Z", "updatedAt": "2026-06-11T14:47:50Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Rotate an image automatically or suggest", "detail": "Contribution description:\nHello!\n\nI noticed that when you add an image to a ticket, some images are distorted.\n\n[Image omitted]\n\nI looked for the cause and realised that the images with this problem contained exit orientation metadata.\n\n[Image omitted]\n\nThe question is: is it possible for the software to rotate the image when viewing it, or to provide a button for this purpose?", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "No idea if an automatic rotation is possible, but that's a feature, not a bug.\n\nFor images with a wrong display; that may be a bug. Please provide a way and files that can be used to reproduce.\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3783639227, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22794#issuecomment-3783639227", "createdAt": "2026-01-22T10:25:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Also, please provde requested information, such as GLPI version used.\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3783640275, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22794#issuecomment-3783640275", "createdAt": "2026-01-22T10:26:07Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "Exemple\n\n[Image omitted]\n\n[Image omitted]\n\nI use GLPI 11.0.4\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3783712105, "author": "zekuraz", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22794#issuecomment-3783712105", "createdAt": "2026-01-22T10:43:13Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "This is the original image\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3783714159, "author": "zekuraz", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22794#issuecomment-3783714159", "createdAt": "2026-01-22T10:43:42Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce, image is correctly displayed:\n\n[Image omitted]\n\nMake sure this is not due to a plugin.\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3783755326, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22794#issuecomment-3783755326", "createdAt": "2026-01-22T10:52:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22794, "url": "https://github.com/glpi-project/glpi/issues/22794", "author": "zekuraz", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-22T10:18:32Z", "updatedAt": "2026-03-02T14:52:45Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Emails not sending with proper HTML tags in", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11,0,6\n\nIssue description:\nI have configured GLPI to send notification emails on change approval requests. They are sending, but in Outlook, the HTML shows up as just the tags for HTML and not as actual formatted HTML code. If I view the source code, I get the following between the opening body tag and \"Automatically generated by GLPI\" line\n\n URL :\nChange: Description\n Title :test Requesters : Shaun McCloud Opening Date :2026-03-12 16:04 Assigned to Technicians : Shaun McCloud Status  : New Urgency : Medium Impact : Medium Priority : Medium No Defined Category Description : test\n\nNumber of Followups : 0\n\nNumber of Problems : 0\n\nNumber of Tasks : 0\n\nI have tried using both our internal SMTP relay sending to Exchange Online and OAuth 2.0 directly to Exchange Online, and the same happens both times. It is also happening with updates to the change tracking tickets, so it is not related directly to my approval notifications.\n\nReproduction steps:\n1. Set up email notifications to send through Exchange Online\n2. Create a new change\n3. Look at the email sent", "priority": "medium", "type": "support", "createdByEmail": "logan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "reese.blair@peppermint.local", "text": "Same here with a simple local SMTP server, all email notifications are unreadable because of missing body tag...\n\nOriginal response date: 2026-04-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4183706746, "author": "Mpic", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23464#issuecomment-4183706746", "createdAt": "2026-04-03T14:27:41Z" } }, { "userEmail": "reese.blair@peppermint.local", "text": "Skyler Adler This is quite a problem : we can't use any transactional emails from GLPI.\nI can try to check the code when I have less on my plate, but don't you have any reports from this or is this an issue only in Logan Adler case and mine ?\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4197977966, "author": "Mpic", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23464#issuecomment-4197977966", "createdAt": "2026-04-07T09:33:34Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Skyler Adler This is quite a problem : we can't use any transactional emails from GLPI. I can try to check the code when I have less on my plate, but don't you have any reports from this or is this an issue only in Logan Adler case and mine ?\n\nI do not currently have time to monitor either community bug reports or paid support reports, so I do not have an answer to that question. Please do not mention people directly. It is counterproductive because everyone will probably now expect me to handle this issue, even though I do not have time to do so.\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4198038715, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23464#issuecomment-4198038715", "createdAt": "2026-04-07T09:39:33Z" } }, { "userEmail": "sage.blair@peppermint.local", "text": "Facing the same issue I found a workaround and maybe the cause as well. This isn't related to anything SMTP or email configuration, it's at template level.\n\nIn your notification templates where you can change the HTML field it shows relatively normal plain HTML. BUT... this field is not a regular textarea, but secretly a WYSIWYG. Copy the contents, right click the textarea, click Source and paste the contents in there. (You will see all HTML data escaped at first)\n\nOriginal response date: 2026-04-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4205899475, "author": "vandijkstef", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23464#issuecomment-4205899475", "createdAt": "2026-04-08T11:27:25Z" } }, { "userEmail": "reese.blair@peppermint.local", "text": "I apologize, Skyler Adler\n\nIs there anyone \"in charge\" of monitoring issues in this repo ?\n\nI wish you the best.\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4214401309, "author": "Mpic", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23464#issuecomment-4214401309", "createdAt": "2026-04-09T12:59:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23464, "url": "https://github.com/glpi-project/glpi/issues/23464", "author": "smccloud", "anonymizedAuthorEmail": "logan.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-12T18:36:36Z", "updatedAt": "2026-07-07T05:04:22Z", "closedAt": null } }, { "title": "SNMP discovery : hostname replacement in glpi/computers", "detail": "Issue description:\nHello\nAs discussed with Elliot Bennett in it seems there is a problem with glpi inventory plugin / netdiscovery.\n\nThe SNMP discovery plugin overwrites the Computers / hostname with discovered host IP address when a host is discovered.\n\nI'm using latest glpi 11 release and glpiinventory plugin version.\n\nTo reproduce, scan with snmp discovery module an IP range on which there's computers inventoried via glpi-agent remote agent. The hostname of the computer is replaced by it's IP address.\n\nUsed to do this with glpi 10 and fusioninventory agent / plugin without problem for years.\nRegards\nCédric", "priority": "medium", "type": "maintenance", "createdByEmail": "cameron.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide basic data that can be used to reproduce; I do not have network to scan.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798971999, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22829#issuecomment-3798971999", "createdAt": "2026-01-26T10:52:36Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "The real question behind is can we avoid to update a still existing computer asset in GLPI when a XML inventory from netdiscovery is submitted for the same asset which is indeed a computer and of course computer doesn't respond to SNMP credentials.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798977884, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22829#issuecomment-3798977884", "createdAt": "2026-01-26T10:54:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I have no idea how that work, I need data to check.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798981283, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22829#issuecomment-3798981283", "createdAt": "2026-01-26T10:55:05Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Also, please make sure you can reproduce with GLPI default rules.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798987800, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22829#issuecomment-3798987800", "createdAt": "2026-01-26T10:57:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The same topic persists regarding inventory management. SNMP discovery should only be performed on devices that support SNMP.\n\nCurrently, the plugin (and GLPI) are not ready to handle SNMP inventory for PCs. In any case, such devices should be excluded by the \"Constrained by Name\" rule — SNMP inventory on computers should be rejected.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798989871, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22829#issuecomment-3798989871", "createdAt": "2026-01-26T10:57:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22829, "url": "https://github.com/glpi-project/glpi/issues/22829", "author": "Rico29", "anonymizedAuthorEmail": "cameron.adler@peppermint.local", "assignees": [], "labels": [ "inventory" ], "state": "open", "stateReason": null, "createdAt": "2026-01-26T10:47:51Z", "updatedAt": "2026-05-22T13:06:09Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI 10.0.24 - Create ticket simplified interface", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.24\n\nIssue description:\nSince GLPI 10.0.23, when creating a ticket from the simplified interface, some are buggy, resulting in display issues and not receiving the ticket creation emails.\n\nLooking at the logs, I have a PHP error for each ticket that has this bug. Here is the information: [php:warn] [pid 2828623:tid 2828623] [client 10.10.10.10:42986] PHP Warning: Undefined array key \"entities_id\" in /var/www/html/glpi/src/Item_Ticket.php on line 159, referer:\n\nAffected page:\n/front/helpdesk.public.php?create_ticket=1", "priority": "medium", "type": "support", "createdByEmail": "quinn.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please first try wth latest stable release, and without any plugins.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4037728383, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23445#issuecomment-4037728383", "createdAt": "2026-03-11T09:24:47Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "Please first try wth latest stable release, and without any plugins.\nI'm on 10.0.24 its the last no ? And i have already tested without plugin ! :)\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4038026528, "author": "Apashh", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23445#issuecomment-4038026528", "createdAt": "2026-03-11T10:10:56Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Sorry, yes: 10.0.24 is indeed the latest v10.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4038048586, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23445#issuecomment-4038048586", "createdAt": "2026-03-11T10:14:26Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "Sorry, yes: 10.0.24 is indeed the latest v10.\n\nOk, so this my version today ! What can i do to help you ?\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4038238960, "author": "Apashh", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23445#issuecomment-4038238960", "createdAt": "2026-03-11T10:39:24Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "Its a probleme with fields, i have created a ticket in the plugin page\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4039784122, "author": "Apashh", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23445#issuecomment-4039784122", "createdAt": "2026-03-11T14:52:36Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23445, "url": "https://github.com/glpi-project/glpi/issues/23445", "author": "Apashh", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2026-03-11T09:15:46Z", "updatedAt": "2026-04-02T10:03:01Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI 11.0.1 - Custom HTTP request in Other authentication method not working", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWhen I try to configure GLPI 11.0.1 to use OIDC_CLAIM_email HTTP request for authentication, is not working.\n\nThe same works perfectly on 10.0.20\n\nReproduction steps:\n1. Go to Setup > Authentication > Others authentication methods\n2. Other authentication sent in the HTTP request\n3. Field storage of the login in the HTTP request\n4. Click to \"+\" icon\n5. Add \"OIDC_CLAIM_email\"\n6. Click Save\n7. Go to Administration > Users > Add\n8. Create a user with a username with the same value as the $_SERVER['OIDC_CLAIM_email']", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello Elliot Blair, I've been investigating this issue and HTTP authentication with custom headers works correctly in GLPI 11.0.1 when properly configured. The issue you're experiencing is likely related to one configuration problem.\n\nCould you please go to Administration > Rules > Authorizations assignment rules and check if you have any rules that could block ? Provide us a screenshot if you suspect anything. In addition, some recent logs that include an attempt could help.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3466728681, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21514#issuecomment-3466728681", "createdAt": "2025-10-30T08:56:36Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Thanks for answer Jordan Blair\n\nHere the screenshot ...\n\n[Image omitted]\n\nI supose that this rule is the default one\n\nNothing relevant in logs\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3466756313, "author": "mserramanxa", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21514#issuecomment-3466756313", "createdAt": "2025-10-30T09:03:13Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Can you try with no plugins on your installation ?\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3467379708, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21514#issuecomment-3467379708", "createdAt": "2025-10-30T11:01:04Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Can you try with no plugins on your installation ?\n\nDone, with the same result :-(\n\nI only disabled the plugins, not removed. It's enough?\n\nJust in case, I also tried clicking the \"Suspend execution of all plugins\" button, with the same result\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3471667155, "author": "mserramanxa", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21514#issuecomment-3471667155", "createdAt": "2025-10-31T07:47:13Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi, could you precise what is your issue exactly? Is there an error whan you create the user? Is this an issue when trying to log-in with this user?\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3479827212, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21514#issuecomment-3479827212", "createdAt": "2025-11-03T10:24:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21514, "url": "https://github.com/glpi-project/glpi/issues/21514", "author": "mserramanxa", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-16T09:09:13Z", "updatedAt": "2026-03-19T11:01:21Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "The user session freezes when entering the marketplace.", "detail": "Issue description:\nHi, everyone!\nI recently manually modified the files of the free Genericobject plugin to add icons for object groups in the sidebar. After doing this, I encountered a problem: when switching to the Plugins/Marketplace tab, the user session would freeze and there was no way to exit without restarting Apache. GLPI continued to work, and other users were unaffected.\nInitially, I thought I'd broken something, so I deleted the plugin. This didn't help, so I decided there were some remaining entries in the database that were preventing it from loading. I cleared the plugin's database.\nThen, as recommended in the guide, I updated to the latest version, but the problem persisted. (Naturally, I had made all backups beforehand.)\nI then decided to delete all plugins and their database entries. This didn't help. I then reverted to my previous version of GLPI, but did a clean installation and dumped the database. The Marketplace started working, but when I entered my registration key, the problem returned.\n\nI am not attaching error logs because there are no entries related to this in either GLPI or Apache logs.", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Did you tried to empty the GLPI files/_cache directory and restart the PHP server?\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3466408874, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21705#issuecomment-3466408874", "createdAt": "2025-10-30T07:15:30Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Yes, I tried clearing the cache first. I also tried restarting all possible services. I also rebooted the server overnight. The problem persists.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3467713175, "author": "Balots", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21705#issuecomment-3467713175", "createdAt": "2025-10-30T12:16:53Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Did you tried to remove the plugins directories? On marketplace/plugins pages, all setup.php files of all plugins are loaded. Maybe one of them causes an infinite loop.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3467757317, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21705#issuecomment-3467757317", "createdAt": "2025-10-30T12:29:20Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "At first, I thought I could delete the plugin files, and I did, but it didn't help. Now I've installed a completely clean GLPI. There are no plugins for it, and I didn't even transfer the configuration files. I just loaded the previous database.\n\nAnd that helped: the marketplace loaded without freezing my session. But the problem returned when I entered the GLPI registration key from my account.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3467780133, "author": "Balots", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21705#issuecomment-3467780133", "createdAt": "2025-10-30T12:36:04Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Today I tried reinstalling a clean version of GLPI. I didn't transfer the database. I simply entered my registration key. And the error persisted: the marketplace terminated the user session.\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3471542375, "author": "Balots", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21705#issuecomment-3471542375", "createdAt": "2025-10-31T06:49:39Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21705, "url": "https://github.com/glpi-project/glpi/issues/21705", "author": "Balots", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-30T06:50:48Z", "updatedAt": "2025-12-04T11:46:17Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Requester does not receive email notifications for follow-ups", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen an answer is added to an open ticket, the assigned technician receives an email notification for the update, but the requester of the ticket does not, but both are included within the recipients for the notification.\n\n[Image omitted]\n\nNo error logs are present, mail.log confirms that only the technician is being emailed, there is no attempt for to send to the requester.\n\nResult:\nOnly the technician receives the email; the requester does not, and no send attempt is logged for the requester.\n\nExpected result:\nThe requester should receive an email notification for the follow-up.\n\nReproduction steps:\n1. Create a new ticket via the helpdesk/self-service portal as a user with a valid email address\n2. Ensure the notification “Add Followup” is active and includes Requester as a recipient\n3. Open the ticket as a technician and assign yourself\n4. Add a public follow-up/comment to the ticket\n5. Check email delivery and notification logs", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "quinn.blair@peppermint.local", "text": "FYI (just so you know), we noticed the same issue very recently. On our GLPI v10.0.25\n\nSimilarly, a requester was not receiving email notifications for follow-ups\n(FYI, our GLPI platform is set to French language by default).\n\nWe realised (by logging into this user’s/requestor’s account) that in their account ‘preferences’, he had (deliberately) set English language.\nAs a test, we changed the language back to French in their account ‘preferences’.\nWe ran a new test by sending a new reply/follow-up in his ticket. And this time, he was indeed included in the recipients (appearing in the notification queue), and he did receive the notification email (he confirmed this to us).\n\nThere you go, if that helps resolve this issue !!!\n\nOriginal response date: 2026-06-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4619751466, "author": "FlorianV54", "anonymizedAuthorEmail": "quinn.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24329#issuecomment-4619751466", "createdAt": "2026-06-04T06:53:56Z" } }, { "userEmail": "rowan.blair@peppermint.local", "text": "Quinn Blair have you checked the notification templates? is there presente a template for \"default translation\" or just for French?\n\nOriginal response date: 2026-06-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4633270986, "author": "Giudy", "anonymizedAuthorEmail": "rowan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24329#issuecomment-4633270986", "createdAt": "2026-06-05T15:55:06Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Unfortunately doesn't look to be the same issue for us - we have English set as default language and all requesters are in English as well.\n\nOriginal response date: 2026-06-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4658106282, "author": "sam-markham", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24329#issuecomment-4658106282", "createdAt": "2026-06-09T08:56:02Z" } }, { "userEmail": "rowan.blair@peppermint.local", "text": "Drew Blair , have you checked anyway if the notification template has a \"default language\" version in the template translations TAB?\n\n[Image omitted]\n\nOriginal response date: 2026-06-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4658186421, "author": "Giudy", "anonymizedAuthorEmail": "rowan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24329#issuecomment-4658186421", "createdAt": "2026-06-09T09:05:37Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Yes there is a \"Default translation\" within translations:\n\n[Image omitted]\n\nOriginal response date: 2026-06-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4658271850, "author": "sam-markham", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24329#issuecomment-4658271850", "createdAt": "2026-06-09T09:15:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24329, "url": "https://github.com/glpi-project/glpi/issues/24329", "author": "sam-markham", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-27T09:33:33Z", "updatedAt": "2026-06-09T10:56:42Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Tickets from mail receiver randomly created without requester", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello,\nSince upgrading to the latest (docker) version of glpi, some ticket from mail receiver are being created without requester.\nThe sender address shows up in the first follow up, but not in the requester field (please see attached image).\n\n[Image omitted]\n\nCan you help me debug this issues as I can find any related information in the log files?\n\nThanks\n\nAffected page:\n\nReproduction steps:\n1. Sendo email to the configures receiver\n2. Randomly the ticket is created without requester", "priority": "medium", "type": "support", "createdByEmail": "kendall.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Can you provide a mail (.eml, with headers) that cause problems ?\nDid you also check that the matched user has the right to be a requester ?\n\nOriginal response date: 2026-03-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4053955319, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23469#issuecomment-4053955319", "createdAt": "2026-03-13T09:55:23Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "Please find the email headers attached.\n(the are from another example has we are using pop and I don't have the header of the previous screenshot)\n\n1773332862.Vfe00Ie0019e28M813347.txt\n\nThanks\n\nOriginal response date: 2026-03-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4054110201, "author": "subdriver", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23469#issuecomment-4054110201", "createdAt": "2026-03-13T10:24:36Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Using the provided email, with a receiver configured with _Automatically create user from email_ = 'yes'\nthe requester is created and set in the created ticket.\nWith this option set to 'no' and no user with the email, there is no requester defined in the ticket (your case), that's expected.\nWith a glpi user having the email [email redacted] , it's correctly received.\n\nCan you provide the exact configuration to let me reproduce the issue ?\nIs the a user having [email redacted] as email in your database ?\n\n[Image omitted]\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4075668317, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23469#issuecomment-4075668317", "createdAt": "2026-03-17T15:02:58Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "It makes sense, but, it has happened at least one case of a user sending an email and the requester not being set, and the same user sending another email and the requester being set.\nWitch configuration do you need? Please let me know and I'll send it to you.\nBellow is the receiver's configuration:\n\n[Image omitted]\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4075899273, "author": "subdriver", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23469#issuecomment-4075899273", "createdAt": "2026-03-17T15:34:04Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I needed the Collection options.\nDo you have an email that is known to have the problem ?\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4076137887, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23469#issuecomment-4076137887", "createdAt": "2026-03-17T16:06:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23469, "url": "https://github.com/glpi-project/glpi/issues/23469", "author": "subdriver", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-13T09:51:32Z", "updatedAt": "2026-03-30T08:32:23Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Profile switch / redirect to homepage when opening a ticket (multi-profile users)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.23\n\nIssue description:\nAfter updating GLPI from 10.0.22 to 10.0.23, some multi-profile users experience an issue where, when they click to open a ticket, their profile seems to change automatically and the interface redirects them to the homepage instead of displaying the ticket.\n\nThe issue is intermittent and does not happen for all tickets or all users.\n\nReproduction steps:\n1. Log in with a user who has multiple profiles\n\n2. Click on a ticket in the list\n\n3. Observe that the user is sometimes redirected to the homepage and the displayed profile changes\n\nEnvironment details:\nOS: Debian 12\n\nGLPI: 10.0.23\n\nPHP: 8.2.29\n\nMariaDB: 10.11.14-MariaDB-0+deb12u2 (Debian 12)\n\nWeb server: Apache 2.4 + PHP-FPM\n\nActive plugins:\n- fields\n- formcreator\n- genericobject\n- oauthimap", "priority": "medium", "type": "support", "createdByEmail": "logan.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "As a note, I have experienced this as well very randomly but I assumed it was something weird with my development environment. I have never been able to track the cause because of how infrequently it happens for me.\n\nOriginal response date: 2026-02-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3928120107, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23187#issuecomment-3928120107", "createdAt": "2026-02-19T15:47:49Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "From what I understand, when you click to read the open ticket, it returns to the home screen instead of opening the ticket, right? I tested 10.0.23 here with two users with multiple profiles and did not identify this problem.\n\nWhat may be the case is that if the person accesses the ticket list and leaves it open, if GLPI is not automatically updating the list, it will remain in that list at that moment. If, for example, the ticket that the person tried to open was removed by the technical group to which they have access, they will no longer be able to access the ticket. The same applies if the ticket is transferred from one entity to another and the person no longer has access to the new entity.\n\nI would try to view the history of these calls to check if it is not a case of group exclusion, associated technician, or entity transfer—these are usually the cases that cause the user to no longer have access—unless the call was opened by the user themselves.\n\nTranslated with DeepL.com (free version)\n\nOriginal response date: 2026-02-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3928555113, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23187#issuecomment-3928555113", "createdAt": "2026-02-19T17:02:00Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Another case: default profile saved in the user's registration. If the user has a default profile associated with their registration, GLPI will usually switch at some point. The same logic applies here: perhaps the default profile does not have the same permissions as the other one, so when switching profiles, they lose access.\n\nIt may also be the user's default entity if a specific entity is set.\n\n[Image omitted]\n\nOriginal response date: 2026-02-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3928572408, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23187#issuecomment-3928572408", "createdAt": "2026-02-19T17:05:07Z" } }, { "userEmail": "logan.bennett@peppermint.local", "text": "Thank you for your responses. We do not use entities.\n\nFor example, a user has both the Technician and Admin profiles. As an Admin, they click on a ticket, it opens correctly, and then they are redirected to the homepage as a Technician, so the data is not saved.\n\nAdditionally, other users who have defined a custom dashboard view experience continuous page refreshing. As a workaround, I set their dashboard back to the default dashboard, which stopped this issue.\n\nOriginal response date: 2026-02-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3932599928, "author": "sy-l20", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23187#issuecomment-3932599928", "createdAt": "2026-02-20T09:18:46Z" } }, { "userEmail": "logan.bennett@peppermint.local", "text": "After disabling Kerberos SSO authentication and switching to LDAP-only authentication, the issue apparently no longer occurs.\nI also tested the Kerberos keytab, and it is functional.\n\nOriginal response date: 2026-02-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3934530949, "author": "sy-l20", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23187#issuecomment-3934530949", "createdAt": "2026-02-20T13:21:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23187, "url": "https://github.com/glpi-project/glpi/issues/23187", "author": "sy-l20", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-19T15:36:29Z", "updatedAt": "2026-03-26T10:26:27Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Mail collector loops forever when ticket creation throws an exception", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.7\n\nIssue description:\nHello,\n\nWe encountered an issue with the mail collector in GLPI.\n\nIf an exception is thrown during ticket creation, the collector does not catch it and keeps retrying the same email indefinitely.\nAs a result, the collector enters an infinite loop until manual intervention.\n\nThe problem seems to happen around:\n\n in MailCollector.php line ~817\n\nIf $ticket->add($tkt) throws instead of returning false, the exception is not handled.\n\nTo mitigate the issue on our side, we added a try/catch(Throwable $e) block to reject the problematic email and move it to the refused folder.\n\nExample patch:\n\nWithout this protection, a single malformed email can permanently block the collector process.\n\nRegards\n\nEnvironment details:\nGLPI 11.0.7 standard\n\nAdditional context:\nThanks a lot :)", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide errror stack trace, and an EML file we can use in our tests suite to reproduce the issue.\n\nOriginal response date: 2026-05-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4429721303, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24200#issuecomment-4429721303", "createdAt": "2026-05-12T10:47:41Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "Thank you very much for your reply and for the time spent investigating this issue.\n\nI completely understand the need for a stack trace and a reproducible EML sample in order to facilitate debugging and automated testing.\n\nUnfortunately, I am unable to provide the original error emails, as they contain sensitive production data that cannot be shared externally. I sincerely apologize for this limitation.\n\nThat said, the observed behavior still appears to highlight an important architectural concern regarding exception isolation within the mail collector workflow.\n\nEven without a fully reproducible case, the current behavior suggests that error handling may not be consistently enforced at the individual message level. In practice, a failure affecting a single email should never be able to interrupt or crash the entire collector process.\n\nIn a production environment, a mail collector should continue processing subsequent messages even when encountering a malformed or problematic email. Each message should ideally be processed in strict isolation so that failures cannot propagate and block the overall incoming mail flow.\n\nTypically, failed messages could instead be redirected to a quarantine or dead-letter mechanism, accompanied by detailed logging and alerting, allowing administrators to later analyze, correct, and potentially reprocess the affected messages. This approach helps ensure resilience, continuity of service, and prevents mailbox saturation.\n\nRegarding the current implementation, I also noticed that around line ~732 in MailCollector.php, there already appears to be an exception handling strategy during ticket creation:\n\nThis seems to confirm that the intended design is already based on per-message fault isolation, which is precisely why the current collector interruption behavior appears unexpected.\n\nThank you again for your attention to this issue and for your continued support.\n\nOriginal response date: 2026-05-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4432608381, "author": "mentaloverflow", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24200#issuecomment-4432608381", "createdAt": "2026-05-12T16:24:28Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please do not copy paste agent answers.\nWe need an EML file to reproduce and fix.\n\nOriginal response date: 2026-05-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4438698282, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24200#issuecomment-4438698282", "createdAt": "2026-05-13T07:59:47Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "I took the time to create several .eml test datasets for you.\n\nSome of them may work while others may not depending on your environment, but at least one of them should demonstrate that GLPI fails to catch the error and ends up breaking the mail collector.\n\nAlso, even if the problematic email is deleted, the current behavior still seems affected by IMAP caching, so the bug continues to persist for a few more minutes.\n\nThis occurs during the INSERT into glpi_tickets :\n\nIn ./src/DBmysql.php(416)\n#0 ./src/DBmysql.php(1377): DBmysql->doQuery()\n#1 ./src/CommonDBTM.php(778): DBmysql->insert()\n#2 ./src/CommonDBTM.php(1382): CommonDBTM->addToDB()\n#3 ./src/MailCollector.php(812): CommonDBTM->add()\n#4 ./src/Glpi/Controller/ItemType/Form/MailCollectorFormController.php(56): MailCollector->collect()\n#5 ./vendor/symfony/http-kernel/HttpKernel.php(181): Glpi\\Controller\\ItemType\\Form\\MailCollectorFormController->invoke()\n#6 ./vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n#7 ./vendor/symfony/http-kernel/Kernel.php(208): Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n#8 ./public/index.php(71): Symfony\\Component\\HttpKernel\\Kernel->handle()\n#9 {main}\n\ntest_a.eml\ntest_b.eml\ntest_c.eml\ntest_d.eml\ntest_e.eml\ntest_too_long.eml\n\nThank's\n\nOriginal response date: 2026-05-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4442872809, "author": "mentaloverflow", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24200#issuecomment-4442872809", "createdAt": "2026-05-13T15:59:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Some of them may work while others may not depending on your environment, but at least one of them should demonstrate that GLPI fails to catch the error and ends up breaking the mail collector.\n\nPlease make sure issue is reproducible, with one EML file. Those files are not related to environment; only GLPI instance may be (and in that case, you didi not provide any useful information).\n\nOriginal response date: 2026-05-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4474953449, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24200#issuecomment-4474953449", "createdAt": "2026-05-18T06:27:26Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24200, "url": "https://github.com/glpi-project/glpi/issues/24200", "author": "mentaloverflow", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": null, "createdAt": "2026-05-11T16:47:17Z", "updatedAt": "2026-05-20T07:34:14Z", "closedAt": null } }, { "title": "Bug on \"Priority\" field on tickets templates", "detail": "Affected version:\n11.0.4\n\nIssue description:\nThe field \"Priority\" do not Follow the predefined value in the ticket template.\nHere is my ticket template (\"Very Low\" as the Predefined Value for the field Priority):\n\n[Image omitted]\n\n[Image omitted]\n\nThe ticket creation page is provided below. The template in the first page is a very limited, forcing the user to change the Entity in order to change the ticket template to see the other fields:\n\n[Image omitted]\n\nAfter changing the Entity, new fields are shown (Priority is still Very Low, as predefined in the new ticket template for the Entity chosen):\n\n[Image omitted]\n\nBut after changing the Category to \"_Ourtos\", the value of Priority change to the sistem default value (medium):\n\n[Image omitted]\n\nEven after the ticket is open, the Priority value do not follow the predefined value in the template.\n\n[Image omitted]\n\nThere is no rules for tickes that change the value, so there is no reason why the valoe do not folow the value predefined in the ticker template.\n\nHere is the \"_Outros\" category configuration page, showing that the ticket template for this category is \"Chamados Usuários STVSEN\" (the one shown above, which wave the \"Very low\" as a predefined value for the field \"Priority\").\n\n[Image omitted]\n\nI already changed every other predefined values on the template and almost all off then follows the pre-defined values in the ticket template when I open a new ticket (\"almost\" because I do not tried all of then, there are many...) The value of the field Priority is the only one who don't.\n\nWhat others informations can I provide to help you determine if it is a bug or not?\n\nAffected page:\n\nReproduction steps:\n1. create a ticket template with the \"Very Low\" predefined value for the field \"Priority\".\n2. Associate the ticket template to an Entity in \\GLPI\\Entities\\Assistance\\Templates Configuration\\Ticket template.\n3. Associate the ticket template to a category in \\GLPI\\Setup\\Dropdowns\\Assistance\\ITIL Category\\choose the category\\ITIL Category\\Template for an Incident.\n4. Open a new ticket using a user with the permission on the Entity in question.\n5. After changing the category field, the 'priority' field should remain at 'Very Low' (as configured), but instead, it automatically changes to 'Medium' in real time, even before the ticket is submitted.", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "lane.bennett@peppermint.local", "text": "I think I just figure out the what is happening. While testing other fields to see if they would behave wrongly as \"Priority\" field, I applied predefined values on both fields \"Urgency\" and \"Impact\" in a ticket template. For my surprise, the value of the Priority do not follow the predefined value in the template because it is following the value determined for the \"Matrix of Calculus for Priority\" using Urgency and Impact values.\n\n[Image omitted]\n\nI understand that the matrix is calculating the value of the field Priority correctly based on the Urgency and impact fields, but, it makes the \"Priority Predefined Value\" in a ticket template useless (because I did not set any predefined value for Urgency and Impact). I found a way to solve my situation by setting the pre-defined values for Urgency and Impact as very low too in the ticket template. But I really think this is a Workaround solution. Not the strict correct solution, considering the Priority value changed just after I change the category Field but before a submit the ticket (before, it was right as \"Very Low\", as it should be). But it is just my conclusion, guys... If I'm wrong, please let me know.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3634857297, "author": "LeoEvaldt", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22312#issuecomment-3634857297", "createdAt": "2025-12-10T00:32:40Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "I came back with news, guys.\nI thought my Workaround solution had worked, but it didn't.\n\nIt only works while you let the fields Urgency and Impact visible in the template. The moment you hide then, they ignore the predefined values too and switch back to the default values (Medium for both). Hide the fields in the template is the key to reproduce the problem.\n\nIf you:\n\n1. define both Urgency and Impact as \"Very Low\" and let them both visible, the priority will be Very Low (because Very Low + Very Low = Very Low):\n\n[Image omitted]\n\n2. define both Urgency and Impact as \"Very Low\", show one of them and hide the other, the priority will be Low (because the value you hide, switch back to the value \"Medium\", and Very Low + Medium = Low):\n\n[Image omitted]\n\n3. define both Urgency and Impact as \"Very Low\", but hide both, the priority will be Medium (because both values you hide, switches back to Medium, and Medium + Medium = Medium):\n\n[Image omitted]\n\n4. define Urgency as Very High and Impact as \"Very Low\", but hide Impact, the priority will be High (because Impact switches back to Medium when you hide it, and Very High + Medium = High):\n\n[Image omitted]\n\nAnd for the other values, the same behavior is shown.\nSo There is no escape. There is no way to choose a Predefined Value to the Priority field in tickets template if you do not set or hide Urgency and/or Impact. Both need to be set and both need to be visible.\nI came back to my original problem: how to predefine Priority field in ticket template hiding Urgency and Impact?\nI'm opened to suggestions.\n\nThanks.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3634935373, "author": "LeoEvaldt", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22312#issuecomment-3634935373", "createdAt": "2025-12-10T01:10:11Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Hello I didn't see any issue on my side, the priority is well defined.\nMaybe the category got a default ticket template that is different and that's why it's not applied when you changed the category.\n\nYou can verify that here : /front/itilcategory.php\n\n[Image omitted]\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3635895881, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22312#issuecomment-3635895881", "createdAt": "2025-12-10T08:16:40Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Hello I didn't see any issue on my side, the priority is well defined. Maybe the category got a default ticket template that is different and that's why it's not applied when you changed the category.\n\nYou can verify that here : /front/itilcategory.php\n[Image omitted]\n\nBefore open this report issue, I did this verification you suggest. In my first post I presented the page you suggest me to verify. Can you see it in my first post? Is there some error in the post that prevent you to see it? If so, please let me know.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3638219698, "author": "LeoEvaldt", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22312#issuecomment-3638219698", "createdAt": "2025-12-10T17:35:56Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "I Just found another weird behavior on this (possible) bug.\nAfter choose the category, the value of field Priority switch to \"Medium\" (as I explained earlier). The image below shows the value of Priority after been switched from the predefined \"Very Low\" Value to \"Medium\".\n\n[Image omitted]\n\nBut an interesting thing happens if you try to submit the ticket with a mandatory field not filled (or with another error): the value of the field Priority switch back to the predefined value \"Very Low\".\n\n[Image omitted]\n\nI really believe there's something wrong here.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3638955174, "author": "LeoEvaldt", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22312#issuecomment-3638955174", "createdAt": "2025-12-10T21:04:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22312, "url": "https://github.com/glpi-project/glpi/issues/22312", "author": "LeoEvaldt", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": null, "createdAt": "2025-12-09T23:09:33Z", "updatedAt": "2025-12-17T23:41:32Z", "closedAt": null } }, { "title": "Cannot add/update multiple devices (computers, monitors, etc.) to a group at the same time.", "detail": "Affected version:\n11.0.0\n\nIssue description:\nThere is no option to add or update when selecting multiple devices to assign to 1 group.\nIn GLPI 10, I can update multiple devices (for example, computers) to 1 group at the same time. However, in GLPI 11, the Group field is not displayed for selection.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "reese.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I guess this is because of the multiple groups feature; this is no longer a \"field\" in the database, but now a relation table.\n\nNot sure how to handle that, Taylor Adler may know.\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3370359201, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21298#issuecomment-3370359201", "createdAt": "2025-10-06T07:54:23Z" } }, { "userEmail": "reese.bennett@peppermint.local", "text": "Do you have any solution to this problem? Taylor Adler\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3374891172, "author": "hoaitran0429", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21298#issuecomment-3374891172", "createdAt": "2025-10-07T01:58:19Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please wait for someone have time to take a look at this one; asking every day for updates won't speed-up the process.\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3375161685, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21298#issuecomment-3375161685", "createdAt": "2025-10-07T04:35:47Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Not sure it is a bug. The massive actions update doesn't seem built to support this kind of field. I could removed the explicit block that keeps the fields from being shown here, but it would treat both \"Group in charge\" and \"Group\" the same way and not set the \"type\" field properly to differentiate the type of group.\n\nI believe this is why there are different actions for some other link/dropdown fields like requesters/observers/technicians for tickets.\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3382274750, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21298#issuecomment-3382274750", "createdAt": "2025-10-08T16:09:52Z" } }, { "userEmail": "reese.bennett@peppermint.local", "text": "this will be very inconvenient if can not update devices to 1 group at the same time. it will take a lot of time to add each device. affect the device allocation by group. can you handle this problem?\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3383861012, "author": "hoaitran0429", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21298#issuecomment-3383861012", "createdAt": "2025-10-09T02:51:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21298, "url": "https://github.com/glpi-project/glpi/issues/21298", "author": "hoaitran0429", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-06T07:43:08Z", "updatedAt": "2025-12-04T11:46:31Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Image attachments not showing a preview in ticket timeline", "detail": "Affected version:\n10.0.20\n\nIssue description:\nImage attachments are not showing up as a preview in ticket timeline either imported from e-mail or form creator; jpeg or png or other format.\nImage is showing up as a preview if it is added in e-mail signature only.\n\nReproduction steps:\n1. Send e-mail with image attachment to GLPI mail receiver ;\n2. Open received ticket in GLPI;\n3. See attachement in ticket timeline\n\n[Image omitted]\n\nAdditional context:\nIn GLPI 10.0.16 and earlier this issue was not present.", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nPlease attach the source email, in eml format, so we can try to reproduce.\n\nOriginal response date: 2025-09-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3308018370, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21062#issuecomment-3308018370", "createdAt": "2025-09-18T15:08:14Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "Hi. Here it is.\n\nPicture preview.eml\n\nOriginal response date: 2025-09-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3310513440, "author": "RaivoMahnovs", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21062#issuecomment-3310513440", "createdAt": "2025-09-19T04:31:05Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce the issue on my side.\n\n[Image omitted]\n\nCould you try to reproduce with no active plugins ?\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3317357434, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21062#issuecomment-3317357434", "createdAt": "2025-09-22T07:32:43Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "I did it with no active plugins and it is the same result for me.. pictures are shown as text.\nI don't understand, what could possibly cache on my server, if i did the install on clean server as shown in the official install tutorial.\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3317385827, "author": "RaivoMahnovs", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21062#issuecomment-3317385827", "createdAt": "2025-09-22T07:41:29Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Do you use IMAP or POP3 ?\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3317525473, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21062#issuecomment-3317525473", "createdAt": "2025-09-22T08:21:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21062, "url": "https://github.com/glpi-project/glpi/issues/21062", "author": "RaivoMahnovs", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-09-18T08:11:38Z", "updatedAt": "2025-12-04T07:35:36Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Assign equipment by hostname", "detail": "Affected version:\n11.04\n\nIssue description:\nIt seems as though the ticket rule \"Associated Elements -> Assign: equipment by name+domain\" isn't working.\nwhat I'm trying to do is this:\n get the hostname of the computer from which the ticket was opened into the ticket body\n locate that value using regex (for example, computer.mydomain.com) and store it as #0\n use the above rule to assign the asset to the ticket\n\nthe first two steps work just fine - it's only the last one that fails. for testing purposes, I added a rule that matches the regex /(.*)/ and assigns the value based on that. I tested a bunch of different formats - FQDN, short hostname, using @ before the domain instead of a dot, all caps, no caps, etc. I even tried appending the domain name to the name of one of my computers and using that, but that didn't work either.\n\nAt this point the only thing I can think of is that the rule must be broken, which is why I'm submitting this as a bug report. If that isn't the case, I apologize.", "priority": "medium", "type": "support", "createdByEmail": "emerson.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I added a rule that matches the regex /(.*)/\n\nThat regular expression matches everything.\n\nThis works for me for the rule you describe:\n/(\\w+\\.[.\\w]+)/\n\nI had to:\n- create an Internet Domain (Setup > Dropdowns) for my domain\n- add a network port on my computer with the network name set to the computer name, and the Internet Domain set to the domain I created\n\nI assume that this is all stuff that GLPI Agent/GLPI Inventory will create during automatic inventories.\n\nOriginal response date: 2026-01-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3703778660, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22506#issuecomment-3703778660", "createdAt": "2026-01-01T14:32:35Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "That regular expression matches everything.\n\nI'm aware, that's why I used it for testing - to be able to try different formats and see if it assigns them properly.\n\nadd a network port on my computer with the network name set to the computer name, and the Internet Domain set to the domain I created\n\nThis is probably the issue. The names of networks imported by the agent are named after the NIC or adapter, realtek-pcie-gbe-family-controller for example, so the rule doesn't work.\n\nOriginal response date: 2026-01-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3703786731, "author": "eran113", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22506#issuecomment-3703786731", "createdAt": "2026-01-01T14:43:14Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "If the automatic inventory doesn't create what is needed for this rule action to work properly, then I think there is indeed a bug somewhere but I don't know enough about the automatic inventory feature to say where.\n\nOriginal response date: 2026-01-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3703794181, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22506#issuecomment-3703794181", "createdAt": "2026-01-01T14:53:44Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "[...]\nThis is probably the issue. The names of networks imported by the agent are named after the NIC or adapter, realtek-pcie-gbe-family-controller for example, so the rule doesn't work.\n\nIf that's the only information available, I'm afraid we can't do that much.\nFirst check if inventory files contains the data you expect.\n\nOriginal response date: 2026-01-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3709364010, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22506#issuecomment-3709364010", "createdAt": "2026-01-05T08:13:03Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "Sorry for the late reply. All the required data is in the inventory json files. Under \"operatingsystem\" you will find the \"fqdn\" field. I believe assigning that as the network's name or alias should fix the issue.\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3736988043, "author": "eran113", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22506#issuecomment-3736988043", "createdAt": "2026-01-12T05:53:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22506, "url": "https://github.com/glpi-project/glpi/issues/22506", "author": "eran113", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-30T13:42:26Z", "updatedAt": "2026-01-12T08:48:24Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI Assistance dashboard not loading after upgrade to 11.0.0", "detail": "Affected version:\n11.0.0\n\nIssue description:\nGLPI Assistance dashboard not loading after upgrade from 10.0.10 to 11.0.0. Please advise.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "cameron.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please test with 11.0.1.\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3458334129, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21675#issuecomment-3458334129", "createdAt": "2025-10-28T20:22:42Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "Thank you so much for the quick guideline.\nAfter upgrading to 11.0.1, i am still facing the same issue for assistance dashboard.\nJust to mention the Asset dashboard and global dashboards are working fine.\n\n[Image omitted]\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3463117020, "author": "kazishakilahmed", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21675#issuecomment-3463117020", "createdAt": "2025-10-29T18:31:12Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Are there any entries in GLPI logs? Also try without any plugin.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3466235977, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21675#issuecomment-3466235977", "createdAt": "2025-10-30T05:57:19Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "Suspended all Plugins but still getting the same issue as before.\n\n[Image omitted]\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3469428124, "author": "kazishakilahmed", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21675#issuecomment-3469428124", "createdAt": "2025-10-30T18:21:30Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "Also getting the following errors on DB schema check\n\n[Image omitted]\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3469435739, "author": "kazishakilahmed", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21675#issuecomment-3469435739", "createdAt": "2025-10-30T18:23:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21675, "url": "https://github.com/glpi-project/glpi/issues/21675", "author": "kazishakilahmed", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-28T20:20:44Z", "updatedAt": "2025-12-25T12:09:16Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI 11 - Option to open a link in a new tab", "detail": "Contribution description:\nHello,\n\nIn the helpdesk customization, I think it would be a real improvement if you added an option to open an external link in a new tab rather than in the current tab.\n\nThank you for your work! Have an excellent day,", "priority": "medium", "type": "support", "createdByEmail": "kendall.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "From an accessibility standpoint, forcing a link to open in a new tab is not a good experience. Users should be able to choose the behavior on their own in most cases. For example, left click to open in the same tab or middle click to open in a new tab.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385914059, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21389#issuecomment-3385914059", "createdAt": "2025-10-09T13:32:07Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "From an accessibility standpoint, forcing a link to open in a new tab is not a good experience. Users should be able to choose the behavior on their own in most cases. For example, left click to open in the same tab or middle click to open in a new tab.\n\nI agree with you from the users' choice perspective, but it all depends on the professional context (and the context of the external link). For example, I work in an environment where users have almost no technical background, which means they get confused if a link opens in a non-separate tab.\n\nFor this type of profile, I think it would be useful to offer this option, especially since the choice of experience depends heavily on the context of the external link.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385936014, "author": "Gor3pig", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21389#issuecomment-3385936014", "createdAt": "2025-10-09T13:37:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "From an accessibility standpoint, forcing a link to open in a new tab is not a good experience. Users should be able to choose the behavior on their own in most cases. For example, left click to open in the same tab or middle click to open in a new tab.\n\nI agree. Maybe we could automatically add an icon to indicates that it will redirect to an external website (when the URL does not match the base URL of GLPI).\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385936410, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21389#issuecomment-3385936410", "createdAt": "2025-10-09T13:37:56Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "~users have a technical profile, which means they get confused if a link opens in a non-separate tab~\n\n~I do not think that users with technical skills are always confused when a link does not target a new tab/page. I remember discussions with other developers about this and almost all of them agreed that it is a pain when websites forces the opening of their links in new tabs/pages.~\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385951556, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21389#issuecomment-3385951556", "createdAt": "2025-10-09T13:42:22Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "That's a translation mistake; I meant users without technical skills 🙂\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385957992, "author": "Gor3pig", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21389#issuecomment-3385957992", "createdAt": "2025-10-09T13:44:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21389, "url": "https://github.com/glpi-project/glpi/issues/21389", "author": "Gor3pig", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": "reopened", "createdAt": "2025-10-09T13:27:31Z", "updatedAt": "2025-12-04T07:05:55Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Language Selector", "detail": "Contribution description:\nHi GLPI Team,\n\nIt would be great to have a language selector directly on the login page.\nCurrently, users can only change their language after logging in.\n\nHaving a dropdown or buttons for installed languages would really help multilingual environments and first-time users.\n\nThanks", "priority": "low", "type": "feature", "createdByEmail": "drew.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nFor information, the displayed languages of the login page is based on the browser preferences. If the browser is configured to display a lang available in GLPI, then this lang will be used, otherwise, it will fallback to the default language of the GLPI instance.\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3748781102, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22657#issuecomment-3748781102", "createdAt": "2026-01-14T10:10:53Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Skyler Adler\nThanks for the clarification.\n\nI tested this behavior further:\n- Firefox works correctly because it can send full Arabic locales (e.g. ar-IQ, ar-SA).\n- Chrome only sends \"ar\" without a locale, which does not match GLPI's available locales (ar_SA, ar_SY, etc.).\n\nBecause of this, the automatic language detection does not work for most Chrome users.\n\nThis is why a language selector on the login page or a mapping from \"ar\" → \"ar_*\" would greatly improve usability.\n\nOriginal response date: 2026-01-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3760891439, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22657#issuecomment-3760891439", "createdAt": "2026-01-16T16:41:02Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "see\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3766933543, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22657#issuecomment-3766933543", "createdAt": "2026-01-19T07:50:00Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Drew Bennett\nWhat should be the default region when the ar language is requested?\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3767082701, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22657#issuecomment-3767082701", "createdAt": "2026-01-19T08:32:07Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Skyler Adler\nAfter reviewing the related discussion about locale fallbacks in GLPI, it appears that Arabic is a pluricentric language with no universally accepted default region.\n\nHistorically, GLPI only had ar_SA available, and it was only partially translated. I recently contributed a full Arabic translation by adding ar_IQ, and for practical reasons the same translation was copied to ar_SA, since both currently use Modern Standard Arabic.\n\nFrom a user perspective, both locales are functionally identical in GLPI today, especially on the login screen.\n\nThat said, I agree that guessing a region is not ideal. Using the full locale when provided by the browser, and otherwise falling back to the instance default, seems the safest approach.\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3770224481, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22657#issuecomment-3770224481", "createdAt": "2026-01-19T21:46:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22657, "url": "https://github.com/glpi-project/glpi/issues/22657", "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [ "enhancement" ], "state": "open", "stateReason": "reopened", "createdAt": "2026-01-14T08:16:54Z", "updatedAt": "2026-03-02T14:53:24Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "gettext locale overrides not applied", "detail": "Issue description:\nGLPI 11.0.4\nHello, I'm trying to make some translation (there is missing translations in lt_LT, so I want to add it) but locale overriding using gettext not applied.\n\nOverride files were created in:\nglpi/files/_locales/core/lt_LT.po\nglpi/files/_locales/core/lt_LT.mo\n\nThe .po file was compiled with msgfmt, permissions are correct, cache was cleared, user language is set to lt_LT.\nHowever, strings remain untranslated even msgids exist in source files and translation catalogs.\n\nExample of lt_LT.po", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nHow did you proceed to clear the cache?\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3668980103, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22377#issuecomment-3668980103", "createdAt": "2025-12-18T08:19:08Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Hi,\n\nHow did you proceed to clear the cache?\n\nHi,\nTried both form CLI and for Debug mode in GUI.\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3669179046, "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22377#issuecomment-3669179046", "createdAt": "2025-12-18T08:56:59Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "We cannot reproduce this issue, and the fix attempt was too complex.\n\nIs this issue still present?\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3753714120, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22377#issuecomment-3753714120", "createdAt": "2026-01-15T09:19:27Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Yes, the issue is still present.\nI created override file exactly as documented:\n\nglpi/files/_locales/core/lt_LT.po\n\nCompiled the file\"\n\nCleared cache:\n\nLogged in with user which has lt_LT language and translation is not applied.\n\nOriginal response date: 2026-02-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3852650458, "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22377#issuecomment-3852650458", "createdAt": "2026-02-05T10:32:25Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the issue\n\nOriginal response date: 2026-03-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4061964051, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22377#issuecomment-4061964051", "createdAt": "2026-03-15T01:55:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22377, "url": "https://github.com/glpi-project/glpi/issues/22377", "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": "reopened", "createdAt": "2025-12-16T08:17:02Z", "updatedAt": "2026-07-20T09:29:08Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Project Template Tasks and Project Task Templates duplicate on project creation", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.04\n\nIssue description:\nWhen creating a project template the project tasks added to the template either manually or from a project task template get duplicated back to the template. Similarly when there are a lot of tasks (96 in my example) the number of duplicated tasks differs when there are sub tasks in the task.\n\nAffected page:\n\nReproduction steps:\n1. got to tools>projects>Templates and create a project template (JM Test Template) and +Add\n2. In the project template create several tasks (2 is enough) Manually added and template task in this example\n3. Check the template - in this case it has two tasks\n4. Nnavigate to tools>projects>Add (new project), name it and +Add\n5. Select the template you created, name it and +Add to save\n6.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "dakota.blair@peppermint.local", "text": "Apologies I took so long between updating the steps that the bug is incomplete. I will post the remaining points here\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4026106965, "author": "jamorrisacc1", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23423#issuecomment-4026106965", "createdAt": "2026-03-09T19:10:05Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "11.0.4 is 2 releases late. Please try with latest stable release, and also without any plugins.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4029254181, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23423#issuecomment-4029254181", "createdAt": "2026-03-10T07:22:22Z" } }, { "userEmail": "skyler.blair@peppermint.local", "text": "Tested with 11.0.6 same hapen.\n\n[Image omitted]\n\nOriginal response date: 2026-03-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4091315965, "author": "veieras", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23423#issuecomment-4091315965", "createdAt": "2026-03-19T16:07:40Z" } }, { "userEmail": "robin.blair@peppermint.local", "text": "Hello, I have the same problem. Did you find a solution? Thanks\n\nOriginal response date: 2026-04-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4266375805, "author": "Karmadibsa", "anonymizedAuthorEmail": "robin.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23423#issuecomment-4266375805", "createdAt": "2026-04-17T08:06:20Z" } }, { "userEmail": "noel.blair@peppermint.local", "text": "I tested with 11.0.6\nI also see the issue when creating a template using project task templates.\nThis means project templates are not usable for large projects\n\nOriginal response date: 2026-04-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4270308565, "author": "JamesM-echo-9", "anonymizedAuthorEmail": "noel.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23423#issuecomment-4270308565", "createdAt": "2026-04-17T18:18:24Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23423, "url": "https://github.com/glpi-project/glpi/issues/23423", "author": "jamorrisacc1", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-09T16:40:20Z", "updatedAt": "2026-05-27T11:56:08Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Add or update user emails via API", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHi team,\n\nWhen I want to create a user or update them via the API, the email address does not go through regardless of the parameters I apply in the payload, I anonymize the data :\n\n{\n \"username\": \"[email redacted]\",\n \"realname\": \"XXX\",\n \"firstname\": \"YYY\",\n \"comment\": \"Sync Azure AD\",\n \"is_active\": 1,\n \"emails\": [\n {\n \"id\": 0,\n \"email\": \"[email redacted]\",\n \"is_default\": true,\n \"is_dynamic\": true\n }\n ]\n}\n\nResponse :\n→ statut 200\n→ Response GLPI : {\"id\":18,\"username\":\"[email redacted]\",\"realname\":\"XXX\",\"firstname\":\"YYY\",\"phone\":null,\"phone2\":null,\"mobile\":null,\"comment\":\"Sync Azure AD\",\"is_active\":true,\"is_deleted\":false,\"picture\":null,\"date_password_change\":null,\"authtype\":1,\"last_login\":null,\"emails\":[],\"location\":null,\"default_profile\":null,\"default_entity\":{\"id\":0,\"name\":\"Entit\\u00e9 racine\"}}\n\nI also tried :\n {\n \"email\": \"[email redacted]\",\n }\n\nOr :\n {\n \"email\": \"[email redacted]\",\n \"is_default\": true,\n \"is_dynamic\": false\n }\n\nand other combinations, but nothing works, neither POST on /Administration/User nor PATCH on /Administration/User/{id}.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Adding emails is currently only supported for the current user through the \"Administration/User/Me/Email\" endpoint.\n\nOriginal response date: 2025-11-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3517102399, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21883#issuecomment-3517102399", "createdAt": "2025-11-11T14:09:12Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Is there a feature release date in the roadmap to be able to manage emails from the PATCH and POST of /Administration/User?\n\nPerhaps the API documentation should be modified to avoid this error.\n\nOriginal response date: 2025-11-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3517119180, "author": "VF404", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21883#issuecomment-3517119180", "createdAt": "2025-11-11T14:14:08Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "No. It is just when there is time to add it. The new API is a work in progress as every schema and endpoint needs to be manually defined to ensure it is user friendly. I already added a bunch of missing things in v2.1 of the new API (GLPI 11.0.2) and I am in the process of working on even more for v2.2. I don't know which version v2.2 will release with.\n\nAs for the documentation, I am not seeing much wrong here. The only API endpoints for emails are under /Administration/User/Me. The only thing I note is that the documentation for the \"emails\" property for the User schema is incomplete. I've made a note to look at this property and the missing endpoints.\n\nOriginal response date: 2025-11-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3517151127, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21883#issuecomment-3517151127", "createdAt": "2025-11-11T14:22:20Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Thanks so much! Can't wait for this feature to be available 🔥\n\nOriginal response date: 2025-11-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3517185490, "author": "VF404", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21883#issuecomment-3517185490", "createdAt": "2025-11-11T14:30:01Z" } }, { "userEmail": "morgan.blair@peppermint.local", "text": "Hi Taylor Adler and Skyler Adler, is this still listed for future versions or does 11.0.6 already allow adding user with emails? I understood that new api requires super-admin profile to generate tokens, thus users without this profile would never be able to use the /Administration/User/Me option, correct?\n\nThanks!\n\nOriginal response date: 2026-03-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4070845296, "author": "tfdasilva", "anonymizedAuthorEmail": "morgan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21883#issuecomment-4070845296", "createdAt": "2026-03-16T21:54:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21883, "url": "https://github.com/glpi-project/glpi/issues/21883", "author": "VF404", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2025-11-11T14:02:58Z", "updatedAt": "2026-04-08T07:31:07Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "[Notification Templates] IF in table tags from source code is moved on top", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen creating a notification template for mail to conditions(IF) are not handled in a table. They will be moved on top of the table.\nExample:\nI write this in the source code:\n\nAfter saving and opening again it will show:\n\nAll the conditions tags are moved on top of the table in source code editor.\n\nReproduction steps:\n1. Create a new notification template\n2. Go to the template translations\n3. In the email body open the source code\n4. Paste some html content with IF in a table/tbody tag and save\n5. After saving open again the source code, the conditions have been moved on top of the table.", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.bennett@peppermint.local", "text": "A workaround is to put those tags in comments, don't know if there's a better solution:\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024105023, "author": "Asmitta-01", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23413#issuecomment-4024105023", "createdAt": "2026-03-09T14:15:59Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "My previous comment was only partially correct. The source code option is one of the correct ways to add a table, but TinyMCE is also correct in removing the tags it sees as plain text from between the table and tbody because it isn't valid HTML for it to exist there. I don't know if it can be fixed as things are now, but my suggestion is to avoid designing the template with tags inside HTML elements that don't accept text content.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024569814, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23413#issuecomment-4024569814", "createdAt": "2026-03-09T15:24:41Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "TinyMCE gives a way to _exclude_ some tags:\nExample:\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024863431, "author": "Asmitta-01", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23413#issuecomment-4024863431", "createdAt": "2026-03-09T16:03:34Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Thanks for the link. I'll take a look later today.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024881129, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23413#issuecomment-4024881129", "createdAt": "2026-03-09T16:05:53Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "It looks like the protect option is used to prevent users from editing specific portions of content while valid_children seems more like what is desired here.\n\nAllowing #text as a child of every element could make this work as expected but IMO it could also lead to unexpected issues with people writing bad HTML even if it were limited to just notification templates. I think the solution here is to rethink the template. Tables shouldn't really be needed for layout these days when grid and flexbox exist in CSS.\n\nA better solution may be possible with the planned notification template rework and the move to Twig instead of the custom syntax. At that point we could switch to a code editor which would understand the template language instead of a rich-text input.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4026111076, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23413#issuecomment-4026111076", "createdAt": "2026-03-09T19:10:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23413, "url": "https://github.com/glpi-project/glpi/issues/23413", "author": "Asmitta-01", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2026-03-09T11:40:20Z", "updatedAt": "2026-03-12T00:49:19Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Automatic actions stopped working and a lot of errors appeared in php-errors.log", "detail": "Affected version:\n11.0.2\n\nReproduction steps:\n_No response_\n\n_No response_", "priority": "medium", "type": "support", "createdByEmail": "remy.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please run database integrety command line tool; you may have a problem in your database.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3509613019, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21865#issuecomment-3509613019", "createdAt": "2025-11-10T06:14:31Z" } }, { "userEmail": "remy.bennett@peppermint.local", "text": "I can't launch tools:check_database_schema_consistency.\nI do this: sudo -u www-data php bin/console tools:check_database_schema_consistency\nI get the answer: there are no commands defined in the namespace \"tools\".\nI'm obviously doing something wrong. Please tell me what needs to be run.\n\nphp bin/console db:check_schema_integrity return Ok\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3509748476, "author": "rean1mat0r", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21865#issuecomment-3509748476", "createdAt": "2025-11-10T07:02:30Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nYou have to run the sudo -u www-data php bin/console db:check command.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3509950864, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21865#issuecomment-3509950864", "createdAt": "2025-11-10T07:50:32Z" } }, { "userEmail": "remy.bennett@peppermint.local", "text": "sudo -u www-data php bin/console db:check returns Ok\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3509959100, "author": "rean1mat0r", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21865#issuecomment-3509959100", "createdAt": "2025-11-10T07:52:37Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please also try if you reproduce without plugins.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3509983284, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21865#issuecomment-3509983284", "createdAt": "2025-11-10T07:58:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21865, "url": "https://github.com/glpi-project/glpi/issues/21865", "author": "rean1mat0r", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2025-11-07T18:34:34Z", "updatedAt": "2026-03-02T09:49:44Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Field Values Not Displayed or Editable When Switching to RTL Language", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHi all,\nWhen the interface language is set to English, certain fields display their saved values correctly and can be edited normally.\n\nHowever, after switching the interface language to Arabic (RTL), those same fields:\n\n- Do not show the previously saved values\n- Appear empty even though they contain data\n- Cannot be edited properly\n\nAffected page:\n ,\n\nReproduction steps:\n1. Setup\n2. Webhooks\n3. Add\n4. URL Field\n5. Fill in the affected field and save\n6. Change the interface language to (RTL) Language\n7. Open the same item again\n&&\n1. Setup\n2. External links\n3. Add\n4. Link or filename Field & File content Field\n5. Fill in the affected field and save\n6. Change the interface language to (RTL) Language\n7. Open the same item again\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It is an issue with Microsoft's Monaco editor:\n\nI'm not sure if it could be fully fixed on our end or not.\n\nOriginal response date: 2026-02-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3866640230, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23045#issuecomment-3866640230", "createdAt": "2026-02-08T09:18:09Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Taylor Adler\nThank you for clarifying that the issue is related to Microsoft’s Monaco Editor.\n\nI have been testing a temporary workaround by forcing LTR direction via CSS and adjusting editor settings. The results are partially successful, but some rendering inconsistencies (such as selection alignment) still occur.\n\nTo properly test and apply a cleaner workaround, could you please advise:\n\n- The correct CSS file(s) where Monaco editor styling should be overridden safely\n- The exact JS file or location where the editor is instantiated and where direction-related options could be adjusted\n\nI would like to experiment with a temporary fix locally and share feedback that might help improve RTL.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3869886275, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23045#issuecomment-3869886275", "createdAt": "2026-02-09T07:43:28Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "You can add any custom CSS to your UI Customization in your entity(s).\n\nThere is no CSS from GLPI for Monaco. The JS is mostly in \"js/modules/Monaco/MonacoEditor.js\" but there are no direction options for the editor. As far as I can tell, not even VSCode which uses Monaco for the editor supports RTL. This is something that would likely be complex for us to fix and would have to be done by Microsoft. RTL support has been in their backlog for VSCode since at least 2016. I'm not even sure how something like JSON or Twig is supposed to look for RTL users.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3871898919, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23045#issuecomment-3871898919", "createdAt": "2026-02-09T14:00:29Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Since 2016...\nWell, appart changing the editor (not planned, it's been added quite recently); I see no solution.\n\nIf you find a CSS way to go, we can try to include it; but I'm affraid this will not be enough.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3875639523, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23045#issuecomment-3875639523", "createdAt": "2026-02-10T06:36:09Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Skyler Adler\nI have applied a scoped CSS override inside the existing stylesheet under the Monaco section.\n\nThe modification was added in:\ncss_glpi.min.css\nUnder the .monaco-editor branch.\n\nThe applied rules are:\n\ntext-align: left;\ndirection: ltr;\n\nThis adjustment improves text visibility and alignment when the interface language is set to (RTL). I have not modified any JavaScript files to avoid unintended side effects. Feel free to integrate or relocate the override in a more appropriate location if needed.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3879781149, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23045#issuecomment-3879781149", "createdAt": "2026-02-10T17:49:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23045, "url": "https://github.com/glpi-project/glpi/issues/23045", "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [ "javascript", "ui" ], "state": "open", "stateReason": null, "createdAt": "2026-02-08T06:15:19Z", "updatedAt": "2026-02-11T06:35:03Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Requester receives follow-up emails about its own follow-ups", "detail": "Affected version:\n10.0.14 (last)\n\nProblem:\nWhen a requester adds a follow-up by email (just replying to a previous notification), this same requester receives a follow-up email with its follow-up content.\n\nRelated info:\nSimilar issues have been discussed on #15362 (this is not the exact case, as it is the REQUESTER who receives the notification, not the agent) and on this forum topic: _Followup author is receiving email notification of their own followup_.\n\nAs commented on the forum by _clutch69rs_, removing the requester from the _Add Followup_ Notification is not applicable: the requester has to receive the notifications when an agent add a followup on its ticket.\n\nIt is kind of a blocking problem for some of us, as _mimix_ comments: _I am currently encountering the same problem and this behavior is absolutely an obstacle to the adoption of GLPI within our company._\n\nReproduction steps:\n1. A ticket is created. Indifferent the way or direction.\n2. Requester (external, not in GLPI users DB) replies to a previous notification email, adding a comment.\n3. When GLPI processes the incoming e-mail, adds the content to ticket AND fires the Add Followupnotification.\n4. This notification is sent to the requester (and others).\n5. The requester feels confused as in 1 minute from its reply, receives a email with the same content.\n\nIt generates so much noise and it is uncommon for any other helpdesk software.\n\nAdditional context:\nThanks a lot in advance!", "priority": "medium", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "rowan.bennett@peppermint.local", "text": "I'm experiencing the same issue in GLPI 11.0.0, but I'm not sure if it's a misconfiguration on my side or a bug. Could someone help me troubleshoot it?\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3378719491, "author": "dioig0", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/16813#issuecomment-3378719491", "createdAt": "2025-10-07T21:05:14Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Hello, Rowan Bennett!\n\nIt's sad to hear that this issue is still happening on GLPIv11.\n\nThere are two ways to configure this on GLPI:\n - _Notification for my changes_, on the user profile\n - _Notification for my changes_, on the Setup > General configuration of GLPI. According to the documentation and what had been talked about in this issue, this setting should be applied by default to all users, even the ones without profile on GLPI (just email as contact).\n\nYou can see screenshots of both options in this previous comment.\n\nAre there any updates on this issue? Skyler Adler Taylor Adler Skyler Adler\n\nThanks in advance!\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385086918, "author": "gonzaleztroyano", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/16813#issuecomment-3385086918", "createdAt": "2025-10-09T09:55:37Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Hello Kai Bennett,\n\nI’ve narrowed down my issue.\n\nThe problem only occurs when I use the “Execute” button in Setup > Automatic Actions > mailgate.\n\nIf I wait for the cron job to run, the notifications are generated and delivered to the correct recipients as expected.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385211526, "author": "dioig0", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/16813#issuecomment-3385211526", "createdAt": "2025-10-09T10:28:10Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Kai Bennett,\n\nI’ve narrowed down my issue.\n\nThe problem only occurs when I use the “Execute” button in Setup > Automatic Actions > mailgate.\n\nIf I wait for the cron job to run, the notifications are generated and delivered to the correct recipients as expected.\n\n#21387 should permit to have the same behaviour for both emails collected by the cron script and emails manually collected. I do not know if it fixes all the cases reported here, but at least it will be easier now to have consistent test results.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385674158, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/16813#issuecomment-3385674158", "createdAt": "2025-10-09T12:37:51Z" } }, { "userEmail": "jamie.bennett@peppermint.local", "text": "Привіт,\n\nТа сама проблема тут, у версії 10.0.16, це трапляється як з анонімними користувачами, так і з користувачами бази даних GLPI.\n\nДля параметра «Сповіщення про мої зміни» в розділі Налаштування > Загальні > За замовчуванням встановлено значення «Ні».\n\nЯкщо коментар додається до заявки через веб-інтерфейс, автор не отримує власного подальшого повідомлення, але якщо коментар додається через відповідь електронною поштою, то автор отримує власне подальше повідомлення.\n\nYes, it's true and this is big problem!\nThis is my situation, the problem is described in more detail here -\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3499700969, "author": "Code-Near", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/16813#issuecomment-3499700969", "createdAt": "2025-11-06T22:46:26Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 16813, "url": "https://github.com/glpi-project/glpi/issues/16813", "author": "gonzaleztroyano", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2024-03-20T13:31:10Z", "updatedAt": "2026-06-03T06:21:28Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI 11 – Disappearance of the “User Equipment” table in the Used Items tab", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello,\nSince upgrading our instance to GLPI 11, we have encountered a significant issue with the display of the “Used Items” tab in user profiles.\n\nProblem description\n\nBefore the upgrade (GLPI 10), the Used Items tab displayed two distinct tables:\n\n1. A first table listing only the equipment directly assigned to the user\n(PC, monitors, docking stations, peripherals… actually belonging to the user)\n\n2. A second table listing equipment assigned to the user’s team / group\n(shared or group‑level assets)\n\nThis separation clearly allowed us to distinguish:\n- what belongs to the user,\n- what is shared at the team/group level.\n\nHowever, since upgrading to GLPI 11, these two tables no longer exist.\nWe now have only one single table, which displays only the equipment assigned to the team/group, and no longer shows equipment assigned directly to the user.\nAs a result, it is no longer possible to obtain the full list of a user’s equipment, even though this was an essential feature in GLPI 10.\n\nFindings / Checks performed\n- User‑specific equipment (PC, screens, peripherals, etc.) is still correctly linked to the user, but no longer appears in the Used Items tab.\n- The same behaviour occurs when logged in as a super‑admin, so this is not a permissions issue.\n- No filters are applied.\n- The issue is reproducible for all users in the system.\n\nRequest\n\nCould you please confirm:\n- whether this is a known bug or an interface regression in GLPI 11,\n- whether a fix, patch, or configuration workaround exists to restore the two‑table display,\n- or whether this behaviour is unintentional and should be addressed in a future release?\n\nGLPI-10.0.20\n[Image omitted]\n\nGLPI-11.0.6\n[Image omitted]\n\nThank you very much for your assistance.\nKind regards,\nDylan\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "quinn.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This was changed in and was presumably intentional.\n\nOriginal response date: 2026-03-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4098037242, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23559#issuecomment-4098037242", "createdAt": "2026-03-20T13:39:34Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "I don’t understand why, it was very practical!\nIs there a way to revert to the previous setup or another way to proceed?\n\nOriginal response date: 2026-03-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4098120669, "author": "dbremaudcerfrance", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23559#issuecomment-4098120669", "createdAt": "2026-03-20T13:54:48Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "If I understand you correctly, you cannot see items assigned to the user at all, only equipment assigned to the users group(s)?\nBut getting a full listing should indeed still work, I can see items assigned to the user and items shared with the group, albeit now in a single list.\n\nIf the problem is this combined listing: The changed view should actually support sorting and that could bring the separation back this way. Unfortunately, the sorting feature seems not to be implemented in the new code, but it isn't disabled in the table either. So you can actually click the column headers for sorting updates, it just won't do anything. The last column heading ('linktype') is not even set, so it displays an empty link.\nI think this is a mix of \"bug\" and \"wishlist\", but it would be great if the sorting could be implemented, maybe even combined with the filter feature.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4117779485, "author": "sl077", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23559#issuecomment-4117779485", "createdAt": "2026-03-24T12:20:20Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "Hello,\n\nCurrently, we do not have a workaround. We have registered more than a thousand assets in our GLPI. On the user page, only 50 lines are displayed, and we do not have the option to access the following pages.\n\nIf there were a way to filter by the “user” field, we could display our user’s equipment at the top, which would help us.\n\n[Image omitted]\n\nOtherwise, a layout similar to the previous version would be ideal.\n\nLooking forward to your feedback.\nThank you.\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4198135853, "author": "dbremaudcerfrance", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23559#issuecomment-4198135853", "createdAt": "2026-04-07T09:56:13Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "We noticed that equipment does not appear in the user's card if the equipment is located in another entity (higher up with inheritance). This might be your case. Changes were made to users.php in line 4716.\n''WHERE' =>$criteria + $item::getSystemSQLCriteria(), //['entities_id' => $this->getEntities()] + $criteria + $item::getSystemSQLCriteria(),'\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4249808007, "author": "rusakkl", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23559#issuecomment-4249808007", "createdAt": "2026-04-15T06:30:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23559, "url": "https://github.com/glpi-project/glpi/issues/23559", "author": "dbremaudcerfrance", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-20T13:32:34Z", "updatedAt": "2026-06-03T13:32:01Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 11.0.6 Project task in Ticket - \"An unexpected Error occured\" - Glpi\\Application\\View\\Extension\\ItemtypeExtension::getItemtypeForeignKey(): Argument #1 ($itemtype) must be of type object|string, null given", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nKlick in Tickets menu on \"Tasks\" to see earlier connected Task.\nGetting a Red bar with\" An unexpected Error occurred\" instead of expected content.\n\nProblem first happened on GLPI 10.0.5.\nUpgrading System RAM and GLPI (to 10.0.6) helped for about a week.\nNow it´s back.\n\nReproduction steps:\nKlick in Tickets menu on \"Tasks\" to see earlier connected Task.\nGetting a Red bar with\" An unexpected Error occurred\" instead of expected content.\n\nProblem first happened on GLPI 10.0.5.\nUpgrading System Ram helped for about a week.\nNow it´s back.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "emerson.bennett@peppermint.local", "text": "Edit 20.3.26:-> happens with firefox, brave and chrome, so its not browser dependend\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4074056528, "author": "Christof48", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23505#issuecomment-4074056528", "createdAt": "2026-03-17T10:50:56Z" } }, { "userEmail": "kendall.blair@peppermint.local", "text": "I have same issue. v11.0.6\n\nOriginal response date: 2026-03-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4092652970, "author": "stachu359", "anonymizedAuthorEmail": "kendall.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23505#issuecomment-4092652970", "createdAt": "2026-03-19T19:09:48Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "add:\nonly if we close the ticket we can disconnect access project-task.\nHappens with old and new tickets (see attached pdf)\n\nGLPI Project Tasks Error.pdf\n\nOriginal response date: 2026-03-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4096701535, "author": "Christof48", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23505#issuecomment-4096701535", "createdAt": "2026-03-20T09:02:45Z" } }, { "userEmail": "reese.blair@peppermint.local", "text": "I have same issue v11.0.6\n\nOriginal response date: 2026-04-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4187428427, "author": "boraergul", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23505#issuecomment-4187428427", "createdAt": "2026-04-04T17:10:49Z" } }, { "userEmail": "morgan.blair@peppermint.local", "text": "I have the same issue GLPI v11.0.6\n\nOriginal response date: 2026-04-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4266518370, "author": "pinciu-sebastian", "anonymizedAuthorEmail": "morgan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23505#issuecomment-4266518370", "createdAt": "2026-04-17T08:32:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23505, "url": "https://github.com/glpi-project/glpi/issues/23505", "author": "Christof48", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-17T10:48:23Z", "updatedAt": "2026-05-06T13:08:46Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Warning Undefined array key \"entities_id\" in CommonITILObject.php when creating", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello,\n\nI am experiencing a warning in GLPI 11.0.4 when creating or editing tickets:\n\nglpi.WARNING: * Warning: Undefined array key \"entities_id\" at CommonITILObject.php line 8361 Backtrace : ./src/CommonITILObject.php:8361 ./src/CommonITILObject.php:2369 CommonITILObject->getITILTemplateFromInput() ./front/ticket.form.php:89 CommonITILObject->enforceReadonlyFields() ...Glpi/Controller/LegacyFileLoadController.php:64 require() ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke() ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw() ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle() ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle(\n\nAdditionally, creating a ticket sometimes results in two tickets being generated instead of one.\n\nI use Multi entities configuration", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I just answered you on the forum. This issue was already supposed to be fixed in 11.0.5. If you update to the latest GLPI 11 version and it still occurs, feel free to reopen this bug report but we need confirmation the latest version is affected.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4117626875, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23595#issuecomment-4117626875", "createdAt": "2026-03-24T11:58:25Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "User reported on the forum they tested on GLPI 11.0.6 and the issues persist.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4117726598, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23595#issuecomment-4117726598", "createdAt": "2026-03-24T12:13:33Z" } }, { "userEmail": "remy.blair@peppermint.local", "text": "Hello,\n\nWe are experiencing the same behavior here, having recently upgraded to GLPI 11.0.6:\nThe first form used by a user each day displays an error and the option to submit a second time, resulting in the creation of two tickets.\n\nIn the form history, we see two \"Reply\" actions and one \"Ticket\" action (2603200002)\n\nIn the Tickets tab, we see the creation of two tickets a few seconds apart: 2603200001 and 2603200002\n\nForms used for the rest of the day do not exhibit this behavior.\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4125615503, "author": "CHCH069", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23595#issuecomment-4125615503", "createdAt": "2026-03-25T11:00:01Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Remy Blair,\n\nSince it only happens with one of your form, it must be something specific to its configuration.\nCan you export your form and send it here so we can try to reproduce the issue?\n\n[Image omitted]\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4141183870, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23595#issuecomment-4141183870", "createdAt": "2026-03-27T09:09:24Z" } }, { "userEmail": "remy.blair@peppermint.local", "text": "Hi\n\nsignaler-un-incident-2026-03-27.json\n\nHere is the exported form\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4141619892, "author": "CHCH069", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23595#issuecomment-4141619892", "createdAt": "2026-03-27T10:24:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23595, "url": "https://github.com/glpi-project/glpi/issues/23595", "author": "hakimbedja", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "open", "stateReason": "reopened", "createdAt": "2026-03-24T11:56:04Z", "updatedAt": "2026-04-24T06:53:08Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Misalignment of Port Mapping Squares on Zoom/Resize", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nIn the Graphical slot definition tab of Network Equipment Models, the mapping squares (image map) do not maintain their position relative to the equipment image when the browser zoom level is changed. Additionally, on smaller screens where the image exceeds the viewport width, there is no horizontal scroll, making it impossible to map ports on the far right of the device.\n\nActual Behavior\n\n- The squares stay \"static\" or scale at a different rate than the background image, leading to misalignment.\n- The UI clips the image on small screens, preventing data entry for high-number ports.\n\nThe error is not just visual during the zoom; once the zoom level is changed (e.g., to 110%) and then returned to 100%, the mapping squares remain stuck in the incorrect offset. This indicates that the coordinate calculation is not being dynamically recalculated or reset when the viewport returns to its default state.\n\nExpected Behavior\n\n- Scaling: The mapping squares should use relative positioning (percentages) or a scaling calculation so they remain pinned to the correct coordinates on the image regardless of zoom level.\n- Responsiveness: The image container should have overflow-x: auto; to allow horizontal scrolling on smaller displays without breaking the coordinate system.\n\nReproduction steps:\n1. Go to Setup > Dropdowns > Network Equipment Models.\n2. Select a model that has a Front Image and Rear Image defined.\n3. Go to the Graphical slot definition tab.\n4. Set browser zoom to 100% and draw a mapping square for a port (e.g., Port 48). Note that it aligns perfectly.\n5. Change the browser zoom to 110% or 125%. Observation: The green/blue squares shift out of place, no longer covering the physical ports on the image.\n6. Resize the window so it is narrower than the equipment image. Observation: The image is cut off, and there is no horizontal scrollbar to reach the end of the device.\n7. Return the browser zoom level to 100%. Observation: The mapping squares remain misaligned and do not \"snap back\" to their original correct positions until the page is fully refreshed.\n\nAdditional context:\nThe misalignment is not exclusive to browser zooming. Any action that triggers a window.onresize event (such as toggling the developer console or resizing the browser window) causes the port mapping squares to lose their anchor point.\n\nThe script likely calculates the initial top/left offsets of the squares based on the image's dimensions at the exact moment of page load. When the viewport changes (zoom or console toggle), the background image scales or shifts, but the mapping squares' coordinates are either not updated correctly or are updated using a faulty ratio that doesn't account for the container's new bounding box.\n\nScreenshots\n\n100% Zoom\n\n[Image omitted]\n\n110% Zoom\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the issue, but I haven't been able to identify a fix yet.\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4122645534, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23609#issuecomment-4122645534", "createdAt": "2026-03-25T02:10:51Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The equipment image scales correctly with the browser zoom, but the mapping overlays appear to be using absolute pixel offsets that do not maintain their anchor point relative to the image asset.\n\nThe fact that the squares do not return to their correct positions when returning to 100% zoom suggests that the coordinate calculation logic is being overwritten in the DOM during the zoom event. The script likely listens for window.onresize, recalculates the port offsets based on the zoomed dimensions, and applies them to the mapping squares. Because these calculations appear to use absolute pixel offsets (or a faulty scaling ratio), the coordinates become \"corrupted\" once a zoom level other than 100% is reached.\n\nPotential Fixes:\n\n- Relative Positioning: They are likely Absolute relative to their parent container (the equipment image div). Instead of absolute pixels, the port coordinates should be stored and rendered as percentages (e.g., top: 15.5%; left: 22.1%;) within a position: relative container that holds the image. This ensures the squares scale 1:1 with the image at any zoom level.\n- Resize Observer: If the coordinates must remain in pixels for the database, the UI should use a ResizeObserver or listen for the resize event to recalculate the square positions based on the image's current getBoundingClientRect() whenever the viewport or zoom level changes.\n- Viewport vs. Element coordinates: Ensure the mapping logic is referencing the image's top-left corner as (0,0) rather than the document's top-left corner.\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4122671537, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23609#issuecomment-4122671537", "createdAt": "2026-03-25T02:18:24Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The zone bounds are relative... to the image.\nWhen the page loads, the image and canvas are made the same size. The drawn zones are therefore correct.\n\nWhen you resize the page, the canvas resizes but not the image so the zones become misaligned.\n\nIf you edit a zone, it changes the size of the image based on the image matrix set in the zone data (restores the image to how it was when the zone was created) and switches to the CropperJS selection. Since the image size remains static, those are properly aligned even when resizing the window.\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4218117064, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23609#issuecomment-4218117064", "createdAt": "2026-04-09T22:34:01Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "When using an HTML over an [Image omitted], they exist as two separate layers. If the browser resizes, the DOM might resize the canvas element, but if the internal drawing context (the actual width/height properties of the canvas) or the image beneath it doesn't scale perfectly in tandem, the drawn elements (the zones) \"drift\" from the visual image.\n\nProposed Solution (ResizeObserver / Redraw):\n\nAttach a ResizeObserver to the image element (or listen to window.onresize). When a resize event fires (whether from browser zoom or toggling the console), the handler should:\n\n1. Update the internal width and height attributes to match the new getBoundingClientRect() of the image.\n1. Trigger the function that redraws the zones so they map to the new canvas scale.\n\nSince CropperJS already handles this by locking the dimensions when editing, applying a similar dimensional sync to the standard view on resize should keep the canvas and image perfectly aligned at all zoom levels.\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4218205941, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23609#issuecomment-4218205941", "createdAt": "2026-04-09T22:46:56Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The CropperJS canvas is not a . Anyways, I don't expect AI to properly diagnose or resolve the issue. Maybe another developer has a better understanding of the feature, but I'm going to leave the stencil-related bugs alone for now as I've already spent several hours looking at them and they don't seem particularly urgent.\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4218252624, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23609#issuecomment-4218252624", "createdAt": "2026-04-09T22:54:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23609, "url": "https://github.com/glpi-project/glpi/issues/23609", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "javascript", "ui", "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-03-25T00:17:55Z", "updatedAt": "2026-04-09T22:56:39Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Unable to connect peripherals to computer", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nThe automatic action of the peripherals is unable to connect to the computer.\nConnections to other components return an error.\n\nAffected page:\n/front/peripheral.php\n\nReproduction steps:\n1. Go to Assets > Peripherals\n2. Check peripherals to connect\n3. Massive actions > Connect\n4. Choose any type and asset\n5. Click \"Connect\"\n\nEnvironment details:\nGLPI: 11.0.5 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: 1 files changed\n A: inc/downstream.php", "priority": "medium", "type": "support", "createdByEmail": "remy.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The provided logs seem only related to plugins. Can you try this again with the plugins disabled?\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967001596, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23255#issuecomment-3967001596", "createdAt": "2026-02-26T14:29:52Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I don't know if it is related, but when testing this I found that peripherals were showing for every computer. For example, my monitor shows it is only connecting to my development PC but from any computer, this monitor shows in its connections list.\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967014555, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23255#issuecomment-3967014555", "createdAt": "2026-02-26T14:31:43Z" } }, { "userEmail": "remy.bennett@peppermint.local", "text": "All plugins are disabled.\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967017216, "author": "Mateusz-Szczykutowicz-sokol-it", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23255#issuecomment-3967017216", "createdAt": "2026-02-26T14:32:14Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The only way I got an actual error was when adding a new peripheral to a computer but it was different than the reported issue.\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967026091, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23255#issuecomment-3967026091", "createdAt": "2026-02-26T14:33:48Z" } }, { "userEmail": "remy.bennett@peppermint.local", "text": "I'm interested in massive actions. I'd like to add many peripherals to a specific computer, but I don't have that option.\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967047290, "author": "Mateusz-Szczykutowicz-sokol-it", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23255#issuecomment-3967047290", "createdAt": "2026-02-26T14:37:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23255, "url": "https://github.com/glpi-project/glpi/issues/23255", "author": "Mateusz-Szczykutowicz-sokol-it", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-26T14:24:32Z", "updatedAt": "2026-03-25T10:44:34Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Add button does not appear in the rules for assigning created through an email receiver", "detail": "Affected version:\n11\n\nIssue description:\nWhen I try to create a new rule for collecting tickets via email, the add button is not displayed.\n\nThis requires that to create a new rule, a native rule must be cloned and modified.\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. Access the menu Administration\n2. Selecte the Rules option\n3. Selecte rules for assigning created through an email receiver option\n\nEnvironment details:\nI am using GLPI Network Cloud.", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Do you have at least one mail collector added and set to active?\nIs the add button showing for other rule types?\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3499976269, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21842#issuecomment-3499976269", "createdAt": "2025-11-07T00:38:25Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Yes. There is an active collection account and the option to create a rule for collecting tickets by email is visible.\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501244993, "author": "jcamargo-teclib", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21842#issuecomment-3501244993", "createdAt": "2025-11-07T08:22:57Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I cannot reproduce.\n\nIs the CREATE right for Rules for assigning a ticket created through a mails receiver enabled on your profile?\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611107392, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21842#issuecomment-3611107392", "createdAt": "2025-12-04T09:35:21Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Here Skyler Adler , I opened a new GLPI Cloud Network instance, and even using a superadmin profile, when trying to create a new rule for collecting tickets by email, the add button does not appear.\n\nI have to clone an existing rule in order to edit it and create new rules.\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3616660468, "author": "jcamargo-teclib", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21842#issuecomment-3616660468", "createdAt": "2025-12-05T12:19:05Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I still cannot recreate the issue. Did the issue persist after logging out and back in to force the menu info to regenerate?\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696636015, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21842#issuecomment-3696636015", "createdAt": "2025-12-29T14:09:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21842, "url": "https://github.com/glpi-project/glpi/issues/21842", "author": "jcamargo-teclib", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": null, "createdAt": "2025-11-06T17:54:14Z", "updatedAt": "2026-01-13T10:46:43Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "The helpdesk dashboard does not display all received requests (Assistance - List of New tickets)", "detail": "Affected version:\n11.0.0\n\nIssue description:\nHelpdesk dashboard does not show all received requests (Assistance - List of New tickets)\n\nIf I have created a dashboard in which I want to select the Assistance - List of New tickets list, only one random ticket is displayed. If I have the dashboard as read only and anonymous, no record is displayed in the table. In my opinion, the list does not work for both logged in and non-logged in users - here you should probably see the list of new requests.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "riley.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello, i'm not able to reproduce your issue : created a dashboard with the same blocks as you did, created some tickets. And i see the correct amount of tickets on the list you showed in your screenshot (i assume on /front/ticket.php). Can you communicate more details if you still have the problem ?\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396394502, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21301#issuecomment-3396394502", "createdAt": "2025-10-13T08:26:21Z" } }, { "userEmail": "riley.bennett@peppermint.local", "text": "I'm sorry, after the upgrade the table in my dashboard shrank to \"one row\" and therefore I didn't notice that the table wasn't stretched downwards. Now I've expanded the table and I can see everything there. The problem still persists in the shared dashboard, when I share the dashboard and open it in an \"anonymous window\", I don't see any requests. I guess the requests are somehow linked to a certain group of users, am I doing something wrong or is it a BUG?\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396421837, "author": "tojeroman", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21301#issuecomment-3396421837", "createdAt": "2025-10-13T08:34:19Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "You may first try if you reproduce with latest release\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396448203, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21301#issuecomment-3396448203", "createdAt": "2025-10-13T08:42:15Z" } }, { "userEmail": "riley.bennett@peppermint.local", "text": "Yes, I'm working with the latest version 11.0.1, the problem is the same and was also in version 10. Most likely this list is set only for a certain group of users and not \"everyone\" - or rather for the Read-Only Profile. We even tried setting the Personal value to YES in the dashboard sharing.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396460016, "author": "tojeroman", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21301#issuecomment-3396460016", "createdAt": "2025-10-13T08:45:24Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I can reproduce on current 11.0/bugfixes branch\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3540287053, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21301#issuecomment-3540287053", "createdAt": "2025-11-17T07:12:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21301, "url": "https://github.com/glpi-project/glpi/issues/21301", "author": "tojeroman", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-06T08:52:12Z", "updatedAt": "2025-11-17T07:19:33Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "[11.0.6] Permanent Deletion of User in Profiles -> Users Tab throws Authorization Error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nIt is not possible to permanently delete a user in Administration -> Profiles -> Users Tab.\nError Msg: failed operation (1 authorizations problems, 0 failures) : authorization error\n\nThere are no further errors logged.\n\nIn Administration -> User -> Authorization Tab the deletion is successful.\n\nReproduction steps:\n1. As Super-Admin navigate to Administration -> Profiles\n2. Click on any profile\n3. Select an user in Users Tab and Post a \"Delete permanently\"\n\nReceive Error in UI: Failed operation (1 authorizations problems, 0 failures) : Authorization error\n\nNo errorlog is written.\n\nEnvironment details:\nGLPI: 11.0.6\nInstallation mode: DOCKER\nCurrent language: en_GB\nSource Integrity: OK\nOperating system: Linux cce127818dd3 5.14.0-570.51.1.el9_6.x86_64 #​1 SMP PREEMPT_DYNAMIC Sat Sep 27 01:10:11 EDT 2025 x86_64\nPHP: 8.5.3 apache2handler\nDatabase:\nServer Software: MySQL Community Server - GPL\nServer Version: 9.6.0", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please include the relevant output in the GLPI logs. Specifically, \"files/_log/access-errors.log\" and \"files/_log/php-errors.log\".\n\nOriginal response date: 2026-03-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4069078074, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23502#issuecomment-4069078074", "createdAt": "2026-03-16T16:44:13Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Thank you for your response.\nAs said, no further logs written related to this problem. I took my time to review the whole system, especially files in \"files/_log/* ( in docker /var/glpi/logs/*)\n\nAlso no problem at the reverse-proxy: The POST action to massiveaction.php returns status 200. The GET action afterwards has the embedded error msg in html.\n\nAny hints?\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4072645357, "author": "ewilli", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23502#issuecomment-4072645357", "createdAt": "2026-03-17T06:16:25Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Error still persists:\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-04-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4176512323, "author": "ewilli", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23502#issuecomment-4176512323", "createdAt": "2026-04-02T11:01:52Z" } }, { "userEmail": "rowan.blair@peppermint.local", "text": "Hello!\nI'm having the same issue on GLPI 11.0.7\nAfter looking a little bit into this issue, it seems like the script that processes the massive action is receiving the User ID of the assigned user instead of the Profile_User ID.\n\n[Image omitted]\n\n[Image omitted]\n\nDuring the first deletion attempt, the system reports a \"successful\" operation because it actually finds and deletes a row matching that incorrect ID in glpi_profiles_users. This is quite critical, as it silently deletes a completely unrelated profile-user link!\nOn the second attempt, it throws the reported \"authorization error\" because that ID no longer exists in the table.\n\n[Image omitted]\n\nIn contrast, the Administration -> User -> Authorization Tab sends the correct ID\n\n[Image omitted]\n\n[Image omitted]\n\nHope this info helps in fixing this issue!\n\nOriginal response date: 2026-06-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4721765107, "author": "ValFran99", "anonymizedAuthorEmail": "rowan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23502#issuecomment-4721765107", "createdAt": "2026-06-16T17:59:27Z" } }, { "userEmail": "riley.bennett@peppermint.local", "text": "Hello!\n\nI'm having the same issue in GLPI 11.0.7. When deleting the profile for a user from the Profiles section, it throws \"successfull\" at first, but the profile remains there! At the second attempt of deleting, throws the same error of \"Authorization error\".\n\nBut in the Users section, I can delete profiles from users without problems.\n\nThanks in advance!\n\nOriginal response date: 2026-06-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4721982194, "author": "Arkham1997", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23502#issuecomment-4721982194", "createdAt": "2026-06-16T18:23:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23502, "url": "https://github.com/glpi-project/glpi/issues/23502", "author": "ewilli", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-16T16:33:49Z", "updatedAt": "2026-06-16T18:24:46Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "MAC address attribute not visible by default", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.5\n\nIssue description:\nDear GLPI team,\n\nI want to synchronize my devices stored in GLPI with another solution, with the API of GLPI.\nI need the MAC address attribute for each device. So I don't know how to get it.\nI tried using the API's requests such as \"/Assets/Computer\" or \"/Assets/Computer/{id}/Component/NetworkCard\".\nFor the first there is no MAC field and the second returns to me : \"[ ]\". I put the rights permissions for my user in GLPI. My question is : How can I find the MAC address of my devices stored in GLPI to automate my process by using API ?\n\nThank you for your time", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. \"/Assets/Computer/{id}/Component/NetworkCard\" correctly returns the list of network card components on a computer and includes the MAC address if it is specified.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3953620857, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23229#issuecomment-3953620857", "createdAt": "2026-02-24T17:26:03Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "I found why. I added a network card manually. So the device is showed on the API's response. I conclude that when a component is entered by auto inventory the response shows no results.\n\n[Image omitted]\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3957363382, "author": "alexandre3685", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23229#issuecomment-3957363382", "createdAt": "2026-02-25T07:29:27Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "I gave permissions for the inventory scope :\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3958356018, "author": "alexandre3685", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23229#issuecomment-3958356018", "createdAt": "2026-02-25T10:42:24Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "If MAC addresses are missing from auto-inventory data it isn't an API issue. The issue is most likely with the GLPI Agent or your system doesn't expose a MAC for that device.\n\nOriginal response date: 2026-04-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4192510794, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23229#issuecomment-4192510794", "createdAt": "2026-04-06T13:30:04Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "For each node using GLPI agent, the MAC address is visible in GLPI interface but not shown on the result of the API request :\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4197072600, "author": "alexandre3685", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23229#issuecomment-4197072600", "createdAt": "2026-04-07T06:48:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23229, "url": "https://github.com/glpi-project/glpi/issues/23229", "author": "alexandre3685", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-24T16:09:19Z", "updatedAt": "2026-04-07T06:48:53Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Problem for plugins - cannot list inventory data from simplified interface", "detail": "Affected version:\nGLPI 11 main\n\nIssue description:\nFollowing this change: Plugins are affected:\n\nFor example, the Consumables plugin, which allows users to request consumables, can no longer list them via its simplified interface. Therefore, it becomes unusable.", "priority": "high", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Casey Blair Is this fixed by #21622?\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3610587396, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21740#issuecomment-3610587396", "createdAt": "2025-12-04T06:58:08Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "No sorry - A consumable item is not taken into account when assigning a ticket.\n\nso :\n\ncannot be used. Perhaps add a $bypass parameter on Dropdown::show ?\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3628378789, "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21740#issuecomment-3628378789", "createdAt": "2025-12-08T18:11:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "If your plugin is supposed to be give the ability to list consumables from the simplified interface, maybe you could add $_SESSION['glpiactiveprofile'][Consumable::$rightname] = READ; in the PluginConsumablesProfile::initProfile() method.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630924678, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21740#issuecomment-3630924678", "createdAt": "2025-12-09T08:14:28Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Hello Cédric\n\nWithout success\n\nI try too to add $_SESSION[\"glpiactiveprofile\"][\"helpdesk_item_type\"][] = Consumable::class; without success\n\nOriginal response date: 2026-02-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3938809033, "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21740#issuecomment-3938809033", "createdAt": "2026-02-21T13:49:26Z" } }, { "userEmail": "taylor.blair@peppermint.local", "text": "Hi! Is there any workaround, even if it involves temporarily editing a GLPi file, so that self-service users can see the consumables again? Thanks.\n\nOriginal response date: 2026-03-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4152996438, "author": "soporteitsoliss", "anonymizedAuthorEmail": "taylor.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21740#issuecomment-4152996438", "createdAt": "2026-03-30T07:54:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21740, "url": "https://github.com/glpi-project/glpi/issues/21740", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [ "complex issue" ], "state": "open", "stateReason": null, "createdAt": "2025-11-01T09:22:36Z", "updatedAt": "2026-03-30T07:54:54Z", "closedAt": null } }, { "title": "Webhook/API error - on create/update with GLPI Agent", "detail": "Affected version:\n11.0.2\n\nIssue description:\nDuring the execution of the inventory by an agent, all the webhooks triggered by the inventory generate a 500 error code for an internal request.\n\nWhen assets are created or updated manually, the webhooks work normally.\nUnder normal circumstances, the webhooks should be triggered just as they are when an asset is manually created or updated.\n\nAn log of the request didn't help much, but there it is:\n[05-Nov-2025 10:57:25 America/New_York] Glpi\\Http\\JSONResponse Object\n(\n [reasonPhrase:GuzzleHttp\\Psr7\\Response:private] => Internal Server Error\n [statusCode:GuzzleHttp\\Psr7\\Response:private] => 500\n [headers:GuzzleHttp\\Psr7\\Response:private] => Array\n (\n [Content-Type] => Array\n (\n [0] => application/json\n )\n\n [X-Content-Type-Options] => Array\n (\n [0] => nosniff\n )\n\n [Access-Control-Expose-Headers] => Array\n (\n [0] => Content-Type\n [1] => Content-Range\n [2] => Accept-Ranges\n )\n\n )\n\n [headerNames:GuzzleHttp\\Psr7\\Response:private] => Array\n (\n [content-type] => Content-Type\n [x-content-type-options] => X-Content-Type-Options\n [access-control-expose-headers] => Access-Control-Expose-Headers\n )\n\n [protocol:GuzzleHttp\\Psr7\\Response:private] => 1.1\n [stream:GuzzleHttp\\Psr7\\Response:private] => GuzzleHttp\\Psr7\\Stream Object\n (\n [stream:GuzzleHttp\\Psr7\\Stream:private] => Resource id #77\n [size:GuzzleHttp\\Psr7\\Stream:private] =>\n [seekable:GuzzleHttp\\Psr7\\Stream:private] => 1\n [readable:GuzzleHttp\\Psr7\\Stream:private] => 1\n [writable:GuzzleHttp\\Psr7\\Stream:private] => 1\n [uri:GuzzleHttp\\Psr7\\Stream:private] => php://temp\n [customMetadata:GuzzleHttp\\Psr7\\Stream:private] => Array\n (\n )\n\n )\n\n)\n\nReproduction steps:\n1. Create a Webhook on create and/or on update of a asset (computer for exemple)\n2. Run a inventory with the agent\n3. Go to the php-error.log to see the API error", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Despite that happen after an inventory, this looks like an API issue; webhook will probably fail if ran from somewhere else.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3500973764, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21846#issuecomment-3500973764", "createdAt": "2025-11-07T06:39:02Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "The error shown in this issues only appears when the update comes from an agent inventory update.\n\nI don't know if it helps, but here is a webhook created by a manual update of a comment on a computer asset:\n\n[Image omitted]\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3541684216, "author": "WBergeron", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21846#issuecomment-3541684216", "createdAt": "2025-11-17T12:50:58Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do not know at all API nor webhooks; it may be related to \"lack\" of authentication from the inventory.\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3541822498, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21846#issuecomment-3541822498", "createdAt": "2025-11-17T13:24:29Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Is this still an issue on GLPI 11.0.5 or 11.0.6? There were several fixes and improvements to the new API between 11.0.2 and 11.0.5.\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4013757390, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21846#issuecomment-4013757390", "createdAt": "2026-03-06T19:42:26Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi,\nIm trying to test the change in the next days or so!\n\nOriginal response date: 2026-03-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4083738059, "author": "WBergeron", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21846#issuecomment-4083738059", "createdAt": "2026-03-18T16:07:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21846, "url": "https://github.com/glpi-project/glpi/issues/21846", "author": "WBergeron", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2025-11-06T21:41:14Z", "updatedAt": "2026-03-18T16:07:11Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Agent Oauth fails when API is enabled", "detail": "Affected version:\n11.0.2\n\nIssue description:\nI have agent's configured with Oauth.\n\nWhen the general API for the server is enabled, the agent auth fails.\n\nIf I turn the API off the agent oauth works", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you check if this issue persist on GLPI 11.0.3?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606773037, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22164#issuecomment-3606773037", "createdAt": "2025-12-03T13:07:24Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "Tested on 11.0.3 and the behaviour is the same. Works when API is turned off and when it’s on I get.\n\n[error] [http client] Failed to request oauth access token: 400 Bad Request\n\nOn 4 Dec 2025, at 12:07 am, Cédric Anne *@*.*> wrote:\n\ncedric-anne\nleft a comment\n(glpi-project/glpi#22164)\n\nHi,\n\nCould you check if this issue persist on GLPI 11.0.3?\n\n—\nReply to this email directly, view it on GitHub , or unsubscribe .\nYou are receiving this because you authored the thread.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3609282781, "author": "trenta", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22164#issuecomment-3609282781", "createdAt": "2025-12-03T23:35:32Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "I am not able to reproduce this on my end; whether the HL API is active or not, OAuth authentication works for my GLPI agents.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3610867808, "author": "flegastelois", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22164#issuecomment-3610867808", "createdAt": "2025-12-04T08:31:29Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "Thanks for the response and testing. I’ll see if I can narrow down the issue. In our setup it is clearly working one way and not the other.\n\nOn 4 Dec 2025, at 7:31 pm, François Legastelois *@*.*> wrote:\n\nflegastelois\nleft a comment\n(glpi-project/glpi#22164)\n\nI am not able to reproduce this on my end; whether the HL API is active or not, OAuth authentication works for my GLPI agents.\n\n—\nReply to this email directly, view it on GitHub , or unsubscribe .\nYou are receiving this because you authored the thread.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611043316, "author": "trenta", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22164#issuecomment-3611043316", "createdAt": "2025-12-04T09:18:42Z" } }, { "userEmail": "parker.blair@peppermint.local", "text": "Hi, I have the same problem with GLPI 11.0.6 and HLAPI enabled. Oauth clients don't work. Commenting out\n#SetEnvIf Authorization \"(.*)\" HTTP_AUTHORIZATION=$1\n\nChanges the http error code from 400 to 500\n\n[2026-03-12 16:11:18] glpi.ERROR: * Caught TypeError: array_merge(): Argument #1 must be of type array, string given\n Backtrace :\n ./src/Glpi/OAuth/ClientRepository.php:94\n ./src/Glpi/OAuth/ClientRepository.php:94 array_merge()\n ...e/oauth2-server/src/Grant/AbstractGrant.php:161 Glpi\\OAuth\\ClientRepository->validateClient()\n ...-server/src/Grant/ClientCredentialsGrant.php:37 League\\OAuth2\\Server\\Grant\\AbstractGrant->validateClient()\n ...e/oauth2-server/src/AuthorizationServer.php:173 League\\OAuth2\\Server\\Grant\\ClientCredentialsGrant->respondToAccessTokenRequest()\n ...c/Glpi/Api/HL/Controller/CoreController.php:591 League\\OAuth2\\Server\\AuthorizationServer->respondToAccessTokenRequest()\n : Glpi\\Api\\HL\\Controller\\CoreController->token()\n ./src/Glpi/Api/HL/RoutePath.php:500 ReflectionMethod->invoke()\n ./src/Glpi/Api/HL/Router.php:721 Glpi\\Api\\HL\\RoutePath->invoke()\n ./src/Glpi/Controller/ApiController.php:98 Glpi\\Api\\HL\\Router->handleRequest()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\ApiController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:208 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:71 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4047973424, "author": "jbonor", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22164#issuecomment-4047973424", "createdAt": "2026-03-12T16:06:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22164, "url": "https://github.com/glpi-project/glpi/issues/22164", "author": "trenta", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2025-12-02T00:23:48Z", "updatedAt": "2026-03-12T16:12:43Z", "closedAt": null } }, { "title": "Missing dialog translation", "detail": "Affected version:\nGLPI 11.0.0\n\nIssue description:\nThe \"Go to menu\" isn't shown in its translated form when the system default language is other than English.\n\n[Image omitted]\n\nReproduction steps:\n1. Ensure default system language as well as the current user language is set to something other than English, e.g. Swedish.\n2. In a private browser session, log in to GLPI.\n3. The site is shown in the selected default language, e.g. in Swedish.\n4. Click on the Go to menu entry\n5. The Go to menu dialog is shown in English and not the selected default language.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Indeed, it seems like any of the strings from js/src/vue/FuzzySearch/Modal.vue are translated, even if they're present in PO files\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396342527, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21434#issuecomment-3396342527", "createdAt": "2025-10-13T08:09:54Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Issue seems to be that the locale strings aren't sent to the browser until after some of the built Vue components are sent so they always use the source strings.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396354519, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21434#issuecomment-3396354519", "createdAt": "2025-10-13T08:13:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "It seems to also affect the kanban component, as it also uses vue.\n\n[Image omitted]\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396393064, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21434#issuecomment-3396393064", "createdAt": "2025-10-13T08:25:56Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Well it isn't a Vue issue. It is literally any JS that executes before the locales file gets loaded on the client side.\nAdd console.log(('Go to menu')); at the end of common.js and you will see the same thing.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396414712, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21434#issuecomment-3396414712", "createdAt": "2025-10-13T08:32:11Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Reopened as the preferred fix from the linked PR was reverted; it only caused a slightly different race condition.\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3485161886, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21434#issuecomment-3485161886", "createdAt": "2025-11-04T10:27:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21434, "url": "https://github.com/glpi-project/glpi/issues/21434", "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "javascript" ], "state": "open", "stateReason": "reopened", "createdAt": "2025-10-13T08:06:48Z", "updatedAt": "2026-03-02T14:52:52Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Unable to set a requester", "detail": "Affected version:\n11\n\nIssue description:\nHi,\n\nI can't affect a requester in ticket.\nIt only show me 2 groups and 0 user\n\nthank you\n\nReproduction steps:\ncreate a new ticket -> no requester\n\nEnvironment details:\ndebian 12, apache 2.4, php 8.3, mysql Ver 15.1 Distrib 10.11.6-MariaDB,", "priority": "medium", "type": "support", "createdByEmail": "finley.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This might be related to entities.\nIs the user in the entity of the ticket ?\nMaybe a plugin changes the possible requesters.\n\nOriginal response date: 2025-10-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3361931004, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21257#issuecomment-3361931004", "createdAt": "2025-10-02T15:44:21Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please also provide requested information.\n\nOriginal response date: 2025-10-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3364224895, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21257#issuecomment-3364224895", "createdAt": "2025-10-03T04:36:45Z" } }, { "userEmail": "finley.blair@peppermint.local", "text": "This might be related to entities. Is the user in the entity of the ticket ? Maybe a plugin changes the possible requesters.\n\nYes user is in the entity of the ticket.\nIf a user was set, and if i remove, and try again, i can choose another user, and all works fine\ni haven't plugins\n\nedit:\nI can see \"2 actors\", but nothing in the case:\n\n[Image omitted]\n\nOriginal response date: 2025-10-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3365602512, "author": "Mystikal57", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21257#issuecomment-3365602512", "createdAt": "2025-10-03T13:00:12Z" } }, { "userEmail": "finley.blair@peppermint.local", "text": "it's a css bug ?\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3371390484, "author": "Mystikal57", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21257#issuecomment-3371390484", "createdAt": "2025-10-06T12:26:52Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The fields are only hidden if you are using a ticket template that hides those fields. You seem to be using a template that hides at least the Requester field which only affects the Users in this selection box.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3524620191, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21257#issuecomment-3524620191", "createdAt": "2025-11-13T01:02:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21257, "url": "https://github.com/glpi-project/glpi/issues/21257", "author": "Mystikal57", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-02T11:50:55Z", "updatedAt": "2026-01-13T10:14:40Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI Inventory / LLDP link detection", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHello,\nI'm building a network topology via GLPI from data generated by glpi-netdiscovery agent.\n\nI've noticed several problems:\n - MAC link detection has some false positive and some interfaces between switches get wrongly linked in GLPI (offen uplinks and trunks)\n - LLDP implementation does not seems to look for name/port but only MAC\n\nIn order to have a consolidated topology, i worded on NetworkPort.php:\n - removed temporarely $this->handleMacConnection($port, $netports_id);\n - patched handleLLDPConnection() to add in foreach:\n\nI think a button to disable mac inventory on switch to enable only LLDP neighbors on networkinventory would be great, I lookup device by name/interfacename would be more precise.\nI'm not sure if my approch is good, but needs to be reworked to word with all items and assets types (and more checks)\n\nSorry for my english,\nLouis", "priority": "medium", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi Kai Bennett\n\nwhen speaking about network inventory, don't forget to tell which glpi-agent version you're using.\n\nCurrent glpi-agent development version has still few fixes regarding LLDP support. Maybe you also can check if using glpi-agent nighty build can help.\n\nOriginal response date: 2025-12-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3665198884, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22400#issuecomment-3665198884", "createdAt": "2025-12-17T12:48:50Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Thanks for your answer\nI'm using glpi-agent 1.15 and tested in 1.12 but I think this is a GLPI server problem, not an agent on this case as CONNECTION tag is well populated on imported XML\n\nOriginal response date: 2025-12-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3665276392, "author": "lchanouha", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22400#issuecomment-3665276392", "createdAt": "2025-12-17T13:07:09Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "* MAC link detection has some false positive and some interfaces between switches get wrongly linked in GLPI (offen uplinks and trunks)\n\n* LLDP implementation does not seems to look for name/port but only MAC\n\nI'm really not sure realying on a name would produce less false positives... Inventory data cannot be guessed; most of the time there a re a really few information on which we can rely.\n\nAnyway, please provide example files so we can reproduce an issue on a fresh GLPI instance.\n\nIn order to have a consolidated topology, i worded on NetworkPort.php:\n[...]\n\nPlease open a PR with proposed changes.\n\nI think a button to disable mac inventory on switch to enable only LLDP neighbors on networkinventory would be great, I lookup device by name/interfacename would be more precise.\n\nThis *should* be possible, but I'm pretty sure the behavior depend on the inventoried hardware, and that won't fit correctly on an entire network.\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3668661646, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22400#issuecomment-3668661646", "createdAt": "2025-12-18T06:51:41Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "I do not agree, SYSNAME & IFDESCR are shared betwwen neighbors and are pretty accurate. We have ArubaCX, ArubaOS, Cisco Nexus, Comware 5 & 7, Procurve switches, and my topology is now well detected.\n\nGLPI makes it less reliable because it does not store hostname of the switch. For exemple, for a stacked switch, GLPI name is \"sw-abc - 5130EI - 1\", for a switch named \"sw-abc\".\n\nMy code is not ready for a PR, before going further, I think we need to:\n\n- check if it is the right place/way to add my code (help :)),\n- store switch internal hostname somewhere (to avoid my ugly LIKE is SQL query), because thats the information sent via LLDP,\n- handle all assets/item type (or not ?), but I'm lacking knowledge of all GLPI codebase to do it well,\n- work on handleMacConnection false positives. I will try to generate anonymized networkinventory files to reproduce the issues.\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3669041584, "author": "lchanouha", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22400#issuecomment-3669041584", "createdAt": "2025-12-18T08:31:45Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi Kai Bennett\n\nyou can eventually send me by email real snmpwalk outputs of connected devices involving your issue and I'll keep them private. I can than transmit privately to Skyler Adler XML generated from these. If finally we see a glpi-agent issue, this can also permit us to test with fixed output.\n\nAbout your topology, you can't assume all other manufacturers are always processing LLDP as expected. You may be in a stable case. Of course, we should implement standards support, but this is not so easy than it seems.\n\nAbout the stored name, GLPI changes the name for stacked devices so stack elements appears in the assets list and we can identify them. We make name assumption for connections. If I remember well, we may find via SNMP which name is really exposed for a device. Maybe snmp inventory can be enhanced to share this data with GLPI to help it to check connections.\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3669525452, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22400#issuecomment-3669525452", "createdAt": "2025-12-18T10:15:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22400, "url": "https://github.com/glpi-project/glpi/issues/22400", "author": "lchanouha", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": null, "createdAt": "2025-12-17T12:42:10Z", "updatedAt": "2025-12-18T10:15:27Z", "closedAt": null } }, { "title": "API clients UI issues in GLPI 10.0.22 (log connections massive action, filters reset 404, child entities, app_token mismatch)", "detail": "Affected version:\n10.0.22\n\nIssue description:\nHello,\n\nWe are facing multiple UI and behavior issues related to the API clients configuration in Setup > General > API. These issues look like regressions or inconsistencies introduced in GLPI 10.0.22.\n\n1. Massive action “Update log connections” shows an empty field\n\nWhen creating or editing an API client, the “Log connections” setting correctly shows three options:\n[Image omitted]\n\nHowever, when using the massive action to update this setting, it shows only an empty text box, with no options to choose from:\n\n[Image omitted]\n\nExpected: The massive action should present the same valid options available in the API client form.\n\n2. The reset filters button redirects to a 404\n\nWhen clicking the reset filters button in the API clients list:\n[Image omitted]\n\nIt redirects to: /front/apiclient.php?reset=reset and returns 404 Not Found.\n\nExpected: Filters should be cleared and the API clients list should reload normally.\n\n3. Child entities checkbox disappears after creating the API client\n\nWhen creating a new API client, a “Child entities” checkbox is visible in the top-right area of the form:\n[Image omitted]\n\nAfter the client is created and you open it again for editing, the “Child entities” option is no longer visible:\n[Image omitted]\n\nExpected: This setting should remain visible and editable after the API client is created.\n\n4. App Token mismatch between form and list\n\nThe App Token shown in the API client form is different from the one shown in the API clients list for the same client:\n[Image omitted]\n\nThis can cause confusion and lead to incorrect configuration of API integrations.\n\nWe also verified that GLPI 10.0.19 does not have this issue of App Token mismatch between form and list. They appear to be introduced in 10.0.22.\n\nExpected: The App Token should be consistent and identical in both the form and the list view.", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "logan.blair@peppermint.local", "text": "To answer point 4:\nGLPI introduces encryption for both user ('password_forget_token', 'personal_token', 'api_token', 'cookie_token') and app token in version 10.0.21. If shared screenshot is a plugin, we might need to contact the plugin dev to actually decrypt the app token itself.\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3749435329, "author": "wildangunawan", "anonymizedAuthorEmail": "logan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22604#issuecomment-3749435329", "createdAt": "2026-01-14T12:53:17Z" } }, { "userEmail": "parker.blair@peppermint.local", "text": "Hi Logan Blair , Elliot Blair\nThat API token on the list is not from a plugin, just add the column Application Token to the list of API clients.\nHowever IMHO that voice should not even be shown in the list for security reasons (one screenshot-->all tokens!). If you want the API token, you need to go into the object and press the \"eye\" button.\n\nOriginal response date: 2026-02-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3885524060, "author": "Mirkk", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22604#issuecomment-3885524060", "createdAt": "2026-02-11T16:26:17Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Hello, Taylor Adler. Any update in this issues?\n\nOriginal response date: 2026-02-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3927797646, "author": "Berlinst", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22604#issuecomment-3927797646", "createdAt": "2026-02-19T14:55:06Z" } }, { "userEmail": "kendall.blair@peppermint.local", "text": "We're facing the same problem. Any information regarding this issue?\n\nOriginal response date: 2026-07-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4908461599, "author": "overag3", "anonymizedAuthorEmail": "kendall.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22604#issuecomment-4908461599", "createdAt": "2026-07-07T20:35:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22604, "url": "https://github.com/glpi-project/glpi/issues/22604", "author": "Berlinst", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2026-01-09T13:29:07Z", "updatedAt": "2026-07-07T20:35:32Z", "closedAt": null } }, { "title": "\"Last inventory update\" date on GLPI (web) not updated", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nThe \"Last inventory update\" information on computer page ( is not updated after the GLPI-Agent performs an inventory.\n\nI'm experiencing this issue on multiple computers (they show on a saved search for computers where \"Characteristics - Last inventory date\" is \"before\" \"- 2 weeks\").\n\nLast contact: 2026-06-17 19:25\nLast inventory update: 2026-05-26 17:22\nLast update on 2026-06-17 19:25\n\nI acknowledge the inventory task can sometimes be postponed:\n\n\"Last contact\" and \"Last update\" fields do get updated (to current date/time), but not \"Last inventory update\".\n\nLast contact: 2026-06-18 17:35\nLast inventory update: 2026-05-26 17:22\nLast update on 2026-06-18 17:35\n\nIf I manually force a full inventory (ignoring postpone mechanism) I get pretty much the same output:\n\nIt's the same behavior, no \"Last inventory update\" update:\n\nLast contact: 2026-06-18 17:42\nLast inventory update: 2026-05-26 17:22\nLast update on 2026-06-18 17:42\n\nI'm sure the inventory is pushed to GLPI server and taken into account as if I start a process (say caffeinate) before executing glpi-agent I get find the process in the \"Processes\" tab (\n\nMaybe GLPI server code has a bug and is not displaying the real \"Last inventory update\"?\n\nAdditional context:\nGLPI-Agent is at version 1.17.\n\nIssue opened as advised by gbougard on\n\nI've added a debug line in Glpi\\Inventory\\MainAsset\\MainAsset::prepare() to make sure this part gets executed:\n\nI get the following in the debug-cduv.log file:\n\nLooks like the last_inventory_update in MainAsset's $data is OK, not sure why/how it gets ignored.", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with latest stable release.\n\nOriginal response date: 2026-06-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4765232941, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24613#issuecomment-4765232941", "createdAt": "2026-06-22T05:36:15Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "I've updated to v11.0.8 and executed glpi-agent --full on 3 different hosts: same issue (Last contact is updated but Last inventory update is not).\n\nOriginal response date: 2026-06-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4846326294, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24613#issuecomment-4846326294", "createdAt": "2026-06-30T17:41:29Z" } }, { "userEmail": "remy.blair@peppermint.local", "text": "Hi,\nI experienced the same issue after upgrading to v11.0.8.\nUsing glpi-agent --full only update the Last contact but not other information. It also generate a new row in table glpi_refusedequipments but doesn't seem to give any hint on why (Even with \"Extra-debug\" on)\n\nImporting .ocs file is working fine though, updating every field as well as Last inventory update.\n\nOriginal response date: 2026-07-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4892285679, "author": "tmartincpp", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24613#issuecomment-4892285679", "createdAt": "2026-07-06T11:32:46Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "Remy Blair I'm not sure it's exactly the same issue.\n\nIn my case inventory data seems to be ingested (e.g. list of process is updated) and my glpi_refusedequipments SQL table stays empty.\n\nOriginal response date: 2026-07-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4892796777, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24613#issuecomment-4892796777", "createdAt": "2026-07-06T12:30:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24613, "url": "https://github.com/glpi-project/glpi/issues/24613", "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-19T09:03:34Z", "updatedAt": "2026-07-06T12:30:10Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Search display bug", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nIn the ticket search interface, when changing the filter field, the value dropdown sometimes fails to refresh its contents and continues to display options from the previously selected filter field.\nThis happens intermittently with various filter items, not just the Technician/Group pair. Sometimes the UI seems to cache or fail to refresh the correct filter list or display filter window in strange position.\n\nAffected page:\n/front/ticket.php\n\nReproduction steps:\n1. Go to \"Tickets\" and open the saved search or standard search filter form.\n2. Add or use an existing filter row. Select, for example, \"Assigned to Technician\" → \"is\".\n3. Observe the correct dropdown (list of technicians) appears.\n4. Change the first dropdown of the same filter row to a different entity, e.g., \"Assigned to Group\".\n5. Observe the dropdown that appears for selecting the value.\n\nEnvironment details:\nServer\n\nOperating system: Linux %%%%%%% 6.8.0-117-generic #​117-Ubuntu SMP PREEMPT_DYNAMIC Tue May 5 19:26:24 UTC 2026 x86_64\n\nPHP: 8.3.6 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, apache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, imap, intl, ldap, exif, memcache, mysqli, pdo_mysql, Phar, posix, pspell, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"60\" max_input_vars=\"1000\" memory_limit=\"1536M\" post_max_size=\"8M\" session.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\" upload_max_filesize=\"100M\"\n\nWeb server: Apache/2.4.58 (Ubuntu) (Apache/2.4.58 (Ubuntu) Server at %%%%%%% Port 443)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 YaBrowser/25.2.0.0 Safari/537.36\n\nDatabase:\n   \nServer Software: Ubuntu 24.04\n   \nServer Version: 10.11.14-MariaDB-0ubuntu0.24.04.1\n   \nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n   \nParameters: root@localhost/glpidb\n   \nHost info: Localhost via UNIX socket", "priority": "medium", "type": "support", "createdByEmail": "rowan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce. This looks like a javascript issue, check browser console output.\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4705328613, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24462#issuecomment-4705328613", "createdAt": "2026-06-15T06:57:18Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "It happens reliable for me when using nested filters. The consol log is empty.\n\n[Image omitted]\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4706766094, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24462#issuecomment-4706766094", "createdAt": "2026-06-15T10:05:07Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot reproduce the issue either, even copying the nested filters used.\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4707254756, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24462#issuecomment-4707254756", "createdAt": "2026-06-15T11:06:21Z" } }, { "userEmail": "logan.blair@peppermint.local", "text": "one thing that may make this easier to pin down is a short interaction receipt from the exact filter-row change, since this sounds like stale async/dropdown state rather than just the final wrong option list.\n\nwhat i’d try to capture in one pass:\n\n- browser name/version and whether extensions are disabled\n- exact filter row state before changing the first dropdown\n- the request(s) fired when switching Technician → Group or another failing pair, including status and response shape\n- console output with verbose logging enabled, even if the normal console is empty\n- DOM state of the value dropdown before and after the stale list appears\n- whether it only happens after using saved searches / nested filters / repeated quick changes\n\nfor this kind of intermittent search UI bug, the useful artifact is less another screenshot of the stale dropdown and more the path + request timing + first stale DOM state. that usually gives maintainers a cleaner handle than “cannot reproduce.”\n\nOriginal response date: 2026-07-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4864772700, "author": "DwayneSamuels", "anonymizedAuthorEmail": "logan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24462#issuecomment-4864772700", "createdAt": "2026-07-02T10:34:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24462, "url": "https://github.com/glpi-project/glpi/issues/24462", "author": "Maximjke", "anonymizedAuthorEmail": "rowan.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-03T12:02:53Z", "updatedAt": "2026-07-02T10:34:46Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Mail receiver creates new requester in Root entity as non-recursive Self-Service, causing first ticket creation to fail in child entities", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.6\n\nIssue description:\nHello,\n\nI am testing GLPI in a multi-entity environment and found a behavior that caused several issues when creating tickets by e-mail for new requesters.\n\nContext:\nWe use a multi-entity structure like this:\n\nRoot entity\n└── INCIFRA\n    ├── Client A\n    ├── Client B\n    └── Client C\n\nEach client has its own entity.\n\nThe goal is:\n\n* tickets received by e-mail should be assigned to the correct client entity;\n* the requester should be preserved correctly;\n* new requesters should be created automatically;\n* users should not need to be manually pre-created before sending their first ticket.\n\nExpected behavior:\nWhen a new requester sends an e-mail and the mail receiver creates the user automatically, GLPI should allow the first ticket to be created in the entity selected by the mail receiver rules.\n\nExpected flow:\n\n1. A new requester sends an e-mail.\n2. GLPI creates the requester user.\n3. Mail receiver rules assign the ticket to the correct child entity.\n4. The ticket is created in that entity.\n5. The requester is correctly associated with the ticket.\n\nExample:\n\nSender: [email redacted]\nTicket rule result: Root entity > INCIFRA > Client A\nExpected ticket entity: Root entity > INCIFRA > Client A\nExpected requester: [email redacted]\n\nObserved behavior:\nWhen the sender does not already exist as a GLPI user, GLPI creates the user automatically with the following authorization:\n\nRoot entity / Self-Service / non-recursive / dynamic\n\nIn the database this appears as:\n\n* entities_id = 0\n* profiles_id = 1\n* is_recursive = 0\n* is_dynamic = 1\n\nThen the mail receiver rule correctly tries to create the ticket in a child entity, for example:\n\nRoot entity > INCIFRA > Client A\n\nHowever, ticket creation fails because the newly created requester only has a non-recursive Self-Service authorization in Root entity and therefore has no authorization in the child entity.\n\nIf I manually change the user authorization to recursive, or manually add authorization in the target child entity, the ticket creation works correctly.\n\nTests performed:\nI tested the following:\n\n1. Mail receiver rule assigns the ticket to Root entity.\n\n * Result: ticket is created successfully.\n\n2. Mail receiver rule assigns the ticket to Root entity > INCIFRA > Client A.\n\n * Result: ticket is not created when the requester is new and only has Root non-recursive authorization.\n\n3. Manually creating a ticket inside Root entity > INCIFRA > Client A.\n\n * Result: works correctly.\n\n4. Manually adding authorization to the user:\n Root entity > INCIFRA > Client A / Self-Service / non-recursive\n\n * Result: subsequent e-mails from that requester create tickets correctly in the child entity.\n\n5. Using “Apply again the rules for assigning authorizations” on the user.\n\n * Result: the authorization rules are applied correctly afterwards.\n * Problem: this is too late for the first ticket, which already failed.\n\n6. Enabling anonymous ticket creation.\n\n * Result: the first ticket is created in the correct entity.\n * Problem: the ticket is created without the requester properly associated as an actor. This is not acceptable operationally, because technicians would need to manually associate the requester on first contact.\n\n7. Entity advanced field “Email domains identifying the entity”.\n\n * Tested with domain syntax without @, for example gmail.com.\n * It did not solve the issue of the requester being initially created in Root entity with non-recursive Self-Service authorization.\n\nWhy this is problematic:\nIn a real helpdesk environment, many customers send tickets from many different e-mail addresses. These users are often not known in advance.\n\nThe current behavior means that the first e-mail from a new requester may fail if the ticket is routed to a child entity.\n\nThe only native alternatives we found were not ideal:\n\n* pre-create every possible requester manually;\n* allow anonymous tickets, but then the first ticket does not have a proper requester actor;\n* manually reapply authorization rules after user creation;\n* give broad recursive permissions manually;\n* use custom automation.\n\nFor an e-mail-only helpdesk workflow, the expected behavior would be that the first ticket from a new requester can be created correctly in the entity selected by the mail receiver rule.\n\nWorkaround used:\nAs a temporary workaround in our test environment, we created a database trigger to force automatically created Root/Self-Service/dynamic authorizations to be recursive.\n\nTrigger:\n\nAfter this workaround:\n\n* the new requester is created as Root entity / Self-Service / recursive / dynamic;\n* the mail receiver rule can create the ticket in the correct child entity;\n* the requester is correctly associated with the ticket;\n* the first e-mail from a new requester works.\n\nThis is only a workaround and not ideal, because it modifies behavior at the database level.\n\nSuggested improvement:\nPossible solutions could be:\n\n1. Apply authorization assignment rules immediately after creating a requester from the mail receiver, before trying to create the ticket.\n2. Add a mail receiver option to create new requesters with recursive authorization.\n3. Add a mail receiver option to create new requesters in the entity selected by the mail receiver rule.\n4. Allow the ticket creation process to create or update the requester authorization before validating ticket creation in the target entity.\n5. Improve documentation to explain this limitation and the expected configuration for multi-entity mail receivers.\n\nDesired behavior:\nA possible correct flow would be:\n\n1. E-mail arrives from an unknown requester.\n2. GLPI creates the requester user.\n3. GLPI applies authorization assignment rules, or grants authorization compatible with the target entity.\n4. GLPI applies the mail\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please test with latest stable release\n\nOriginal response date: 2026-06-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4738919061, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24598#issuecomment-4738919061", "createdAt": "2026-06-18T07:03:52Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Please test with latest stable release\n\nI tested again on GLPI 11.0.7 with a clean scenario and without the database trigger workaround.\n\nThe issue is still reproducible.\n\nTest conditions:\n- GLPI upgraded to 11.0.7\n- database trigger workaround removed\n- anonymous ticket creation disabled\n- sender did not exist as a GLPI user\n- mail receiver rule routes the ticket to a child entity: Root entity > INCIFRA > ARIANI\n- authorization assignment rule exists and works when manually reapplied\n\nActual result:\n- GLPI creates the new requester user as Root entity / Self-Service / non-recursive / dynamic\n- the authorization assignment rule is not applied before ticket creation\n- the ticket is not created in the child entity\n\nIf I manually apply “Apply again the rules for assigning authorizations” on the created user, the authorization rule works. If I use the database trigger workaround to make the Root/Self-Service authorization recursive at insert time, the ticket is created correctly.\n\nSo the behavior is unchanged in 11.0.7.\n\nOriginal response date: 2026-06-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4739419159, "author": "andreiIncifra", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24598#issuecomment-4739419159", "createdAt": "2026-06-18T07:54:10Z" } }, { "userEmail": "noel.blair@peppermint.local", "text": "Another user experiencing this exact same issue.\nIn our setup, we have multiple departments setup as sub-Entities of the root (IT, HR, Accounting, etc...)\n\nOur assignment rules are setup to add self-service users as Recursive users in the Root entity.\n\nWe're using SSO authentication w/ Microsoft, but most new tickets are coming from inbound emails.\n\nAn additional issue we've run into around this:\nWhen a technician working with only permissions in their sub-entity may open a new ticket & need to create a new user. When they create the user, that user is created with Self-Service Profile within the Entity being worked in by the technician. Later, if that new user sends an email that lands in a different sub-entity, the email will be rejects because they do not have permissions.\n\nWe would ideally like to see the Auth Assignment Rules applied on new user creation regardless of how the users are created.\n\nOriginal response date: 2026-06-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4790319410, "author": "thomassmithpchasorg", "anonymizedAuthorEmail": "noel.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24598#issuecomment-4790319410", "createdAt": "2026-06-24T14:28:07Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Another user experiencing this exact same issue. In our setup, we have multiple departments setup as sub-Entities of the root (IT, HR, Accounting, etc...)\n\nOur assignment rules are setup to add self-service users as Recursive users in the Root entity.\n\nWe're using SSO authentication w/ Microsoft, but most new tickets are coming from inbound emails.\n\nAn additional issue we've run into around this: When a technician working with only permissions in their sub-entity may open a new ticket & need to create a new user. When they create the user, that user is created with Self-Service Profile within the Entity being worked in by the technician. Later, if that new user sends an email that lands in a different sub-entity, the email will be rejects because they do not have permissions.\n\nWe would ideally like to see the Auth Assignment Rules applied on new user creation regardless of how the users are created.\n\nLet's wait and see if we get any response from the developers.\n\nOriginal response date: 2026-06-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4799449863, "author": "andreiIncifra", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24598#issuecomment-4799449863", "createdAt": "2026-06-25T12:55:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24598, "url": "https://github.com/glpi-project/glpi/issues/24598", "author": "andreiIncifra", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-18T07:00:40Z", "updatedAt": "2026-06-25T12:55:49Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "A null date field causes an error in a custom asset ([...]Failed to parse time string (null) at position 0 (n)[...])", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nIn a custom asset, a \"null\" date field triggers a \"Null invalide\" error.\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. Create a custom asset with nullable date fields.\n2. Add data with empty date fields.\n3. Edit the asset list by adding a column for the date fields.\n4. The error will appear.\n\nExample :\n\n[Image omitted]\n\nAdditional context:\nI reproduced the bug in a clean GLPI 11 instance as well.", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "How are you making the fields nullable? This isn't a feature of the field creator.\n\nOriginal response date: 2026-04-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4290793900, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23977#issuecomment-4290793900", "createdAt": "2026-04-21T18:12:59Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Hi,\nThere is a checkbox to make a field mandatory or not; I simply leave it unchecked to make the field nullable.\n\n[Image omitted]\n\nOriginal response date: 2026-04-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4295009204, "author": "Aruileen85", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23977#issuecomment-4295009204", "createdAt": "2026-04-22T09:15:16Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Hello,\n\nI'm also having the same problem.\n\nHere are my error logs:\n\nglpi.ERROR: * Caught DateMalformedStringException: Failed to parse time string (null) at position 0 (n): The timezone could not be found in the database\n Backtrace :\n ./src/Html.php:157\n ./src/Html.php:157 DateTime->construct()\n ./src/Glpi/Search/Provider/SQLProvider.php:6710 Html::convDate()\n ./src/Glpi/Search/Provider/SQLProvider.php:5360 Glpi\\Search\\Provider\\SQLProvider::giveItem()\n ./src/Glpi/Search/SearchEngine.php:678 Glpi\\Search\\Provider\\SQLProvider::constructData()\n ./src/Glpi/Search/SearchEngine.php:693 Glpi\\Search\\SearchEngine::getData()\n ./src/Glpi/Search/SearchEngine.php:650 Glpi\\Search\\SearchEngine::showOutput()\n : Glpi\\Search\\SearchEngine::show()\n ...Application/View/Extension/PhpExtension.php:105 call_user_func_array()\n ...ates/2a/2ae321a82e7bdc72fe092b53dae2c511.php:55 Glpi\\Application\\View\\Extension\\PhpExtension->call()\n ./vendor/twig/twig/src/Template.php:402 TwigTemplate_674fe7b54092fadbc34de61995e6c9a7->doDisplay()\n ./vendor/twig/twig/src/Template.php:358 Twig\\Template->yield()\n ./vendor/twig/twig/src/Template.php:373 Twig\\Template->display()\n ./vendor/twig/twig/src/TemplateWrapper.php:51 Twig\\Template->render()\n .../Glpi/Application/View/TemplateRenderer.php:170 Twig\\TemplateWrapper->render()\n ./src/Glpi/Controller/AbstractController.php:68 Glpi\\Application\\View\\TemplateRenderer->render()\n ./src/Glpi/Controller/GenericListController.php:51 Glpi\\Controller\\AbstractController->render()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\GenericListController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:208 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:71 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\n[Image omitted]\n\nWhen I create a new resource in a custom asset that has non-mandatory, therefore empty, date fields, it defaults to \"null\".\n\nI am on version 10.0.7 (in UAT) and I still have the same problem.\n\nI am available to answer any questions you may have.\n\nThanks.\n\nOriginal response date: 2026-05-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4418991729, "author": "Yann843", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23977#issuecomment-4418991729", "createdAt": "2026-05-11T08:52:39Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Hi! Do you have any news about my ticket regarding this bug fix?\n\nOriginal response date: 2026-06-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4786421230, "author": "Aruileen85", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23977#issuecomment-4786421230", "createdAt": "2026-06-24T06:15:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23977, "url": "https://github.com/glpi-project/glpi/issues/23977", "author": "Aruileen85", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": null, "createdAt": "2026-04-21T13:19:19Z", "updatedAt": "2026-06-24T06:15:33Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI 11 Webhook sending html encoded output instead of JSON", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.7\n\nIssue description:\nI'm trying to set up a discord notification for new tickets opened by someone not in a group, but the JSON that I have confirmed to be working by sending the generated output of the preview function with curl gets a 400 response in glpi.\nWhen I look at the message queue and try to send it manually, I can see that it is html encoded and not valid JSON.\nI don't know how to tell glpi not to encode it as html, I have tried adding\n\nand it seems to be interpreted as it is not part of the output, but there's still no change in behaviour\nI have also tested the default payload and it behaves the same way.\nI've also tried setting a Content-Type application/json header to see if it did anything, it didn't.\n\nhere's the generated custom payload\n\nhere's the generated default payload\n\nReproduction steps:\n1. Make a new webhook and set it as active\n2. Set the url to a discord webhook\n3. Set itemtype to assistance - ticket, and event to New\n4. Leave the payload as default and save\n5. Create a new ticket\n6. Go to Setup -> Webhooks -> Message Queue\n7. Check the generated JSON", "priority": "medium", "type": "support", "createdByEmail": "remy.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "robin.blair@peppermint.local", "text": "Bonjour,\nJe rencontre le même problème. Quelqu'un pourrait nous assister ?\n\nOriginal response date: 2026-06-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4613243515, "author": "SANSY-KABA", "anonymizedAuthorEmail": "robin.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24254#issuecomment-4613243515", "createdAt": "2026-06-03T14:10:08Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "What does the data look like directly in the glpi_queuedwebhooks table? Is it encoded or normal?\n\nOriginal response date: 2026-06-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4737102228, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24254#issuecomment-4737102228", "createdAt": "2026-06-18T01:46:32Z" } }, { "userEmail": "remy.bennett@peppermint.local", "text": "Pasted below is the result of querying glpi_queuedwebhooks for id 8 which corresponds to one of the tests I did before submitting this issue\n\nOriginal response date: 2026-06-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4742268583, "author": "arb103", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24254#issuecomment-4742268583", "createdAt": "2026-06-18T13:12:16Z" } }, { "userEmail": "riley.blair@peppermint.local", "text": "I'm facing the exact same formatting issue with webhooks during my MS Teams notification tests.\n\nOriginal response date: 2026-06-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4749543271, "author": "Tony710", "anonymizedAuthorEmail": "riley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24254#issuecomment-4749543271", "createdAt": "2026-06-19T07:45:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24254, "url": "https://github.com/glpi-project/glpi/issues/24254", "author": "arb103", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-19T12:48:45Z", "updatedAt": "2026-06-23T08:20:53Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Cannot expand menu on mobile phone", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen you click here :\n\n[Image omitted]\n\nThis activate this parameter :\n$user = new User();\n$success = $user->update(\n [\n 'id' => Session::getLoginUserID(),\n 'fold_menu' => (bool) $_SESSION['glpifold_menu'] ? 0 : 1,\n ]\n);\n\nAnd With this parameter, when you use mobile phone you cannot expand menu :\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.blair@peppermint.local", "text": "I have the exact same issue (version 11.0.6)\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4007048040, "author": "slytara", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23124#issuecomment-4007048040", "createdAt": "2026-03-05T19:00:48Z" } }, { "userEmail": "morgan.blair@peppermint.local", "text": "I also have the same issue with 11.0.6.\n\nOriginal response date: 2026-04-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4334833420, "author": "errror", "anonymizedAuthorEmail": "morgan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23124#issuecomment-4334833420", "createdAt": "2026-04-28T11:33:43Z" } }, { "userEmail": "sage.bennett@peppermint.local", "text": "The same problem occurs in versions 11.0.6 and 11.0.7.\n\nOriginal response date: 2026-05-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4440891089, "author": "RobertoMarcelino", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23124#issuecomment-4440891089", "createdAt": "2026-05-13T12:19:53Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "I confirm the issue at 11.0.7\n\nOriginal response date: 2026-06-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4755150911, "author": "ftoledo", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23124#issuecomment-4755150911", "createdAt": "2026-06-19T22:27:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23124, "url": "https://github.com/glpi-project/glpi/issues/23124", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-16T08:50:15Z", "updatedAt": "2026-06-19T22:27:51Z", "closedAt": null } }, { "title": "Skip \"Invalid Cookie Data\" notification, redirect to login page w/fields instead", "detail": "Contribution description:\nIn the latest current release of GLPI; If a browser's cookie expires, etc. (I'm sure there are criteria for this) GLPI presents an error to the user:\n\n[Image omitted]\n\nThis message is confusing to the layperson. Is it broken? What do cookies mean? Why is my login 'empty'?\nInstead; Can we simply redirect this switch/case to the normal login page and utilize some kind of low-impact notification? Perhaps a notification/pop-up/warning that says \"Login Expired\" or something to that effect?\n\nAs it sits; Redirecting the user to a unique page, that is removed from the login process, with an \"Error\" just confuses the average user and obfuscates the UI-flow with a box that has to be clicked, when there are no alternative actions to be taken.", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This intermediate page exists solely because the login page is currently protected by CSRF tokens with short lifespans stored in a PHP session. If the user's session times out and they get sent directly back to the login page, and let the page sit about 24 minutes (default php session expiration. Depends on garbage cleanup config too.) the page would give them an even more vague error when they tried logging in again.\n\nThe message itself could possibly be improved though.\n\nOriginal response date: 2026-05-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4567533178, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24383#issuecomment-4567533178", "createdAt": "2026-05-28T19:32:42Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Taylor Adler Cleaning up the language would be a good start. I am not looking to make something more convoluted but my skillset is definitely not in session security. However, it feels like there has to be a cleaner way to handle this bit of security. Thanks for the response!\n\nOriginal response date: 2026-05-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4570435712, "author": "misterjmw", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24383#issuecomment-4570435712", "createdAt": "2026-05-29T04:06:46Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "There is. (Haven't reviewed it myself but should be coming with GLPI 12).\n\nOriginal response date: 2026-05-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4573038064, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24383#issuecomment-4573038064", "createdAt": "2026-05-29T09:14:06Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Delightful. So; How can I help? Or does the open ticket of \"Can we change this?\" do anything?\n\nOriginal response date: 2026-05-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4579704116, "author": "misterjmw", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24383#issuecomment-4579704116", "createdAt": "2026-05-29T20:43:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24383, "url": "https://github.com/glpi-project/glpi/issues/24383", "author": "misterjmw", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-28T19:22:29Z", "updatedAt": "2026-05-29T20:43:25Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "PHP warnings about PendingReasonCron.php : PendingReasonCron::cronPendingreason_autobump_autosolve", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWe have warning in php-errors.log and don't know if we may have a configuration deficit.\nHelp would be appreciated.\n\nReproduction steps:\nIt seems to be standard behaviour of the cron job cronPendingreason_autobump_autosolve,\nthe warning is created every time the job runs, manually or sheduled.", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I guess you have a pending reason defined with automatic resolution but no solution template selected. It remains a bug though because GLPI should not allow this to happen. Same with automatic followups without a followup template. Same with being able to configure \"Follow-ups before automatic resolution\" when no automatic followups are configured.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4139267489, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23190#issuecomment-4139267489", "createdAt": "2026-03-27T00:47:16Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Hello!\n\ni am not shure about the correct config,\nin the definition of our pending reason \"wait for response\",\nwe have \"automatic follow-up disabled\"\nand \"automatic resolution disabled\",\nbecause we want to configure the follow-up intervals and auto-resolution on/off separately per ticket (?),\nas we have \"Pending per default\" set to NO.\n\nWe have the templates defined in this pending reason.\n\nAlas, we don't see to which ticket/pending reason the LOG entry belongs to..\n\nHow can we check something specific, e.g. per ticket what exactly is happening ?\n\nOriginal response date: 2026-05-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4543162266, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23190#issuecomment-4543162266", "createdAt": "2026-05-26T10:03:23Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Ehm..\nHow do i check for tickets with entry auto-solve-after-something\nand a pending reason that has _no_ automatic resolution template set ??\n\nThis gave me the AI bot:\n\nSELECT\n t.id AS ticket_id,\n t.name AS ticket_title,\n t.status,\n\n pri.pendingreasons_id,\n pr.name AS pending_reason,\n\n pri.followups_before_resolution,\n pri.bump_count,\n pri.followup_frequency,\n\n pr.solutiontemplates_id\n\nFROM glpi_pendingreasons_items pri\n\nINNER JOIN glpi_tickets t\n ON t.id = pri.items_id\n AND pri.itemtype = 'Ticket'\n\nINNER JOIN glpi_pendingreasons pr\n ON pr.id = pri.pendingreasons_id\n\nWHERE t.status = 4\n AND pri.followups_before_resolution > 0\n AND (\n pr.solutiontemplates_id IS NULL\n OR pr.solutiontemplates_id = 0\n )\n\nORDER BY t.id;\n\n... and is now clean for our system.\n\nOriginal response date: 2026-05-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4543449025, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23190#issuecomment-4543449025", "createdAt": "2026-05-26T10:33:03Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "We did see the notifications in the tickets,\nnow we get the emails :-)\nThe notification Automatic reminder - ID 91 was not set to \"active\" :-/\n\nOriginal response date: 2026-05-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4543929814, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23190#issuecomment-4543929814", "createdAt": "2026-05-26T11:59:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23190, "url": "https://github.com/glpi-project/glpi/issues/23190", "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-02-20T08:50:36Z", "updatedAt": "2026-05-26T11:59:13Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "V11.0.7 AllAsset search fail SQL error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen performing a search of AllAssets (Assets->Global) using the default 'Items seen' / contains search criteria, the 'An unexpected error occurred' is displayed. The resulting error is attached in a text file.\n\nGLPI-v1107AllAssetSearchSQLFail.txt\n\nPHP-Errors glpi.CRITICAL.txt\n\nAffected page:\n\nReproduction steps:\n1. Assets menu\n2. Select Global\n3. Accept default 'Items Seen' search criteria, enter any text as search term.\n4. SQL related error occurs with an 'unexpected error occurred' message.\n\nEnvironment details:\nRunning on IIS: System config attached:\n\nGLPI-11.0.7PrdConfig.txt\n\nAdditional context:\nInterestingly this issue is occurring on my Prod instance of GLPI, but not on my DEV system, both systems have same plugins (inc version) and are same release. I am at a loss as to why the same search succeeds on DEV, but not on Prod.", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Issue seems to be with the appliance name search option/column.\n\nOriginal response date: 2026-05-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4487129498, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24249#issuecomment-4487129498", "createdAt": "2026-05-19T11:07:16Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "As a workaround/short-term solution, you should remove the column from your display.\n\nIf it is in your personal view:\n1. Click the user dropdown menu in the top-right\n2. Select My settings\n3. Go to the Personal View tab\n4. Find \"Asset\" and select it\n5. Remove the column from the list\n\nIf it is a global view:\n1. Go to Setup > General > Search result display tab\n2. Find \"Asset\" and select it\n3. Remove the column from the list\n\nOriginal response date: 2026-05-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4487155670, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24249#issuecomment-4487155670", "createdAt": "2026-05-19T11:11:14Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "Thankyou Taylor Adler . I have worked around the issue by removing 'Appliances-Name' from your suggestion:\n\nIf it is a global view:\n\nGo to Setup > General > Search result display tab\nFind \"Asset\" and select it\nRemove the column from the list\n\nOriginal response date: 2026-05-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4492845848, "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24249#issuecomment-4492845848", "createdAt": "2026-05-19T23:05:58Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "[Solved]\n\nOriginal response date: 2026-05-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4493161177, "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24249#issuecomment-4493161177", "createdAt": "2026-05-19T23:49:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24249, "url": "https://github.com/glpi-project/glpi/issues/24249", "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-19T07:11:28Z", "updatedAt": "2026-05-19T23:49:49Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Graphql HLAPI 11.0.7 Ticket", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nGraphql solves the ticket_item not exposed directly in v2.x but the team and teammember does not work (error 500).", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Hello. Could you explain a little more? What specific queries are you trying that give the 500 error?\n\nOriginal response date: 2026-05-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4408966395, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24178#issuecomment-4408966395", "createdAt": "2026-05-08T18:40:01Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "My mistake. It's not an error 500. Just an internal error.\nDoing a 'simple' query on a ticket to retrieve items, status and team.\nThe query fails for status and team at sublevel, works at cost and item\n\nOn May 8, 2026 6:40:22 PM UTC, Curtis Conard *@*.*> wrote:\ncconard96 left a comment (glpi-project/glpi#24178)\nHello. Could you explain a little more? What specific queries are you trying that give the 500 error?\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4411503273, "author": "acopernic", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24178#issuecomment-4411503273", "createdAt": "2026-05-09T04:53:26Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The team issues sounds like the same one I logged in #20743.\n\nFor status, I still need to see a minimal reproducible example of a query.\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4412368558, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24178#issuecomment-4412368558", "createdAt": "2026-05-09T11:03:39Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "Maybe same problem. Not expert.\n\n$schemas['TeamMember'] = [\n 'type' => Doc\\Schema::TYPE_OBJECT,\n 'properties' => [\n 'itemtype' => [\n 'type' => Doc\\Schema::TYPE_STRING,\n ],\n 'items_id' => [\n 'type' => Doc\\Schema::TYPE_INTEGER,\n ],\n 'role' => [\n 'type' => Doc\\Schema::TYPE_STRING,\n ],\n ],\n];\n\nOn May 9, 2026 11:04:01 AM UTC, Curtis Conard *@*.*> wrote:\ncconard96 left a comment (glpi-project/glpi#24178)\nThe team issues sounds like the same one I logged in #20743.\nFor status, I still need to see a minimal reproducible example of a query.\n--\nReply to this email directly or view it on GitHub:\n\nYou are receiving this because you authored the thread.\nMessage ID: *@*.*>\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4412799762, "author": "acopernic", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24178#issuecomment-4412799762", "createdAt": "2026-05-09T14:54:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24178, "url": "https://github.com/glpi-project/glpi/issues/24178", "author": "acopernic", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2026-05-08T11:31:22Z", "updatedAt": "2026-05-09T14:54:12Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Dashboard Error Simplified Interface", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAfter accessing the Helpdesk/Dashboard page, the interface fails to load some components. The browser console shows a critical error regarding the resolution of JavaScript modules and a TypeError in the Dashboard resizing logic.\n\nAffected page:\n\nReproduction steps:\nSteps to reproduce the behavior:\n\nGo to 'Helpdesk' or 'Home/Dashboard'\n\nOpen the Browser Console (F12)\n\nSee errors: Failed to resolve module specifier and Cannot read properties of undefined (reading 'text').\n\nEnvironment details:\nEnvironment:\n\nGLPI version: 11.0.6\n\nBrowser: Chrome\n\nServer OS: Linux\n\nPHP version: 8.3", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "GLPI 11.0.7 is not released yet. Please confirm if you are using a nightly release or if you are in fact on 11.0.6 or an earlier version.\n\nOriginal response date: 2026-03-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4100643293, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23567#issuecomment-4100643293", "createdAt": "2026-03-20T19:53:40Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "Sorry, I made the correction for GLPI 11.0.6.\n\nOriginal response date: 2026-03-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4100663242, "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23567#issuecomment-4100663242", "createdAt": "2026-03-20T19:58:10Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "No problem.\n\nThe problem with the module specifier should be fixed by which will be part of 11.0.7.\n\nThe dashboard error seems like it may be a separate issue. Which cards are added on this dashboard?\n\nOriginal response date: 2026-03-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4100725978, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23567#issuecomment-4100725978", "createdAt": "2026-03-20T20:12:39Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "Actually, there were no cards created for the Self Service profile; what existed were the native cards from the old FormCreator plugin. I updated to version 11.0.6 and ran the command to migrate the forms to the core, and currently the old plugin has even been uninstalled. However, when switching to the Self Service profile, this buggy dashboard loads.\n\nnative cards from the old FormCreator plugin:\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-03-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4100942255, "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23567#issuecomment-4100942255", "createdAt": "2026-03-20T21:03:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23567, "url": "https://github.com/glpi-project/glpi/issues/23567", "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-20T19:26:13Z", "updatedAt": "2026-03-20T21:06:25Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "REST API v2: POST/PATCH do not persist request body fields (Ticket requester/team, User, etc.)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nSummary:\nWhen using the REST API v2 (e.g. api.php/Assistance/Ticket, api.php/User/...), POST and PATCH requests return 200/201 but many fields sent in the request body are not persisted. This affects at least:\n- Ticket: _users_id_requester, _actors, team (requester/team never saved; response always has team: []).\n- User: PATCH on user fields (e.g. email) does not update the record.\n- Other resources may be affected (see related forum topics).\n\nEnvironment:\n- GLPI: [11.0.6]\n- API: High-Level REST API v2.2 (OpenAPI doc at api.php/v2.2/doc)\n- Auth: Bearer token (OAuth2)\n\nExpected behavior:\n- POST/PATCH should persist the fields documented in the OpenAPI schema (e.g. requester/team for Ticket).\n- Either the API should accept the schema format (e.g. team array) and map it internally, or the doc should state the actual input format (e.g. _users_id_requester, _actors).\n\nRelated:\n- Forum: \"API does not use the values\" (no response)\n- Forum: \"GLPI11 api.php/v2.1/Assistance/Problem\" (resolution_date not saved)\n\nReproduction steps:\n1. POST – Create a ticket with requester using the format from the API doc v2.2:\n - Body (no input wrapper): \"name\", \"content\", \"team\": [{ \"role\": \"requester\", \"id\": 8, \"name\": \"user.name\", ... }] (same structure as the API returns in GET).\n - Result: 201/200, ticket is created, but GET returns team: [].\n2. POST – Same ticket with internal format: body includes _users_id_requester: 8 (and optionally users_id_recipient: 8).\n - Result: ticket created, but GET still shows team: [] (and user_recipient may be the API user, not 8).\n3. PATCH – Update existing ticket with requester using doc format:\n - Body: \"team\": [{ \"role\": \"requester\", \"id\": 8, \"name\": \"...\", \"href\": \"/front/user.form.php?id=8\" }].\n - Result: 200 OK, but GET still returns team: [].\n4. PATCH – Same ticket with internal format: body _users_id_requester: 8 or _actors: { \"requester\": [{ \"itemtype\": \"User\", \"items_id\": 8 }] }.\n - Result: 200 OK, but GET still shows team: [].\n5. PATCH a User (e.g. email) → 200 OK, but the value is not updated in the database.\n\nEnvironment details:\nDocker swarm + traefik.", "priority": "medium", "type": "support", "createdByEmail": "remy.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "- _users_id_requester, _actors - Not supported. These are internal fields and the v2 API doesn't directly rely on internal logic.\n- team - Not supported. There are two different linked item types:\n - Links directly saved in the parent item's table where it is just a simply field. These can be updated using syntax like {\"location\": 1} or {\"location\": {\"id\": 1}}.\n - Linked that are stored with a unique link type. These usually have separate endpoints for adding/removing the links like /Assistance/Ticket/{id}/TeamMember.\n- PATCH on user fields (e.g. email) does not update the record - See previous point. Emails are stored in a separate place. Some email endpoints exist for your own user like /Administration/User/Me/Email but I am aware it needs expanded to work for other users.\n\nI didn't respond immediately because the image was broken when I saw the post and the text was vague. I remember saving it in a tab to respond later to get clarification but lost the tab at some point.\n\nShould be fixed in the upcoming v2.3 of the API.\n\nOriginal response date: 2026-03-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4062882961, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23485#issuecomment-4062882961", "createdAt": "2026-03-15T12:20:02Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "If you haven't seen it yet, there is a Swagger UI that lists every endpoint and the related schemas at \"/api.php/v2/doc\" on your GLPI.\n\nAlso, improving how linked data is created/updated from main items is on my list of things to investigate after the remaining missing endpoints, schemas, and properties get added.\n\nOriginal response date: 2026-03-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4062887978, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23485#issuecomment-4062887978", "createdAt": "2026-03-15T12:23:28Z" } }, { "userEmail": "remy.bennett@peppermint.local", "text": "First of all, thank you very much for the quick response. I saw the documentation, but since the example within the /assistance/ticket post includes team information that can be passed, I thought it could be done there. Now I understand the logic of the process and I will adjust it here.\n\nThank you again.\n\nOriginal response date: 2026-03-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4062894744, "author": "dersonbsb2022", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23485#issuecomment-4062894744", "createdAt": "2026-03-15T12:27:56Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "but since the example within the /assistance/ticket post includes team information that can be passed, I thought it could be done there. Now I understand the logic of the process and I will adjust it here.\n\nI don't remember if there was a reason I didn't mark the property readOnly or if it was simply because I did the ticket endpoints/schema in the initial High-Level API before I really started taking advantage of the full OpenAPI schema spec.\n\nIn some cases, I know I don't have much control over it. I can make a property readOnly or writeOnly but I cannot make it change depending on the context. For example, if a field can be set during an item creation but then cannot be changed during an update. The only solution I found is to have separate schemas for it and that isn't as clean as I would like.\n\nOriginal response date: 2026-03-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4062913394, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23485#issuecomment-4062913394", "createdAt": "2026-03-15T12:40:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23485, "url": "https://github.com/glpi-project/glpi/issues/23485", "author": "dersonbsb2022", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2026-03-15T12:10:15Z", "updatedAt": "2026-03-15T12:40:50Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Statuses of items dropdown: children tab not showing correct values", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nIf a \"Status of items\" entry has children, the tab \"Statuses of items\" (2nd tab in editor) shows a list of these children and their visibility values:\n\n[Image omitted]\n\nHowever, these values are not correct, as they can not be determined. On opening of this tab a warning for each child column is added to php-errors.log (a single one is included below at \"Relevant log output\"), pointing to this line:\n\nI think the code tries to read the visibility values from the child item dataset (DB table \"glpi_states\"), while they are stored in a different database table (\"glpi_dropdownvisibilities\").\n\nAffected page:\nfront/state.form.php?id=\n\nReproduction steps:\n1. Go to Setup -> Dropdowns -> Common -> Statuses of items\n2. Click \"+ Add\" to add a parent item\n3. (name item, click \"+ Add\" to save and end up in its item editor)\n4. Add child item in 2nd tab \"Statuses of items\" of parent (or create new as in 2. and set \"As child of\" to parent from 3.)\n5. Return to parent item and open tab \"Statuses of items\" (as seen in screenshot), the child item should be listed at the bottom\n6. Default visibility is \"Yes\" on all columns (e.g. for all shown item classes) of child item, but this tab shows them as \"No\"\n7. Additionally, a warning for each processed child visibility column is added to php-errors.log", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "micah.blair@peppermint.local", "text": "Taylor Adler Can I work on this?\n\nOriginal response date: 2026-02-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3940858010, "author": "anirban6996", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23162#issuecomment-3940858010", "createdAt": "2026-02-22T12:29:50Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Taylor Adler Can I work on this?\n\nSure 👍\n\nOriginal response date: 2026-02-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3940869288, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23162#issuecomment-3940869288", "createdAt": "2026-02-22T12:36:35Z" } }, { "userEmail": "micah.blair@peppermint.local", "text": "[Image omitted]\nI have successfully replicated the bug I will be looking into it now...\n\nOriginal response date: 2026-02-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3941229667, "author": "anirban6996", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23162#issuecomment-3941229667", "createdAt": "2026-02-22T15:38:53Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "the issue is on 11.0.5 too\n\nthe file contains the correction\n\n[Image omitted]\nbut\n\n[Image omitted]\nfor information, $field['name'] contains is_visible_computer, and of course is not found in $data[]\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3991977402, "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23162#issuecomment-3991977402", "createdAt": "2026-03-03T15:56:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23162, "url": "https://github.com/glpi-project/glpi/issues/23162", "author": "sl077", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-18T11:48:46Z", "updatedAt": "2026-03-12T02:04:50Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "RuleRight work on single rule but not globally", "detail": "Affected version:\n11.0.1 DOCKER version (tested with 11.0.2 also)\n\nIssue description:\nThe bug is in the rules definition for users in root entity.\nWhen I test a rule with anything that concern LDAP attributes, it works within the rule:\n[Image omitted]\nbut not in the global test (test rule engine):\n[Image omitted]\n(second test criteria is an authentication type on LDAP)\nof course the test criteria is exactly the same in the two tests.\n\nIs there something to add that I'm missing for the rules to work ?\nIs this a bug in the engine?\n\nReproduction steps:\n1. start a fresh docker install\n2. connect to an AD with ldap authentication\n3. create rule with LDAP criteria Memberof / DistinguishedName / ...\n4. test rule in engine\n\nEnvironment details:\ntwo docker GLPI services in a Ubuntu server host. the two have the same behavior.", "priority": "medium", "type": "support", "createdByEmail": "cameron.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try if you reproduce with latest stable release (11.0.2)\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491412998, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21813#issuecomment-3491412998", "createdAt": "2025-11-05T14:07:50Z" } }, { "userEmail": "cameron.blair@peppermint.local", "text": "Please try if you reproduce with latest stable release (11.0.2)\n\nthe behavior is exactly the same with 11.0.2. tested a minute ago.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491477624, "author": "Minikea", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21813#issuecomment-3491477624", "createdAt": "2025-11-05T14:19:42Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "I have the same issue, on version 11.0.5.\n\nI can't make my rules match, only the default \"Root\" rule is applied (according to rules engine test).\n\nI have the following 4 rules:\n\n1. Société\n * Criteria (Logical operator = AND):\n * LDAP directory = acme_company\n * Actions:\n * Entity = Root>acme_company\n * Profiles = Self-Service\n * Default entity = Root>acme_company\n * Recursive = Yes\n\n2. Groupe administrateurs\n * Criteria (Logical operator = AND):\n * LDAP directory = acme_company\n * Group = admins\n * Actions:\n * Profiles = Super-Admin\n * Recursive = Yes\n * Entity = Root\n\n3. Groupe techniciens\n * Criteria (Logical operator = AND):\n * LDAP directory = acme_company\n * Group = technicians\n * Actions:\n * Profiles = Technician\n * Recursive = Yes\n * Entity = Root>acme_company\n4. Root\n * Criteria (Logical operator = OR):\n * Authentication type = LDAP directory\n * Authentication type = Email server\n * Actions:\n * Profiles = Technician\n * Recursive = Yes\n * Entity = Root>acme_company\n\nIf I test the rules engine with the following criteria:\n\n* Authentication type = LDAP directory (\"Authentication on a LDAP directory\")\n* LDAP directory = acme_company\n* Group = admins\n\nI get the following result:\n\n* Société = No\n* Groupe administrateurs = No\n* Groupe techniciens = No\n* Root = Yes\n\nI tried to:\n\n* Remove the \"Authentication type = LDAP directory\" criteria in the tester: still won't match my rules (logically, \"Root\" isn't anymore)\n* Add the \"Authentication type = LDAP directory\" criteria in my rules no 1, 2 and 3: still won't match my rules\n\nBut If I test the rule no 1 (\"Société\") with the following criteria:\n\n* Authentication type = LDAP directory (\"Authentication on a LDAP directory\")\n* LDAP directory = acme_company\n\nI get the following result:\n\n* Validation = Yes\n* Entity = Root>acme_company\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4040255263, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21813#issuecomment-4040255263", "createdAt": "2026-03-11T15:56:56Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "I've analyzed both front/rule.test.php and front/rulesengine.test.php files, leading to the following business code:\n\n* src/Rule.php (and src/RuleRight.php)\n* src/RuleCollection.php (and src/RuleRightCollection.php),\n\nI've added some naive debug calls to Rule::showRulePreviewResultsForm() and RuleCollection::testAllRules():\n\nWhen directly testing the rule (here \"Société\", of ID 145), the POST data are:\n\nAnd my debug log file receives:\n\nWhen testing the engine (all rules), the POST data are:\n\nAnd my debug log file receives:\n\nWhat puzzled me was:\n\n1. In the single-rule test (the working test)\n * $input contains the criteria:\n\n * $params is empty.\n2. In the whole-engine test (the failing test):\n * $input lacks my \"LDAP_SERVER\" criteria:\n\n * $params looks just like the $input from the single-rule test:\n\n3. The _groups_id key created in $input by the RuleCollection::prepareInputDataForProcess() call in RuleCollection::testAllRules(). This is since 97a68213e6919208475ea9d7c5f0f1e03ab296e0 from #6794.\n\nWhat I did was swap $input and $params in Rule::process() call (in RuleCollection::testAllRules()):\n\nAnd then, it works: when testing all rules I get a match for my first \"Société\" rule (and also for the Root rule).\n\nI'm not saying this is the fix (as I did not tested it against all kind of criteria), but there is something there.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4042716976, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21813#issuecomment-4042716976", "createdAt": "2026-03-11T22:45:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21813, "url": "https://github.com/glpi-project/glpi/issues/21813", "author": "Minikea", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-11-05T14:01:19Z", "updatedAt": "2026-03-11T22:45:42Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Inventory fails because of rejected \"1970-01-01 01:00:00\" date in glpi_items_processes.started", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nThe inventory of my macOS (OS v15.6, Agent v1.16) fails to be accepted by the GLPI server (v11.0.5).\n\nIt seems the SQL server does not like a \"1970-01-01 01:00:00\" date.\n\nDiagnostic information:\nThis log line is from GLPI Agent's /var/log/glpi-agent.log log file but it contains an error returned by the server:\n\nReproduction steps:\n1. Install the agent v1.16\n2. Configure the agent\n3. Run the inventory with pkill -USR1 -f -P 1 glpi-agent\n\nAdditional context:\nI took a look at the inventory (using glpi-inventory --json): there is (only) one process with a \"1970-01-01 01:00:00\" start date: /sbin/launchd (PID 1).\n\nThere are 82 other processes from the past, all started at \"1976-04-01 02:00:00\": /usr/libexec/logd, /usr/sbin/systemstats --daemon, /System/Library/CoreServices/powerd.bundle/powerd, etc.\n\nI have other macOS 15.6 devices running the same GLPI Agent and targeting the same GLPI server without an issue, but none has processes with a 1970-*-* start date.", "priority": "medium", "type": "maintenance", "createdByEmail": "avery.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "avery.bennett@peppermint.local", "text": "Workaround: reboot the system so that all processes gets a recent (2026-*) start date.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3951150281, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23222#issuecomment-3951150281", "createdAt": "2026-02-24T11:44:24Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Even if inventory should probably not fail (not tested, iwll do later), that also seems an agent issue.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3951306007, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23222#issuecomment-3951306007", "createdAt": "2026-02-24T12:09:26Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "You think it should not generate \"1970\" dates?\n\nI'm not 100% sure but this specific computer might have never been rebooted when I got the issue.\n\nI kept the JSON inventory but did not checked /proc/1's files.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3951392776, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23222#issuecomment-3951392776", "createdAt": "2026-02-24T12:23:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "You think it should not generate \"1970\" dates?\n\nUnless it's not been rebooted since 1970; I would have expected something more accurate :)\nThis looks like a kind of \"default date\", no idea if it's expected or if there is something wrong.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3951631732, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23222#issuecomment-3951631732", "createdAt": "2026-02-24T13:02:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23222, "url": "https://github.com/glpi-project/glpi/issues/23222", "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [ "inventory" ], "state": "open", "stateReason": null, "createdAt": "2026-02-24T11:19:18Z", "updatedAt": "2026-02-24T13:02:17Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Gateway Timeout when transferring computers with linked software – issue still occurs", "detail": "Affected version:\nGLPI 12.0.0-dev\n\nIssue description:\nWhen transferring a computer and selecting the option to transfer its linked software together, the operation fails with a Gateway Timeout (504) error and the transfer is not completed.\n\nThis issue has already been reported in the past and was marked as closed, however the problem is still happening in production environments.\n\nBecause of this error, it is currently impossible to properly inventory machines together with their associated software, since any attempt to transfer both at the same time always results in a timeout.\n\nAdditionally, no error is logged in PHP or in the GLPI logs, which makes troubleshooting extremely difficult.\n\nThe only way to successfully transfer a computer to another entity is by disabling the option to transfer linked software. However, when doing this, the computer is moved without any of its related software, causing the loss of all software associations.", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "You should really not use v12 in a production environment; this is a development version.\nAlso, it can suffer some issues that do not exists in stable release.\n\nFirst, what existing issue are you talking about?\n\nTransfer process is very costly, and software management is complex; it would not be surprising this can cause issues. However, as far as I remember, last time someone reported a getaway timeout, it was due to a server configuration that can be changed or improved.\nSince you do not provide any information on your setup, it will be difficult for anyone to help.\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3749409350, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22666#issuecomment-3749409350", "createdAt": "2026-01-14T12:46:15Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "You should really not use v12 in a production environment; this is a development version. Also, it can suffer some issues that do not exists in stable release.\n\nFirst, what existing issue are you talking about?\n\nTransfer process is very costly, and software management is complex; it would not be surprising this can cause issues. However, as far as I remember, last time someone reported a getaway timeout, it was due to a server configuration that can be changed or improved. Since you do not provide any information on your setup, it will be difficult for anyone to help.\n\nI will forward the server information.\n\nI understand that there may be problems transferring machines, but even with a single machine there is a problem with the transfer.\n\nOperating system: Linux zbxglp01.justica.local 5.14.0-611.11.1.el9_7.x86_64 #​1 SMP PREEMPT_DYNAMIC Wed Dec 3 09:47:37 EST 2025\nx86_64\n\nPHP: 8.2.30 fpm-fcgi\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard,\ncgi-fcgi, bcmath, bz2, calendar, ctype, curl, dba, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, gmp, iconv, intl, ldap, exif,\nmysqlnd, PDO, Phar, posix, shmop, SimpleXML, snmp, soap, sockets, sodium, sqlite3, sqlsrv, sysvmsg, sysvsem, sysvshm, tokenizer,\nxml, xmlwriter, xsl, mysqli, pdo_dblib, PDO_Firebird, pdo_mysql, pdo_sqlite, pdo_sqlsrv, xmlreader, xmlrpc, zip, apcu, igbinary,\nimagick, msgpack, ssh2, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"9000\" max_input_vars=\"4000\" memory_limit=\"2048M\" post_max_size=\"256M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"256M\"\n\nWeb server: Apache/2.4.62 (AlmaLinux) OpenSSL/3.5.1 ()\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0\n\nDatabase:\n\nServer Software: Source distribution\n\nServer Version: 8.0.44\n\nServer SQL Mode: STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION\n\nParameters:\n\nHost info: 127.0.0.1 via TCP/IP\n\nRequirements:\nPHP version (8.2.30) is supported.PHP version (8.2.30) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexm\n\n[Content truncated.]\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3749796440, "author": "FelipeBasilio1991", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22666#issuecomment-3749796440", "createdAt": "2026-01-14T14:22:55Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "Hello, i got similar bug on GLPI v11.0.4 (since 11.0.1). When transferring computer with complete transfert to other entity (with linked software) i got php error like following :\n glpi.ERROR: * Caught RuntimeException: MySQL query error: Duplicate entry 'Computer-XXXX-XXXXX' for key 'glpi_items_softwareversions.unicity' (1062) in SQL query \"UPDATE glpi_items_softwareversions SET softwareversions_id = 'XXXXX' WHERE id = 'XXXXXXX'\".\n\nShould i open new issue for GLPI version 11.0.4 ?\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3784624305, "author": "Bigthibo", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22666#issuecomment-3784624305", "createdAt": "2026-01-22T14:13:25Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Emerson Blair,\nWhen an issue is different from the original post, it is preferable to open a new one, if only to make management and tracking easier.\n\nIn your case, this issue could be resolved by the following pull request:\n\nKind regards,\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3784636577, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22666#issuecomment-3784636577", "createdAt": "2026-01-22T14:17:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22666, "url": "https://github.com/glpi-project/glpi/issues/22666", "author": "FelipeBasilio1991", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-14T11:59:56Z", "updatedAt": "2026-01-22T14:24:05Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Error on oldest logs", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHi team,\nAfter upgrading GLPI to version 11.0.4, I’m unable to access the /front/log.php page.\n\n[Image omitted]\n\nThis screen contains logs that are important for our operations. Can you assist me with this issue? If I have to access other page to consult this logs please let me know\n\nAffected page:\n/front/log.php", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "As far as I know, this page isn't meant to exist and it shouldn't be linked anywhere. Historical data is not meant to be searchable due to performance and complexity issues. I think it only exists because there is no exclusion for it in the generic list controller.\n\nDo you remember which version it was working on?\n\nOriginal response date: 2025-12-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3657256246, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22373#issuecomment-3657256246", "createdAt": "2025-12-15T19:30:51Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "As Taylor Adler said, this page should not exists. There were no front/log.php in v10. Logs are available in dedicated tab on each object, there is no global search.\n\nOriginal response date: 2025-12-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3659032838, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22373#issuecomment-3659032838", "createdAt": "2025-12-16T06:28:16Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "IMO the bug here is that the GenericListController shouldn't work on every CommonDBTM itemtype without any exceptions. It is a low priority though because these bad list pages are not linked anywhere and the result is not different from if a user accessed them through the legacy API.\n\nAt least, these itemtypes should be excluded since they are not mean to be searched:\n- Log\n- Config\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696818512, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22373#issuecomment-3696818512", "createdAt": "2025-12-29T15:26:49Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I took a look a few weeks ago, but I've been lost in the way all of that works; and I've not been able to see where an exclusion list would be setted up.\n\nOriginal response date: 2026-01-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3710424104, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22373#issuecomment-3710424104", "createdAt": "2026-01-05T13:27:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22373, "url": "https://github.com/glpi-project/glpi/issues/22373", "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-15T19:10:28Z", "updatedAt": "2026-01-05T13:27:09Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Custom assets drag and drop", "detail": "Issue description:\nIt is impossible to add a new field in between two exisiting fields in a column.\n\nHere if you try to drag \"Test\" between \"Template name\" and \"Location\":\n\n[Image omitted]\n\nIt end up pushing \"Location\" to the left column instead:\n\n[Image omitted]\n\nThe issue is that the page use a single gridstack instance when it should probably have two dedicated instances (one per column).\n\nReported by out partner ITSM Factory.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The issue is that the page use a single gridstack instance when it should probably have two dedicated instances (one per column).\n\nProbably not so easy to support since you can configure any field to be \"full width\" and take up both columns.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3524466250, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21890#issuecomment-3524466250", "createdAt": "2025-11-13T00:16:36Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Indeed, two grids might not be a good solution with that in mind.\n\nNote that if I try on the gridstack demo I seem to be able to insert items into a column without issue.\n\nMaybe it is our implementation that is wrong then?\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3526063740, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21890#issuecomment-3526063740", "createdAt": "2025-11-13T07:33:05Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "It uses html5sortable, not gridstack. I don't recall the difference between them but for Kanban we wanted to use html5sortable to be close to the native drag-drop API so I used it here too.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3527186668, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21890#issuecomment-3527186668", "createdAt": "2025-11-13T10:50:18Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "IMO, I don't see this as a bug or a desired UX change. Ignoring special writing directions, people read naturally from left to right and line by line, not the full first column, back to the top, and down the next column. Thus, shifting items the way it does now seems logical.\nBy placing \"Test\" in the position of \"Location\", you move \"Location\" to the next natural reading position. This is also reinforced with the tab order left to right.\n\nI have some other concerns about form layout related to UX, but given the current layout I believe this to be the best.\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3697660974, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21890#issuecomment-3697660974", "createdAt": "2025-12-29T22:21:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21890, "url": "https://github.com/glpi-project/glpi/issues/21890", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2025-11-12T08:44:12Z", "updatedAt": "2025-12-29T22:21:11Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "GLPI connection problem", "detail": "Affected version:\n11.04\n\nIssue description:\nHere's my problem. My colleagues are having trouble connecting to GLPI, but I don't have this problem. Attached is a screenshot. They remain on this page even after deleting the entire URL and clicking on the link. The only solution is to switch to private browsing or delete cookies. Do you have any ideas? I have already reinstalled the server while keeping the database and files.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "finley.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "finley.bennett@peppermint.local", "text": "Update: My colleague tried leaving the “Remember me” box unchecked and did not encounter any errors. However, when he checked the box again, the same message reappeared.\nHere is my automatic identification configuration in Configuration > General.\nI have had this configuration since I first installed GLPI (two years ago). This has been the case since I updated to GLPI 11. Is this due to the migration or an HTTPS configuration issue?\n[Image omitted]\n\nOriginal response date: 2025-12-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3666147653, "author": "GamingRB", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22411#issuecomment-3666147653", "createdAt": "2025-12-17T16:26:30Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you provide GLPI logs? When an error occurs, there are usually usefull log lines written in them.\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3668663738, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22411#issuecomment-3668663738", "createdAt": "2025-12-18T06:52:37Z" } }, { "userEmail": "finley.bennett@peppermint.local", "text": "I tested it again with a colleague this morning, and here are the logs I got.\n\n[Image omitted]\n\nphp-errors.log\n\n(redacted - apache logs are not relevant)\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3670349985, "author": "GamingRB", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22411#issuecomment-3670349985", "createdAt": "2025-12-18T13:41:22Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "Hi. Check free disk size on server.\nAnd also check in GLPI DB table glpi_users if your loggin user (red line is hidding it) is here twice (as msg says).\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3671750838, "author": "jerry-ne", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22411#issuecomment-3671750838", "createdAt": "2025-12-18T18:54:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22411, "url": "https://github.com/glpi-project/glpi/issues/22411", "author": "GamingRB", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-17T15:35:57Z", "updatedAt": "2025-12-19T06:42:24Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Wrong network device port connection reporting", "detail": "Affected version:\n10.0.20\n\nIssue description:\nI was exploring port connection failure between TP-Link devices reported here: glpi-project/glpi-agent#1026\n\n1. First reporting problem:\n\nGLPI reports connected port for which we only know the remote MAC address with the same port designation than the local port it is connected to. I mean if a connection to a remote mac is reported in XML to port eth0, GLPI will show remote port as \"eth0\" where we know nothing of the real remote port:\n\n[Image omitted]\n\nHere we can see for example \"Vlan-interface1\" interface connected to \"Vlan-interface1 > Vlan-interface1\n00:0d:48:35:77:03\n\"\nwhere in the XML we only have:\n\nThis is the same for \"gigabitEthernet 1/0/5\", \"gigabitEthernet 1/0/6\", \"gigabitEthernet 1/0/7\", \"gigabitEthernet 1/0/8\" and so on...\n\nOn the screenshot, I removed few not relevant columns to make it as clear as possible.\n\nHere is the XML generated with nightly build glpi-agent applied on walk provided by @loginone33 on linked and fixed glpi-agent issue: SG2218P-2.0.xml\n\n2. Second reporting problem:\n\nNo connection appears for LLDP connections, only the connected status is set. For example, for port \"gigabitEthernet 1/0/2\", we have this in XML, but the column remains empty:\n\nHere I think we could expect GLPI to create an unmanaged \"eth0\" port for \"EAP225-Outdoor\" system.\n\nReproduction steps:\n1. Import manually provided xml: SG2218P-2.0.xml\n2. Check network ports table of the imported device\n3. Compare to xml nodes data from inventory\n\nAdditional context:\nAlso checked in GLPI 10.0.20, issue is the same.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "There are 2 issues reported, that does not seems related; it probably would be better to open 2 distinct github issues.\n\nAnyway, regarding \"First reporting problem\": if I understand well, we should just expect no connexion at all?\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3370122897, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21285#issuecomment-3370122897", "createdAt": "2025-10-06T06:42:38Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "(maybe #21286 is about the second issue)\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3370129449, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21285#issuecomment-3370129449", "createdAt": "2025-10-06T06:43:20Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Behavior is the same with plugin in glpi 9.5\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3370420232, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21285#issuecomment-3370420232", "createdAt": "2025-10-06T08:13:20Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi Skyler Adler\n\nfor the first problem, IMHO, if we are able to associate the given MAC to only one known network port, I don't see why we won't be able to make the link. For example, if it's the MAC of a PC, a printer or a phone, we should make the link.\n\nBut if it's the MAC shared by all port of a router, we can't know which port is connected or only an inventory if the remote router could give the data permitting to know which port is really connected. In that case, also we should probably not disconnect the port if it is still connected thanks to a remote router inventory.\n\nAlso note we also can have a list of MAC address reported, for example for a vlan port or a wifi one. In that case, we should of course keep it reported as a HUB.\n\nIndeed, this issue is more about what we see in port list: the second case is surely linked to how we handle LLDP connection and #21286 is clearly related. But here I just wanted to report the port list is wrongly reported in the 2 cases. Feel free of course to split the second case to another issue or define it part of #21286.\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3370913504, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21285#issuecomment-3370913504", "createdAt": "2025-10-06T10:22:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21285, "url": "https://github.com/glpi-project/glpi/issues/21285", "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-03T15:55:00Z", "updatedAt": "2025-11-26T13:46:24Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "(Non) Screen reader bug", "detail": "Affected version:\n10.0.18\n\nIssue description:\nGreetings community,\n\nOver the last two weeks, we have been experiencing a situation with an employee who is having some difficulties with the accessibility features in GLPI 10.0.18.\n\nThis employee has a visual impairment and uses a screen reader (NVDA) to work.\n\nMost features work well, but he is having issues when the screen reader cannot recognize the category menu once it is selected.\n\nInstead, the screen reader reports it as a blank field.\n\nWe suspect this may be caused by the field’s behavior when clicked, since the ability to search a category in the menu seems to make it appear blank.\n\nWe are working with all of our knowledge to try to help him, but we would really appreciate suggestions from the community.\n\nDoes the community have any ideas on how to make the screen reader properly read this menu?\n\nPerhaps this could also be a good improvement to consider for future releases, to help others as well.\n\nWe count on the community’s collaboration to help this person.\n\nBest regards,\n\nAndre Antunes\n\nReproduction steps:\nUsing NVDA open a new ticket\nCheck if when choosing categories NVDA says something like \"blank field\" or something like this.", "priority": "medium", "type": "support", "createdByEmail": "logan.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "finley.bennett@peppermint.local", "text": "Hello GLPI Community and GLPI Developers,\n\nI could confirm the same the new version of GLPI 11.x version has the same accessibility issues as it has before. I think nothing changed.\nI am going to open a separated issue with my listed issues and suggestions.\n\nThat would be really good to have aria labels and title for the form and buttons elements as this is the key aspect for all of the well-known screen readers like: JAWS, NVDA, Narrator, Voice over, etc..\n\nI was trying to find the HTML buttons and form elements in your repository, but it is really hard to find it if I am not really familier with programing in PHP or not familiar with the structure of the files and the codes.\n\nI could really suggest to use the Accessibility Insight for Web Extension for validate the basic screen reader issues or accessibility issues before the new version is out.\n\nPlease let me know if you need anything from my side I am also a screen reader user as that person colleague of the reporter.\n\nThanks for your support,\nregards,\ngabor\n\nPlease let me know\n\nOriginal response date: 2025-11-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3567979929, "author": "citygabor", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20828#issuecomment-3567979929", "createdAt": "2025-11-23T13:54:52Z" } }, { "userEmail": "logan.bennett@peppermint.local", "text": "Hi there.\n\nDoes we have some new feature about creen readers?\nI made a test on v11 but had no success.\n\nIt makes me happy if we have some answer.\n\nThanks for all.\n\nOriginal response date: 2026-07-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 5003078638, "author": "andreantunes2602", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20828#issuecomment-5003078638", "createdAt": "2026-07-17T12:04:42Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nWe began to work a little on accessibility; v11 will unfortunately never be compliant.\nSome more work has been done on the main branch; but that's far to be done. 3rd party libraries are another problem (there is a PR currently in review to update select2 that has make some changes on their side, I have no real idea if it will be OK or not :/).\n\nOriginal response date: 2026-07-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 5003354389, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20828#issuecomment-5003354389", "createdAt": "2026-07-17T12:37:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20828, "url": "https://github.com/glpi-project/glpi/issues/20828", "author": "andreantunes2602", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-08-28T19:19:45Z", "updatedAt": "2026-07-17T12:37:47Z", "closedAt": null } }, { "title": "[HLAPI] Need a way to filter ticket actors", "detail": "Issue description:\nCurrently, the API groups all requesters, observers, and assigned technicians into a \"team\" property. Unfortunately, I had done this using the mapping functionality which means the data is built in GLPI after the SQL query is finished. This means filters do not work here and this is likely to be a big requirement to users.\n\nA user asked about this on the forum already:\n\nThe roadblock here is a design decision to cleanly define the filtering or find a way to specify joins on a subquery.\n\nThe current property definition for the team.\n\nThe TeamMember schema:\n\nEven if we split this into \"requesters\", \"observers\" and \"assigned\" we would still need to combine data from the three linking tables for users, groups and suppliers.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "elliot.blair@peppermint.local", "text": "Hi Taylor Adler ,\n\nI am also very interested in this feature. My goal is to filter tickets by assigned technicians :\n\nteam.name=in=(tech1,tech2);team.role==assigned)\n\nThanks\n\nOriginal response date: 2026-04-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4266575808, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20743#issuecomment-4266575808", "createdAt": "2026-04-17T08:42:25Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Hi Taylor Adler,\n\nDo you have any news regarding this feature ?\n\nThx\n\nOriginal response date: 2026-06-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4621079279, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20743#issuecomment-4621079279", "createdAt": "2026-06-04T10:02:09Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Not really, sorry.\n\nThe HLAPI is in a better position now to support this since the addition of the support for OpenAPI's anyOf syntax in and the GraphQL changes from v2.3 that made it use proper resolvers instead of directly using the Search code used by the REST side of the API.\n\nI haven't revisited this subject since those changes. There is other ongoing work that I need to finish up first.\n\nOriginal response date: 2026-06-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4621511876, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20743#issuecomment-4621511876", "createdAt": "2026-06-04T10:59:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20743, "url": "https://github.com/glpi-project/glpi/issues/20743", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "api", "help wanted" ], "state": "open", "stateReason": null, "createdAt": "2025-08-21T15:50:17Z", "updatedAt": "2026-06-04T10:59:48Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Replace laminas/mail", "detail": "Issue description:\naka\n\nPackage is abandoned:\n\nWe will abandon laminas-mail and laminas-mime. We will add recommendations to the three other projects in the README, and link to symfony/mailer for the \"abandoned\" property of the project.\n\nImportant, the replacement shouldn't be a wrapper above the php-imap system extension (itself being also a wrapper above a deprecated C library)\nUnless, the extension evolve (not the case at this point)\n\nRequirements:\n- imap without the c library and the php-imap extension (unbundled since php8.4)\n- Xoauth2 support\n- proxy support\n- (optionnal) jmap support\n\nCandidates:\n\n- webklex/php-imap\n- horde/Imap_Client\n- javanile/php-imap2\n- zetacomponents/Mail\n\nMore candidates (2026-01):\n- DirectoryTree/ImapEngine\n\nPossible consequences:\n\n- drop of pop support -> probably acceptable at this point, usage should be scarse", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "DirectoryTree/ImapEngine seems promising, but as far as I can see, it miss support for oauth2.\nzetacomponents/Mail and horde/Imap_Client also miss oauth2 support.\n\nOriginal response date: 2026-01-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3804408761, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/18411#issuecomment-3804408761", "createdAt": "2026-01-27T10:37:38Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "For ImapEngine:\n\nOriginal response date: 2026-01-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3804412514, "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/18411#issuecomment-3804412514", "createdAt": "2026-01-27T10:38:30Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Oh! That's great, then 👍\n\nOriginal response date: 2026-01-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3804760410, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/18411#issuecomment-3804760410", "createdAt": "2026-01-27T11:52:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 18411, "url": "https://github.com/glpi-project/glpi/issues/18411", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-11-28T14:00:34Z", "updatedAt": "2026-02-04T07:13:13Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI 10 : CalDAV All-Day Events Timezone Issue", "detail": "Affected version:\n10.0.19\n\nIssue description:\nAll-day events synchronized from Outlook via CalDAV are incorrectly shifted by timezone offset in GLPI, causing them to start at 2:00 AM and extend into the next day instead of covering the intended full day (00:00-23:59).\nEnvironment\n\nGLPI Version: 10\nTimezone: Europe/Brussels (UTC+1/+2)\nClient: Microsoft Outlook (CalDAV sync)\n\nSteps to Reproduce\n\nCreate an all-day event in Microsoft Outlook (e.g., \"Meeting\" for January 15, 2025)\nSynchronize calendar via CalDAV with GLPI\nCheck the imported event in GLPI calendar view\n\nExpected Behavior\n\nAll-day event should display from 00:00 to 23:59 on the specified date\nEvent should remain within the boundaries of a single day\nEvent should maintain its \"all-day\" properties\n\nActual Behavior\n\nAll-day event starts at 02:00 AM (timezone offset applied)\nEvent duration extends 24 hours from 02:00 AM, spilling into the next day\nEvent no longer behaves as an all-day event", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "avery.blair@peppermint.local", "text": "Any update ? I've tested in 11.0.2 and the bug is still here.\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3496212112, "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20414#issuecomment-3496212112", "createdAt": "2025-11-06T09:44:51Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Hello, is there a problem ?\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3811610025, "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20414#issuecomment-3811610025", "createdAt": "2026-01-28T14:24:10Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Hello, tested with 11.08, always the same problem...\n\nOriginal response date: 2026-07-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4916232461, "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20414#issuecomment-4916232461", "createdAt": "2026-07-08T15:07:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20414, "url": "https://github.com/glpi-project/glpi/issues/20414", "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-07-25T14:16:44Z", "updatedAt": "2026-07-08T15:07:18Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "pb category knowledge base", "detail": "Issue description:\nWhen creating categories for the knowledge base, they do not appear under the \"Browse\" tab.\n\n[Image omitted]\n\nIf I add a category using the bulk action, the category is not added.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Do those categories have any articles in them?\n\nOriginal response date: 2026-07-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4904316733, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24799#issuecomment-4904316733", "createdAt": "2026-07-07T13:26:53Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I'm trying, but it's not working. I used the bulk action to do it. But I think that's the problem we were talking about in the meeting with Taylor Adler this afternoon.\n\n[Image omitted]\n\nOriginal response date: 2026-07-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4904566041, "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24799#issuecomment-4904566041", "createdAt": "2026-07-07T13:53:07Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Just so you know, if I run a test using a database import, I can see the categories that were already present in the old instance. However, if I create the categories myself, I don't see them (even when adding an item via the bulk action).\n\nOriginal response date: 2026-07-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4914979425, "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24799#issuecomment-4914979425", "createdAt": "2026-07-08T12:53:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24799, "url": "https://github.com/glpi-project/glpi/issues/24799", "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "beta / rc" ], "state": "open", "stateReason": null, "createdAt": "2026-07-07T08:43:22Z", "updatedAt": "2026-07-08T12:53:58Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "View glpi_forms_answerssets", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nPreviouly, in formcreator, it was possible to see the answers input in form : it was seen as an item under ticket or change, and there was a form to see them.\nNow we must see glpi_forms_answerssets and a mix of answers fields using glpi_forms_questions.\n\nUnless error, I didn't see such a possibility : is it scheduled ?\n\nMore :\ni think in glpi_items_tickets, in items we could see the id of answersset and not the \"form template\" id ?", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "riley.blair@peppermint.local", "text": "In previous versions of GLPI, form responses were accessible through Administration → Forms → Answers, which is essential for auditing and tracking the usage of the module.\n\nIn version 11.x, this functionality has disappeared.\nCurrently, in ticket view with source: form, only the responses of forms that create tickets are displayed.\nForms that do not generate tickets have their responses unavailable, making it impossible to access historical data or audit the module.\n\nThis behavior appears to be a bug, as it prevents access to responses from standalone forms, which were always accessible in earlier versions.\n\nOriginal response date: 2026-04-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4345361836, "author": "msodrep", "anonymizedAuthorEmail": "riley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23784#issuecomment-4345361836", "createdAt": "2026-04-29T15:55:46Z" } }, { "userEmail": "quinn.blair@peppermint.local", "text": "We are experiencing the same issue. In order to comply with GDPR requirements, we need to delete the form responses, as they contain sensitive data.\n\nOriginal response date: 2026-06-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4600183271, "author": "pzbdkp", "anonymizedAuthorEmail": "quinn.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23784#issuecomment-4600183271", "createdAt": "2026-06-02T08:21:52Z" } }, { "userEmail": "robin.blair@peppermint.local", "text": "We are experiencing the same problem as well. This indeed means answers that do not match a ticket target in a form (which previously could be at least seen on the \"Answers\" page), can now only be seen by browsing the database and comparing creation dates between the ticket and answer tables.\n\nThis means that any answer that didn't have a target cannot be assigned to a ticket through the UI, but has to either be manually assigned in the DB or deleted (in the DB) and resubmitted by the user.\n\nOriginal response date: 2026-06-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4840973775, "author": "CiaranHagen", "anonymizedAuthorEmail": "robin.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23784#issuecomment-4840973775", "createdAt": "2026-06-30T07:33:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23784, "url": "https://github.com/glpi-project/glpi/issues/23784", "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-07T12:45:18Z", "updatedAt": "2026-06-30T07:33:10Z", "closedAt": null } }, { "title": "Menu and Widget Display Problem with a Limited Profile", "detail": "Affected version:\n11.0.1\n\nIssue description:\nI am trying to set up a limited user profile whose role is to:\n\nView their own tickets,\nView tickets from sub-entities to which they have access,\nCreate and update tickets.\nTo do this, I configured a profile with a standard interface (because the simplified interface does not allow enabling \"view all tickets,\" which is essential for accessing tickets from sub-entities).\n\nProfile Configuration\nOnly the following rights are enabled in the Support section:\n\nView my tickets\nUpdate\nCreate\nView all tickets\nView new tickets\nAll other rights (in Support, Configuration, Tools, etc.) are disabled.\n\nObserved Behavior\n\nWhen I log in with a user having this profile:\n\nOn the homepage, I see the following widgets:\n\nReminders\nPersonal View\nGroup View\nGlobal View\nRSS Feed\nAll\n\nAccess to this page is, however, denied if you click on it.\n\nExpected Behavior\n\nA user with such a restricted profile should not see:\n\nThe \"Reminders,\" \"Group View,\" \"Global View,\" \"RSS Feed,\" etc. widgets.\nThe Configuration > Dropdowns menu, since they do not have the associated rights.\n\nIn the 'Support' menu, the \"service catalog\" also appears, even though it has been disabled at the entity level.\n\nQuestion / Hypothesis\n\nI don't know if this is:\n\na display bug (menus visible without associated rights), or a current limitation of GLPI for profiles with a standard interface and partial rights.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "The user should be able to always see its own reminders and rss feeds. I guess the rights check must be reviewed a bit.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611215211, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21773#issuecomment-3611215211", "createdAt": "2025-12-04T09:58:38Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The Configuration > Dropdowns menu, since they do not have the associated rights.\n\nThis specific point has already been fixed.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611219434, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21773#issuecomment-3611219434", "createdAt": "2025-12-04T09:59:21Z" } }, { "userEmail": "micah.blair@peppermint.local", "text": "GLPI 11.0.8\nThe RSS feed continues to appear even though it is disabled. Any updates on this?\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-06-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4833136476, "author": "willysaurio", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21773#issuecomment-4833136476", "createdAt": "2026-06-29T13:29:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21773, "url": "https://github.com/glpi-project/glpi/issues/21773", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2025-11-03T21:31:30Z", "updatedAt": "2026-06-29T13:29:09Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Email Notification don't send attachment", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nSince the update, the attachment is not being sent with the notification either to users with external email addresses or to users with internal profiles.\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The setting \"Add documents into notifications sent to anonymous users\" was added in 10.0.25 but when the commit was merged into the 11.0 branch, the migration that added the default config value was not moved to the 11.0.7 migration. The screenshot shows the setting for non-anonymous users which does not apply here, while the relevant field is on the same form.\n\nIt should work properly if you save the settings though as it would add the missing value.\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4412354227, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24182#issuecomment-4412354227", "createdAt": "2026-05-09T10:56:09Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi,\n\nEven after saving the setting in the UI as suggested, the issue still persisted.\n\nIt was only resolved by manually injecting the missing configuration value directly into the database, since the key was not present in the \"glpi_configs\" table.\n\nThe following SQL query fixed the problem:\n\nINSERT INTO glpi_configs (context, name, value)\nVALUES ('core', 'attach_documents_to_notifications_for_anonymous', '1');\n\nAfter this change, the warning disappeared and attachments started being correctly included in notifications.\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4412436530, "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24182#issuecomment-4412436530", "createdAt": "2026-05-09T11:42:07Z" } }, { "userEmail": "dakota.blair@peppermint.local", "text": "I am also having this bug. I have to constantly go into the database and run the SQL command. Please can this be fixed.\n\nOriginal response date: 2026-06-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4831409028, "author": "MNSPJack", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24182#issuecomment-4831409028", "createdAt": "2026-06-29T10:23:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24182, "url": "https://github.com/glpi-project/glpi/issues/24182", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-09T10:08:03Z", "updatedAt": "2026-06-29T10:23:58Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Facing weird issue after today's 28th JUNE 2026 (sunday), GLPI maintenance/upgrade for 6 hours.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n2.2.3\n\nAffected page:\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please review your bug report and provide the information requested in the bug report template including your GLPI Setup information. Also, review the GLPI version provided as there is no such version.\n\nOriginal response date: 2026-06-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4826281927, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24693#issuecomment-4826281927", "createdAt": "2026-06-28T13:44:08Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "glpi version 10.0.26\n\nOriginal response date: 2026-06-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4826318156, "author": "bchandra369", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24693#issuecomment-4826318156", "createdAt": "2026-06-28T13:58:34Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "Hello,\n\nI have reviewed the bug report requirements. Because my user account has a Technician profile, the \"Setup > General > System\" tab is entirely restricted and hidden from my menu layout, preventing me from downloading the automated system dump.\n\nPlease find the manual GLPI Setup and environment information requested below:\n\n### GLPI setup information\n- GLPI Core Version: [Insert your version number here, e.g., 10.0.12]\n- Active Interface: Standard ITIL Technician layout\n- Permission State: Admin logs are inaccessible due to lack of Super-Admin access for me, I have only technician access.\n\nOriginal response date: 2026-06-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4826330483, "author": "bchandra369", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24693#issuecomment-4826330483", "createdAt": "2026-06-28T14:03:24Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24693, "url": "https://github.com/glpi-project/glpi/issues/24693", "author": "bchandra369", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-28T13:09:45Z", "updatedAt": "2026-06-28T14:03:24Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Form cloning fails with error, leaving incomplete copy", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nAfter upgrading to version 11.0.7, we found a bug when trying to clone a form. When we select a form, click on \"Actions\", choose the \"Clone\" option, and enter the number of copies, GLPI starts the cloning process but suddenly stops with the error \"An unexpected error occurred.\" However, when we go back to the forms list, the copy is there but incomplete.\n\nReproduction steps:\n1. Select a form.\n2. Click on Actions.\n3. Select the Clone option.\n4. Enter the number of copies and confirm.", "priority": "medium", "type": "support", "createdByEmail": "emerson.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please include your relevant log file entries. You specified the folder was empty, but it looks like you have your log location changed to \"var/glpi/logs\" so please make sure you are checking there instead of the default \"files/_log\" location inside your GLPI.\n\nOriginal response date: 2026-06-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4692117096, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24551#issuecomment-4692117096", "createdAt": "2026-06-12T14:19:09Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "It's my first time opening an issue so i don't know if this is the right info that you are asking. The php-errors.log:\n\n[2026-06-12 14:24:48] glpi.CRITICAL: * Uncaught PHP Exception InvalidArgumentException: \"Invalid extra data for question\" at Question.php line 417\n Backtrace :\n ./src/Glpi/Form/Question.php:417\n ./src/Glpi/Form/Question.php:278 Glpi\\Form\\Question->prepareInput()\n ./src/CommonDBTM.php:1339 Glpi\\Form\\Question->prepareInputForAdd()\n ./src/Glpi/Features/Clonable.php:293 CommonDBTM->add()\n ./src/Glpi/Features/Clonable.php:151 CommonDBConnexity->clone()\n ./src/Glpi/Features/Clonable.php:299 CommonDBConnexity->cloneRelations()\n ./src/Glpi/Features/Clonable.php:151 CommonDBConnexity->clone()\n ./src/Glpi/Features/Clonable.php:299 Glpi\\Form\\Form->cloneRelations()\n ./src/Glpi/Features/Clonable.php:229 Glpi\\Form\\Form->clone()\n ./src/MassiveAction.php:1657 Glpi\\Form\\Form->cloneMultiple()\n ./src/MassiveAction.php:1348 MassiveAction::processMassiveActionsForOneItemtype()\n ./src/MassiveAction.php:1326 MassiveAction->processForSeveralItemtypes()\n ./front/massiveaction.php:63 MassiveAction->process()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:208 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:71 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\n[2026-06-12 14:24:48] glpi.WARNING: * Warning: Cannot modify header information - headers already sent at Html.php line 1046\n Backtrace :\n ./src/Html.php:1046\n ./src/Html.php:1643 Html::includeHeader()\n : Html::header()\n ...Application/View/Extension/PhpExtension.php:105 call_user_func_array()\n ...ates/14/144296670cba4d69f43d568ccf0077a2.php:45 Glpi\\Application\\View\\Extension\\PhpExtension->call()\n ./vendor/twig/twig/src/Template.php:402 TwigTemplate_58885a336dfb202edaa9c2400aa6f1df->doDisplay()\n ./vendor/twig/twig/src/Template.php:358 Twig\\Template->yield()\n ./vendor/twig/twig/src/Template.php:373 Twig\\Template->display()\n ./vendor/twig/twig/src/TemplateWrapper.php:51 Twig\\Template->render()\n .../Glpi/Application/View/TemplateRenderer.php:170 Twig\\TemplateWrapper->render()\n ./src/Glpi/Controller/AbstractController.php:68 Glpi\\Application\\View\\TemplateRenderer->render()\n ./src/Glpi/Controller/ErrorController.php:177 G\n\n[Content truncated.]\n\nOriginal response date: 2026-06-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4692509316, "author": "murilo-hyper", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24551#issuecomment-4692509316", "createdAt": "2026-06-12T15:07:23Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "It's my first time opening an issue so i don't know if this is the right info that you are asking.\n\nYes. Thank you :)\n\nOriginal response date: 2026-06-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4694761175, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24551#issuecomment-4694761175", "createdAt": "2026-06-12T19:51:01Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24551, "url": "https://github.com/glpi-project/glpi/issues/24551", "author": "murilo-hyper", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-12T14:14:33Z", "updatedAt": "2026-06-12T19:51:10Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Bug: SQL query error (Unknown column) on Search Engine when filtering by interconnected Custom Assets dropdown", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.6 Copyright (C)\n\nReproduction steps:\n1. Go to Assets > Custom Assets (using GLPI 11.0.6).\n2. Create two Custom Asset types that interconnect with each other through an object dropdown field (e.g., a system pointing to a server).\n3. Go to the search view of the main asset.\n4. Add a global search criterion/filter to search by the name of the interconnected asset (e.g., filtering the server name like %VPS12%).\n5. Click on \"Search\".\n\nExpected behavior:\nThe search engine should successfully perform a LEFT JOIN between the custom fields table and the assets table, returning the filtered list of assets.\n\nObserved behavior:\nThe page crashes with a Twig template rendering exception due to a MySQL query error (1054: Unknown column).\n\nThe GLPI search engine generates an inconsistent table alias. In the LEFT JOIN clause, it aliases the table as glpi_assets_assets_custom_fields_[hash], but in the WHERE clause, it mistakenly looks for glpi_assets_assets_[hash].name (omitting the _custom_fields part from the alias).\n\nGLPI setup and logs:\nGLPI Version: 11.0.6\nPHP Version: 8.5.5 apache2handler\nDatabase: [e.g., MariaDB 10.11 / MySQL 8.0]\n\nFull Debug Stack Trace:\nshell", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "I tested the same scenario on a separate GLPI test environment and upgraded it to GLPI 11.0.7.\n\nUnfortunately, the bug is still present in the latest version.\n\nThe error is still related to the SQL alias generated for a custom asset field of type DropdownType pointing to another custom asset.\n\nIn the query, GLPI creates this JOIN alias:\n\nLEFT JOIN glpi_assets_assets AS glpi_assets_assets_custom_fields_ca32cd85115e6cc5e9d06a75047968b7\n\nbut in the WHERE clause it tries to use a different alias that does not exist:\n\nglpi_assets_assets_ca32cd85115e6cc5e9d06a75047968b7.name LIKE '%VPS01%'\n\nSo MySQL returns:\n\nUnknown column 'glpi_assets_assets_ca32cd85115e6cc5e9d06a75047968b7.name' in 'where clause'\n\nIn my production environment the affected custom field ID was 31. In the test environment it is 17, but the behavior is the same.\n\nSo the issue is reproducible on GLPI 11.0.7 as well.\n\nOriginal response date: 2026-06-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4671631886, "author": "andreiIncifra", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24521#issuecomment-4671631886", "createdAt": "2026-06-10T15:03:30Z" } }, { "userEmail": "kai.blair@peppermint.local", "text": "We have also received the reported error in GLPI 11.0.6. Since the function is essential for us and cumbersome for users due to the saved search filters, I have been looking for a solution.\n\nThe function getWhereCriteria() in file SQLProvider.php should probably take care of the _custom_field_-prefix for joinparams, if linkfield is set. The part\n\ncould be changed to\n\nIn issue #22771 (SQL Error 1054 when searching linked Custom Assets) the same error was reported.\n\nOriginal response date: 2026-06-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4677957040, "author": "hpk-lentia", "anonymizedAuthorEmail": "kai.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24521#issuecomment-4677957040", "createdAt": "2026-06-11T06:52:20Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "We have also received the reported error in GLPI 11.0.6. Since the function is essential for us and cumbersome for users due to the saved search filters, I have been looking for a solution.\n\nThe function getWhereCriteria() in file SQLProvider.php should probably take care of the _custom_field_-prefix for joinparams, if linkfield is set. The part\n\ncould be changed to\n\nIn issue #22771 (SQL Error 1054 when searching linked Custom Assets) the same error was reported.\n\nThank you very much for your help.\n\nI tested the proposed change in a separate GLPI test environment where I was able to reproduce the same issue, and I can confirm that it fixes the search error in my scenario.\n\nAfter applying the patch, the search no longer fails when filtering a custom asset that has a DropdownType custom field pointing to another custom asset.\n\nHowever, I am a bit concerned about applying this kind of core modification directly in production, because I am not sure if it could introduce side effects in other search scenarios, filters, exports, or future GLPI updates.\n\nFrom my test, the fix seems correct for this specific issue, but I would feel more comfortable if this could be reviewed and eventually included as an official fix in GLPI.\n\nThanks again for pointing me in the right direction.\n\nOriginal response date: 2026-06-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4681323089, "author": "andreiIncifra", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24521#issuecomment-4681323089", "createdAt": "2026-06-11T13:55:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24521, "url": "https://github.com/glpi-project/glpi/issues/24521", "author": "andreiIncifra", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-10T08:12:15Z", "updatedAt": "2026-06-11T13:55:51Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Getting \"An unexpected error occurred\" when adding a Simcard item to an issue from \"My devices\"", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI can't add a Simcard to a Ticket, I get a \"An unexpected error occurred\".\n\nAffected page:\n/front/ticket.form.php?id=XXX\n\nReproduction steps:\n1. With the following data:\n * An user \"jdoe\" of ID 7 as follow (glpi_users SQL table):\n\n | id | name | locations_id | use_mode | list_limit | is_active | auths_id | authtype | is_deleted | profiles_id | entities_id | usertitles_id | usercategories_id | is_ids_visible | priority_1 | priority_2 | priority_3 | priority_4 | priority_5 | priority_6 | followup_private | task_private | default_requesttypes_id | registration_number | set_default_tech | set_followup_tech | set_solution_tech | display_count_on_home | notification_to_myself | is_deleted_ldap | keep_devices_when_purging_item | backcreated | task_state | set_default_requester | groups_id | users_id_supervisor | nickname | substitution_end_date | substitution_start_date | toast_location |\n | ---: | --- | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | --- | --- | --- | --- | --- | --- | ---: | ---: | ---: | --- | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | --- | --- | --- | --- |\n | 7 | jdoe | 0 | 0 | \\N | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | \\N | \\N | \\N | \\N | \\N | \\N | \\N | \\N | \\N | \\N | | \\N | \\N | \\N | \\N | \\N | 0 | \\N | \\N | \\N | \\N | 0 | 0 | \\N | \\N | \\N | \\N |\n * A Simcard component \"Mini SIM\" of ID 1 as follow (glpi_devicesimcards SQL table):\n | id | designation | comment | entities_id | is_recursive | manufacturers_id | voltage | devicesimcardtypes_id | date_mod | date_creation | allow_voip |\n | ---: | --- | --- | ---: | ---: | ---: | ---: | ---: | --- | --- | ---: |\n | 1 | Mini SIM | | 0 | 0 | 0 | 0 | 2 | 2026-05-07 08:44:00 | 2026-05-07 08:43:51 | 0 |\n * A sime card item \"11111\" of ID 1 as follow (glpi_items_devicesimcards SQL table):\n | id | items_id | itemtype | devicesimcards_id | is_deleted | is_dynamic | entities_id | is_recursive | serial | otherserial | states_id | locations_id | lines_id | users_id | users_id_tech | pin | pin2 | puk | puk2 | msin | comment |\n | ---: | ---: | --- | ---: | ---: | ---: | ---: | ---: | --- | --- | ---: | ---: | ---: | ---: | ---: | --- | --- | --- | --- | --- | --- |\n | 1 | 0 | | 1 | 0 | 0 | 0 | 0 | 11111 | | 0 | 0 | 1 | 7 | 0 | | | | | | |\n2. Create a ticket or open an existing one (path=/front/ticket.form.php?id=XX)\n3. Go to \"Items\" tab\n4. Search for the SIM card in \"My devices\" dropdown and select it.\n [Image omitted]\n5. Click the \"Add\" button to add the item to the Ticket.\n\nExpected result:\n\nThe SIM card should be added to the Ticket.\n\nObtained result:\n\nI get an error:\n\nDebug mode informations:\n\nPOST payload:\n\nSQL requests:\n\n0.\n\n (time=0.4 ms ; rows=0)\n1.\n\n (time=0.2 ms ; rows=0)\n2.\n\n (time=0.6 ms ; rows=1)\n3.\n\n (time=0.5 ms ; rows=1)\n4.\n\n (time=0.3 ms ; rows=1)\n5.\n\n (time=0.3 ms ; rows=1)\n6.\n\n (time=0.2 ms ; rows=1)\n\nAdditional context:\nUsing the \"Or complete search\" field to add the SIM card (instead of the \"My devices\" field) works (SIM card is added) but it triggers a PHP warning:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "POST payload:\n\n{\n\"tickets_id\": \"1\",\n\"_glpi_csrf_token\": \"ca9…1e7\",\n\"my_items\": \"Item_DeviceSimcard_1\",\n\"itemtype\": \"Item\",\n\"add\": \"1\",\n\"items_id\": \"DeviceSimcard\"\n}\n\nI guess the issue is on that wrong items_id (an int is certainly expected). Maybe something wrong in a template file? I don't have time to investigate.\n\nOriginal response date: 2026-05-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4396149761, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24162#issuecomment-4396149761", "createdAt": "2026-05-07T10:04:01Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "For comparison, here is the POST payload for \"complete search\" addition is:\n\n(different presentation as this is obtained from my browser, not GLPI's debug mode)\n\nOriginal response date: 2026-05-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4396760267, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24162#issuecomment-4396760267", "createdAt": "2026-05-07T11:37:46Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the bug(s).\n- The list of items seems to try using a name field which simcards don't have.\n- The JS for the item selector splits the dropdown value by \"_\" and expects the first value to be the itemtype and 2nd to be the items_id. For itemtypes with an underscore, it messes up.\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4585195796, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24162#issuecomment-4585195796", "createdAt": "2026-05-30T23:55:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24162, "url": "https://github.com/glpi-project/glpi/issues/24162", "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2026-05-07T09:19:43Z", "updatedAt": "2026-05-30T23:56:03Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Sidebar language does not update without re-login when changing default system preferences", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen a new LDAP user logs into GLPI for the first time and inherits the system default language (English), changing the language to Portuguese-Brazil only partially applies to the current session. The main page content translates immediately upon saving, but the navigation sidebar remains in English until the user logs out and logs back in. Logging off and logging back into GLPI forces the session to reload, and the sidebar is subsequently rendered in Portuguese-Brazil.\n\nPrerequisites:\n- GLPI is configured with LDAP authentication.\n- A GLPI Rule is configured to assign the Super-Admin profile to the new LDAP user upon login.\n- The GLPI's default language is set to English.\n- The LDAP user is logging in for the very first time (no existing user preferences in the database).\n\nAffected page:\n/front/config.form.php\n\nReproduction steps:\n- Log into GLPI as a new LDAP user.\n- Navigate to the language settings (General > Default Values).\n- Change the Language from English to Portuguese-Brazil.\n- Click Save.\n- Observe the UI language changes, except the sidebar.\n\nAdditional context:\nMy suspicion is that because the new user does not have a language explicitly defined in their preferences upon first login, they inherit the system default (English). When the preference is updated and saved, the session language variable is updated for the main page rendering, but the sidebar component fails to catch the state change or flush its cache during that specific request, requiring a fresh session to apply fully.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I was not able to recreate the issue by changing a user's language to NULL in the DB, logging in as them, and then changing the default GLPI language as another user.\n\nIf it could be recreated, IMO the reported bug is not correct.\n\nNothing that gets changed in the global default preferences like language, date format, number format, etc should affect a user's current login session since they did not ask for that change themselves. So, the bug isn't that the menu doesn't get regenerated with the new default language, but rather that the session language changes at all.\n\nI believe the only way this would occur is after the PHP session \"expires\" via the PHP session lifetime config (default 24 minutes). When GLPI starts a new \"session\" from the rememberme cookie, the session data is reset to the defaults which is a known issue and causes other issues like the current profile also resetting to the user's default. At that point though, the menu would also need regenerated, so I am not able to see how the reported issue could occur.\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4582684820, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24370#issuecomment-4582684820", "createdAt": "2026-05-30T11:32:03Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "If the user with no default language changes the global default language, all of the GLPI UI gets the new language for me so I still cannot recreate the issue. I made sure my GLPI was in production mode with debug mode turned off.\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4582702419, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24370#issuecomment-4582702419", "createdAt": "2026-05-30T11:35:41Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello, Taylor Adler\nThank you for your fast response.\nI was able to reproduce this issue with the glpi user (built-in) in normal mode. You can see that \"Encontrar um menu\" (Find menu) is translated, but the sidebar items are not. That's so strange.\n\n[Image omitted]\n\nBut I think this issue is related to the GLPI 11 translation system, which has been refactored in GLPI 12 (src/Plugin.php) and this issue shouldn't happen in the newer version.\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4582933684, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24370#issuecomment-4582933684", "createdAt": "2026-05-30T13:17:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24370, "url": "https://github.com/glpi-project/glpi/issues/24370", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-28T13:03:50Z", "updatedAt": "2026-05-30T13:20:05Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "[11.0.6] sha1_file error when pasting images in ticket followups - File already moved/deleted", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen pasting images (Ctrl+V) into ticket followups, GLPI throws errors in the logs but the comment is still saved successfully with the image. The errors occur because of a race condition where temporary files are checked/deleted before they can be fully processed.\n\nReproduction steps:\nThe issue occurs in the following flow:\n\n1. Image is pasted and uploaded to /var/lib/glpi/_tmp/\n2. CommonDBTM::addFiles() checks if the image tag exists in content (line 5508)\n3. If tag is missing, the file may be deleted (lines 5510-5514)\n4. Later, Document::getFromDBbyContent() tries to calculate SHA1 of a non-existent file (line 521)\n5. Document::moveDocument() also fails when the file doesn't exist (line 1188)\n\nAdditional context:\nProposed Fix:\n\n I applied the following patches that resolved the issue:\n\n 1. In src/Document.php line 521-524:\n // Check if file exists before calculating SHA1\n if (!file_exists($path) || !is_file($path)) {\n return false;\n }\n\n 2. In src/Document.php line 1187-1190:\n if (!is_file($fullpath)) {\n // File may have been moved/deleted already - this is not always an\n error\n // Silently return false without triggering errors\n return false;\n }\n\n 3. In src/CommonDBTM.php line 5610:\n if ($docID > 0 && isset($input['_tag'][$key]) &&\n isset($doc->fields[\"tag\"])) {\n // Store image tag\n $docadded[$docID]['tag'] = $doc->fields[\"tag\"];\n }\n\n Expected Behavior:\n Images pasted in followups should be processed without errors in the logs.\n\n Actual Behavior:\n Images are saved correctly but errors are logged, causing confusion and polluting logs.\n\n Related Issues:\n - #12849 - Image paste does not work in all cases (10.0.3)\n - #13793 - Copied/pasted images won't load (10.0.5)\n - #1244 - sha1_file error in php.log", "priority": "medium", "type": "support", "createdByEmail": "jamie.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "devon.blair@peppermint.local", "text": "Same error here\n\nOriginal response date: 2026-03-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4155683492, "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23526#issuecomment-4155683492", "createdAt": "2026-03-30T14:53:43Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "Any updates on the issue?\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4216057395, "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23526#issuecomment-4216057395", "createdAt": "2026-04-09T17:05:46Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "The problem still occurs in version 11.0.7.\n\nOriginal response date: 2026-05-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4521707355, "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23526#issuecomment-4521707355", "createdAt": "2026-05-22T18:27:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23526, "url": "https://github.com/glpi-project/glpi/issues/23526", "author": "deguiremathieu", "anonymizedAuthorEmail": "jamie.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-18T13:39:30Z", "updatedAt": "2026-05-22T18:27:03Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "The pending reason automatic action is using the date of a previous follow-up as a reference and incorrectly sends an automatic follow-up.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.22\n\nIssue description:\nHello! We identified incorrect behavior when the automatic action pendingreason_autobump_autosolve adds an automatic follow-up to a ticket after changing the pending reason and the automatic follow-up frequency.\n\n[Image omitted]\n\n[Image omitted]\n\nScenario\n\nAs shown in the screenshot:\n\n11 days ago, a follow-up was added with a pending reason without automatic frequency.\n\n5 days ago, another follow-up was created, changing the pending reason to another one that also does not have automatic frequency.\n\nToday, a new follow-up was created, changing the pending reason to one that has an automatic follow-up frequency of 2 days preconfigured.\n\nIssue\n\nOn the next execution of the automatic action pendingreason_autobump_autosolve, an automatic follow-up was generated immediately, as if the 2-day frequency had already been reached.\n\nGLPI appears to be using the elapsed time since the previous follow-up (pending reason without frequency) as the reference, rather than the moment when the frequency was configured/enabled on the new follow-up.\n\nCurrent behavior\n\nThe automatic action sends an automatic follow-up right after the frequency-based follow-up is created (because the interval between follow-ups is greater than the configured duration).\n\nExpected behavior\n\nWhen creating a follow-up with automatic frequency, the counter/deadline should start from the timestamp of this new frequency-based follow-up (or from the moment the frequency is enabled), and should not reuse the date of older follow-ups that did not have frequency.", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "elliot.blair@peppermint.local", "text": "Hello! Any update on this?\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3873468085, "author": "Berlinst", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23039#issuecomment-3873468085", "createdAt": "2026-02-09T19:32:39Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "We are trying to use this, we have problems to debug/track what is actually happening.\nWe have entries of the automatic job \" pendingreason_autobump_autosolve\" in the ticket,\n and entries in the protocols of the automatic job,\n but the expected emails to the users are not happening (?)\n\nHow to Debug the correlations/actions performed by the GLPI system? Where/what are the devs looking at/into, when they are testing ?\n\nGreetings from Germany!\n\nOriginal response date: 2026-05-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4405297126, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23039#issuecomment-4405297126", "createdAt": "2026-05-08T09:26:21Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Hello, Lane Bennett.\n\nWe were able to fix this bug on our side by making some adjustments to the following GLPI file:\n\n/yourglpi/src/PendingReason_Item.php\n\nI’m attaching the updated version of the file so you can review it, compare it with the original GLPI version, and, if appropriate, test it in your own GLPI instance to check whether it also resolves the issue in your environment.\n\nWe strongly recommend testing it in a test/staging environment first before applying it to production. Also, please make sure to back up the original file before replacing it.\n\nI hope this helps. Greetings from Brazil! 😉\n\nPendingReason_Item.php\n\nOriginal response date: 2026-05-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4491869380, "author": "serviceticst", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23039#issuecomment-4491869380", "createdAt": "2026-05-19T20:42:01Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23039, "url": "https://github.com/glpi-project/glpi/issues/23039", "author": "vpkleo", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-06T13:06:24Z", "updatedAt": "2026-05-19T20:42:01Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Inefficient entity transfer process", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nWhile trying to troubleshoot entity transfer issues again, I noticed over 34,000 SQL queries had been made when I finally got a computer with 3700 software installations to transfer (ignored SQL errors from unicity constraints). A lower priority than the current blocking issues, but transferring this one computer shouldn't make that many queries or lead to timeouts (> 30 seconds) and OOM errors like I also experienced.\n\nIt seems that for every single item that may need to be transferred (including indirectly), we load the entire item using getFromDB just to check its entity and recursivity during the \"evaluateTransfer\" part of the process. The entire item is then loaded again during the \"transfer\" process. For updates, the request is made for each item individually (it seems without checking unicity first). There are other cases of loading items in full and queries that could be batched, but I think this highlights the core of the issue.\n\nThis probably has no impact unless transferring a computer with a lot of attached items or transferring a lot of items at once.", "priority": "high", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Well, Transfer issues are not just about performances; code is very complex; any issue is a pain to fix. I guess this needs an entire rewrite, rather than focusing on performances .\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3595069161, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22109#issuecomment-3595069161", "createdAt": "2025-12-01T07:45:02Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I agree, but felt it necessary to point out. To be fair, the timeout and memory issues may have been just because I was in debug mode so it was recording the queries for the debug bar, but it could still be an issue when there are many items transferred. I've been extra particular about GLPI performance and user experience lately, but as I mentioned this instance is a lower priority and clearly not having a big impact on users at the moment, at least not in the cases where entity transfers still work at all.\n\nGiven that assets are always sent to a kind of queue to be transferred, it seems like it is expected to be able to handle mass-transfers and that wouldn't work well with computers at the moment.\n\nAlso, I forsee a lot of rewrites in my future so this one may not be mine.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3595962934, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22109#issuecomment-3595962934", "createdAt": "2025-12-01T11:13:54Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "I can confirm similar behavior on GLPI 11.0.7.\n\nOut environment:\n\nGLPI 11.0.6 initially\nUpgraded to GLPI 11.0.7 and reproduced again\nDebian\nApache 2.4.62\nPHP 8.2 via Apache\nTested PHP memory_limit values:\n 256M\n 512M\n 1024M\n\nScenario:\n\nTrying to transfer a single Computer item from a parent entity to a child entity using a transfer profile intended to preserve linked information. The asset itself is not unusually large, but it has normal inventory/history data attached.\n\nResult:\nThe transfer fails with an unexpected error / HTTP 500. PHP exhausts memory during /front/transfer.action.php.\n\nExamples from Apache/PHP logs:\n\nAdditional test::\n\nI also tested with GLPI extensions/plugins paused/disabled, and the transfer still failed with the same memory exhaustion behavior\nI also tried a transfer profile without software information, but the transfer still failed.\n\nOriginal response date: 2026-05-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4462876088, "author": "dioig0", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22109#issuecomment-4462876088", "createdAt": "2026-05-15T19:41:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22109, "url": "https://github.com/glpi-project/glpi/issues/22109", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "open", "stateReason": null, "createdAt": "2025-11-28T23:01:03Z", "updatedAt": "2026-05-15T19:42:26Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "[Bug] Cannot change local user passwords, field locked with padlock in GLPI 11.0.6", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nDescribe the bug\nIt is not possible to change the password of local users in GLPI 11.0.6: the password field appears locked (showing a padlock icon), even when the user uses \"GLPI database\" as authentication method and a Super-Admin account with all permissions is used.\n\nTo Reproduce\n\nLog in as a Super-Admin user.\nGo to Administration → Users.\nSelect any user that has \"GLPI database\" as their authentication method.\nGo to the Password tab.\nThe password field is locked, shows a padlock, and cannot be edited.\n\nExpected behavior\nSuper-Admin should be able to change the password for any local user (authenticated by the GLPI database).\n\nGLPI Version: 11.0.6\nBrowser: (e.g., Chrome 122, Firefox 124, etc.)\nActive plugins: (List them, or specify if issue is present with all plugins disabled)\nOperating system: (e.g., Ubuntu 22.04)\nAuthentication method of affected user: GLPI database", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Could you provide a screenshot? There is no Password tab on the user form and there should be no field locking for user fields either.\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4316373813, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24013#issuecomment-4316373813", "createdAt": "2026-04-24T21:01:50Z" } }, { "userEmail": "harper.bennett@peppermint.local", "text": "We reviewed the user configuration and confirmed that there is no \"Password\" tab available in the user form. We also validated that there should be no field locking applied to user fields.\n\nAs part of the troubleshooting, we updated existing profiles and created new profiles to test if the behavior was profile-related. Additionally, we reviewed the authentication settings, but the issue persists.\n\nDespite all these changes and our attempts, we were unable to remove the password lock for the users.\n\n[Image omitted]\n[Image omitted]\n\nOriginal response date: 2026-04-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4339345670, "author": "gdavidlt", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24013#issuecomment-4339345670", "createdAt": "2026-04-28T21:50:45Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "This is not a blocking issue. See comments in #19373.\n\nOriginal response date: 2026-05-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4360118629, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24013#issuecomment-4360118629", "createdAt": "2026-05-01T15:41:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24013, "url": "https://github.com/glpi-project/glpi/issues/24013", "author": "gdavidlt", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-04-24T18:02:02Z", "updatedAt": "2026-05-01T15:41:58Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Issue with cyrillic encoded attachments from mailbox", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen mailcollector collecting mail from mailbox - csv files that were encoded in Windows1251 encoding will be processed by Mailcollector so they'll no longer have valid encoding. I find issue in src/Mailcollector.php in getDecodedContent method. The files that doesn't include charset info get decoded with ISO-8859-1\nThe issue is that - the files that mailcollector process will have corrupted encoding - so when you download them from GLPI - they no longer valid\nI provide a PR that will solve this issue\n\nReproduction steps:\n1. Configure mailcollector in GLPI\n2. Send an email with attachment encoded with Windows1251 for example\n3. Recieve a ticket, with attachment that'll have broken encoding\nNote: not every encoded file will be corrupted, only files that doesn't have charset data in it", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "lane.blair@peppermint.local", "text": "The following change in the file worked for me Mailcollector.php:\n/\n * Retrieve properly decoded content\n *\n * @param Part $part Message Part\n *\n * @return string\n */\npublic function getDecodedContent(Part $part)\n{\n $contents = $part->getContent();\n\n $encoding = null;\n if (isset($part->contentTransferEncoding)) {\n $encoding = $part->contentTransferEncoding;\n }\n\n // Декодирование содержимого в соответствии с Content-Transfer-Encoding\n switch (strtolower(trim($encoding))) {\n case 'base64':\n $contents = base64_decode($contents, true);\n if ($contents === false) {\n // Если декодирование не удалось, пробуем с игнорированием некорректных символов\n $contents = base64_decode($contents, false);\n }\n break;\n case 'quoted-printable':\n $contents = quoted_printable_decode($contents);\n break;\n case '7bit':\n case '8bit':\n case 'binary':\n default:\n // возвращаем как есть\n break;\n }\n\n // Проверяем, является ли часть текстовой\n if (\n !$part->getHeaders()->has('content-type')\n || !(($content_type = $part->getHeader('content-type')) instanceof ContentType)\n || preg_match('/^text\\//', $content_type->getType()) !== 1\n ) {\n // Для нетекстовых вложений (изображения, архивы и т.д.) возвращаем как есть\n return $contents;\n }\n\n $charset = $content_type->getParameter('charset');\n\n // Определяем кодировку, если не указана\n if ($charset === null) {\n // Пробуем определить кодировку автоматически\n $detectedEncoding = mb_detect_encoding($contents, ['UTF-8', 'Windows-1251', 'KOI8-R', 'ISO-8859-5', 'CP866'], true);\n $charset = $detectedEncoding ?: 'Windows-1251'; // По умолчанию Windows-1251 для кириллицы\n }\n\n // Нормализуем название кодировки\n $charset = $this->normalizeCharset($charset);\n $charsetUpper = strtoupper($charset);\n\n // Если кодировка уже UTF-8, возвращаем как есть\n if ($charsetUpper === 'UTF-8' || $charsetUpper === 'UTF8') {\n return $contents;\n }\n\n // Специальная обработка для кириллических кодировок\n if (in_array($charsetUpper, ['WINDOWS-1251', 'CP1251', 'WINDOWS1251'])) {\n return $this->convertToUtf8($contents, 'Windows-1251');\n }\n\n // Специальная обработка для корейских кодировок\n if (in_array(strtolower($charset), ['ks_c_5601-1987', 'ks_c_5601-1989'])) {\n $charset = 'UHC';\n }\n\n // Специальная обработка для ISO-8859-8-i\n if ($charsetUpper === 'ISO-8859-8-I') {\n $charset = 'ISO-8859-8';\n }\n\n // Конвертация в UTF-8\n return $this->convertToUtf8($contents, $charset);\n}\n\n/\n * Нормализует название кодировки\n *\n * @param string $charset\n * @return string\n */\n\n[Content truncated.]\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4074857425, "author": "Aleko-SaR", "anonymizedAuthorEmail": "lane.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22997#issuecomment-4074857425", "createdAt": "2026-03-17T13:12:23Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Lane Blair your comment is not really lisible, please fix. There are many comments that are not in English, please translate.\n\nFor code changes, please open a PR. There is already one existing (#22998); but it does not work; therefore you can propose your own.\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4074886377, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22997#issuecomment-4074886377", "createdAt": "2026-03-17T13:16:54Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "See\n\nOriginal response date: 2026-04-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4344346035, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22997#issuecomment-4344346035", "createdAt": "2026-04-29T13:49:30Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22997, "url": "https://github.com/glpi-project/glpi/issues/22997", "author": "akstis-typer", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "akstis-typer", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-04T06:02:52Z", "updatedAt": "2026-04-29T13:49:30Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Plugin rules massive action fails because of JS escape", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHello,\nRecently, I've deployed the samlSSO plug-in and noticed that massive action fails with \"No selected items\" for massive actions at GLPI > Setup > Rules > samlSSO. I've reported the bug to the plugin author ( but after digging into the issue further, I've figured out it's related to GLPI core instead of the plugin, because it's an issue that may affect multiple plugins and the plugin author uses the GLPI native rule page and rule forms, as can be seen at:\n\nThe message \"No selected items\" is triggered by:\n\nComparison between the plug-in /front/massiveaction.php payload (Chrome > F12 > Network > massiveaction.php) and built-in GLPI rules:\n\nsamlSSO plug-in (/plugins/samlsso/front/rulesaml.php) rules page:\n\nGLPI Built-in \"Automatic user assignment\" rules page (/front/ruleright.php):\n\nYou can notice that the built-in GLPI rule page has the checkbox item IDs on its payload, while the samlSSO plugin does not.\n\nThe massive action fails because the jQuery code fails to find the container ID that contains the items checkbox on the GLPI > Setup > Rules > samlSSO page.\n\nThe plug-in uses a namespace to handle rules, e.g. \"GlpiPlugin\\Samlsso\\RuleSaml\", while GLPI built-in rules don't use \\ in their name (e.g. RuleRight).\n\nThe JavaScript code that gets the checkboxes doesn't escape \\ correctly, and jQuery is unable to find the container ID that contains the rules checkboxes of the SAML SSO plugin.\n\nThe code above adds an inline tag to the page, while the jsescape($p['container']) PHP function escapes the container ID of the plug-in in the generated JS code to massGlpiPlugin\\\\Samlsso\\\\RuleSamlCollection1891979255 (by escaping \\ to \\\\), but jQuery expects \\ be escaped to \\\\\\\\ instead, as can be seen in the code run on the browser Console:\n\n[Image omitted]\n\n[Image omitted]\n\nI do believe we have two approaches to fix the issue:\n\n1. Modify the jsescape($p['container']) PHP code to duplicate \\ to \\\\ so jsescape will convert it to \\\\\\\\ which is the format that jQuery expects. This is an issue that can happen again in the future when creating new JS code that relies on the container ID.\n2. Convert \\ to _ in a higher level than this function or remove the namespace denomination of the container ID (e.g. GlpiPlugin\\Samlsso\\RuleSamlCollection becomes RuleSamlCollection), but removing the namespace denomination may create issues if two plugin authors create a class with the same name between third-party plugins.\n\nAffected page:\n\nReproduction steps:\n1. Go to (requires samlSSO plugin)\n2. Create a new JIT rule\n3. Return to\n4. Check its box\n5. Click on [Actions]\n6. See error \"No selected items\" on modal.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do believe we have two approaches to fix the issue:\n\n1. Modify the jsescape($p['container']) PHP code to duplicate \\ to \\\\ so jsescape will convert it to \\\\\\\\ which is the format that jQuery expects. This is an issue that can happen again in the future when creating new JS code that relies on the container ID.\n2. Convert \\ to _ in a higher level than this function or remove the namespace denomination of the container ID (e.g. GlpiPlugin\\Samlsso\\RuleSamlCollection becomes RuleSamlCollection), but removing the namespace denomination may create issues if two plugin authors create a class with the same name between third-party plugins.\n\n\\ is not a valid char in an HTML ID. Therefore, the correct approach is the second proposal. This canbe done using the |safe_dom_id Twig filter or the Html::sanitizeDomId() PHP method.\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744776645, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22614#issuecomment-3744776645", "createdAt": "2026-01-13T14:50:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Theoretically, the ID attribute with \\ is valid on HTML5 (but not HTML4), as the only requirement for it now is not containing spaces, but it's recommended to use it in compliance with CSS identifiers to avoid using escapes (this is the case of this issue). Source:\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744926995, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22614#issuecomment-3744926995", "createdAt": "2026-01-13T15:19:29Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Indeed. The solution could also be to use CSS.escape(id) on the JS side.\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744966498, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22614#issuecomment-3744966498", "createdAt": "2026-01-13T15:26:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22614, "url": "https://github.com/glpi-project/glpi/issues/22614", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-11T01:07:56Z", "updatedAt": "2026-01-13T15:26:58Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI: User belongs to Group but doesn't shown on \"Users\" tab of the Group", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHello,\nI'm using YunoHost (it's a bundle of Web Server and LDAP server) that sets up GLPI LDAP auth during GLPI installation, as can be seen at\nThe user authenticates through SSO ($REMOTE_USER).\nIn the \"Group\" tab of the LDAP user, it shows the \"admin\" and \"all_users\" group (the user belongs to both LDAP groups):\n[Image omitted]\nBut in the \"Users\" tab of the LDAP group, the LDAP user isn't shown:\n[Image omitted]\n\nAffected page:\n\nAdditional context:\nPlease let me know if I can provide any information / DB or LDAP dump/info to help troubleshoot this issue.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "micah.blair@peppermint.local", "text": "testing your branch, I get all the LDAP users listed.\n\n[Image omitted]\n\nOriginal response date: 2025-12-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3666449462, "author": "ericgaspar", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22415#issuecomment-3666449462", "createdAt": "2025-12-17T17:39:01Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The user is shown at Adminsitration > Users page too, no issues about it, but when clicking into the group in Administration > Group page, the tab \"Users\" for the 'admins' group is empty, but into the user page (Administration > Users > [user]), the 'admins' group is listed at the 'Groups' tab, as can be seen in my screenhots.\n\nOriginal response date: 2025-12-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3666489413, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22415#issuecomment-3666489413", "createdAt": "2025-12-17T17:48:35Z" } }, { "userEmail": "micah.blair@peppermint.local", "text": "Ah, yes, I see what you mean. (all_users users are listed, but not admins)\n\nOriginal response date: 2025-12-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3666509144, "author": "ericgaspar", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22415#issuecomment-3666509144", "createdAt": "2025-12-17T17:54:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22415, "url": "https://github.com/glpi-project/glpi/issues/22415", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-17T17:16:50Z", "updatedAt": "2025-12-17T17:54:43Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI 11 - getItemTypeForTable and getSingular conflict", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWe encountered this issue when attempting to migrate a plugin from GLPI 10 to 11.\nWe have a class called Menu that inherits from CommonDropdown, so we have removed the front pages and this happens:\n\n[Image omitted]\n\nI've been diving into the code and I understand that the problem is as follows.\nFrom the table in the database that is in plural, the singular is extracted, and from the singular, it is concatenated to find the plugin class, but looking at the getSingular function, it has this comment:\n\n[Image omitted]\n\nI understand that getSingular is designed to give the singular form of any word that is included, but in the case of tables, it seems a little strange. I don't know if there could be problems with custom dropdowns.\n\n[Image omitted]\n\nIn our case, we are going to avoid it this way for now.\n\n[Image omitted]", "priority": "high", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI noticed a few weeks ago that getSingular() and getPlural() are not always reversible. Fixing this may have unexpected side effects, so it has to be done in a GLPI majo version to be able to detect issues in the beta/RC versions.\n\nOriginal response date: 2025-11-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3579965422, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22023#issuecomment-3579965422", "createdAt": "2025-11-26T08:01:53Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "Yes, I think so too. I started by thinking of a function that assumes the string always comes in plural form, but English is a curious language.\n\nLooking through it, I see that perhaps the inflector library could be implemented in Symfony I don't know how feasible it is to implement in GLPI.\n\nOriginal response date: 2025-11-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3580170165, "author": "FrancisTicgal", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22023#issuecomment-3580170165", "createdAt": "2025-11-26T08:44:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The idea would be to remove need to guess singular/plural (which in fact is not the only issue in that part of the code).\n\nOriginal response date: 2025-11-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3580233511, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22023#issuecomment-3580233511", "createdAt": "2025-11-26T08:56:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22023, "url": "https://github.com/glpi-project/glpi/issues/22023", "author": "FrancisTicgal", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [ "complex issue" ], "state": "open", "stateReason": null, "createdAt": "2025-11-21T11:38:23Z", "updatedAt": "2025-11-26T08:56:56Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "FORMS - Error do not appears Current logged-in user on GLPI 11.0.2", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen I use a question Item > GLPI Objects On GLPI 11.0.1 I have this option:\n\n[Image omitted]\n\nOn GLPI 11.0.2:\n\n[Image omitted]\n\nThis is a bug or this resource will not be available anymore?\n\nAffected page:\n/front/form/form.form.php?id=ID_form\n\nReproduction steps:\nCreate a question with this parameters:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Bailey Bennett,\n\nThis option from GLPI 11.0.1 was actually a bug, the list of users would not be shown correctly and the \"current logged in user\" was displayed instead by accident (it probably didn't work as expected).\n\nIf you'd like an option to prefill this field with the current user, we could think about adding it properly as a legitimate option.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3527974741, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21929#issuecomment-3527974741", "createdAt": "2025-11-13T14:01:37Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "I Think this field is really useful, If possible use on 11.0.3.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3528051407, "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21929#issuecomment-3528051407", "createdAt": "2025-11-13T14:20:45Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "Hi team, any feedback?\n\nOriginal response date: 2025-11-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3547419372, "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21929#issuecomment-3547419372", "createdAt": "2025-11-18T12:29:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21929, "url": "https://github.com/glpi-project/glpi/issues/21929", "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-11-13T13:46:51Z", "updatedAt": "2025-11-20T15:12:05Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Auth.php: User->getFromSSO() returns deleted user with new user", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen logging-in with SSO using HTTP headers, with a username matching two accounts:\n\n- one deleted account (in trash, but not completely deleted)\n- one new account created manually.\n\nThe SSO fails with an error due to User->getFromSSO() query returning both User accounts.\n\nReproduction steps:\n1. configure GLPI to auth via HTTP headers (basic auth,...)\n2. disable automatic user creation with SSO.\n3. add a user with username 'test-user'\n4. delete it, but keep it in trash\n5. add a user with username 'test-user'\n6. try to login with username 'test-user' using HTTP headers", "priority": "high", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Seems like this may be a duplicate of #20073\n\nDifferent action, but same underlying issue.\nAuthentication flow is finding the user by the token in getAlternateAuthSystemsUserLogin, but then the user is being fetched again by name right after.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521395173, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21896#issuecomment-3521395173", "createdAt": "2025-11-12T11:10:16Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "Taylor Adler In my case, User::getFromDBbyName is what fetch the User. The underlying issues are:\n\n1. it's materially possible to create users with the same login as a deleted user, thus breaking user unity (uniq) in database.\n2. Authentication processes use User::getFromDBbyName(). This method returns deleted users. It's a correct behavior since it's name hint to this behavior.\n\nA solution is to add a User::getActiveFromDBbyName() that add this criteria to the user finding query:\n\nand to update Auth SSO and API methods to use it.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521492679, "author": "landure", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21896#issuecomment-3521492679", "createdAt": "2025-11-12T11:37:14Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nFor the moment, you can bypass this issue by removing the deleted user or change its username. Fixing this is pretty complex and will not be done right now.\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558158089, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21896#issuecomment-3558158089", "createdAt": "2025-11-20T13:46:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21896, "url": "https://github.com/glpi-project/glpi/issues/21896", "author": "landure", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [ "complex issue" ], "state": "open", "stateReason": null, "createdAt": "2025-11-12T11:05:59Z", "updatedAt": "2025-11-20T13:49:37Z", "closedAt": null } }, { "title": "Mailgate task stuck", "detail": "Affected version:\n10.0.7\n\nIssue description:\nHello,\nWhen the mailgate task is triggered, sometimes it get stuck. Sometimes took a day, a week or month, but it get stuck again eventually. For me, it seems that the mail server is the culprit because it's slow, even when browsing mails through Webmail. But GLPI should be able to handle those laminas library exceptions and close the DB lock as expected, so when running the mailgate task again into the future when the mailserver is available again it should pull the messages instead of getting stuck and not running the mailgate task anymore. We have to go to the Actions page, click on \"X\" on \"Running\" task status of mailgate to make it scheduled again.\n\nIt doesn't seems that the task is reaching PHP/IIS request limit, and it's running a GLPI task instead of a CLI one, so it should be respecting PHP timeout and unlocking the task even when ended prematurely. I'm not sure, but maybe it's getting locked because it uses the same DB as queuednotifications or because it got stuck itself because laminas library failed? This error already shown into the past and it seems that when queuednotification is running and mailgate task is triggered, it seems more prone to this issue.\n\nI'm facing this kind of issue for at least two years, and I'd have the opportunity to chat with cedric-ane and trasher about this. While talking to them, they'd said that GLPI tasks code doesn't seem to properly handle task execution failures, so the mailgate task get locked/stuck. We're running GLPI on Windows Server now, but I was already able to face this issue on Linux as well.\n\nI do not believe this specific issue is related with attachments (as can be seen on #7327) because no pending mail message has attachments on it's receiver mail account, and when pulling mails manually it pulls the messages as expected.\n\nDiagnostic information:\nphp-errors.log when collecting through mailgate task:\n\nThe error on php-errors.log seems to be slightly different when attempting to collect mails manually through \"Receivers page\":", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "An attempt to improve reliability/resilience of automatic actions for GLPI 12 was started in #23672. Long-term, I would suggest we look at Symfony Scheduler to improve reliability and flexibility even more while shifting most of the responsibility to Symfony since we locked GLPI more into the Symfony framework in GLPI 11.\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4159089044, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/14662#issuecomment-4159089044", "createdAt": "2026-03-31T00:53:27Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "An attempt to improve reliability/resilience of automatic actions for GLPI 12 was started in #23672. Long-term, I would suggest we look at Symfony Scheduler to improve reliability and flexibility even more while shifting most of the responsibility to Symfony since we locked GLPI more into the Symfony framework in GLPI 11.\n\nThat's great to hear. Symfony is a good framework; it's always had high-quality components thanks to Fabien Potencier. I haven't followed its development for a while. I used it in the early days of version 1.0. =)\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4159219494, "author": "ftoledo", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/14662#issuecomment-4159219494", "createdAt": "2026-03-31T01:37:37Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 14662, "url": "https://github.com/glpi-project/glpi/issues/14662", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-05-04T16:45:54Z", "updatedAt": "2026-03-31T01:37:37Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Linux machines are no longer updated", "detail": "Affected version:\n10.0.19\n\nIssue description:\nWe have a handful of Linux machines that are no longer being updated via inventory run.\nOne particular machine not for over a month.\n\nWhen investigating the sql-errors.log the agent sends other to the database rather than 4 (which is the numeric value for Other)\nLogs See below\n\nIn another instance the computer model is send rather than the numeric value for the model:\nLogs See below\n\nReproduction steps:\nWould not know how to replicate.", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Lane Bennett\n\nDoes th issue persist? Could you provide logs and inventory file related to this specific issue?\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611600798, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20621#issuecomment-3611600798", "createdAt": "2025-12-04T11:10:57Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Skyler Adler I still have the problem but it's not exclusive to Linux as I initially suspected. It's just a handful of machines and I suspect my Import Rules are the root cause. I am currently investigating and it seems to me that only the machines that have their NAME set manually are affected.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611701212, "author": "GuidoWilden", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20621#issuecomment-3611701212", "createdAt": "2025-12-04T11:30:15Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20621, "url": "https://github.com/glpi-project/glpi/issues/20621", "author": "GuidoWilden", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": null, "createdAt": "2025-08-11T07:05:54Z", "updatedAt": "2025-12-04T11:30:15Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "[9.5.6] Active Directory location sync creates locations in root entity instead of user's entity", "detail": "Issue description:\nHi GLPI Team !\n\nI'm facing what it seems to be au bug :\n\nBug Description\n\nIn AD User object, physicaldeliveryofficename attribute is set to give a location of the user like [Site x] > [Floor y] > [Room z], according of the existing locations set in a given entity in GLPI. But user sync creates a duplicate location in root entity and don't take the existing one in the user's entity.\n\nTo reproduce\nIt would be hard work to explain all steps to reproduce this issue... I'll try with this :\n1. In _Home >Setup > Dropdowns > Locations_, a location is set as [Site x] > [Floor y] > [Room z] in [root Entity] / [Entity1]\n2. Considering a fully functionnal AD or LDAP user sync to GLPI. Users are successfully imported in [root Entity] / [Entity1]\n3. In _Home >Setup > Authentication > LDAP directories > Users_, physicaldeliveryofficename attribute is binded with \"location\" field\n4. In AD user's object, the physicaldeliveryofficename attribute is set as [Site x] > [Floor y] > [Room z]\n5. Forcing user sync from AD in GLPI : A new location [Site x] > [Floor y] > [Room z] is created in [root entity] instead of using the existing one [root Entity] / [Entity1] > [Site x] > [Floor y] > [Room z]\n\nExpected behavior\n\nThe AD attribute should link the existing location of the user's entity.\n\nRegards,\nEric", "priority": "high", "type": "support", "createdByEmail": "casey.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "quinn.blair@peppermint.local", "text": "This fix works for the web interface via action 'Force synchronization'. But it doesn't work when use command php bin/console glpi:ldap:synchronize_users -u -n\n\nI'm using GLPI 9.5.7\n\nOriginal response date: 2025-11-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3561617129, "author": "jerrylu2008", "anonymizedAuthorEmail": "quinn.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/9287#issuecomment-3561617129", "createdAt": "2025-11-21T06:33:16Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I'm using GLPI 9.5.7\n\nGLPI 9.5.x is discontinued since 06/2023.\n\nOriginal response date: 2025-11-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3561745719, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/9287#issuecomment-3561745719", "createdAt": "2025-11-21T07:15:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 9287, "url": "https://github.com/glpi-project/glpi/issues/9287", "author": "CireSacud26", "anonymizedAuthorEmail": "casey.adler@peppermint.local", "assignees": [], "labels": [ "complex issue" ], "state": "open", "stateReason": null, "createdAt": "2021-07-15T06:55:02Z", "updatedAt": "2025-11-21T07:15:43Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Screenshots are not added", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nUp to version 11.0.6 we could paste screenshots into ticket replies.\n\nIn version 11.0.7 we cannot paste screenshots and also, when there is a followup template that contains an image, it is not added to the ticket.\n\nFollowup template:\n\n[Image omitted]\n\n[Image omitted]\n\nWhen replying to the ticket, the image is not shown:\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "sage.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "dakota.bennett@peppermint.local", "text": "We had the same problem, but found in the browser's Javascript console that it was actually just being blocked by a content security policy in our server.\n\nOriginal response date: 2026-05-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4553761985, "author": "cfuchs-mpi", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24235#issuecomment-4553761985", "createdAt": "2026-05-27T10:38:17Z" } }, { "userEmail": "sage.bennett@peppermint.local", "text": "Any update on this?\n\nOriginal response date: 2026-07-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4908124883, "author": "RobertoMarcelino", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24235#issuecomment-4908124883", "createdAt": "2026-07-07T19:58:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24235, "url": "https://github.com/glpi-project/glpi/issues/24235", "author": "RobertoMarcelino", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-16T15:46:41Z", "updatedAt": "2026-07-07T19:58:47Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "AllAssets (Global) search: \"Group\" field (search option 71) is always empty due to an unsubstituted itemtype placeholder in the JOIN clause", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.6\n\nIssue description:\nWhen using the Global assets search (front/allassets.php, itemtype AllAssets), the Group column/criterion (search option id 71) is always empty for every item type, even when the corresponding item has a Group correctly assigned. The same Group value displays correctly when searching directly in the type-specific view (e.g. front/computer.php), so the data itself is correct — only the AllAssets aggregated search fails to retrieve it.\n\nBy enabling debug mode and inspecting the generated SQL for the AllAssets search, I found that the UNION sub-query generated for each item type contains two separate LEFT JOINs on glpi_groups_items:\n\nThe first one (used to populate search option 71, \"Group\") uses a literal, unsubstituted placeholder string as the itemtype value:\n\nsqlLEFT JOIN glpi_groups_items\n ON (glpi_groups_items.items_id = glpi_computers.id\n AND glpi_groups_items.itemtype = 'glpi_computers_TYPE'\n AND glpi_groups_items.type = '1')\nLEFT JOIN glpi_groups\n ON (glpi_groups.id = glpi_groups_items.groups_id)\n\n'glpi_computers_TYPE' is not a valid value stored in glpi_groups_items.itemtype (real values are class names such as 'Computer'). This condition can therefore never match any row, so glpi_groups.completename (aliased as ITEM_AllAssets_71) is always NULL.\n\nThe second JOIN, used for a different search option (id 49, \"Group in charge\" / \"Group responsible\"), correctly substitutes the real itemtype:\n\nsqlLEFT JOIN glpi_groups_items AS glpi_groups_items_c6f7f58b9365babf7388e555e526efd5\n ON (glpi_computers.id = glpi_groups_items_c6f7f58b9365babf7388e555e526efd5.items_id\n AND glpi_groups_items_c6f7f58b9365babf7388e555e526efd5.itemtype = 'Computer'\n AND ((glpi_groups_items_c6f7f58b9365babf7388e555e526efd5.type = '2')))\n\nThis pattern repeats identically across every UNION-ed sub-query for every item type in the AllAssets search, including standard types (Computer, Monitor, NetworkEquipment, Peripheral, Phone, Printer, SoftwareLicense, Certificate, Unmanaged, Appliance) and custom assets created via the native GLPI 11 custom asset system (e.g. Glpi\\CustomAsset\\ExpositionsAsset).\n\nThis looks like the itemtype placeholder used internally when building the generic AllAssets query (something like {itemtype}_TYPE or similar templating) is not being correctly replaced with the actual item class name for this specific JOIN, while the equivalent JOIN for \"Group in charge\" right next to it is built correctly.\n\nSteps to reproduce\n\nGo to Assets > Global (front/allassets.php).\nMake sure several items of different types (e.g. a Computer and a Monitor) have a Group assigned (visible/filterable correctly from their respective type-specific list, e.g. front/computer.php).\nIn the Global search, add Group as a displayed column and/or as a search criterion.\nTry filtering by an existing group name.\n\nExpected behavior\n\nThe Global search should return the items that have the selected Group, and the Group column should display the assigned group name, consistently with what is shown in the type-specific search (e.g. Computers).\n\nActual behavior\n\nThe Group column is empty for all rows in the Global search, regardless of type.\nFiltering by Group in the Global search returns zero results, even for groups that are confirmed (via the type-specific search) to be assigned to existing items.\nNo SQL error or warning is raised; the query executes successfully but structurally cannot match any row for that condition.\n\nEvidence: relevant excerpt of generated SQL (debug mode, GLPI 11.0.6)\n\nsql(SELECT DISTINCT glpi_computers.id AS id, 'Rayane' AS currentuser,\n glpi_computers.name AS ITEM_AllAssets_1,\n glpi_computers.id AS ITEM_AllAssets_1_id,\n glpi_entities.completename AS ITEM_AllAssets_80,\n glpi_states.completename AS ITEM_AllAssets_31,\n glpi_groups.completename AS ITEM_AllAssets_71,\n GROUP_CONCAT(DISTINCT CONCAT(IFNULL(glpi_groups_62d33fd288e43e0c5b1ccc8085234976.completename, 'NULL'), '$#$', glpi_groups_62d33fd288e43e0c5b1ccc8085234976.id)\n ORDER BY glpi_groups_62d33fd288e43e0c5b1ccc8085234976.id SEPARATOR '$$##$$') AS ITEM_AllAssets_49,\n 'Computer' AS TYPE\nFROM glpi_computers\nLEFT JOIN glpi_entities ON (glpi_computers.entities_id = glpi_entities.id)\nLEFT JOIN glpi_states ON (glpi_computers.states_id = glpi_states.id)\nLEFT JOIN glpi_groups_items\n ON (glpi_groups_items.items_id = glpi_computers.id\n AND glpi_groups_items.itemtype = 'glpi_computers_TYPE'\n AND glpi_groups_items.type = '1')\nLEFT JOIN glpi_groups ON (glpi_groups.id = glpi_groups_items.groups_id)\nLEFT JOIN glpi_groups_items AS glpi_groups_items_c6f7f58b9365babf7388e555e526efd5\n ON (glpi_computers.id = glpi_groups_items_c6f7f58b9365babf7388e555e526efd5.items_id\n AND glpi_groups_items_c6f7f58b9365babf7388e555e526efd5.itemtype = 'Computer'\n AND ((glpi_groups_items_c6f7f58b9365babf7388e555e526efd5.type = '2')))\nLEFT JOIN glpi_groups AS glpi_groups_62d33fd288e43e0c5b1ccc8085234976\n ON (glpi_groups_items_c6f7f58b9365babf7388e555e526efd5.groups_id = glpi_groups_62d33fd288e43\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "jamie.adler@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with latest stable release (11.0.8).\n\nOriginal response date: 2026-06-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4797881431, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24674#issuecomment-4797881431", "createdAt": "2026-06-25T09:43:00Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I could not recreate the issue with 11.0.8.\n\nOriginal response date: 2026-07-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4849719286, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24674#issuecomment-4849719286", "createdAt": "2026-07-01T02:28:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24674, "url": "https://github.com/glpi-project/glpi/issues/24674", "author": "AstroWorld95", "anonymizedAuthorEmail": "jamie.adler@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": null, "createdAt": "2026-06-25T09:39:33Z", "updatedAt": "2026-07-01T02:28:55Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Translations for Form titles are not applied to Site title", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nTranslation of form titles are not applied to the site title\n\n[Image omitted]\n\nAffected page:\n/Form/Render/", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with a nightly build if issue persists.\n\nOriginal response date: 2026-06-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4765192381, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24609#issuecomment-4765192381", "createdAt": "2026-06-22T05:27:01Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "Hi,\nI've tried with the 11.0 Nightly Build (11.0-b8f0d06), which currently does not work for me, as it throws an error when i try to login:\n\nWith the Dev Nightly Build (dev-8248578) which works, the issue still persists:\n\n[Image omitted]\n\nOriginal response date: 2026-06-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4840173785, "author": "SimonTheIman", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24609#issuecomment-4840173785", "createdAt": "2026-06-30T05:24:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24609, "url": "https://github.com/glpi-project/glpi/issues/24609", "author": "SimonTheIman", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "open", "stateReason": null, "createdAt": "2026-06-19T05:26:22Z", "updatedAt": "2026-06-30T05:55:36Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Webhook URLs with explicit ports are incorrectly rejected as unsafe", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nSince the SSRF protection introduced after GLPI 11.0.4, valid webhook URLs containing an explicit port, such as are rejected by Toolbox::isUrlSafe(). The default allowlist regex is documented as being based on Symfony's UrlValidator, but the optional port expression (:[0-9]+)? is missing.\n\n[Image omitted]\n\nReproduction steps:\n1. Create a workflow on MS Teams\n2. Copy and Paste the url webhook enpoint on the webhook glpi configuration page", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "jamie.blair@peppermint.local", "text": "Root cause: Toolbox::isUrlSafe() is fine; it just applies GLPI_SERVERSIDE_URL_ALLOWLIST. The bug was in the default regex definitions: they matched protocol + host, then immediately path/query, with no optional :port segment.\nI added this line after the host/IP/IPv6 block in both allowlist regexes:\n(?: : \\d{1,5} )? # a port (optional)\nOn these files\n- src/Glpi/Application/SystemConfigurator.php after line 148\n- src/Glpi/Application/Environment.php after line 170\nAnd it works again with the port\n\nOriginal response date: 2026-06-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4838312574, "author": "Jonathan-R23", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24704#issuecomment-4838312574", "createdAt": "2026-06-29T23:19:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please open a pull request with your changes. Tests case must be added.\n\nOriginal response date: 2026-06-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4839886563, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24704#issuecomment-4839886563", "createdAt": "2026-06-30T04:32:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24704, "url": "https://github.com/glpi-project/glpi/issues/24704", "author": "Jonathan-R23", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-29T23:18:00Z", "updatedAt": "2026-06-30T04:32:27Z", "closedAt": null } }, { "title": "Global assets list / unexpected error when exporting filtered list", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8 (and 11.0.7)\n\nIssue description:\nWhen filtering Assets/Global list with Inventory number contains, all exports fail with\n\n[Image omitted]\n[Image omitted]\n\nOther filters - I tried Status - seem to work. Export of Computers, Monitors etc. via their respective lists works, too.\n\nReproduction steps:\n1. go to Assets -> Global\n2. apply filter \"Characteristics - Inventory Number\" \"contains\" \"\"\n3. search\n4. export current page as landscape pdf (or any other export)", "priority": "medium", "type": "support", "createdByEmail": "bailey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please first try with latest stable release.\n\nOriginal response date: 2026-06-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4808062733, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24685#issuecomment-4808062733", "createdAt": "2026-06-26T08:57:11Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "Sorry, I noticed the error some days ago and oversaw the new release.\n\nUpgraded to 11.0.8, error is still there.\n\nOriginal response date: 2026-06-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4808175884, "author": "troloff", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24685#issuecomment-4808175884", "createdAt": "2026-06-26T09:13:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24685, "url": "https://github.com/glpi-project/glpi/issues/24685", "author": "troloff", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-26T08:51:35Z", "updatedAt": "2026-06-26T09:34:03Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Fix checkRights() (and sibblings) for new phpstan rule", "detail": "Issue description:\nrelated pr :", "priority": "low", "type": "feature", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "It is probably impossible to completely automate this refactoring, since there may be some cases where trying to guess this automatically could result in an unexpected change, but the following case could probably be handled in our rector extension.\n\nWhen a call to these methods is made from a /front/(.form)?.php file, we can extract the expected classname from the URL. If the $rightname value of the corresponding class matches the hardcoded value, then we can replace it by a reference to the class $rightname property. See \\Glpi\\Kernel\\Listener\\RequestListener\\LegacyItemtypeRouteListener::findGenericClass().\n\nOriginal response date: 2026-06-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4798330054, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24667#issuecomment-4798330054", "createdAt": "2026-06-25T10:38:06Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "seems complicated, risky and not so fast to implement. But maybe not.\nI planned to do it by hand (search/replace across codebase).\nI'll give a shot this afternoon.\n\nOriginal response date: 2026-06-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4799036852, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24667#issuecomment-4799036852", "createdAt": "2026-06-25T12:08:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24667, "url": "https://github.com/glpi-project/glpi/issues/24667", "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "beta / rc", "enhancement" ], "state": "open", "stateReason": null, "createdAt": "2026-06-24T15:34:56Z", "updatedAt": "2026-06-25T12:08:31Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "LDAP Sync doesn't respect \"is_deleted\" field", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI have added a field in the LDAP config and want to synchronize to get the new field filled in the user data.\n\nThe sync fails because of duplicate IDs, from which 1 is in the trash, marked with the field is_deleted = 1.\n\nSync para command line shows the problem:\n\nsudo -u www-data php bin/console glpi:ldap:synchronize_users --ldap-server-id=3:\n+--------------+-----------------+\n| LDAP Servers | oventrop.de (3) |\n| LDAP Filter | |\n| Startdatum | |\n| Enddatum | |\n+--------------+-----------------+\nMöchten Sie fortfahren? [Yes/no]Yes\nVerarbeitung des LDAP-Servers \"oventrop.de\"...\nNeue Benutzer vom Server importieren \"oventrop.de\"...\n 1/1 [============================] 100%\n\nIn CommonDBTM.php line 434:\n\n User::getFromDBByCrit() expects to get one result, 2 found in query \"SELECT id FROM glpi_users WHERE user_dn_hash = 'f79399626af0065d2ca9a91b1aacfd5b'\".\n\nldap:synchronize_users [-c|--only-create-new] [-u|--only-update-existing] [-s|--ldap-server-id [LDAP-SERVER-ID]] [-f|--ldap-filter [LDAP-FILTER]] [--begin-date [BEGIN-DATE]] [--end-date [END-DATE]] [-d|--deleted-user-strategy [DELETED-USER-STRATEGY]] [-r|--restored-user-strategy [RESTORED-USER-STRATEGY]]\n\nWe now have a look at the two entries:\n\nMariaDB [glpi]> SELECT id, is_deleted FROM glpi_users WHERE user_dn_hash = 'f79399626af0065d2ca9a91b1aacfd5b'\n -> ;\n+-----+------------+\n| id | is_deleted |\n+-----+------------+\n| 135 | 1 |\n| 696 | 0 |\n+-----+------------+\n2 rows in set (0,001 sec)", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "lane.bennett@peppermint.local", "text": "Workaround:\n\nupdate glpi_users set user_dn_hash = null, sync_field = null where is_deleted = '1';\n\nOriginal response date: 2026-06-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4787569345, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24656#issuecomment-4787569345", "createdAt": "2026-06-24T08:58:56Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "AI found (closed) references that i didn't:\n\nThe persisting problem seems to be, that LDAP sync doesn't like deleted users.\n\nOriginal response date: 2026-06-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4787603979, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24656#issuecomment-4787603979", "createdAt": "2026-06-24T09:03:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24656, "url": "https://github.com/glpi-project/glpi/issues/24656", "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-24T08:46:27Z", "updatedAt": "2026-06-24T09:03:13Z", "closedAt": null } }, { "title": "Authorization assignment rules - actions types doesn't work", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5, 11.0.6, 11.0.7\n\nIssue description:\nWhen using Administration > Rules > Authorizations assignment rules, rules using the \"Assign\" action type silently fail to apply the following fields on user login:\n\n- Profiles\n- Groups\n- Entity\n- Recursive\n\nOnly the \"Active\" field is correctly applied. No error is shown in the UI, no PHP/SQL error is logged, and the rule test page only shows \"Active: Yes\" and \"Validation: Yes\" — all other actions are missing from the test output.\n\nThe issue is not related to corrupted data: direct SQL inspection of glpi_ruleactions confirms all 5 actions are correctly stored in the database:\n\nRecreating the rule from scratch does not fix the issue.\n\nPartial workaround observed: using action type \"Default group\", \"Default entity\" etc, causes the actions to appear in the test output but not be applied on login.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\n/front/ruleright.form.php\n\nReproduction steps:\n1. Create a new rule with the following criteria:\n - Email → contains → yourdomain.com\n2. Add the following actions with type \"Assign\":\n - Active → Yes\n - Entity → Root entity\n - Recursive → Yes\n - Groups → your_group\n - Profiles → your_profile\n3. Save the rule\n4. Use the \"Test\" button with an email matching the criteria\n5. Observe: only \"Active: Yes\" and \"Validation: Yes\" appear in the test result — Groups, Profiles, Entity and Recursive are absent\n6. Create a new user with a matching email and log in → only \"Active\" is applied; no group or profile is assigned\n\nExpected behavior:\nAll configured actions (Active, Entity, Recursive, Groups, Profiles) should be applied to the user on first login and should appear in the rule test output.\n\nObserved behavior:\nOnly the \"Active\" field is applied. Groups, Profiles, Entity and Recursive are silently ignored, both in the test output and at runtime.", "priority": "medium", "type": "support", "createdByEmail": "jordan.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "jordan.bennett@peppermint.local", "text": "Hello,\n\nI ran a few tests with the help of Claude AI (I'm not developper, sorry).\nHere is what I found :\n\n## Root cause analysis\n\nAfter deep investigation into the GLPI 11.0.7 source code, I identified two distinct bugs causing authorization assignment rules to silently fail for users authenticated via an SSO plugin (e.g. singlesignon).\n\n---\n\n### Bug 1 — RuleRight.php: test UI only shows \"Active\" (cosmetic)\n\nFile: src/RuleRight.php\nMethod: missing override of preProcessPreviewResults()\n\nThe rule test preview in Rule::showRulePreviewResultsForm() iterates over the top-level keys of $output to display results. However, RuleRight::executeActions() stores entities_id, profiles_id, is_recursive and groups_id inside a nested key $output[\"_ldap_rules\"], which is never promoted to the top level before display.\n\nAs a result, the test UI only shows Active: Yes and Validation: Yes — all other actions are invisible, even when the rule matches correctly and the data is properly stored in glpi_ruleactions.\n\nFix: override preProcessPreviewResults() in RuleRight to flatten _ldap_rules to top-level keys before display:\n\n---\n\n### Bug 2 — User.php: wrong auth type passed to processAllRules() in getFromSSO()\n\nFile: src/User.php\nMethod: getFromSSO() around line 2715\n\ngetFromSSO() calls processAllRules() with 'type' => Auth::EXTERNAL (value 4), but users authenticated via the native GLPI SSO mechanism are stored with authtype = Auth::DB_GLPI (value 1). The rule criterion \"Authentication type → is → Internal GLPI database\" therefore never matches.\n\nAdditionally, the result of processAllRules() is stored in $this->fields but applyRightRules() reads from $this->input[\"_ldap_rules\"], so even if the rule matched, the assignments would be lost. willProcessRuleRight() is also never called, making applyRightRules() a no-op.\n\nFix:\n\n---\n\n### Summary\n\n| # | File | Method | Impact |\n|---|------|--------|--------|\n| 1 | RuleRight.php | missing preProcessPreviewResults() | Test UI misleading — all actions invisible except Active |\n| 2 | User.php | getFromSSO() | Wrong auth type + lost _ldap_rules result — rules never applied for native SSO users |\n\nAll two bugs confirmed on GLPI 11.0.7. The database (glpi_ruleactions) is intact — the issue is purely in the PHP execution path.\n\nOriginal response date: 2026-06-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4603628047, "author": "AlexisCay", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24160#issuecomment-4603628047", "createdAt": "2026-06-02T14:51:00Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "I found this issue too on 11.0.4 I set Entity=xxx, Profile=xxx and Recursive=yes.\n\nA workaround was Reset Rules and modify again adding the default profile an recursive. Then I forced the synchronization (of LDAP users in my case) and they obtained the correct authorization.\n\n(Unfortunately, I didn't take the time to check the previous state of the rules in the database before performing the reset.)\n\nOriginal response date: 2026-06-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4753828359, "author": "ftoledo", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24160#issuecomment-4753828359", "createdAt": "2026-06-19T18:13:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24160, "url": "https://github.com/glpi-project/glpi/issues/24160", "author": "AlexisCay", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-07T07:21:57Z", "updatedAt": "2026-06-19T18:13:41Z", "closedAt": null } }, { "title": "OLA/SLA can become violated even when the ticket is pending and with a pending reason", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI have noticed on a ticket that despite being on pending, the OLA time to resolve has been violated. When the ticket is on pending, the OLA/SLA should be recalculated.\n\n[Image omitted]\n[Image omitted]\n[Image omitted]\n\nReproduction steps:\nCreate a ticket with an OLA/SLA applied. Put the ticket on pending with a pending reason, the the OLA/SLA will still become violated.\n\nEnvironment details:\nGLPI: 11.0.7 ( => /var/www/html/ithelpdesk.msnpartnership.com)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: 2 files changed\n A: inc/downstream.php\n D: install/install.php\n\nOperating system: Linux MNSP-GLPI-PROD 6.17.0-1017-azure #​17~24.04.1-Ubuntu SMP Wed May 27 21:05:32 UTC 2026 x86_64\n\nPHP: 8.3.6 fpm-fcgi\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, cgi-fcgi, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "dakota.blair@peppermint.local", "text": "Hi\nIs there any update on this? Is this confirmed to be a bug?\nThank you\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4709141194, "author": "MNSPJack", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24481#issuecomment-4709141194", "createdAt": "2026-06-15T14:47:22Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi, you'll have news if someone have time to work on this.\n\nOriginal response date: 2026-06-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4715644183, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24481#issuecomment-4715644183", "createdAt": "2026-06-16T06:31:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24481, "url": "https://github.com/glpi-project/glpi/issues/24481", "author": "MNSPJack", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-04T13:25:58Z", "updatedAt": "2026-06-16T06:31:08Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Element overflow and missing translation on user profile", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nSome ui bugs on the user overview form\n\n[Image omitted]\n\nOverflow of Verbrauchsmaterialien and missing translations.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Translations are managed on Transifex, not GitHub. If something is missing, please add it on that platform.\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4582633213, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24366#issuecomment-4582633213", "createdAt": "2026-05-30T11:15:36Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Thanks for your answer. I added the translations for created problem and created changes. However, to correctly translate\n\"New %s for this User\" I would need different Keys for tickets,problems and changes because it is \"Neues Problem... \" but \"Neue Änderung\" in German. You can get away with \"Erstelle xxx für diesen Nutzer\", which I have currently put but it sounds a bit off for a native speaker.\n\nOriginal response date: 2026-06-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4590350658, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24366#issuecomment-4590350658", "createdAt": "2026-06-01T07:15:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24366, "url": "https://github.com/glpi-project/glpi/issues/24366", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "open", "stateReason": null, "createdAt": "2026-05-28T08:27:48Z", "updatedAt": "2026-06-01T07:15:14Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "API v2 does not return emails for actors on Tickets without accounts in users (stored in tickets_users)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nThe v2 API does not return the emails of actors in Tickets without accounts in Users (stored in tickets_users)\nWhat happens: GETting returns [] when a requester just has an email that is not linked to a User. Type is not returned even when a User record is linked.\nExpected: name would be set to the email address from tickets_users, id would be, e.g. -1, the id from tickets_users (maybe as tuid) or unset, role would be as usual. Alternatively, name would be empty and an email field would be set-- this is consistent with existing behaviour, where other fields than those in the schema are returned.\n\nAffected page:\n/api.php/v2.2/doc\n\nReproduction steps:\n1. Set Setup > General > Assistance > Allow anonymous ticket creation (receiver) to \"Yes\"\n2. create a ticket via the mailgate from an email address not associated with a User record. Note the ticket number, N.\n3. Go to /api.php/v2.2/doc and authenticate, allowing all action types.\n4. Go to GET /Assistance/Ticket/{id}/TeamMember , set id to N\n5. Click Execute\n\nAdditional context:\nWhat I'm looking to do is, via the v2 API, find existing tickets not linked to a User, and link them. Adding emails to Users would help (though I think this is unsupported in API v2 at present?) going forward, but would not address existing unlinked tickets. I hope to look at the code that implements this (either in the API or the code called by the API to get the data) and submit a PR. Pointers on how to approach this would be welcome.", "priority": "medium", "type": "support", "createdByEmail": "emerson.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This isn't really an API issue, but an issue with the underlying team management code. You can see in the global Kanban for example that the anonymous assigned users are not present either. The code that is used to display the \"team\" in the ticket UI is separate. The team code was supposed to help unify how team members are fetched and managed between Tickets, Changes, Problems and Projects but it is only really used in Kanban and the new API.\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4413473356, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23999#issuecomment-4413473356", "createdAt": "2026-05-09T19:21:39Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Seems like the issue was introduced with #16064 changing from LEFT JOIN to INNER JOIN in the query as no entry exists in the user table for anonymous users (ID 0), the INNER JOIN ignores those records while LEFT JOIN had included them with the missing data set to NULL.\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4413506102, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23999#issuecomment-4413506102", "createdAt": "2026-05-09T19:37:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23999, "url": "https://github.com/glpi-project/glpi/issues/23999", "author": "Russell-Jones-OxPhys", "anonymizedAuthorEmail": "emerson.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-23T15:19:53Z", "updatedAt": "2026-05-09T19:37:32Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Ticket Created from mailgate get's first tickettemplate_id assigned", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nOn 11.0.6 when a ticket was received by mailgate it gets the field glpi_tickets.tickettemplate_id equals 0 so the template displayed whas the one associated with the user viewing the ticket.\n\nOn 11.0.7 it gets the value of the default ticket template for entity and if the user viewing the ticket (techs in my case) have a differente template set on their profile that profile is only applied (and saved on glpi_tickets.ticketstemplate_id) when the technician saves something on the ticket.\n\nReproduction steps:\n1. hide some fields on default ticket template\n2. create another ticket template with all fields visible\n3. set this created on the techs profile\n4. receive a ticket on mailgate\n5. access ticket you should see the default view (glpi_tickets.tickettemplates_id = 1)\n6. save something and the template changes to the one you have set on your profile (glpi_tickets.tickettemplate_id = 2)\n7.", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "harper.blair@peppermint.local", "text": "The solution proposed for the category set on #24082 can't be aplied because the ticket when created by mailgate don't gets a category assigned\n\nOriginal response date: 2026-05-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4396449725, "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24165#issuecomment-4396449725", "createdAt": "2026-05-07T10:50:23Z" } }, { "userEmail": "morgan.blair@peppermint.local", "text": "When updating to version 11.0.7, the following message was sent to the log while attempting to create a support ticket:\n\nglpi.ERROR: * An error occured during the form Form_1 MySQL query error: Out of range value for column 'tickettemplates_id' at row 1 (1264)\n\nOriginal response date: 2026-05-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4396551042, "author": "MeskitaNetzarim", "anonymizedAuthorEmail": "morgan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24165#issuecomment-4396551042", "createdAt": "2026-05-07T11:06:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24165, "url": "https://github.com/glpi-project/glpi/issues/24165", "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-07T10:48:12Z", "updatedAt": "2026-05-07T11:07:12Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Automatic follow-up is not added when pending reason frequency is set only on task or follow-up", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.24\n\nIssue description:\nWhen a new pending reason is created without configuring the automatic follow-up frequency, and this pending reason is later used in a new task or follow-up where the frequency is manually set to \"every day\", the automatic follow-up is not added to the ticket. The automatic follow-up is only added when the pending reason was originally created with the automatic follow-up frequency already configured.\n\nExpected result: the automatic follow-up should be added to the ticket even when the frequency is manually configured in the task or follow-up, without requiring the pending reason to have this frequency predefined.\n\nReproduction steps:\n1. Create a new pending reason without configuring the automatic follow-up frequency.\n2. Create a new task or follow-up in GLPI and select this pending reason.\n3. Manually set the automatic follow-up frequency to \"every day\".\n4. Save the task or follow-up.\n5. Check the ticket and verify that the automatic follow-up is not added.\n6. Create another pending reason, this time with the automatic follow-up frequency already configured.\n7. Use this new pending reason in a task or follow-up and save it.\n8. Check the ticket and verify that the automatic follow-up is added.", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "jamie.blair@peppermint.local", "text": "Hello! Any update on this issue? Skyler Adler, Taylor Adler, Skyler Adler\n\nBy the way, it’s quite easy to reproduce and identify this bug.\n\nOriginal response date: 2026-04-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4296775580, "author": "serviceticst", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23775#issuecomment-4296775580", "createdAt": "2026-04-22T13:53:09Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nFirst of all, please do not ping anyone not involved in issues.\n\nCommunity issues are handled on a best effort basis. This is not professional support.\nYou can also consider opening a PR to fix.\n\nRegards.\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4311768539, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23775#issuecomment-4311768539", "createdAt": "2026-04-24T08:31:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23775, "url": "https://github.com/glpi-project/glpi/issues/23775", "author": "serviceticst", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-06T20:09:42Z", "updatedAt": "2026-04-24T08:32:09Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "CSV export from “Assets → Global” truncated to ~300 rows while “Computers” export returns full 18,000 rows", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHello,\n\nOn GLPI 11.0.4, the CSV export from the Assets → Global view does not contain all items.\nWith the same instance and PHP configuration, the Computers view exports the full dataset correctly, so this seems to be a bug specific to the “Global” view export.\n\nAffected page:\n\nReproduction steps:\n1. Have an instance with about 18,000 computers in the inventory.\n\n2. Go to Assets → Computers.\n\n3. Set the list to show all items (then use Export → CSV → All pages).\n\n4. Observe that the resulting CSV contains ~18,000 rows (all expected items).\n\n5. Now go to Assets → Global.\n\n6. Use Export → CSV → All pages.\n\n7. Open the downloaded CSV and count the lines (or use wc -l on the server).\n\nAdditional context:\nThanks in advance for your help, and tell me if you need more debug info or a test query to run on the database.", "priority": "medium", "type": "support", "createdByEmail": "parker.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with a up to date GLPI version - or a nightly build, and also without any plugin.\n\nOriginal response date: 2026-04-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4279971391, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23967#issuecomment-4279971391", "createdAt": "2026-04-20T10:45:21Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm. The all pages exports for Global Assets are limited to N items per type where N is the results per page limit.\nThe LIMIT is removed for the union request, but for the individual queries it is forced to the page limit. Apparently this was for performance reasons, but maybe it should be bypassed for export_all cases.\n\nThis issue should affect any union searches.\n\nOriginal response date: 2026-04-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4290775871, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23967#issuecomment-4290775871", "createdAt": "2026-04-21T18:09:45Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23967, "url": "https://github.com/glpi-project/glpi/issues/23967", "author": "elidjah", "anonymizedAuthorEmail": "parker.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-20T09:27:50Z", "updatedAt": "2026-04-21T18:10:37Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "A validation error during change creation resets linked problem", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen creating a change from a problem, the link is missing if during change creation the validation failed.\n\nReproduction steps:\n1. Configer a change template and make assigning an element mandatory\n2. Create a change from a problem\n3. try to save with a missing element\n4. Add an computer\n5. save again\n6. -> Link to Problem is missing", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue on 11.0.6 or the latest 11.0 development branch.\n\nPlease include all the requested information from the bug report template including log output and GLPI setup information.\n\nOriginal response date: 2026-04-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4246341209, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23851#issuecomment-4246341209", "createdAt": "2026-04-14T18:48:57Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Hi,\nthanks for looking into that. I attached the sysinfo of my test instance\nsysinfo.txt\n\nIn addition here is a step by step guide with images how to recreate:\nSetup:\n- Change Default change template to require category and associated element\n\n[Image omitted]\n\n- Create a Problem\n- Create a Computer asset\n- Create a Problem category\n\nTrigger Bug:\n - Create a change from the problem\n\n[Image omitted]\n\n- On the new change click add without setting category and associated element ( This is crucial otherwise it works)\n- Set category and element\n- click add again\nResult:\n\n[Image omitted]\n\nAs you can see the problem is not linked to the change as it would be if we correctly set category and associated element before adding the change.\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4250152491, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23851#issuecomment-4250152491", "createdAt": "2026-04-15T07:40:45Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23851, "url": "https://github.com/glpi-project/glpi/issues/23851", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-13T18:24:14Z", "updatedAt": "2026-04-15T07:53:40Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Suppliers Missformation", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nI have separate entities for different departments within my organization, including a procurement-focused entity that manages our suppliers. All of our vendors have been registered under this specific sub-entity. However, these suppliers are not showing up in the 'Global View' of the institution, unlike the data from other areas.\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Are you connected to the root entity with child entities included?\n\nOriginal response date: 2026-03-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4137841903, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23634#issuecomment-4137841903", "createdAt": "2026-03-26T19:59:24Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Yeah, I noticed that when I use a child entity for the suppliers, the root entity can't see all of them.\n\nOriginal response date: 2026-04-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4177955855, "author": "Killink61", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23634#issuecomment-4177955855", "createdAt": "2026-04-02T13:38:16Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23634, "url": "https://github.com/glpi-project/glpi/issues/23634", "author": "Killink61", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-25T22:23:02Z", "updatedAt": "2026-04-15T05:55:42Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Project Task and Project Task template is different", "detail": "Affected version:\nGLPI11\n\nIssue description:\nSome fields of project task are not included in project task template, such as Team members and the 2 checkbox \"Automatically calculate\".\n\n[Image omitted]\n\n[Image omitted]\n\nAnd the template of project or project task should be same to ticket template, we can predefine some fields of the form.\n\n[Image omitted]\n\nAffected page:\nfront/projecttasktemplate.form.php, front/projecttask.form, /front/tickettemplate.form.php\n\nReproduction steps:\n1. click tools-project\n2. open one of the project, and click the project task\n3. then click the \"add a task\"\n4. click \"tamplates\" on the top menu\n\nEnvironment details:\nGLPI: 11.0.0 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\n\nPHP: 8.3.19 fpm-fcgi\n\nPHP extensions: Core, date, libxml, hash, pcre, zlib, filter, json, SPL, random, Reflection, session, standard, openssl,\nsockets, cgi-fcgi, bcmath, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, iconv, intl, ldap, exif,\nmysqlnd, PDO, Phar, SimpleXML, sqlite3, tokenizer, xml, xmlwriter, xsl, mysqli, pdo_mysql, pdo_sqlite, sodium, xmlreader, zip,\nZend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"8M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"2M\"\n\nWeb server: Apache/2.4.63 (Rocky Linux) OpenSSL/3.2.2 ()\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:145.0) Gecko/20100101 Firefox/145.0\n\nDatabase:\n\nServer Software: MariaDB Server\n\nServer Version: 10.11.11-MariaDB\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION", "priority": "medium", "type": "support", "createdByEmail": "bailey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "And the template of project or project task should be same to ticket template, we can predefine some fields of the form.\n\nThis part is not a bug. Feel free to make the suggestion, or upvote it if it was already suggested, on UserEcho.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3500042470, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21804#issuecomment-3500042470", "createdAt": "2025-11-07T01:12:44Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "This issue seems more complex that I originally thought. While making a test that ensured parity between the task and template fields, I noticed that for some reason, project tasks have 2 different template systems. First, and the only one that seems completely usable in the UI, is a separate Project Task Template type. The second is the kind used by assets using a template_name and is_template field.\n\nSince project tasks satisfy the \"maybeTemplate\" criteria but don't actually use it in the UI, there is a broken action to create a template from an existing project task. It does technically work, but it creates templates that are not normally usable.\n\nIMO, the separate ProjectTaskTemplate type and the ability to select the template again after creating the task does not make sense. It should be migrated to the same template system assets use, or migrated to use the system Tickets use.\n\nOriginal response date: 2025-12-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3699128333, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21804#issuecomment-3699128333", "createdAt": "2025-12-30T11:55:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21804, "url": "https://github.com/glpi-project/glpi/issues/21804", "author": "DWXXX", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-11-05T10:27:56Z", "updatedAt": "2026-04-05T12:19:19Z", "closedAt": null } }, { "title": "Actors Infinite Scroll not working", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen we add an actor to a ticket - we got a dropdown, that show us users and groups to choose from.\nThe issue is that this list isn't infinitely loaded.\n\nExample: we have 26 users and 190 groups, when we open dropdown we see 26 users and 100 groups, other 90 groups never gets to load.\n\nI provide a PR that solved this issue for me\n\nReproduction steps:\n1. Open a new ticket\n2. Try to add actor using dropdown\n3. Scroll down to the bottom of the list\n4. You'll see, that you can choose from one of 100 groups however you have more that that", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "11.0.4 is outdated. Please first try to reproduce on latest stable, without any plugin.\n\nOriginal response date: 2026-03-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4134890169, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23644#issuecomment-4134890169", "createdAt": "2026-03-26T13:37:57Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The issue persist. I updated my instance of GLPI. I'll provide PR\n\n[Image omitted]\n\nOriginal response date: 2026-03-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4135116499, "author": "akstis-typer", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23644#issuecomment-4135116499", "createdAt": "2026-03-26T14:02:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23644, "url": "https://github.com/glpi-project/glpi/issues/23644", "author": "akstis-typer", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-26T13:37:05Z", "updatedAt": "2026-03-27T07:25:32Z", "closedAt": null } }, { "title": "No attachement in email notification", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.24\n\nIssue description:\nHi,\n\nWe upgraded to GLPI version 10.0.24 in order to fix the issue with sending email attachments. However, the problem is still not resolved.\n\nSometimes the attachments are correctly included in the email, but sometimes they are missing. In those cases, we have to reopen the ticket and recreate the solution so that the attachment is properly sent by email.\n\nThis issue is really problematic for us because we send resolutions to users who do not have direct access to GLPI.\n\nWe also noticed that this problem seems to occur only for email notifications sent to external users (users who do not have access to GLPI). They do receive the email, but the attachment is missing.", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "rowan.blair@peppermint.local", "text": "We have the same issue, but it happens for all users.\nqueuednotification is set to CLI, sending the notification manually correctly sends the email with attachments.\nThe behaviour is the same as before the 10.0.24 update.\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4073385990, "author": "cihlmi", "anonymizedAuthorEmail": "rowan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23430#issuecomment-4073385990", "createdAt": "2026-03-17T09:04:47Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Do you have any updates regarding this bug, which is still present in version 10.0.24?\nSince upgrading from GLPI 10.0.19 for security reasons, we’ve been experiencing an issue where notifications are no longer attached to emails sent to our external requesters. This is causing significant problems for us.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4117174262, "author": "xseth03", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23430#issuecomment-4117174262", "createdAt": "2026-03-24T10:44:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23430, "url": "https://github.com/glpi-project/glpi/issues/23430", "author": "xseth03", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-10T09:42:16Z", "updatedAt": "2026-03-24T10:44:09Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Unable to add a picture from Camera app", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen creating a ticket in GLPI using an Android Device and clicking \"Add an attachement\". Selecting Camera option to take a picture and upload it directly, GLPI is unable to accept the picture.\nIt seems that the input missed the option accept=\"image/*;capture\" to accept it.\n\nReproduction steps:\n1. Create a new ticket\n2. Click \"add and attachement\"\n3. Choose the Camera option\n4. Take a picture\n5. Accept the picture\n6. The Camera app closes and GLPI doesn't trigger the upload/accept the picture", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I don't see where it is valid for \"capture\" to be specified in the accept attribute. Do you have a reference for this?\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4114958625, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22735#issuecomment-4114958625", "createdAt": "2026-03-24T02:30:57Z" } }, { "userEmail": "harper.bennett@peppermint.local", "text": "I guessed it was a shortcut for the capture attribute referenced here and here but the standard should be: accept=\"image/*\" capture=\"environment\"\n\nI'm not sure it would make sense to allow the user uploading selfies in this case\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4116915605, "author": "kranack", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22735#issuecomment-4116915605", "createdAt": "2026-03-24T10:05:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22735, "url": "https://github.com/glpi-project/glpi/issues/22735", "author": "kranack", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": null, "createdAt": "2026-01-19T13:42:57Z", "updatedAt": "2026-03-24T10:05:50Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Expiration date + notice field is incorrect for tacit renewal contracts", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nI have a contract that is tacitly renewed every year, with a renewal period of 12 months and a 2 months notice.\nThe field \"Expiration date + notice\" adds (or rather removes) the notice period to the initial end date instead of the renewed expiration date once the contract has been tacitly renewed.\n\n[Image omitted]\n\n_Informations :_\nCurrent date : 11/02/2026\nInitial contract end date : 2025-08-28\nRenewal period : 12 months\nNotice : 2 months\nExpiration : 2026-08-28 (Initial contract end date + renewal period, the contract has been correctly renewed)\n\n_Expected outcome :_\nExpiration date + notice : 2026-06-28 (2 months prior to expiration date).\n\n_Current outcome :_\nExpiration date + notice : 2025-06-28 (2 months prior to initial contract end date).", "priority": "medium", "type": "support", "createdByEmail": "cameron.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I think this is being addressed in #23358\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4043452185, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23084#issuecomment-4043452185", "createdAt": "2026-03-12T02:24:02Z" } }, { "userEmail": "cameron.blair@peppermint.local", "text": "I downloaded and replaced the 3 files from the PR on my instance and my specific issue is still there, the PR is addressing the virtual_expiration date in the test files and not the expire_notice.\n\nAfter reviewing the content of the files and testing said PR, it seems to me the logic of #23358 on renewal is wrong (but as Herafia said on a comment, adjustments need to be made on the contracts anyway).\n\nFrom an end user perspective :\n- The contract end date being - 1 day is a great addition (and it should also be - 1 day for tacit contracts)\n- The express renewal contracts should NOT have their virtual_expiration date be automatically bumped up. The express mention implies a manual action is needed to renew the contract.\n- The tacit renewal period should be the periodicity, and not the initial contract period (\"addWarranty\" field)\n\nWhat I think _would_ be a great solution is to have a dedicated tab in contracts for \"Periods\", that would essentially look like the \"Costs\" tab with a line for each period. Those periods would be auto generated at the renewal date for tacit contracts, and generated manually via a \"Renew contract\" massive action for express renewal. A great bonus would be to have a \"max n° of renewal\" for tacit contracts as well.\n\nNow that I know in which files to look, I will try to fix my specific issue with a PR, but I think there is a lot of potential around the contracts feature, and I would love to help\n\nOriginal response date: 2026-03-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4053830697, "author": "troncoli", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23084#issuecomment-4053830697", "createdAt": "2026-03-13T09:30:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23084, "url": "https://github.com/glpi-project/glpi/issues/23084", "author": "troncoli", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-11T10:43:04Z", "updatedAt": "2026-03-13T12:59:33Z", "closedAt": null } }, { "title": "Date format inconsistency between Forms input and variable output", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.5\n\nIssue description:\nThere is an inconsistency in how dates are handled when using the native form builder in GLPI 11. Even when the global date format is configured correctly, the output of a date variable does not follow the configured format.\n\nExpected behavior:\nThe date should appear in the ticket (or output) using the configured system format: 11/03/2026\n\nObserved behavior:\nThe date is displayed using the database/ISO format: 2026-03-11\n\nReproduction steps:\n1. Go to Setup → General → Defaults.\n2. Set the date format to d/m/Y.\n3. Create a form using the native form builder.\n4. Add a Date field to the form.\n5. In the form processing (for example in the generated ticket description), insert the variable corresponding to the date response, such as:\n(#Answer: Submission date) (or the equivalent variable for the date field)\n6. Submit the form and enter a date using the UI.", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "When creating a ticket from a form, those variables are resolved and added as static content in the description. The user submitting the form, which is sometimes not a user at all but an anonymous submission, may not have the same date format as everyone who would view the ticket. Re-formatting it for everyone viewing the ticket may be complex.\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4047111646, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23458#issuecomment-4047111646", "createdAt": "2026-03-12T14:15:29Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Thanks for the clarification.\n\nIn practice, this ends up being a bit confusing for my users when they submit the form. They enter the date in the format shown in the interface, but when the ticket is created the same date appears in a different format.\n\nIt would be great if the output could either follow the language/locale used when the form was submitted or respect the global date format configured in GLPI.\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4049930689, "author": "pedroalves5770", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23458#issuecomment-4049930689", "createdAt": "2026-03-12T20:45:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23458, "url": "https://github.com/glpi-project/glpi/issues/23458", "author": "pedroalves5770", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "open", "stateReason": null, "createdAt": "2026-03-12T14:08:51Z", "updatedAt": "2026-03-12T20:45:48Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Entity selection via CTRL+ALT+E requires multiple clicks when searching by name", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nTitle\nEntity selection via CTRL+ALT+E requires multiple clicks when searching by name\n\nGLPI version\n11.0.5\n\nExpected behavior\nEntity is selected immediately\n\nActual behavior\nFirst click highlights the row\nSecond click triggers a console warning\nThird click finally switches entity\n\nConsole warning\nForm submission canceled because the form is not connected (central.php)\n\nAdditional notes\nIssue occurs only after using the text search filter\nSelecting an entity directly (without search) from the list/tree works correctly on first click\nReproducible on multiple browsers (Chrome, Firefox), including private mode\nNo browser extensions\nSuggests an issue in the search-filtered selection workflow (Vue re-render vs legacy form submit)\nFirst issue on GitHub for me, please be kind if I made a mistake ;-)\n\nReproduction steps:\n1. Press CTRL + ALT + E to open the entity selector\n2. Type part of the entity name (e.g., \"lux\")\n3. Click the matching entity in the filtered results\n→ First click highlights\n→ Second click shows warning\n→ Third click selects\n\nIf selecting directly from the list/tree (no text search), entity is selected on first click.\n\nEnvironment details:\nSelf-Hosted, installed with GLPI best practices.", "priority": "medium", "type": "support", "createdByEmail": "logan.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "logan.bennett@peppermint.local", "text": "Hi, any update on this annoying bug ?\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3992619851, "author": "xtrem57", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22935#issuecomment-3992619851", "createdAt": "2026-03-03T17:46:39Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I spent some time debugging this and it seems like an issue with the library used to display the tree, not GLPI.\nWhen it is not working properly, the tree item gets set to focused, then active, and then finally allows the buttons to be clicked to change entity.\nWhen it is working the button, which is just a basic form submit button, obviously works immediately. However, clicking on the item outside of the button also just immediately goes to an active state.\n\nIf I add a click event listener to the buttons and follow the steps to recreate the issue, the listener doesn't fire until you click 3 times. So, something in FancyTree is intercepting click events and stopping additional listeners from working.\n\nThere is already a plan to rewrite the entity selector in Vue without FancyTree for GLPI 12, and this issue doesn't exist in the rewrite.\nI don't have a workaround or fix for GLPI 11 at the moment.\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4046716700, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22935#issuecomment-4046716700", "createdAt": "2026-03-12T13:21:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22935, "url": "https://github.com/glpi-project/glpi/issues/22935", "author": "xtrem57", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-01-31T14:06:59Z", "updatedAt": "2026-03-12T13:21:28Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Unexpected redirect when adding Child Service Catalog Category", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen adding a \"New child Service catalog category\" from the Forms tab of an existing Service catalog category, the system redirects the browser to the configuration page of the newly created child. If the user doesn't notice the URL or the header changed, they might end up creating a \"chain\" of nested categories (Grandparent > Parent > Child > Grandchild) instead of a flat list of subcategories under one parent.\n\n[Image omitted]\n\nThe user should remain on the current (parent) category page, with the \"Sons of [Category]\" list updated to show the new entry, allowing for the quick creation of multiple subcategories.\n\nAffected page:\n/front/form/category.form.php\n\nReproduction steps:\n1. Go to Administration > Forms > Service catalog categories.\n2. Select an existing category.\n3. Click on the Service catalog categories tab (the one showing children/sons).\n4. Enter a name in the \"New child Service catalog category\" field.\n5. Click the [Add] button.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "GLPI is following the user's preference for \"Go to created item after creation\". It does cause issues, but I guess this is a desired preference rather than GLPI assuming what it should do based on context.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3880915711, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23076#issuecomment-3880915711", "createdAt": "2026-02-10T21:47:27Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I tested and you're right, I didn't even know this flag existed. But I think that this page should be an exception to this behavior, or at least it could redirect to the first tab of the created item to avoid creating a \"chain\" of nested categories (Grandparent > Parent > Child > Grandchild) instead of a flat list of subcategories under one parent.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3881038971, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23076#issuecomment-3881038971", "createdAt": "2026-02-10T22:17:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23076, "url": "https://github.com/glpi-project/glpi/issues/23076", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-02-10T21:36:24Z", "updatedAt": "2026-03-03T21:18:46Z", "closedAt": null } }, { "title": "Search and Computer overview takes very very log if Memory and Hard Drive Size is included in view", "detail": "Affected version:\n10.0.18\n\nIssue description:\nWhen adding Components - Memory and/or Components - Hard drive size to Select default items to show, the loading time of gobal searches and opening Computer Assets tooks very very long.\n\nAffected page:\n\nReproduction steps:\n1. Adding these both values to personal view\n2. Start a search or open the computer view\n\nAdditional context:\nThe following statement took 30 secs - all others are fine.\n\nSo either display a warning on activating these calculated values or cache them in any way or do not do calculations in sql?", "priority": "high", "type": "support", "createdByEmail": "sage.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "parker.blair@peppermint.local", "text": "following the ticket because I often see the same performance issue. Of course the joins are huge and performance improvements would probably be very difficult.\nA IMHO very valid workaround would be to be able to switch forth and back between global and personal view (without having to delete the personal view). So, users could work on a slim global view and switch to a complex personal view only when they really need the data.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3953425477, "author": "Mirkk", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21019#issuecomment-3953425477", "createdAt": "2026-02-24T16:51:54Z" } }, { "userEmail": "sage.bennett@peppermint.local", "text": "Would be cool to have more than 2 views ;) maybe nameable\n\nOriginal response date: 2026-03-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3979832190, "author": "Megachip", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21019#issuecomment-3979832190", "createdAt": "2026-03-01T12:01:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21019, "url": "https://github.com/glpi-project/glpi/issues/21019", "author": "Megachip", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "open", "stateReason": null, "createdAt": "2025-09-16T08:41:10Z", "updatedAt": "2026-03-01T12:01:34Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Move monitor specific fields to model", "detail": "Issue description:\n- ports\n- size\n- ...\n\nProbably due to the legacy of GLPI, a few fields of monitor are directly part of the main item and should be placed under the model.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "noel.blair@peppermint.local", "text": "Defining the type and number of ports per monitor model would be very helpful given the limited number of ports available... Adding USB ports, VGA (instead of sub-d)... and defining it per model instead of per monitor.\nLike to add bluetooth...\n\nOriginal response date: 2026-02-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3884709201, "author": "fab44240", "anonymizedAuthorEmail": "noel.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/17380#issuecomment-3884709201", "createdAt": "2026-02-11T14:16:03Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Noel Blair this is off-topic. Please use suggestions website for RFEs.\n\nOriginal response date: 2026-02-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3884824735, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/17380#issuecomment-3884824735", "createdAt": "2026-02-11T14:33:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 17380, "url": "https://github.com/glpi-project/glpi/issues/17380", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-06-28T09:00:27Z", "updatedAt": "2026-02-11T14:33:56Z", "closedAt": null } }, { "title": "Reject unknown emails", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello everyone, my goal is to set up notifications for clients (external users) who are not in the GLPI database, informing them that their message was received but could not be processed because they are not in the database.\n\nOn versions below 11.0.4> it worked, I remember that I edited some file, but after the updates it doesn't work.\n\n[Image omitted]\n\nI may have changed the text of the message using this method, but now even this default text is not being sent.", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "On versions below 11.0.4> it worked, I remember that I edited some file, but after the updates it doesn't work.\n\nWe cannot support hacks you made on your side.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3869788540, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23032#issuecomment-3869788540", "createdAt": "2026-02-09T07:17:55Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "I pointed to the link as an example of how it used to help achieve the desired goal. but after the latest updates, the method listed on the link does not work and the standard functionality that I reflected in the screenshot does not work.\n\nSo I created an issue to find a solution to the problem.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3869799236, "author": "Smiley-k", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23032#issuecomment-3869799236", "createdAt": "2026-02-09T07:20:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23032, "url": "https://github.com/glpi-project/glpi/issues/23032", "author": "Smiley-k", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-05T21:29:05Z", "updatedAt": "2026-02-09T07:20:41Z", "closedAt": null } }, { "title": "Dictionaries Bug", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.1\n\nIssue description:\nHello,\n\nI upgraded my GLPI installation from version 10.0.16 to version 11.0.1. Everything worked fine after installation until I created two rule in the manufacturers dictionary, after glpi display an error in manufaturers page and not display any data.\n\nAffected page:\n\nReproduction steps:\nIn dictionary i have cretaed rules\n\nHTTP\n\nManufacturer regular expression matches /^https?:\\/\\//i\nManufacturer Assign Generic Manufacturer\n\nIBM\nManufacturer regular expression matches /IBM\\s/\nManufacturer contains IBM\nManufacturer Assign IBM\n\nand applied \"Replay the dictionary rules\"\n\nEnvironment details:\nUbuntu 24.04.3 LTS\nmysqld Ver 10.11.14-MariaDB-0ubuntu0.24.04.1 for debian-linux-gnu\npgp-fpm8.3\nnginx version: nginx/1.24.0", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "11.0.1 is outdated. Please check if you reproduce with latest stable release, and without any plugins.\n\nOriginal response date: 2026-02-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3846156410, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22999#issuecomment-3846156410", "createdAt": "2026-02-04T08:54:54Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "Hello,\nas you sugest, i have upgraded to 11.0.5 but i have same issue\n\n[2026-02-04 09:39:40] glpi.CRITICAL: * Uncaught PHP Exception Twig\\Error\\RuntimeError: \"An exception has been thrown during the rendering of a template (\"CommonDBTM::isMassiveActionAllowed(): Argument #1 ($items_id) must be of type i\nnt, null given\") in \"components/search/table.html.twig\" at line 135.\" at table.html.twig line 135\n Backtrace :\n ./templates/components/search/table.html.twig:135\n ./vendor/twig/twig/src/Template.php:358 Twig\\Template->yield()\n ./vendor/twig/twig/src/Template.php:373 Twig\\Template->display()\n ./vendor/twig/twig/src/TemplateWrapper.php:51 Twig\\Template->render()\n .../twig/twig/src/Extension/CoreExtension.php:1518 Twig\\TemplateWrapper->render()\n ...tes/4d/4d690df561bc44afabd95dac382cf5a4.php:147 Twig\\Extension\\CoreExtension::include()\n ./vendor/twig/twig/src/Template.php:402 TwigTemplate_25507905388ad9f4d6bd229db0964f87->doDisplay()\n ./vendor/twig/twig/src/Template.php:358 Twig\\Template->yield()\n ./vendor/twig/twig/src/TemplateWrapper.php:61 Twig\\Template->display()\n .../Glpi/Application/View/TemplateRenderer.php:188 Twig\\TemplateWrapper->display()\n ./src/Glpi/Search/Output/HTMLSearchOutput.php:214 Glpi\\Application\\View\\TemplateRenderer->display()\n ./src/Glpi/Search/SearchEngine.php:690 Glpi\\Search\\Output\\HTMLSearchOutput->displayData()\n ./src/Glpi/Search/SearchEngine.php:646 Glpi\\Search\\SearchEngine::showOutput()\n : Glpi\\Search\\SearchEngine::show()\n ...Application/View/Extension/PhpExtension.php:105 call_user_func_array()\n ...ates/83/83b49924d20478424e4a206a5bead745.php:55 Glpi\\Application\\View\\Extension\\PhpExtension->call()\n ./vendor/twig/twig/src/Template.php:402 TwigTemplate_dd5b9e23f4215e75a1cbba3ea00ad299->doDisplay()\n ./vendor/twig/twig/src/Template.php:358 Twig\\Template->yield()\n ./vendor/twig/twig/src/Template.php:373 Twig\\Template->display()\n ./vendor/twig/twig/src/TemplateWrapper.php:51 Twig\\Template->render()\n .../Glpi/Application/View/TemplateRenderer.php:170 Twig\\TemplateWrapper->render()\n ./src/Glpi/Controller/AbstractController.php:68 Glpi\\Application\\View\\TemplateRenderer->render()\n ./src/Glpi/Controller/GenericListController.php:51 Glpi\\Controller\\AbstractController->render()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\GenericListController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Sym\n\n[Content truncated.]\n\nOriginal response date: 2026-02-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3846389413, "author": "vitalev", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22999#issuecomment-3846389413", "createdAt": "2026-02-04T09:44:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22999, "url": "https://github.com/glpi-project/glpi/issues/22999", "author": "vitalev", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-04T08:27:23Z", "updatedAt": "2026-02-08T14:53:10Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Predefined technician group from template is not added to tickets created via simplified interface", "detail": "Affected version:\n10.0.19\n\nIssue description:\nWhen creating a ticket through the simplified interface using a template that has a predefined technician group, the resulting ticket does not include the technician group.\n\nScreenshots:\n\nTemplate \"Test Template\" with technician group predefined\n[Image omitted]\n\nCreate a ticket with category related to \"Test Template\" in simplified interface\n[Image omitted]\n\nTicket created without Technician Group (Assigned to)\n[Image omitted]\n\nEnvironment details:\nWithout any plugin activated\n\nAdditional context:\n- The fix for issue #19590 involves observer groups; maybe it could help with this issue\n- I am sharing some log records that appear starting from the update to version 10.0.19, but they seem to be mostly associated with issue #20641.", "priority": "medium", "type": "support", "createdByEmail": "riley.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI confirm the issue.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611585776, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20832#issuecomment-3611585776", "createdAt": "2025-12-04T11:08:36Z" } }, { "userEmail": "micah.blair@peppermint.local", "text": "Good afternoon,\nWhen opening a ticket using the simplified interface, I cannot auto-assign a technician in any way\n\n - Adding in the ITIL Category\n - Adding in the Template\n - Adding a business rule.\n\nAll options fail. Unfortunately I was forced to upgrade to 10.0.22 because of the latest CVEs but this bug completely broke my workflow.\n\nPlease let me know if I can be of any help.\n\n-EDIT-\nI can now add using the ITIL Category, I had to configure in the Entities configuration menu. Stragely, before updating I did not had to change anything there.\n\nOriginal response date: 2026-02-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3835885794, "author": "iohann95", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20832#issuecomment-3835885794", "createdAt": "2026-02-02T15:29:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20832, "url": "https://github.com/glpi-project/glpi/issues/20832", "author": "racingfoss", "anonymizedAuthorEmail": "riley.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-08-29T13:15:50Z", "updatedAt": "2026-02-02T17:45:33Z", "closedAt": null } }, { "title": "User-based filtering for webhook activation", "detail": "Contribution description:\nDescription :\nCurrently, when a webhook is configured in GLPI, it is triggered on every creation or modification of an object, regardless of who performs the action (end user, technician, or automated process).\nThis becomes an issue when an external system updates an asset via the API (e.g., a PATCH request to add a reconciliation key): such an update triggers the webhook again, which sends a new event to the external system, potentially creating infinite event loops.\n\nIt would be very useful to add a filter based on the user who performed the last modification, in order to better control when the webhook is triggered.\n\nUse cases:\n\n- Prevent a webhook from being triggered if the modification is made by an end user.\n- Trigger the webhook only if the modification is made by a technician or a technical account.\n- Exclude specific profiles/actors from triggers to avoid unnecessary events or loops with external integrations.\n\nBenefits:\n\n- Prevent event loops when integrating with external systems.\n- Reduce noise by avoiding unnecessary webhook calls.\n- Provide more flexibility and granularity in integrations with third-party tools.\n\nSteps to reproduce:\n\n- Create a webhook in GLPI.\n- Do not set any filter → every object modification generates an event.\n- Go to the Filter tab and create a filter: currently, you can filter by last modification author, but only for notes.\n- Missing feature: ability to filter by last modification author of the asset or object itself.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "Skyler Adler Hello, I noticed that this issue has been removed from the list of pending tasks. Does this mean that the idea has been abandoned? I'm following up just to get a sense of its future and whether this is of interest to you, and if it's likely to be implemented in the short or medium term. Thank you in advance for your reply.\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3618938576, "author": "Yann843", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20902#issuecomment-3618938576", "createdAt": "2025-12-05T23:19:08Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Hello Micah Bennett imo, this is a feature request, I've flagged it as his so we can discuss it later for it's implementation in the next version of GLPI.\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3627690769, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20902#issuecomment-3627690769", "createdAt": "2025-12-08T15:58:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20902, "url": "https://github.com/glpi-project/glpi/issues/20902", "author": "Yann843", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-09-03T09:26:39Z", "updatedAt": "2025-12-08T15:58:43Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Accessibility Improvement - GLPI 11.x there are a lot of buttons and form elements without aria labels or titles", "detail": "Issue description:\nHello GLPI Community and GLPI Engineering Team,\n\nI would like to report some accessibility issues to you about the new GLPI 11.x version.\nI have a visual loss and working with screen reader for my daily computer usage . I am mainly working with JAWS, but sometimes I validate the applications with Narrator (Windows built in screen reader) and NVDA (Open source and freely available screen reader) as well.\nPlease note I have collected some of my findings with manual detection using my screen reader, but I also used Accessibility Insight for Web (Chromium based extension).\nYou can find the extension in the Chrome or Microsoft Edge Extension store or you can find more info in the given URL.\n\nI used the \"Fast pass\" option to generate the accessibility issues. Please find as a attachment.\n\nPlease note I have collected only from two pages, but as I could confirm all of the form or dropdown or button has the same issue as any of the menues.\n\n1. Buttons do not have aria label text on the pageNavigation page (left side)\n As I attached the result from the accessibility Insight for Web the following buttons:\n Assets, Assistance, Management, Tools, etc. buttons do not have aria labels or title. Also it worth to mentioned when I collapsed the navigation bar my screen reader can only read the following \"Buttons without labell\" on each of the mentioned buttons.\n\n2. Collapse menu\n When I navigate to the \"Collapse menu\" and hit my space or enter key after the button has no aria label or title.\n 3. Missing Aria labels for the keyboard shortcuts\n Somehow the Narrator and the NVDA could read some of the navigation menu keyboard shortcuts for example : Computer - Alt+o, Software - Alt+s, Home - Alt+1. However my JAWS could not read the keyboard shortcuts for these menus. Interesting when I asked a person who has better eyes she said that when she tried with mouse to points to those menues which has keyboard shortcut the tooltip did not show the shortcut for the menus.\n I suggest to add the aria label for the menues with the shortcuts as well as for the tooltip.\n 4. Form and drop down elements do not have title and aria labels\n When I am adding a new computer there are 9 dropdown list without title and aria labels. Also one other important thing with a keyboard there is no way to move when I open a dropdown list and it also worth to highlighted with screen reader nothing to read with it. It means I cannot hear anything when I am trying to moving between the listed elements inside te dropdown list. But this sympthom is also true for any of the similar dropdown lists inside the GLPI.\n\n5. Find menu\n When I hit the find menu button there is a dropdown list appears and when I am trying to type any of the menu keyword with screen reader it is impossible to move as I cannot hear anything with my screen readers.\n\n 6. Find menu results without keyboard shortcut help\n (This is just a suggestion to improve and teach the users to use the )menu(s) with keyboard.)\n When I am typing inside the find menu the result(s) do not show the keyboard shortcut. With this the users can easily can learn the keyboard shortcuts for the submenus.\n\n I am attaching the result what I created with Accessibility Insight for Web Extension.\n Please see as an attachment.\n\n Please try to use the Accessibility Insight for Web extension finding the accessibility bugs before the next release created for public.\n\n Please let me know if you need anything else from my side.\n\n Thanks for your support,\n Regards,\n Gabor\n\nFastPass_20251122_ComputerNewitemGLPI.html\nFastPass_20251122_StandardinterfaceGLP.html", "priority": "medium", "type": "support", "createdByEmail": "finley.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Thank you for your report.\n\nPlease try to use the Accessibility Insight for Web extension finding the accessibility bugs before the next release created for public.\n\nThis is not a task that can be completed in just a few days for the next bugfix release. Many of the accessibility issues lie with external libraries and even the issues that are with GLPI's own code are not always so easy to fix.\n\nThere is an issue open currently asking to work towards WCAG/RGAA compliance (#5996), but this task would likely be done as part of a larger UI/UX effort.\n\nI'll leave this open in case there are quick fixes though that can be done for the specific issues reported here.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3570965914, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22034#issuecomment-3570965914", "createdAt": "2025-11-24T14:08:51Z" } }, { "userEmail": "finley.bennett@peppermint.local", "text": "Hello,\n\nThanks for your quick response,\n\nTill that time the fix can be done in this issue: You may add the keyboard shortcuts as a tooltip and for the find menu results as well. The tooltip will not help for screen reader users, but may help for who has no problem with her/his eyes. In the Find menu the keyboard shortcut key combination may added for the find menu results. like: Computer, Alt+O, Software, Alt+S, etc.\n\nThese request may not related for accessibility, but help for those who would like to use GLPI with keyboard shortcuts.\n\nThanks for your support,\nRegards,\nG\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3572349918, "author": "citygabor", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22034#issuecomment-3572349918", "createdAt": "2025-11-24T19:19:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22034, "url": "https://github.com/glpi-project/glpi/issues/22034", "author": "citygabor", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2025-11-23T15:04:04Z", "updatedAt": "2025-12-04T13:31:02Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Profile problem", "detail": "Affected version:\n11.0.3\n\nIssue description:\nHi everyone. I’ve run into an issue where, even though the notifications menu is not enabled on the profile page, but if setup is readable profile can still see it. It’s true that they can’t open it, but it still appears for them in the sidebar menu. But for General menu its still openable even its restricted\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1 Make a profile with forexample no Notification menu enabled\n2 Change to that profile\n3You can see the notification menu at the left menu bar, and can open general settings.\n\nEnvironment details:\nOperating system: Linux szamacka.hu 5.15.0-161-generic #​171-Ubuntu SMP Sat Oct 11 08:17:01 UTC 2025 x86_64\n\nPHP: 8.3.25 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem,\nsysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"1000\" max_input_vars=\"1000\" memory_limit=\"512M\" post_max_size=\"512M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"512M\"\n\nWeb server: Apache/2.4.56 (Debian) (Apache/2.4.56 (Debian) Server at helpdesk.szamacka.hu Port 80)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 11.2.3-MariaDB-1:11.2.3+maria~ubu2204\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@glpi-mariadb/glpidb\n\nHost info: glpi-mariadb via TCP/IP\n\nRequirements:\nPHP version (8.3.25) is supported.\nOS and PHP are relying on 64 bits integers.\nSessions configuration is OK.\nAllocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installed\ncurl extension is installed\ngd extension is installed\nintl extension is installed\nmbstring extension is installed\nzlib extension is installed\nbcmath extension is installed\nThe constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installed\nDatabase engine version (11.2.3) is supported.\nThe log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.\nexif extension is installed\nldap extension is installed\nFollowing extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installed\nFollowing extensions are installed:\nctype, iconv, sodium.\nWrite access to\n/var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.", "priority": "high", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "It seems that this right is only impacting the ability to access notifications themselves, but the user is still able to globally enable/disable the notifications, update the SMTP configuration and so on.\n\nThere is indeed something to review here. I consider it is a bug, but I guess the rights management on this part has never worked as expected, or at least are unclear to administrators.\n\nFor information, actually only people with the ability to read/update the general configuration, so basically GLPI super admins, are able to change the access these setting.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3610943515, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22216#issuecomment-3610943515", "createdAt": "2025-12-04T08:52:38Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "I found a solution. If i untick the Setup Read, they only see the tabs that are enabled.\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3610952267, "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22216#issuecomment-3610952267", "createdAt": "2025-12-04T08:55:16Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22216, "url": "https://github.com/glpi-project/glpi/issues/22216", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "complex issue" ], "state": "open", "stateReason": null, "createdAt": "2025-12-04T07:21:11Z", "updatedAt": "2025-12-04T09:08:34Z", "closedAt": null } }, { "title": "Focus lost after click in saved search name", "detail": "Issue description:\nWhen I try to save my current search, the new popup appears; and the search criteria is still visilbe. When I click on the serach name, focus is lots and search criteria hides at the same time.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Note: I'm using Firefox, not tested on chromium.\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3336847246, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21161#issuecomment-3336847246", "createdAt": "2025-09-26T05:37:58Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "It affects chrome too. The modal exists outside of the dropdown, so when you click in it the autoClose is triggered on the dropdown.\n\nOriginal response date: 2025-09-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3344596744, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21161#issuecomment-3344596744", "createdAt": "2025-09-29T02:01:59Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21161, "url": "https://github.com/glpi-project/glpi/issues/21161", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "javascript", "ux" ], "state": "open", "stateReason": null, "createdAt": "2025-09-26T05:30:49Z", "updatedAt": "2025-12-04T07:11:07Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Managed items by groups are false", "detail": "Affected version:\n11.0.1\n\nIssue description:\nGo to Administration / Groups menu\nSelect a group of users\nThe managed items tab show the correct number of managed items\nBut when you open the tab, the showed list is the list of the managed items by the users who belong to the group, not by the group itself.\n\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "micah.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the issue. It seems to only count assets that have the group, not assets with a user that is a member of the group.\n\nOriginal response date: 2025-10-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3444187424, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21616#issuecomment-3444187424", "createdAt": "2025-10-24T17:27:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "In GLPI 10.0, in this tab, we had a User: yes/no dropdown to chose whether the user items should be displayed or not. This filter should be restored.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3527190601, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21616#issuecomment-3527190601", "createdAt": "2025-11-13T10:51:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21616, "url": "https://github.com/glpi-project/glpi/issues/21616", "author": "ssegard", "anonymizedAuthorEmail": "micah.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-23T07:45:22Z", "updatedAt": "2025-11-13T10:51:08Z", "closedAt": null } }, { "title": "Ticket assignment error to another group", "detail": "Affected version:\n10.0.2\n\nIssue description:\nWhen a ticket is assigned to another group, a message appears on the screen: \"You don't have permission to perform this action.\"\n\nAffected page:\n\nReproduction steps:\n1. Access a ticket:\n\n2. Assign the ticket to another group and remove it from the current group:\n\n3. Click on the \"Save\" button.\n\n4. Error is displayed, but ticket is assigned:\n\n5. Ticket in the other group:\n\nAdditional context:\nProfile settings", "priority": "medium", "type": "support", "createdByEmail": "elliot.adler@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Is there something that still needs fixed here? As far as I can tell, it was fixed in 10.0.7 with the redirect and two messages.\n\nOriginal response date: 2026-03-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4138093141, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/12337#issuecomment-4138093141", "createdAt": "2026-03-26T20:44:45Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 12337, "url": "https://github.com/glpi-project/glpi/issues/12337", "author": "wc55", "anonymizedAuthorEmail": "elliot.adler@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "open", "stateReason": "reopened", "createdAt": "2022-07-29T14:59:19Z", "updatedAt": "2026-03-26T20:45:00Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Notification error expired license", "detail": "Affected version:\n10.0.11\n\nIssue description:\nHello,\n\nWe have configured in Administration > Entities > Root Entity > Notifications:\n\nEnabled email notification for licenses and set an alert period.\n\nEmail notification is configured and successfully receiving test emails and email notifications for open tickets.\n\nThe license notification has been created with a specified recipient.\nThe license has been created, and an expiration date has been set accordingly for the alert.\n\nWe executed the manual automatic action, but did not receive the notification email and received the following message in the log.\n\nAffected page:\nglpi/front/crontask.form.php?id=4\n\nReproduction steps:\nWe have configured in Administration > Entities > Root Entity > Notifications:\n\nEnabled email notification for licenses and set an alert period.\n\nEmail notification is configured and successfully receiving test emails and email notifications for open tickets.\n\nThe license notification has been created with a specified recipient.\nThe license has been created, and an expiration date has been set accordingly for the alert.\n\nWe executed the manual automatic action, but did not receive the notification email and received the following message in the log.", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "jamie.blair@peppermint.local", "text": "Hello, Skyler Adler. Any update on this issue?\n\nOriginal response date: 2026-04-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4296763288, "author": "serviceticst", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/16475#issuecomment-4296763288", "createdAt": "2026-04-22T13:51:24Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 16475, "url": "https://github.com/glpi-project/glpi/issues/16475", "author": "serviceticst", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2024-01-31T01:15:57Z", "updatedAt": "2026-04-22T13:51:24Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Unable to change ticket template type/category (both simplified/standard view)", "detail": "Affected version:\n10.0.17\n\nIssue description:\nProblem\nAttempting to create/edit ticket templates - am unable to change types from INCIDENTS to REQUESTS - Different failures in both Simplified and Standard interfaces.\n\n_Simplified interface_\nWhen changing Template Type from INCIDENT to REQUEST - The page redirects, and completing the fields submits a new trouble ticket\n\n_Standard Interface_\nWhen changing Template Type from INCIDENT to REQUEST - Nothing appears to happen, no errors in logs, discovered reference related error using Developer Console in Browser.\n\nAttempted to diagnose on\nWindows 10/Windows 11/MAC OS 15.1.1/ipadOS Safari\nLatest versions of Edge/Safari/Chrome/Brave/Firefox as of 01/21/2025\nno firewall/av/plugins\n\nInstalled on fresh UBUNTU to test following these instructions:\n\nInstalled on my personal home Synology NAS with Docker container diouxx/glpi - latest\n\nResult is always the same.\n\nAffected page:\n\nReproduction steps:\nStandard Interface\n1. Navigate to Assistance\n2. Navigate to Tickets\n3. Navigate to Template\n4. Create new or choose existing template\n5. Choose Standard Interface\n6. Change \"TYPE\" from INCIDENT to REQUEST\n7. Nothing changes - Notice DEV Console Output\n(Console output)\nUncaught TypeError: Cannot read properties of null (reading 'submit')\n at HTMLSelectElement.onchange (tickettemplate.form.php?id=1:1:11)\n at Object.trigger (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:186:71680)\n at HTMLSelectElement. (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:186:72261)\n at Function.each (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:175:3076)\n at obj..each (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:175:1448)\n at obj..trigger (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:186:72236)\n at n.define.i.select (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:205:34738)\n at r. (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:205:35582)\n at n.define.i.invoke (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:205:5008)\n at n.define.i.trigger (base.min.js?v=a6aeb338cce60c87e3e83de0cb79ff1a0bb4564c:205:4822)\n\nSIMPLIFIED INTERFACE\n1. Navigate to Assistance\n2. Navigate to Tickets\n3. Navigate to Template\n4. Create New or Choose Existing Template\n5. Choose SIMPLIFIED Interface\n6. Change TYPE from INCIDENT to REQUEST - Window changes to SUBMIT TICKET (altering anything here will submit a new trouble ticket)\n\nEnvironment details:\nOur information changed to TLD.ORG", "priority": "medium", "type": "support", "createdByEmail": "kendall.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This issue is resolved in GLPI 11.\n1. The simplified interface preview no longer exists since direct ticket creation for these profiles is replaced by forms.\n2. The preview form contains no real form element or submit buttons\n3. Changing fields that usually cause a template recalculation can no longer do so with the missing form/submit\n4. The fields remain without forcing readonly states for them all which helps reflect the real state the field would be in according to the template and also lets you see the valid options in the case of the \"Status\" field as you can restrict these options in the template too.\n\nOriginal response date: 2025-12-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3691347904, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/18792#issuecomment-3691347904", "createdAt": "2025-12-25T11:31:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 18792, "url": "https://github.com/glpi-project/glpi/issues/18792", "author": "iambucketdotcom", "anonymizedAuthorEmail": "kendall.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-01-22T17:35:20Z", "updatedAt": "2025-12-25T11:31:31Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Unable to search for percentage (%) or less-than/greather-than () in contains filters", "detail": "Affected version:\n10.0.18\n\nIssue description:\nWhile searching items with a contains filter, I can't search for the percentage sign %, for example \"Ticket title contains '%'\" will display every ticket, this is due to % not being escaped in the sql request so it will get \"name like '%%%'\" in the request\n\nI have the same issue with but these are because the name in the database are encoded as so it won't find them\n\nReproduction steps:\n1. With version GLPI 10.0.18\n2. Go to Ticket (or any searchable item really)\n3. Try to search for title containing '%'", "priority": "medium", "type": "support", "createdByEmail": "dakota.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "In GLPI 11.0, searching for works as expected for tickets created after the update to GLPI 11.0.\n\nSearching for % still not works as expected, as it is considered as a wildcard.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3632488852, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19011#issuecomment-3632488852", "createdAt": "2025-12-09T14:16:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 19011, "url": "https://github.com/glpi-project/glpi/issues/19011", "author": "Vireth4114", "anonymizedAuthorEmail": "dakota.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-02-18T15:45:07Z", "updatedAt": "2025-12-09T14:16:12Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Work for WCAG and RGAA", "detail": "Issue description:\nRelated resources:\n\n- WC3 International Guidelines [EN]\n- French Certified Translation [FR]\n- Resources from DINSIC (a French Interministerial initiative) [FR]\n- French RGAA [FR]", "priority": "medium", "type": "support", "createdByEmail": "cameron.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "As a note, I believe GLPI needs to meet the standards set by the EU Accessibility Act of 2025 by June 2030.\n\nThis would mean at least WCAG 2.1 AA level.\n\nOriginal response date: 2025-10-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3368190950, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/5996#issuecomment-3368190950", "createdAt": "2025-10-04T12:40:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 5996, "url": "https://github.com/glpi-project/glpi/issues/5996", "author": "flegastelois", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2019-06-07T06:31:52Z", "updatedAt": "2025-12-04T07:06:28Z", "closedAt": null } }, { "title": "Tests failure on MariaDB 10.6", "detail": "Issue description:\nSince 2e70f825946e9c5c62c33c474c72b63caec5f59d, tests are failing on the main branch, only on MariaDB 10.6. See", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "10.6 reached EOL 2 days ago with the exception of Enterprise support. 10.11 is the current LTS v10 version.\n\n- The DESC usage in an index is not supported in 10.6, and seems to be silently ignored which should be OK. This functionality was added in 10.11.\n- Not sure why or where a new table/column is being tested as datetime, but users have had 4 years (since 10.0 released) to migrate so I wonder if this is still needed. At the very least, it could be ignored for these new tables.\n\nOriginal response date: 2026-07-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4914215221, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24806#issuecomment-4914215221", "createdAt": "2026-07-08T11:16:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24806, "url": "https://github.com/glpi-project/glpi/issues/24806", "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-08T07:46:07Z", "updatedAt": "2026-07-16T10:28:31Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Child entity isn't being shown at the dropdown when created through \"New user\" form", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen creating a child entity in the \"New user\" dropdown, it isn't being listed in the \"New user\" form, but it's shown as expected in the Entity dropdown when reloading the page manually.\n\nAffected page:\n\nReproduction steps:\n1. Create a new user.\n2. Create a new child entity on the new user form.\n3. Entity is created, but the dropdown isn't updated to show the new child entity.\n\nAdditional context:\nPlease let me know if there's anymore information I can provide to troubleshoot this issue.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Reopen issue since this issue is reproducible on GLPI 11.0.4. Updated the description to reflect the new GLPI information. It's shown in the dropdown at the top right of the page without requiring reloading the page.\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3716495308, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/13537#issuecomment-3716495308", "createdAt": "2026-01-06T21:50:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 13537, "url": "https://github.com/glpi-project/glpi/issues/13537", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2022-12-06T12:53:22Z", "updatedAt": "2026-01-06T21:53:15Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Project Kanban column state is overwritten on page refresh", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nGLPI version: 11.0.8\nBrowser: Chrome/Edge\n\nActual result:\n\nThe configured columns are not displayed. During page initialization, the stored Kanban state is overwritten in the database with an incomplete state. After refreshing again, the columns are also unchecked in the “Insert column” menu.\n\nExpected result:\n\nThe stored columns, visibility state and card positions should be restored and must not be overwritten during page initialization.\n\nReproduction steps:\n1. Open a project Kanban board.\n2. Add one or more columns through “Insert column”.\n3. Move or create project tasks in these columns.\n4. Verify that the Kanban state is correctly stored in the database.\n5. Reload or reopen the page.\n\nEnvironment details:\nDebian, Docker and GLPI-Version 11.0.8", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.bennett@peppermint.local", "text": "I was able to reproduce the issue more precisely.\n\nWhen I add several columns and every selected column contains at least one task before refreshing the page, all columns remain visible after the refresh.\n\nHowever, if one of the selected columns contains zero tasks, the behavior changes:\n\nThe empty column disappears after the next refresh.\nEvery column positioned after that empty column also disappears.\nThis also happens when the later columns contain tasks.\n\nIn other words, the first empty column seems to act as a cutoff point. The empty column itself and all following columns are removed from the saved Kanban state.\n\nThis matches the following code in loadColumn():\n\nDuring the initial loading of the Kanban, the columns are loaded asynchronously. When the first empty column is loaded, saveState() may be called before the remaining columns have been added to columns.value.\n\nBecause saveState() saves the entire currently loaded board state, it may overwrite the complete saved state with a partial state containing only the columns loaded before the empty column.\n\nThis would explain why the empty column and every following column disappear after the refresh.\n\nThere is also another suspicious detail:\n\nloadColumn(entry.column, true, false);\n\nis called from loadState(), while the current function definition is:\n\nasync function loadColumn(column_id)\n\nThe additional arguments are therefore ignored. It is possible that the last argument was intended to prevent saveState() from being called while the saved board state is being restored.\n\nI will test this by temporarily disabling the saveState() call for empty columns.\n\nOriginal response date: 2026-07-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 5034822152, "author": "rol4nd", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24912#issuecomment-5034822152", "createdAt": "2026-07-21T13:46:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24912, "url": "https://github.com/glpi-project/glpi/issues/24912", "author": "rol4nd", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2026-07-21T12:19:30Z", "updatedAt": "2026-07-22T06:49:25Z", "closedAt": null } }, { "title": "Cannot set an end time to External Events via API", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI generated this example post request via the REST API swagger page. I removed the template property. This creates an event that lasts 1 hour, instead of 4 days.\n\ncurl -X 'POST' \\\n '' \\\n -H 'accept: application/json' \\\n -H 'GLPI-Entity: 0' \\\n -H 'GLPI-Profile: 3' \\\n -H 'Accept-Language: en_GB' \\\n -H 'Authorization: Bearer {MYTOKEN} \\\n -H 'Content-Type: application/json' \\\n -d '{\n \"name\": \"testy\",\n \"text\": \"string\",\n \"category\": {\n \"id\": 1\n },\n \"is_recursive\": true,\n \"user\": {\n \"id\": 15\n },\n \"group\": {\n \"id\": 0\n },\n \"date\": \"2026-06-23T20:16:49.789Z\",\n \"date_begin\": \"2026-06-23T20:16:49.789Z\",\n \"date_end\": \"2026-06-27T20:16:49.789Z\",\n \"rrule\": \"string\",\n \"state\": 0,\n \"is_background\": true,\n \"date_creation\": \"2026-06-23T20:16:49.789Z\",\n \"date_mod\": \"2026-06-23T20:16:49.789Z\"\n}'\n\nAffected page:\n/Assistance/ExternalEvent\n\nReproduction steps:\n1. Submit that cURL requet\n2. Verify the ExternalEvent dates\n\nAdditional context:\nI have played around with including a template, removing the template property, date formats, removing \"extra\" properties. Even though the server returns 200 response, I cannot set an end date to an External Event.", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "dakota.blair@peppermint.local", "text": "GLPI 11 seems to reject any date sent in any date field on a POST operation. I had to use a 2-step process to create the External Event, and the a PATCH operation to update the event with the correct dates.\n\nOriginal response date: 2026-06-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4812762949, "author": "RuarriS", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24651#issuecomment-4812762949", "createdAt": "2026-06-26T19:26:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24651, "url": "https://github.com/glpi-project/glpi/issues/24651", "author": "RuarriS", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-23T20:43:48Z", "updatedAt": "2026-06-26T19:26:09Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Add statements parameters in debug view", "detail": "Issue description:\nFollows #23156.\n\nPrepared statements are show in the debug bar, parameters are passed and should probably be displayed.\n\nParameters array can be quite huge and are positional - I do not know how to display that in a human readable way.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "We talked about that on our internal channel; it appears that we should show the query with parameters replaced directly.\nWe could also propose a view with the real query and the parameters array.\n\nOriginal response date: 2026-06-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4809779628, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24682#issuecomment-4809779628", "createdAt": "2026-06-26T12:55:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24682, "url": "https://github.com/glpi-project/glpi/issues/24682", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-26T07:23:54Z", "updatedAt": "2026-06-26T12:55:54Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Refactor QueryFunction", "detail": "Issue description:\nValues have to be extracted in almost every function, but I think it could be centralized in the getExpression method.\n\nThis could be done in another PR. This whole class should probably be refactored to simplify its usage and its maintainability.\n\n_Originally posted by Skyler Adler in", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Follows #23156\n\nOriginal response date: 2026-06-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4776463784, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24646#issuecomment-4776463784", "createdAt": "2026-06-23T06:43:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24646, "url": "https://github.com/glpi-project/glpi/issues/24646", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-23T06:42:55Z", "updatedAt": "2026-06-23T08:28:19Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Rework QueryExpression", "detail": "Issue description:\nHere is a global remark, not strictly related to this PR, but related to parts of our code that makes this PR pretty complex to review.\n\nConcatenation of query expressions based on the magic toString() method may lead to issues since we can now forgot to use the query parameters related to this expression. Maybe we should deprecate this usage (in a later PR) to have a clear view in the code that it is not a simple string that is used, but a query expression that may have parameters.\n\nWhere we have method parameters that may be either a scalar value or a QueryExpression, there is enough code complexity to forgot t handle these QueryExpression parameters.\n\nFor instance, in the following piece of code, $interval may be an expression with parameters, but they will completely be ignored.\n\nI think we should introduce a QueryIdentifier class for strings that must be quoted by the DBmysql::quoteName() method (i.e. tables names, fields names, ...) and have a class (maybe reuse the QueryParam class) for scalar values used during statements execution.\n\nThis is out of the current PR scope, but, IMHO, it would greatly improve the code readability, since we will not have to guess anymore whether a sting is used for a name or a value, and whether the value is a scalar value to transform into a QueryExpression.\n\n_Originally posted by Skyler Adler in", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Follows #23156\n\nOriginal response date: 2026-06-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4777245392, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24647#issuecomment-4777245392", "createdAt": "2026-06-23T08:27:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24647, "url": "https://github.com/glpi-project/glpi/issues/24647", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-23T08:27:45Z", "updatedAt": "2026-06-23T08:28:09Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Tests Dashboard & Auto-balancing Playwright Shards", "detail": "Issue description:\nHey folks,\n\nI used to work on Playwright, and I noticed that GLPI uses Playwright too, including sharding in CI.\n\nThese days I’m building Flakiness.io: a GitHub-native test analytics dashboard that tracks flaky tests and detects regressions in pull requests.\n\nWe’re prototyping Playwright shard balancing, where Flakiness.io uses historical test timings to produce better-balanced shards. Since GLPI has a real-world Playwright setup, I’d be very happy if you’re open to testing it on your workload.\n\nI also saw that you already generate a merged Playwright HTML report and upload it as a GitHub artifact. Flakiness.io can simplify that setup: it hosts test reports online for each commit/PR, and adds flakiness, performance, and regression analytics out of the box.\n\nOSS projects can use Flakiness.io for free. I’d be happy to help set it up and see if you find it useful.", "priority": "medium", "type": "support", "createdByEmail": "sage.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "sage.bennett@peppermint.local", "text": "FYI: we've released shard balancing for Playwright Test.\n\nTo start using it:\n\n1. Create a project on Flakiness.io to store your test history\n1. Install flakiness/playwright\n1. Replace npx playwright test with npx flakiness-playwright-shard in Github Actions:\n\nIt will start balancing shards nicely as soon as it gets initial historic results. Details:\n\nOriginal response date: 2026-06-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4654814822, "author": "aslushnikov", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24287#issuecomment-4654814822", "createdAt": "2026-06-09T00:29:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24287, "url": "https://github.com/glpi-project/glpi/issues/24287", "author": "aslushnikov", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-23T23:02:27Z", "updatedAt": "2026-06-22T19:56:26Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Unable to unlink related tickets without DELETE permission on ticket (GLPI 11.0.7)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nUsers are able to link tickets together, but they cannot unlink them unless the \"Delete\" permission is granted on Tickets.\n\nThe problem is that granting the \"Delete\" permission also allows users to permanently delete tickets, which is a much broader permission than simply removing a relationship between tickets.\n\nExpected behavior\n\nA user with access to both tickets and permission to update tickets should be able to remove the relationship between linked tickets without requiring the \"Delete\" permission.\n\nCurrent behavior\n\nWhen the \"Delete\" permission is removed from the profile:\n\nThe \"Unlink\" action disappears from linked tickets.\nUsers can no longer remove ticket relationships.\n\nWhen the \"Delete\" permission is granted:\n\nThe \"Unlink\" action becomes available.\nUsers are also able to delete tickets.\n\nReproduction steps:\n1. Create two tickets.\n2. Link the tickets together.\n3. Use a profile with Read and Update permissions on tickets.\n4. Remove the Delete permission from the profile.\n5. Open one of the linked tickets.\n6. Observe that the Unlink action is not available.\n7. Grant the Delete permission.\n8. Observe that the Unlink action becomes available.\n\nAdditional context:\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "parker.bennett@peppermint.local", "text": "Expected result\n\nThe ability to unlink tickets should be independent from the ability to delete tickets.\n\nAdditional information\n\nThe user has access to both tickets and was the user who created the relationship between them.\n\nThis creates a permission escalation problem: to allow users to only remove a relationship between tickets, administrators must also grant permission to delete the ticket itself.\n\nOriginal response date: 2026-06-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4681408112, "author": "marceloprado93", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24546#issuecomment-4681408112", "createdAt": "2026-06-11T14:05:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24546, "url": "https://github.com/glpi-project/glpi/issues/24546", "author": "marceloprado93", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-11T13:44:08Z", "updatedAt": "2026-06-17T18:56:57Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Wrong opening date on recurrent tickets with multiple items", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nObserved problem:\nIf there are more than one item associate to a recurrent ticket, the first ticket is created correctly with real \"opening date\", while the others are create with \"opening date\" as the recurrent ticket next creation date.\n\nThis sympton was verified in 2 different installations on 11.0.7 release, tested with native and custom assets, with plugins disabled.\n\nExample:\nRecurrent ticket scheduled for 2026-06-07 09:29:00, periodicity of 4 months and 3 associated items.\nFirst ticket created with opening date = 2026-06-07 09:29:00.\nThe second and third tickets created with opening date = 2026-10-07 09:29:00.\nThe '2026-10-07 09:29:00' value is related to the next creation date, due the 4 months periodicity.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\n/front/ticketrecurrent.form.php\n\nReproduction steps:\n1. Create a ticket template without associated items.\n2. Create a recurrent ticket: choose the created template and set the parameter \"Create a ticket per linked element\" to \"yes\".\n4. Associate 2 or assets to the recurrent ticket.\n5. Wait or run the automatic action to generate the recurrent items.", "priority": "medium", "type": "support", "createdByEmail": "quinn.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "quinn.bennett@peppermint.local", "text": "There is a workaround:\nOn ticket template, set the opening date field to \"Now\".\n\nOriginal response date: 2026-06-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4642900746, "author": "raultak", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24495#issuecomment-4642900746", "createdAt": "2026-06-07T14:06:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24495, "url": "https://github.com/glpi-project/glpi/issues/24495", "author": "raultak", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-07T13:03:26Z", "updatedAt": "2026-06-17T15:39:55Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Object unlock request notification", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHi.\nA faced an issue that if i enable locking items (tickets, computers) and i set up a notification to Object unlock request, only that users got the notification that are in the root entity. Is this okay like this?\n\nReproduction steps:\n1. Turn on \"Use locks\" function\n2. Enable \"Request Unlock Items\" notification with Child entities\n3. Creat a user in the Root entity and create another on in the Root>A entity as well\n4. Lock items with all 2 users\n5. Request unlock items with a third user\n6. Only the user in the root entity get a notification user in Root>A not\n\nEnvironment details:\nGLPI: 11.0.4 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: OK\n\nPHP: 8.3.25 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem,\nsysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"1000\" max_input_vars=\"1000\" memory_limit=\"512M\" post_max_size=\"512M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"512M\"\n\nWeb server: Apache/2.4.56 (Debian) (Apache/2.4.56 (Debian) Server at *)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 11.2.3-MariaDB-1:11.2.3+maria~ubu2204\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@glpi-mariadb/glpidb\n\nHost info: glpi-mariadb via TCP/IP\n\nRequirements:\nPHP version (8.3.25) is supported.\nOS and PHP are relying on 64 bits integers.\nSessions configuration is OK.\nAllocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installed\ncurl extension is installed\ngd extension is installed\nintl extension is installed\nmbstring extension is installed\nzlib extension is installed\nbcmath extension is installed\nThe constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installed\nDatabase engine version (11.2.3) is supported.\nThe log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.\nexif extension is installed\nldap extension is installed\nFollowing extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installed\nFollowing extensions are installed:\nctype, iconv, sodium.\nWrite access to\n/var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "kendall.blair@peppermint.local", "text": "Same problem here\n\nour users doesn't exists in root entity, only on the sub entities and they don't receive notification for unlock objects\nbut it's working for super admin, (2 guys), because they exists in the root entity\n\nOriginal response date: 2026-06-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4682157521, "author": "doumhfr", "anonymizedAuthorEmail": "kendall.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22766#issuecomment-4682157521", "createdAt": "2026-06-11T15:23:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22766, "url": "https://github.com/glpi-project/glpi/issues/22766", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-21T07:12:02Z", "updatedAt": "2026-06-11T15:23:41Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Ticket Approvals are not shown when ticket is not locked", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen entering a ticket in read-only mode (i.e. not locking the ticket), a previously added approval is not shown in the approval tab of the ticket. Only after locking the ticket by clicking the \"Edit\" button, the approval is shown. These two screenshots show the same ticket before and after clicking the \"Edit\" button:\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. Add a new ticket, filling out Title and Description\n2. Open the ticket in edit mode\n3. Click the arrow next to the \"Answer\" button and click \"Ask for approval\"\n4. Put in a user who should approve and a text\n5. Open the ticket in read-only mode (e.g. by using a new private browser window or a different user)\n6. Click the \"Approvals\" tab, the approval is not visible.", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "dakota.bennett@peppermint.local", "text": "Hi all,\n\nis there any chance that this will be fixed? I see that there has been an attempt to solve this problem, would it be possible to reevaluate that pull request?\n\nThanks for your great work,\nChristian.\n\nOriginal response date: 2026-06-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4677914672, "author": "cfuchs-mpi", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23455#issuecomment-4677914672", "createdAt": "2026-06-11T06:45:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23455, "url": "https://github.com/glpi-project/glpi/issues/23455", "author": "cfuchs-mpi", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-12T06:40:27Z", "updatedAt": "2026-06-11T06:45:34Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI 11 Marketplace View Causes 504 Gateway Timeout / PHP-FPM Session Lock On Ajax Requests", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nReproduction steps:\n1. Install a clean instance of GLPI 11.0.7 (or upgrade from 10.x).\n2. Go to Setup -> Plugins.\n3. Click on the button to switch the view to \"Marketplace\" mode.\n4. The page hangs indefinitely, resulting in a 504 Gateway Time-out from Nginx.\n\nExpected result:\nThe Marketplace grid should load successfully or fail gracefully with a network error timeout message if the external Teclib API is unreachable or slow.\n\nActual result:\nThe application triggers an internal Ajax request:\nGET /ajax/common.tabs.php?_glpi_tab=Glpi\\Marketplace\\View$0&_target=/front/marketplace.php&_itemtype=Glpi\\Marketplace\\View&id=0\n\nThis request causes the PHP-FPM worker to hang indefinitely in the background. Because of PHP's default session locking mechanism, the user's entire session becomes locked. The user cannot access any other GLPI pages (like the homepage) from the same browser until the PHP-FPM service is restarted or the session files are manually deleted on the server. Opening GLPI in Private/Incognito mode (a new session) works instantly until navigating back to the Plugins page.\n\nNginx error log throws:\n[error] upstream timed out (110: Connection timed out) while reading response header from upstream, request: \"GET /ajax/common.tabs.php?_glpi_tab=Glpi\\Marketplace\\View$0...\"\n\nEnvironment & Diagnostics:\n- GLPI Version: 11.0.7\n- PHP Version: 8.2 (PHP-FPM via UDS socket)\n- Web Server: Nginx 1.22.1\n- OS: Ubuntu / Debian\n- Network check: Running curl -I directly from the server console under root works perfectly fine and returns HTTP/1.1 200 OK instantly.\n- CLI Check: Running php bin/console plugin:list via CLI under the www-data user executes instantly and returns an empty table without any delays.\n\nIt seems that when the Glpi\\Marketplace\\View class is initialized via the web interface/Ajax, the underlying HttpClient or stream socket handling gets stuck in an infinite loop or fails to handle timeouts properly when communicating with remote Teclib servers under the www-data user context.\n\nWorkaround used:\nCurrently, we have to forcefully disable the marketplace by modifying the source code (src/Marketplace/View.php -> isEnabled() { return false; }) to restore classic local plugin management functionality.", "priority": "medium", "type": "support", "createdByEmail": "noel.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Currently, we have to forcefully disable the marketplace by modifying the source code\n\nYou don't need to mess with the source code for that. You can use a config/local_define.php file (or set through an ENV variable) to control marketplace access.\n\nOriginal response date: 2026-06-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4649410175, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24503#issuecomment-4649410175", "createdAt": "2026-06-08T13:21:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24503, "url": "https://github.com/glpi-project/glpi/issues/24503", "author": "sta-zot", "anonymizedAuthorEmail": "noel.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-08T13:06:08Z", "updatedAt": "2026-06-08T13:21:52Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI 11 — Inventory agent calls add() instead of update() for pre-existing assets", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen a GLPI agent sends an inventory for a computer that already exists in GLPI\n(created via purchase order or manually), GLPI incorrectly calls\nCommonDBTM->add() instead of CommonDBTM->update(). This triggers the unicity\ncheck, which detects the duplicate and returns a 500 Internal Server Error.\nThe inventory is never processed and the agent remains unlinked.\n\n---\n\nExpected behavior\n\nGLPI should match the existing computer via import rules (by serial number),\nlink the agent to the existing asset, and perform an UPDATE. No new asset\nshould be created.\n\nActual behavior\n\nGLPI attempts to CREATE a new computer (calls add()), triggering the unicity\ncheck. The unicity check detects the duplicate and returns HTTP 500.\n\n---\n\nAgent error output\n\n [error] communication error: 500 Internal Server Error,\n Unable to create item.; Enregistrement impossible pour Nom = Arcanin\n Un autre élément existe [Arcanin - ID : 973 - Série : FD4ZW84]\n\n---\n\nRoot cause\n\nAfter import rules evaluate and match an existing asset (rulepassed() is\ncalled), MainAsset.php line 773 calls add() instead of update(). This happens\neven when:\n- The import rule matches by serial number (rule \"Computer update by serial\",\n action \"Link if possible\")\n- The agent is manually linked to the computer (items_id set in glpi_agents)\n\nThe PHP warning \"Undefined array key glpiID\" in AssignableItem.php lines 62-64\nconfirms that the Computer object passed to canViewItem() is uninitialized —\nit is a new empty object, not the existing one fetched from the database.\n\n---\n\nImport rules configuration (standard, unmodified)\n\n #12 Computer update (by serial)\n Criteria: Item Type=Computers AND Serial is already present=Yes\n AND Serial exists=Yes\n Action: Link if possible\n\n #18 Computer import (by serial)\n Criteria: Item Type=Computers AND Serial exists=Yes\n Action: Link if possible\n\n---\n\nSuggested fix\n\nInvestigate:\n- src/RuleImportAsset.php line 1013 (rulepassed): when a matching asset is\n found, the code must set the found ID and call update(), not add()\n- src/Glpi/Inventory/MainAsset/MainAsset.php line 773: verify the condition\n that decides between add() and update()\n- src/Glpi/Features/AssignableItem.php lines 62-64: fix the uninitialized\n object passed to canViewItem() during the unicity check\n\n---\n\nReproduction steps:\nSteps to reproduce\n\n1. Create a computer in GLPI manually or via the purchase order module.\n Set a name (e.g. \"Arcanin\") and serial number (e.g. \"FD4ZW84\").\n Do NOT link any agent to it.\n\n2. Install GLPI Agent on the physical machine with matching name and serial.\n Point it to the GLPI server.\n\n3. Run: glpi-agent --force --logger=stderr\n\n4. Observe the 500 error in agent output and PHP error log.\n\n---\n\nEnvironment details:\nGLPI: 11.0.7 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_US\nSource Integrity: OK\n\nOperating system: Linux glpi 6.17.0-19-generic #​19~24.04.2-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 6 23:08:46 UTC 2 x86_64\n\nPHP: 8.4.21 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, apache2handler, mysqlnd, PDO, xml, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"8M\" session.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"Lax\" session.save_handler=\"files\" upload_max_filesize=\"2M\"\n\nWeb server: Apache/2.4.67 (Ubuntu) (Apache/2.4.67 (Ubuntu) Server at glpi.gac-technology.com Port 80)\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: Ubuntu 24.04\n\nServer Version: 10.11.14-MariaDB-0ubuntu0.24.04.1\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@localhost/glpi\n\nHost info: Localhost via UNIX socket\n\nRequirements:\nPHP version (8.4.21) is supported.PHP version (8.4.21) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader, xmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (10.11.14) is supported.Database engine version (10.11.14) is supported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated. Write access to /var/www/html/glpi/files/_cron has been validated. Write access to /var/www/html/glpi/files has been validated. Write access to /var/www/html/glpi/files/_graphs has been validated. Write access to /var\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "robin.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Looking at the stack trace, it seems like the import rules weren't able to match it to an existing asset so all of the code called after the rules passed seems correct.\n\nOriginal response date: 2026-06-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4603923326, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24408#issuecomment-4603923326", "createdAt": "2026-06-02T15:22:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24408, "url": "https://github.com/glpi-project/glpi/issues/24408", "author": "TheLaskY", "anonymizedAuthorEmail": "robin.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-01T06:57:52Z", "updatedAt": "2026-06-02T15:22:41Z", "closedAt": null } }, { "title": "Unable to reaffect given elements when associating network name to server", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI have successfully imported Network Names using the Data Injection plugin and I am trying to associate them with Network Devices. The imported Network Names contain a name and an IP address.\n\nWhen I try to associate them with Network Devices I get the alert:\n\n\"Unable to reaffect given elements!\"\n\n[Image omitted]\n\n[Image omitted]\n\nI also have the OCS Inventory plugin installed, where Network Names are created automatically for some Network Devices and associated correctly.\n\nFor testing purposes, I removed one Network Name association from a Network Device. However, when I try to associate the same Network Name again manually, the same alert appears.\n\nAffected page:\nfront/networkname.form.php?id=1126#\n\nReproduction steps:\n1. Import Network Names using Data Injection plugin or create manually.\n2. Open a Network name.\n3. Try to associate, Actions -> Associate.\n4. Error appears\n\nOR\n\n1. Take an existing OCS-Inventory created association\n2. Remove the Network Name association\n3. Try to associate the same Network Name again\n4. Error appears", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the issue. It seems like the NetworkName class needs to override the getConnexityMassiveActionsSpecificities method and specify the itemtypes that Network Names can be linked to similar to\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4585108177, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24314#issuecomment-4585108177", "createdAt": "2026-05-30T23:09:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24314, "url": "https://github.com/glpi-project/glpi/issues/24314", "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2026-05-26T17:15:11Z", "updatedAt": "2026-05-30T23:09:22Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "budget not show value", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen I add a cost in Management -> Financial & Administrative Information and link it to a budget, the costs from other tickets do not appear in that budget.\nIf I do not link a budget in Management -> Financial & Administrative Information, the cost in the ticket is displayed normally in Budget.\n\n[Image omitted]\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jesse.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the bug. The UNION query used to get the items and their values has fields in a different order for the Ticket subquery and UNION evaluates fields by position instead of by name. This caused the ticket value data to be placed in the devices_id property instead.\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4584391914, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24280#issuecomment-4584391914", "createdAt": "2026-05-30T20:02:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24280, "url": "https://github.com/glpi-project/glpi/issues/24280", "author": "hagianghi", "anonymizedAuthorEmail": "jesse.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2026-05-22T04:42:23Z", "updatedAt": "2026-05-30T20:07:47Z", "closedAt": null } }, { "title": "All form fields are displayed when creating a ticket.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.7\n\nIssue description:\nIn GLPI 10 with the formcreator plugin, empty fields were hidden in generated tickets using :\n % if answer is not empty %}\n {{ answer }}\n {% endif %}\n\nIn GLPI 11, all fields and sections are displayed even if they are empty, which leads to unreadable tickets.\nThis is a regression in usability.\n\nReproduction steps:\nCreate a form with several questions, the answers to which are not mandatory.\nIn the destinations section, add all the #questions and #answers.\nSet yourself up as a self-service user and fill out the form by answering only 1 question.\nChecking the created ticket, we see that all questions are displayed, even those without answers.", "priority": "medium", "type": "support", "createdByEmail": "remy.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "noel.blair@peppermint.local", "text": "I have the same issue.\nGLPI 11.0.7\n\nOriginal response date: 2026-05-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4554908745, "author": "plutoflyby", "anonymizedAuthorEmail": "noel.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24159#issuecomment-4554908745", "createdAt": "2026-05-27T13:24:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24159, "url": "https://github.com/glpi-project/glpi/issues/24159", "author": "PSGCV85", "anonymizedAuthorEmail": "remy.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-07T07:08:30Z", "updatedAt": "2026-05-27T13:24:18Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Form location tag uses name instead of complete name", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nOriginally reported in", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Comment from forum post:\n\nOriginal response date: 2026-05-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4496693110, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24252#issuecomment-4496693110", "createdAt": "2026-05-20T09:23:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24252, "url": "https://github.com/glpi-project/glpi/issues/24252", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "open", "stateReason": null, "createdAt": "2026-05-19T11:23:45Z", "updatedAt": "2026-05-20T09:24:16Z", "closedAt": null } }, { "title": "Planning view multiple memory leaks", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nPerforming actions that trigger events to be loaded from the server, such as switching views/months or manually clicking the refresh button in the planning view, causes a memory leak as some elements/variables become detached and remain in memory. The more events in the calendar views, the faster memory usage grows, but this is less of an issue since you have to be hovering over an event for a minimum amount of time before the loading can start. The main culprit in this case seems to be qtip tooltips not being disposed.\n\nAnother memory leak happens if you happen to hover over a lot of events and trigger qtip tooltips to load since they remain in the DOM for the life of the page.\n\nYet another occurs if you click events to view them as the modals they load remain in the DOM for the life of the page. One of the issues with that is TinyMCE which loads its own copy of the very bloated stylesheet (700kb not compressed) which has to be loaded into memory for the editor's iframe.\n\nNavigating months seems to cause a new Flatpickr instance to be created and a new element to be added to the body which remains for the entire life of the page.", "priority": "high", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "FullCalendar has Vue component support\n\nOriginal response date: 2025-11-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3577368105, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22071#issuecomment-3577368105", "createdAt": "2025-11-25T20:00:39Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22071, "url": "https://github.com/glpi-project/glpi/issues/22071", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "javascript", "performance" ], "state": "open", "stateReason": null, "createdAt": "2025-11-25T16:42:32Z", "updatedAt": "2026-05-18T06:30:37Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "ITIL objects - Submit does not highlight required fields with missing data", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen there is ITIL template (for example for tickets) active which has some mandatory fields (for example Title, Requester , Category , Description) and you don't have them all filled in, you can't submit and you don't know what you are missing.\nFields seems honor \"required\" attribute but browser does not show any warning (eg. Please fill out this field) when trying to submit the form.\nYou simply hit \"Add\" button and nothing happens, click is ignored, until you have filled in all fields.\nOnly field which seems to be working is \"Title\" which is highlighted by red frame when empty.\n\nIn 10.x version, browser shows warning (eg. Please fill out this field) and sets focus to field which is missing some data.\nThere is similar issue#20678, but that seems to be about post processing once form is submitted.\n\n[Image omitted]\n\nAffected page:\n/front/ticket.form.php\n\nReproduction steps:\n1. Go to Ticket templates. Modify default template and add following fields to Mandatory (Title, Requester, Category, Description)\n2. Go to Tickets click \"Add\"\n3. Fill in Title, leave other fields empty\n4. Click \"Add\" button\n\nAdditional context:\nLooks like problem is with Actors fields which can't be probably focused by browser.\nIf I remove the attribute \"required\" from \"Requester\" select2 field, browser allows submitting form and after processing GLPI displays error box what fields are still missing (eg. Category.. ). This was also behavior in 10.20 version.\n\nPS.\nIn 10.20 it worked also for Description field before submission, In 11.x it is not the case and \"Description\" is evaluated just after submission.", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "remy.blair@peppermint.local", "text": "Confirmation of the issue in 11.0.7\n\nI'm running a migration from 10.0.11 to 11.0.7 and encountered the same issue. In 10.0.11, all required fields show either a GLPI toast notification or the browser's native validation message. In 11.0.7, this works for all fields except Actor fields (Requester, etc.).\n\nTested in two environments:\n- Migration case from GLPI demo data\n- Fresh, clean GLPI instance using default template (adding requester, etc as required)\n\nBehavior replicated in both environments.\n\nThis confirms the Actor fields specifically are not triggering browser validation, while other required fields (Title, Category, Description) work correctly in 11.0.7.\n\nOriginal response date: 2026-05-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4441078879, "author": "jussara-ti", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21933#issuecomment-4441078879", "createdAt": "2026-05-13T12:42:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21933, "url": "https://github.com/glpi-project/glpi/issues/21933", "author": "VladoTTX", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-11-13T15:39:35Z", "updatedAt": "2026-05-13T12:42:23Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Allow documents in notifications sent to anonymous users independently of global variable for documents into ticket notifications", "detail": "Issue description:\nHello,\n\nThanks for having repaired attachments to notifications for anonymous users ( ) . I'd like to propose to get them independent of the activation of \"Add documents into ticket notifications\". The reason is that in environments with both known users and anonymous users, sometimes people need to have a way to send documents to these anonymous users. Standard way of GLPI link sharing does not work as they can't log in to the system in order to get files. On the other hand, configuring GLPI to systematically send documents in notifications for everybody is a little bit too heavy when multiple messages are exchanged in tickets.\n\n Actually, there is a pre-check filter in private static function attachDocuments(GLPIMailer $mmail, array $documents_ids):\n\nif (!$CFG_GLPI['attach_ticket_documents_to_mail']) {\n return;\n\nthat could easily be modified to (needs also adding bool $is_anonymous_requester as third parameter of the function and calling it with):\n\nif (!$CFG_GLPI['attach_ticket_documents_to_mail'] && (!($CFG_GLPI['attach_documents_to_notifications_for_anonymous']) || !($is_anonymous_requester))) {", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "bailey.bennett@peppermint.local", "text": "And probably something to change the same manner for\n\nif ($is_html || $CFG_GLPI['attach_ticket_documents_to_mail']) {\n\nin public static function send...\n\nOriginal response date: 2026-05-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4398052405, "author": "kabassanov", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24171#issuecomment-4398052405", "createdAt": "2026-05-07T14:34:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24171, "url": "https://github.com/glpi-project/glpi/issues/24171", "author": "kabassanov", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-07T13:45:47Z", "updatedAt": "2026-05-07T14:34:42Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "[11] Can't authorize from Docker compose solution", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nCan't auth after fresh install in GLPI.\nBut if I downgrade version to 10 all good.", "priority": "medium", "type": "support", "createdByEmail": "sage.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "sage.bennett@peppermint.local", "text": "Same for local installaion (Not a Docker)\n\n[Image omitted]\n\nOriginal response date: 2026-05-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4385492549, "author": "Disinterpreter", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24138#issuecomment-4385492549", "createdAt": "2026-05-06T05:57:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24138, "url": "https://github.com/glpi-project/glpi/issues/24138", "author": "Disinterpreter", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-05T12:57:31Z", "updatedAt": "2026-05-06T07:16:52Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Visual issues in ticket form for theme dark_auror", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nBefore closing the ticket, all fields are displayed correctly.\n\n[Image omitted]\n\nBut after closing it, the fields on the left side in the ticket panel become difficult to read.\n\n[Image omitted]\n\nReproduction steps:\ncreate and close tickets in auroa_dark theme", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "All dark themes (dark auror, darker and midnight), have color contrast issues with the field input disabled styles.\n\nOriginal response date: 2026-04-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4275703744, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23962#issuecomment-4275703744", "createdAt": "2026-04-19T10:24:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23962, "url": "https://github.com/glpi-project/glpi/issues/23962", "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "open", "stateReason": null, "createdAt": "2026-04-18T14:59:21Z", "updatedAt": "2026-04-19T16:57:05Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Massive action ticket linking ignores entity tree structure", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen linking tickets via massive action, the dropdown only shows tickets from the root entity, despite having a tree structure selected.\n\nExpected behavior:\n\nDropdown should display tickets from all entities within the selected tree structure, not only the root entity.\n\nAdditional context:\nWe discovered that this issue occurs due to the entity_restrict parameter in the POST request.\n\nPotential problematic code locations:\n\ndropdown.php\n'if (isset($post['entity_restrict']) && 'default' === $post['entity_restrict'])'\n\nHere, $post['entity_restrict'] never equals 'default', so the condition is never satisfied.\n\n CommonITILObject_CommonITILObject.php\n''entity_restrict' => $_SESSION['glpiactive_entity'],'\n\nThis should likely use 'glpiactiveentities' instead of 'glpiactive_entity' to properly handle tree structure selection.", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "devon.blair@peppermint.local", "text": "In versions prior to 11, simply specifying the ticket number worked as expected. As a temporary workaround, we modified CommonITILObject_CommonITILObject.php.\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4249593919, "author": "rusakkl", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23876#issuecomment-4249593919", "createdAt": "2026-04-15T05:52:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23876, "url": "https://github.com/glpi-project/glpi/issues/23876", "author": "rusakkl", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-15T05:49:00Z", "updatedAt": "2026-04-16T12:21:09Z", "closedAt": null } }, { "title": "GraphQL RSQL Ordering", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nnightly 11.0-1355f4e\n\nIssue description:\nWe are following the nightly releases on our testing server, to implement GraphQL in our automation. This time I looked through the last few pull requests to check if this problem was already addressed, but found nothing open that I understood as related. Please tell me if I should not open issues for nightly versions.\n\nToday we noticed issues with the =notnull= and =notempty= RSQL operators. The same queries work or fail, depending on the order of the filters given.\n\nThis query returns sucessfully:\n\nIf we move the last two directives to another position, this returns an \"Internal Server Error\", e.g. with a filter string like this:\n\nInterestingly, moving them to the very front of the filter string works as well.", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The internal exception is \"RSQL query has one or more unclosed groups\".\nIt seems like the group open character \"(\" after an operator that doesn't expect a value is skipped by the Lexer. This kind of issue would not be exclusive to the GraphQL side of the API.\n\nOriginal response date: 2026-04-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4259073166, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23936#issuecomment-4259073166", "createdAt": "2026-04-16T09:51:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23936, "url": "https://github.com/glpi-project/glpi/issues/23936", "author": "tst-plutex", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2026-04-16T09:10:12Z", "updatedAt": "2026-04-16T09:51:27Z", "closedAt": null } }, { "title": "The entity import rule is not working in a larger environment.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nI have configured import rules to assign entities based on IP address ranges.\nHowever, GLPI is not applying these rules correctly and is assigning all imported assets to the root entity.\n\nThis issue occurs in a large-scale environment with more than 50,000 computers.\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. Configure import rules for entity assignment (e.g., based on IP ranges)\n2. Run inventory import (via GLPI Agent / Inventory)\n3. Check the assigned entity of imported assets", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "bailey.bennett@peppermint.local", "text": "HI team, any feedback about this problem?\n\nOriginal response date: 2026-04-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4209397818, "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23568#issuecomment-4209397818", "createdAt": "2026-04-08T20:26:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23568, "url": "https://github.com/glpi-project/glpi/issues/23568", "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-21T15:27:25Z", "updatedAt": "2026-04-08T20:26:35Z", "closedAt": null } }, { "title": "KB FAQ - Target not working in simplify interface", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nCurrently, i have a KB, with only 1 target on on a specific user and FAQ enable.\n\nWhen i'm logged on another user, in the simplified interface. The KB is still visible.\n\nWe expect the KB not to been shown\n\nReproduction steps:\n1. Write a KB, enable the FAQ and affect a target to a specific user\n2. Connect on another user, in simplified interface, the KB will be shown in FAQ", "priority": "medium", "type": "support", "createdByEmail": "reese.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "reese.bennett@peppermint.local", "text": "Reference in docs:\n\n[Image omitted]\n\nOriginal response date: 2026-04-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4207004783, "author": "mat44444-us", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23794#issuecomment-4207004783", "createdAt": "2026-04-08T14:27:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23794, "url": "https://github.com/glpi-project/glpi/issues/23794", "author": "mat44444-us", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-08T04:59:57Z", "updatedAt": "2026-04-08T14:29:10Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Helpdesk Translation Tab Name performance issue with many entities", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0/bugfixes\n\nIssue description:\nAfter adding 100,000 entities to my dev instance to stress test certain features and prepare to restart my PR rewriting the entity selector with Vue, I noticed it was impossible to view the Config page without increasing the max memory to 2GB and removing the max execution time. I finally tracked down the issue to Helpdesk\\HelpdeskTranslation::getTabNameForItem.\n\nIn order to show the Helpdesk translation tab, it always tries to count the number of translations even if tab counters are not shown.\nEven if the counters are shown, the process is not optimal.\n\nTo count the translations, it seems to:\n1. Calls Entity::find() with no arguments causing all 100,000+ entities with every single column to be loaded into memory.\n2. Takes just the keys from the loaded entities array, which are the IDs, and again loads every single entity fresh from the DB into an object instance using Entity::getById. So now, I have 200,000+ entities with all of their data loaded into memory.\n3. All 100,000 entities are run through array_map calling Helpdesk\\HelpdeskTranslation::getTranslationsForItem.\n4. For each entity, getTranslationsForItem takes just the ID for the entity and loads every single translation into memory in its entirety.\n5. All translations are then reduced with array_reduce into an array keyed by language\n6. Finally, the count of languages is found.\n\nEven with the huge number of entities, which is apparently how many an actual client has, this seems like it could be optimized and would affect even instances with less entities.\n\nCurrent metrics:\n- Page load time: 1.6 minutes\n- Peak memory usage: 1.4 GB\n- 202,331 SQL requests", "priority": "high", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Similar issues seem to exist for other methods in Glpi\\Helpdesk\\HelpdeskTranslation.\n\nOriginal response date: 2026-03-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4060433401, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23274#issuecomment-4060433401", "createdAt": "2026-03-14T12:00:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23274, "url": "https://github.com/glpi-project/glpi/issues/23274", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "forms", "performance" ], "state": "open", "stateReason": null, "createdAt": "2026-02-28T18:31:51Z", "updatedAt": "2026-03-30T22:03:20Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Inconsistent lifecycle of _promoted_task_id parameter on new ticket creation screen after task promotion (GLPI 11)", "detail": "Affected version:\n11.04\n\nIssue description:\nWhen promoting a task to a ticket in GLPI 11, the _promoted_task_id URL parameter presents an inconsistent lifecycle on the new ticket creation screen.\n\nThis parameter is used to keep the context of the promoted task, but it is not consistently handled, which can result in unintended linking of newly created tickets to the parent ticket.\n\nReproduction steps:\nSteps to reproduce the behavior:\n\n1. Open an existing ticket.\n2. From one of its tasks, click “Promote to ticket”.\n3. The new ticket creation form is opened with the _promoted_task_id parameter present in the URL.\n4. On the ticket creation form, change any of the following fields:\n - Type\n - Category (ITIL Category)\n - Requester\n5. Observe the URL and/or save the ticket.\n\nExpected behavior:\nThe _promoted_task_id parameter should have a well-defined and consistent lifecycle, for example:\n\n- Be used only during the promoted ticket creation and automatically cleared after save, or\n- Be handled internally (server-side) without relying on a persistent URL parameter, or\n- Be explicitly invalidated after the first form submission.\n\nThe parameter should never:\n- Be silently removed when editing form fields, nor\n- Remain active after saving the ticket, allowing unintended reuse of the promotion context.\n\n---\n\nObserved behavior:\n- The new ticket creation screen initially loads with _promoted_task_id in the URL.\n- When editing certain form fields (Type, Category, Requester), the _promoted_task_id parameter is automatically removed from the URL without explicit user action.\n- If the ticket is saved while the _promoted_task_id parameter is still present in the URL, the parameter remains active.\n- As long as the user stays on the same page, any newly created tickets are automatically linked to the original parent ticket, until:\n - the page is refreshed, or\n - the user navigates away.\n\n---\n\nScreenshots / Videos:\nVideo demonstrating the issue:", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "As far as I can tell, the only issue here is that the parameter remains in the URL when a ticket is created and the user's preference is to not go to newly created items.\n\nAs for the lifecycle of the parameter, once the form is loaded the URL parameter is not needed as a hidden input is set in the form for it.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4139469317, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22464#issuecomment-4139469317", "createdAt": "2026-03-27T01:41:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22464, "url": "https://github.com/glpi-project/glpi/issues/22464", "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-22T15:12:39Z", "updatedAt": "2026-03-27T01:42:19Z", "closedAt": null } }, { "title": "Custom asset search columns is incorrect", "detail": "Issue description:\nI've created a custom asset with 2 fields:\n\n[Image omitted]\n\nBut on search page, several fields that are not part of the asset are still shown:\n\n[Image omitted]\n\nNothing wrong in logs.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "AFAIK the field customization here was only meant to affect the form UI. If native fields are removed from a form, they still exist but are hidden for everyone. This also does not affect the API, much like ticket templates.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993913536, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22804#issuecomment-3993913536", "createdAt": "2026-03-03T22:17:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22804, "url": "https://github.com/glpi-project/glpi/issues/22804", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-23T08:07:15Z", "updatedAt": "2026-03-27T00:57:13Z", "closedAt": null } }, { "title": "## Bug report: Planning recall notification - empty variables since 11.0.6", "detail": "Issue description:\nGLPI version: 11.0.6\nPrevious working version: 11.0.2\n\nIssue description:\nSince upgrading to GLPI 11.0.6, the variables ##recall.item.name## and ##recall.item.url## return empty values in the planning recall notification template.\n\nReproduction steps:\n1. Create a task linked to a ticket and set a reminder\n2. Wait for the planning recall notification to be sent\n3. The variables ##recall.item.name## and ##recall.item.url## are empty in the received email\n\nExpected behavior:\nThe variables ##recall.item.name## and ##recall.item.url## should return respectively the name of the task and the URL to access it, as they did in version 11.0.2.\n\nObserved behavior:\nBoth variables return an empty string, resulting in a broken notification with no task name and no link.\n\nAdditional context:\nI tested the exact same notification template on a GLPI instance running version 11.0.2 and everything works perfectly. The issue appears to be a regression introduced in version 11.0.6.\n\nThe notification template and configuration are identical on both instances.", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "noel.bennett@peppermint.local", "text": "## Additional findings\n\nAfter further investigation, I was able to narrow down the issue:\n\nThe variable ##recall.item.url## is working correctly on version 11.0.6. The problem is solely with ##recall.item.name## which returns an empty string.\n\nIn the default notification template:\n\nSince ##recall.item.name## is empty, the link exists in the HTML but is invisible to the user, as there is no visible text to click on. This gives the impression that ##recall.item.url## is also broken, but it is not.\n\n### Workaround\n\nReplacing ##recall.item.name## with a static text fixes the issue:\n\nThe link works correctly with this workaround. The only remaining bug is ##recall.item.name## returning an empty value since version 11.0.6, which worked fine on version 11.0.2.\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4125358107, "author": "Manu-emn", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23619#issuecomment-4125358107", "createdAt": "2026-03-25T10:21:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23619, "url": "https://github.com/glpi-project/glpi/issues/23619", "author": "Manu-emn", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-25T10:07:35Z", "updatedAt": "2026-03-25T10:21:41Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Uncaught PHP Exception Twig\\Error\\RuntimeError", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nI have tried to make a search in tickets. with conditions \"All contains word\"\nAnd it throws an error \"An unexpected error occurred\". After that only one temporary solution is only restarting MariaDB and Apache services and clearing cache.\n\n[Image omitted]\n\nReproduction steps:\n1. Go to tickets.\n2. Press search.\n3. Change Status to All (last option).\n4. Choose contains.\n5. Enter word what to search.\n\nEnvironment details:\nGLPI: 11.0.4 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: 2 files changed\n A: inc/downstream.php\n D: install/install.php\n\nOperating system: Linux VM-GLPI01 6.1.0-42-amd64 #​1 SMP PREEMPT_DYNAMIC Debian 6.1.159-1 (2025-12-30) x86_64\n\nPHP: 8.2.29 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, redis, shmop, SimpleXML, soap, sockets,\nsysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"60\" max_input_vars=\"5000\" memory_limit=\"256M\" post_max_size=\"20M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"20M\"\n\nWeb server: Apache/2.4.66 (Debian) (Apache/2.4.66 (Debian) Server at support.company.net Port 443)\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36\nEdg/144.0.0.0\n\nDatabase:\n\nServer Software: Debian 12\n\nServer Version: 10.11.14-MariaDB-0+deb12u2\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@localhost/glpi\n\nHost info: Localhost via UNIX socket\n\nRequirements:\nPHP version (8.2.29) is supported.PHP version (8.2.29) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (10.11.14) is supported.Database engine version (10.11.14) is\nsupported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/lib/glpi/_cache has been validated. Write access to /var/lib/glpi/_cron\nhas been validated. Write access to /var/lib/glpi has been validated. Write access to /var/lib/glpi/_graphs has been validated.\nWrite access to /var/lib/glpi/_lock has been validated. Write access to /var/lib/glpi/_pictures has been validated. Write access\nto /var/lib/glpi/_plugins has been validated. Write access to /var/lib/glpi/_rss has been validated. Write access to\n/var/lib/glpi/_sessions has been validated. Write access to /var/lib/glpi/_tmp has been validated. Write access to\n/var/lib/glpi/_uploads has been validated.Write access to /var/lib/glpi/_cache has been validated.\nWrite access to /var/lib/glpi/_cron has been validated.\nWrite access to /var/lib/glpi has been validated.\nWrite access to /var/lib/glpi/_graphs has been validated.\nWrite access to /var/lib/glpi/_lock has been validated.\nWrite access to /var/lib/glpi/_pictures has been validated.\nWrite access to /var/lib/glpi/_plugins has been validated.\nWrite access to /var/lib/glpi/_rss has been validated.\nWrite access to /var/lib/glpi/_sessions has been validated.\nWrite access to /var/lib/glpi/_tmp has been validated.\nWrite access to /var/lib/glpi/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed:\nctype, iconv, sodium.\nWrite access to /var/www/html/glpi/marketplace has been validated.Write access to\n/var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.Timezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I don't know how much this can be changed.\n\nThe \"All\" search option is not well supported at all by DB servers and is a big performance concern on larger GLPI installations. I cannot even test it because it tries using more than 61 table joins in the query and that is the limit for MariaDB.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4120659090, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22898#issuecomment-4120659090", "createdAt": "2026-03-24T18:57:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22898, "url": "https://github.com/glpi-project/glpi/issues/22898", "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-29T13:13:59Z", "updatedAt": "2026-03-24T18:57:19Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Issue - Can't transfer items between entities", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nGLPI returns errors when it tries to transfer items between entities.\n\nWhat is expected to happen is for the item to transfer between another entity.\n\nAffected page:\nfront/devices.php\n\nReproduction steps:\n1. Go to any component\n2. Select items\n3. Select add to transfer list\n4. Gives out error\n\n[Image omitted]\n[Image omitted]\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "dakota.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I think the bug is that the option to transfer individual components is shown. From what I can tell, component items are supposed to inherit the entity settings from the component definition/type. If you create a component in the root entity and enable \"Child entities\" on the item, you cannot switch to a child entity and then add an individual component for it.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4119765119, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23596#issuecomment-4119765119", "createdAt": "2026-03-24T16:43:39Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23596, "url": "https://github.com/glpi-project/glpi/issues/23596", "author": "Giorgio6846", "anonymizedAuthorEmail": "dakota.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-24T14:14:53Z", "updatedAt": "2026-03-24T17:50:34Z", "closedAt": null } }, { "title": "Failed to submit form from Service Catalog: Out of range for users_id_tech (-1) in tickettasks INSERT with dynamic task assignment to logged user", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen submitting a form from the Service Catalog (native Forms in GLPI 11) that uses a Ticket Template which includes a Task Template assigned to the \"current user\" / \"requester\" / \"logged-in user\", the form submission fails with the user-facing message:\n\n\"Failed to submit form, please contact your administrator.\"\n\nIn the logs (files/_log/php-errors.log), the following MySQL error appears during INSERT into glpi_tickettasks:\n\n[2026-03-19 17:11:20] glpi.ERROR: * An error occured during the form Reunió puntual submission: MySQL query error: Out of range value for column 'users_id_tech' at row 1 (1264) in SQL query \"INSERT INTO glpi_tickettasks (content, taskcategories_id, actiontime, state, is_private, users_id_tech, groups_id_tech, tickets_id, date, tasktemplates_id, uuid, users_id, timeline_position, date_creation, date_mod) VALUES ('Registre de temps de la reunió.', '23', '1800', '2', '1', '-1', '0', '15', '2026-03-19 17:11:20', '1', '547b7050-ccbe-4668-9450-0e1d043737cd', '8', '1', '2026-03-19 17:11:20', '2026-03-19 17:11:20')\".\n\nReproduction steps:\n1. Create a Form in Assistance → Forms (e.g. name: \"Reunió puntual\").\n2. Create or use a Task Template (Setup → Dropdowns → Task templates) with \"Technician\" assigned to \"Current user\" / \"Requester\" / \"Logged user\" (the option that sets users_id_tech = -1 internally).\n3. Link this Task Template to a Ticket Template (via predefined fields → add Task and select the template).\n4. Associate the Ticket Template with the Form (or use it in destination configuration).\n5. Log in as a regular user (not super-admin if possible).\n6. Go to Service Catalog and submit the form to create a ticket.\n→ Submission fails with \"Failed to submit form...\".", "priority": "medium", "type": "support", "createdByEmail": "reese.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello, I believe this issue is already fixed here:\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4110659694, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23551#issuecomment-4110659694", "createdAt": "2026-03-23T13:36:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23551, "url": "https://github.com/glpi-project/glpi/issues/23551", "author": "pplaniol", "anonymizedAuthorEmail": "reese.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-19T17:36:13Z", "updatedAt": "2026-03-23T13:36:28Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "SLA paused in solution and counting as a pending in the statistics", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.15\n\nIssue description:\nwhen i chance one ticket status for solution and one time after, other people reopen this ticket, the time of solution is count with pending in statistics. When I change one status for pending, too count with pending in stistcs. How count with pending only the status is pending and the time of solution resume the date/time with the hour what the ticket was solution, no with time was reopen?\n\nReproduction steps:\n1 open one ticket\n2 solution the ticket\n3 wait one time\n4 reopen the ticket\n5 look the tab statistics in pending time", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "kai.blair@peppermint.local", "text": "I also have this question, what is the correct approach for this situation?\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4008393519, "author": "wandersilva-code", "anonymizedAuthorEmail": "kai.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23359#issuecomment-4008393519", "createdAt": "2026-03-05T23:16:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23359, "url": "https://github.com/glpi-project/glpi/issues/23359", "author": "wesleipedroza", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-04T21:27:37Z", "updatedAt": "2026-03-05T23:16:10Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Dropdowns: missing, extra or inconsistent types and models for components", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAll components (Setup -> Components) have either a \"Type\" or a \"Model\" field or both. These items show up under Setup -> Dropdowns -> Types|Models, but I think there are some problems:\n\nMissing Types/Models\nSome Types|Models are missing here and the only way to reach or configure them is via the respective component editor. Over there the \"Type\" or \"Model\" selector has an i and a + to the right of it and the + allows to add a new type/model for this specific component. The target of the i depends on whether you are creating a new item (then it goes to the list of all configured types/models, but without an \"Add\" button there) or if you are editing an existing one, then the i will lead to the editor of the currently selected type/model. This is a quite inconvenient way to handle those.\nI think the following component types/models are affected:\n\n- Battery: Type\n- Firmware: Type and Model\n- Hard drives: Type\n\nExtra Models\nOn the other hand there are dropdowns, where I couldn't find a corresponding field in the component editor:\n\n- Device sensor models (\"Sensor\" component doesn't have a \"Model\" field)\n- Device generic models (\"Generic device\" component doesn't have a \"Model\" field)\n\nThis leads me to the related question, why do some components only have a \"Type\" field, others only a \"Models\" field and some have both, what does this depend on?\n\nNaming\nSome dropdown type/model names are inconsistent and/or difficult to match to the corresponding component name. Maybe they are used elsewhere too, otherwise it's e.g. noticeable here:\n\nComponent: Controllers\nDropdowns: Device Control Model\n\nComponent: Generic devices (assuming it should have both \"Type\" and \"Model\")\nDropdowns: \"Generic types\" and \"Device generic models\"\n\nComponent: PCI devices\nDropdowns: Other component models\n\nOn most components the models are named \"Device ITEM models\", while the corresponding types are \"ITEM types\".\n\nMisc\n\n- The \"Soundcards\" component does have a \"Type\" field, but in this case it's a string and not a dropdown. Is this intentional?\n- Setup -> Dropdowns -> Types -> \"Interface types (Hard drive...)\" is used for \"Hard drives\", but also for \"Drives\", \"Graphics cards\" and \"Controllers\", maybe there is a better name for it (like \"Bus interface types\"?). Also, would it make sense to allow this field for \"Network cards\" as well?\n\nReproduction steps:\n(I hope the description above is sufficient.)", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I immediately confirm, mainly because I saw these a few days ago and fixed some (naming inconsistencies) in the Vue frontend project.\n\nOriginal response date: 2026-03-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3997612895, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23350#issuecomment-3997612895", "createdAt": "2026-03-04T13:37:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23350, "url": "https://github.com/glpi-project/glpi/issues/23350", "author": "sl077", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-03-04T13:32:20Z", "updatedAt": "2026-03-04T13:38:09Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Many non-existent rules", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI only have 212 Business rules for tickets.\n\n[Image omitted]\n\nWhen selecting a rule, the quantity increases in size.\n\n[Image omitted]\n\n[Image omitted]\n\nAfter a certain rule, an error occurred.\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "sage.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm.\nSince the rule list is loaded in a tab, which is an AJAX request, the list of IDs in the user's session never gets cleared but it happily keeps re-adding the same items to the list each time the list shows.\n\nI have no suggestion at the moment. The feature itself seems very prone to breaking and a misuse of the session global, but it was specifically asked to re-add it for rules after it was removed while rewriting the UI code for it.\n\nOriginal response date: 2026-01-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3829276234, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22936#issuecomment-3829276234", "createdAt": "2026-01-31T20:20:07Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22936, "url": "https://github.com/glpi-project/glpi/issues/22936", "author": "RobertoMarcelino", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-31T19:29:36Z", "updatedAt": "2026-03-02T14:50:52Z", "closedAt": null } }, { "title": "Webhooks : display bug on URL column", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello,\n\nWe noticed a display bug in the queries log tab in the webhook configuration :\nThe URL column extends too much when this url is long\n\n[Image omitted]\n\nThis causes other columns to overflow outside of the main container :\n[Image omitted]\n\nThank you in advance,\n\nSincerely\n\nAnthony B from IT Gouvernance.", "priority": "medium", "type": "bug", "createdByEmail": "reese.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Probably related to #21148\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3961301946, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23247#issuecomment-3961301946", "createdAt": "2026-02-25T18:50:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23247, "url": "https://github.com/glpi-project/glpi/issues/23247", "author": "bessantoy", "anonymizedAuthorEmail": "reese.adler@peppermint.local", "assignees": [], "labels": [ "bug" ], "state": "open", "stateReason": null, "createdAt": "2026-02-25T16:06:12Z", "updatedAt": "2026-02-25T18:50:50Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Contribution request: Add German date and number formats (dd.mm.yyyy, dd.mm.yy, #.###,##)", "detail": "Contribution description:\nI would like to contribute support for additional German-style display formats in GLPI user preferences:\n\nDate formats:\ndd.mm.yyyy\ndd.mm.yy\n\nNumber format:\n#.###,## ((thousands separator . (dot) and decimal separator , (comma))\n\nThe goal is to make these formats selectable in preferences and applied consistently across UI rendering (date and numeric display), while keeping backward compatibility with existing format options.\n\nPlanned scope of contribution:\n\n- Add new date format options to the existing date format list\n- Add one new number format option to the existing number format list\n- Ensure formatting logic supports these options in display/serialization layers where applicable\n- Update related API schema enums/documentation for preference fields if needed\n- Add/adjust tests to cover the new options and avoid regressions\n\nIf this direction is acceptable, I can open a PR with implementation + tests", "priority": "medium", "type": "support", "createdByEmail": "avery.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi, thanks for your proposition.\n\nThat sounds OK with me, I've never really used/worked on those features, I have no idea how stable/reliable it currently is.\nYou plan seems also correct.\n\nMaybe wait until next week before beginning to work on that, giving time to others to give feedback if they want.\nJust note it must target current main branch (to be included in next major, since v11 is bugfixes only).\n\nHappy coding :)\n\nOriginal response date: 2026-02-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3890261262, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23095#issuecomment-3890261262", "createdAt": "2026-02-12T11:11:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23095, "url": "https://github.com/glpi-project/glpi/issues/23095", "author": "rbrannath", "anonymizedAuthorEmail": "avery.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-12T10:57:24Z", "updatedAt": "2026-02-12T11:11:17Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Mailgate does not record rejected emails in glpi_notimportedemails when recipient is unauthorized", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.22\n\nIssue description:\nWhen an email is rejected by the mailgate because the recipient is not authorized, GLPI correctly counts the email as refused, but no record is created in the table glpi_notimportedemails, and therefore nothing appears in the Not imported emails list.\n\nThe root cause is that the field to is NULL at insert time, while the database schema defines this column as NOT NULL, causing the INSERT to fail.\n\nThis results in a loss of traceability for rejected emails.\n\nReproduction steps:\n1. Configure a mail collector (IMAP).\n2. Send an email to the collector address.\n3. Ensure the recipient is not authorized (e.g. no matching user / entity permissions).\n4. Run the mailgate (cron or manual).\n\nActual behavior\n\n- The mailgate reports the email as refused.\n- No entry is created in glpi_notimportedemails.\n- The Not imported emails list remains empty.\n- Only MySQL / GLPI logs show the failure.", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed in #21681for GLPI v11.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3874211437, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23060#issuecomment-3874211437", "createdAt": "2026-02-09T22:30:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23060, "url": "https://github.com/glpi-project/glpi/issues/23060", "author": "SruiSan", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-09T16:07:10Z", "updatedAt": "2026-02-09T22:30:20Z", "closedAt": null } }, { "title": "Updating asset name do not update it on existing Dropdown::show", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello,\nWhen renaming an existing software, it renames it in Dropdown but when selecting it, it still shows the old name.\nVideo:\n\nAffected page:\n\nReproduction steps:\n1. Go to Assets > Computer.\n2. Create or select an existing computer.\n3. Go to \"Softwares\" tab.\n4. In \"Install a software field\", select an existing software on dropdown.\n5. Open a new browser tab.\n6. Go to Assets > Software in this new tab.\n7. Select the software on the table.\n8. Rename the software.\n9. Go back to the previous tab.\n10. The AJAX dropdown updates the name of the software, but when selecting it, it shows the old name.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Really minor issue, that only happen on this very specific workflow.\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3822193519, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22905#issuecomment-3822193519", "createdAt": "2026-01-30T07:01:15Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22905, "url": "https://github.com/glpi-project/glpi/issues/22905", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2026-01-29T19:38:42Z", "updatedAt": "2026-01-30T07:01:15Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Duplicated forms keep the original name in the Service Catalog", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nIn GLPI 11, when a form is duplicated and then renamed, the Service Catalog may still display the original name.\n\nAs an example, I duplicate the “Report a problem” form and rename it to “My form title”:\n[Image omitted]\n\nand here is the result when I preview my form:\n[Image omitted]\n\nThis problem seem to appears only with the built-in forms in GLPI 11\n\nAffected page:\n/ServiceCatalog\n\nReproduction steps:\n1. Go to Administration → Forms\n2. Select a built-in form (e.g. “Report a problem”)\n3. Clone the form\n4. Change its name\n5. Save\n6. Open the Service Catalog", "priority": "medium", "type": "support", "createdByEmail": "bailey.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "It seems you have translations for your form, did you make sure to update them too?\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3778515744, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22763#issuecomment-3778515744", "createdAt": "2026-01-21T14:46:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22763, "url": "https://github.com/glpi-project/glpi/issues/22763", "author": "Julien-lgx", "anonymizedAuthorEmail": "bailey.adler@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-20T17:00:10Z", "updatedAt": "2026-01-21T14:46:29Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Mail collector entity assignment fails for child entity users", "detail": "Affected version:\n11\n\nIssue description:\n## Problem\n Mail collector rejects emails from users in child entities with \"Unable to affect the email to an entity\" error.\n\n ## Solution\n I've created a fix for this issue:\n ## Details\n Bug in src/RuleMailCollector.php line 298 - type comparison issue.", "priority": "medium", "type": "support", "createdByEmail": "morgan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "~~Hi, please open a pull request with your changes.~~ see #22637\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3742149147, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22636#issuecomment-3742149147", "createdAt": "2026-01-13T06:11:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22636, "url": "https://github.com/glpi-project/glpi/issues/22636", "author": "loulouontop", "anonymizedAuthorEmail": "morgan.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-12T16:27:08Z", "updatedAt": "2026-01-13T06:11:52Z", "closedAt": null } }, { "title": "Impact analysis doesn't use GLPI permissions", "detail": "Affected version:\n10 and 11\n\nIssue description:\nImpact itemtypes do not use any of the GLPI permission system as they do not have their own \"rightname\" and aren't extending CommonDBChild. This prevents users from accessing the information in the legacy API and it is also blocking a clean implementation in the new API.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "drew.bennett@peppermint.local", "text": "I second this.\nImpact analysis seems to be the only asset-related resource that can't be obtained via API.\nOur team, in particular, is working on integrations with other tools, and this information is extremely important.\n\nOriginal response date: 2025-12-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3661758976, "author": "ftoledo", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22052#issuecomment-3661758976", "createdAt": "2025-12-16T18:00:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22052, "url": "https://github.com/glpi-project/glpi/issues/22052", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2025-11-24T19:35:40Z", "updatedAt": "2025-12-16T18:00:42Z", "closedAt": null } }, { "title": "v11.0.4: My Client users see all technicians in the “Requester” field", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen client accounts are restricted to their sub-entity, they see all technicians in the Requester dropdown menu (and possibly Assigned/Observer), even if:\n\nThe client profiles are in standalone mode with only the right to view their own tickets.\n\nThe clients do not have permissions on the parent entity.\n\nThe clients have recursive permissions on their own entity.\nThe technicians have recursive permissions on the parent entity. (Of course, if I remove this recursive authorization on the technicians' parent entity, the problem will be solved, but that's not the goal because otherwise the technicians won't see the tickets created in the sub-entities.)\n\nThis behavior makes it impossible to hide the lists of technicians and other accounts belonging to the parent entity from clients while maintaining recursive access to tickets for technicians.\n\nReproduction steps:\nCreate a root entity \"PIC\".\n\nCreate child entities \"Client 1\" and \"Client 2\" under PIC.\n\nCreate a technician in the PIC entity, with recursive access and the \"Technician\" profile.\n\nCreate a client in the Client 1 entity, with the \"Client\" profile.\n\nLog in with the client account → create a ticket → open the Requester field.\n\nExpected result:\n\nThe client only sees themselves as the requester.\n\nCurrent result:\n\nThe client sees all technicians from the PIC entity in the list.\n\nTechnical information\n\nAdditional context:\nExpected behavior\n\nTechnicians should not appear in the Requester/Assigned/Observer fields for client accounts limited to their sub-entity, while maintaining recursive ticket tracking for technicians.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "emerson.bennett@peppermint.local", "text": "A topic similar to my problem but dating from 2016:\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3638960254, "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22311#issuecomment-3638960254", "createdAt": "2025-12-10T21:06:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22311, "url": "https://github.com/glpi-project/glpi/issues/22311", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-09T21:44:33Z", "updatedAt": "2025-12-11T06:56:01Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Cannot see referenced instances of an Asset Definition", "detail": "Affected version:\n11.0.4-dev\n\nIssue description:\nHi,\n\nI have two types of Asset Definitions, \"A\" and \"B\". \"B\" contains a custom field linking to an instance of \"A\". But when I open an instance of \"A\" (that is referenced in the \"B\" instance) this relation is nowhere to be found. I have checked all capacities for both Asset Definition Types.\n\nIn \"B\" I reference an instance of \"A\":\n\n[Image omitted]\n\nBut then in \"A\", the relation is not visualized anywhere.\n\n[Image omitted]\n\nReproduction steps:\n1. Create two Asset Definitions - \"A\" amd \"B\".\n2. Check all capacity types for \"A\" and \"B\".\n3. Add a custom field (Dropdown) to \"B\" of type \"A\".\n4. Create an instance of \"A\" and \"B\".\n5. In \"B\", select the newly created \"A\" instance and save.\n6. Open the \"A\" instance and look for any back reference to \"B\".", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nIt is indeed currently impossible to see, from the linked items, their relations declared in custom asset fields. I doubt it is technically possible without introducing serious performances degradation.\n\nWe initially planned to have a \"Is a peripheral\" capacity, that could be used to declare an asset as a peripheral of another asset, but we did not had time to do it in GLPI 11. I hope we will find time to implement it in GLPI 12.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612092777, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22232#issuecomment-3612092777", "createdAt": "2025-12-04T12:47:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22232, "url": "https://github.com/glpi-project/glpi/issues/22232", "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-04T11:55:15Z", "updatedAt": "2025-12-04T12:47:48Z", "closedAt": null } }, { "title": "Can't add multiple groups in charge of an asset using Business Rules for Assets", "detail": "Affected version:\nGLPI 11 RC3\n\nIssue description:\nWhen creating a business rule for assets and adding the action of Assign Group in Charge I can't choose more than one, neither add a new action with the item Group in charge\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. Create a business rule for assets\n2. Add any criterion\n3. Try to assign Group in charge – you may just add one\n4. Assign a Group in charge\n5. Try to assign a new Group in charge – you don't find the action anymore, since it's already added\n\nAdditional context:\nSince GLPI 11 there's the option of multiple groups in charge of an asset. It would be greato to be possible to add them using business rules for assets.", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I requested additional info in PM.\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3451521215, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20837#issuecomment-3451521215", "createdAt": "2025-10-27T14:16:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20837, "url": "https://github.com/glpi-project/glpi/issues/20837", "author": "arthurrschaefer", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-08-30T20:37:36Z", "updatedAt": "2025-12-04T11:45:22Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Reservable Items should only be seeable if Item is managed or owned by group", "detail": "Affected version:\n11-RC5\n\nIssue description:\nHi,\n\nWith the added functionality of being able to create new asset types in glpi11 we would want to use it for reservations of meeting rooms but we dont want these reservations to be viewable by all.\n\nI created a profile with in the assistance tab 'See hardware of my groups' enabled\nThey also have 'Make a reservation' as allowed but no 'read' permissions\n\n[Image omitted]\n\nIt seems like this would mean that the user can only see the reservable items which are assigned to them or a group they are in. But in fact they can see all the reservable Items. I dont know if this is a bug or a feature?\n\nThe intended idea is:\nWe give a Helpdesk user this helpdesk profile and assign it to all the groups it should be able to create tickets for.\nThey can see only the forms that are available for their groups -> This works\nThey should only be able to reserve Items that are assigned to their groups or user. -> This is faulty (they see all reservable items)\n\nOr is there a better way to manage who can reserve what items?\n\nKind regards", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I created a profile with in the assistance tab 'See hardware of my groups' enabled\n\nThis setting is only related to visibility of the assets in the ticket form.\n\nThere is actually no way to have a different visibility of assets in the reservation feature for each profile.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611126165, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21127#issuecomment-3611126165", "createdAt": "2025-12-04T09:40:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21127, "url": "https://github.com/glpi-project/glpi/issues/21127", "author": "QuantumNomad26", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-09-24T10:55:27Z", "updatedAt": "2025-12-04T09:40:10Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 10.0.20 - search change or tickets by tasks without technician not working", "detail": "Affected version:\n10.0.20\n\nIssue description:\nI'm trying to search for changes with tasks assigned to a dedicated group but without technician but the search in list doesn't seems to work.\n\nI tried to investigate in debug on test environment and even if the SQL query in debug specify '0' as users_id_tech and it's the right value in table, the tasks are not founded and the changes not founded.\nIt works correctly when looking for changes with a task assigned to a dedicated technician\n\nI have the same behavior with tickets\n\nReproduction steps:\n1. Create a change\n2. Create a task without technician\n3. Create a change\n4. Create a task with a technician\n5. Go back to list and search for changes with criteria Tasks - Technician in charge is ------- : The resulting list is empty\n6. Go back to list and search for changes with criteria Tasks - Technician in charge is : The resulting list returns the correct change", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "casey.bennett@peppermint.local", "text": "Ok, after investigation, the error comes from the last part of the sql query :\n\nThe following part cannot work when we want users_id_tech = 0 :\n\nOriginal response date: 2025-09-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3291291366, "author": "keguira", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20998#issuecomment-3291291366", "createdAt": "2025-09-15T09:42:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20998, "url": "https://github.com/glpi-project/glpi/issues/20998", "author": "keguira", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-09-15T09:30:05Z", "updatedAt": "2025-12-04T07:50:11Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 11 : overflow issue in filters preview", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nThe \"Preview\" feature in the new filters (for notifications and webhooks) does not display a fully responsive table.\n\nFilter tab in Notification configuration\n\nFilter tab in Webhook configuration\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "cameron.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Issue is from use of table-responsive-lg in the search results list which is not unique to this context. In the regular search, the list can still overflow in some screen sizes but it is less noticeable since it takes up more of the screen. Looking back at the related PRs and issues (#11521), I think we used a specific breakpoint for responsiveness due to sticky elements breaking. We use the specific breakpoint to know when to remove the sticky table header.\n\nOriginal response date: 2025-09-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3344111941, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21148#issuecomment-3344111941", "createdAt": "2025-09-28T19:06:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21148, "url": "https://github.com/glpi-project/glpi/issues/21148", "author": "flegastelois", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "open", "stateReason": null, "createdAt": "2025-09-25T12:33:15Z", "updatedAt": "2025-12-04T07:12:50Z", "closedAt": null } }, { "title": "Setup: headers incoherence between tabs", "detail": "Issue description:\nThere is at least 4 designs in all tabs of setup, a rationalization is required", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "After looking at the various sections headers in the Setup page I see mainly 2 types\n\n[Image omitted]\n\n[Image omitted]\n\nI personally prefer the first one that has a more modern and cleaner look\n\nThe only issue is if it's been used at the top of the page, it looks a bit weird\n\n[Image omitted]\n\nMaking it left aligned could also be a solution.\nMaybe this one could be only used as a section separator and not a page title\n\n[Image omitted]\n\nOriginal response date: 2025-09-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3303212239, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/18169#issuecomment-3303212239", "createdAt": "2025-09-17T14:13:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 18169, "url": "https://github.com/glpi-project/glpi/issues/18169", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "open", "stateReason": null, "createdAt": "2024-10-31T08:54:40Z", "updatedAt": "2025-12-04T06:52:38Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Make Field Units of Measurement Explicit on Device Models", "detail": "Context:\nCurrently, several fields in the system that accept numerical values for power, mass, and dimensions (such as watts, kg, cm, meters, etc.) do not have their unit of measurement clearly and explicitly stated in the field label or as help text.\n\nProblem:\nThe lack of clarity regarding the expected Unit of Measurement for data input can lead to errors in data entry, impacting the accuracy of the data within the system. For instance, a user might enter '200' thinking in grams when the system expects kilograms.\n\nModels, I see the labels, and believe that units of measurements would be beneficial. Notably, models of assets that can be placed on a rack:\n\n- Network Devices\n- Computers\n- Enclosures\n- PDU - Max Power is already ok on 11.0.2.\n\n[Image omitted]\n\nProposed Solution (Acceptance Criteria):\nTo improve usability and data accuracy, the following modifications should be implemented:\n\nInclude the Unit in the Label: All fields that require a specific unit must have that unit included in the field label or as part of an auxiliary text immediately adjacent to the input field.\n\nExamples:\n- Change \"Power consumption\" to \"Power consumption (Watts)\" or \"Power consumption (W)\".\n- Change \"Weight\" to \"Weight (kg)\".\n\nBenefits:\nError Reduction: Drastically lowers the probability of data entry errors.\n\nImproved Usability: Makes the interface more intuitive and less ambiguous for the user.\n\nData Quality: Increases the reliability and accuracy of stored data.", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This is also useful for the plugin Carbon.\n\nOriginal response date: 2025-11-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3581345142, "author": "btry", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22075#issuecomment-3581345142", "createdAt": "2025-11-26T13:32:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22075, "url": "https://github.com/glpi-project/glpi/issues/22075", "author": "arthurrschaefer", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-11-26T13:29:24Z", "updatedAt": "2025-12-03T14:34:41Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Impact graph performance issues", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nPanning the impact graph immediately causes CPU and memory usage to spike to the point the graph becomes temporarily unresponsive after a few seconds. The longer you remain panning/zooming, the more resource usage grows. Resource usage returns to normal a short time after idle. There are likely a bunch of actions being queued up on pan and it takes a while to catch up.\n\nI did not find any obvious memory leak issues. They may exist but are less likely to occur with no auto-refresh/auto-replacement of HTML from the server.", "priority": "high", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Same on main with the latest Cytoscape version 3.33.1 and I don't see anything in the GLPI code triggering on pan/zoom.\nThe graph library I use in a plugin (VueFlow) has no such issue and doesn't spam \"network\" requests for the same data:image/svg+xml request thousands of times when panning/zooming (maybe related to the performance issue). May be a good library to switch to in core.\n\nOriginal response date: 2025-11-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3577421811, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22069#issuecomment-3577421811", "createdAt": "2025-11-25T20:16:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22069, "url": "https://github.com/glpi-project/glpi/issues/22069", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "javascript", "performance" ], "state": "open", "stateReason": null, "createdAt": "2025-11-25T15:00:04Z", "updatedAt": "2025-11-26T06:17:39Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Search results has slow DOM memory leak", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nMay address tomorrow, but adding report in case I cannot get to it or forget.\nSeen Chrome using over 9GB and found a ticket search tab I had open from a few days ago was using over 7GB.\n\nEach time the search results refresh (not a full page reload), a new massive action modal is added to the DOM. In most cases, this isn't an issue but if you have the automatic ticket list refresh enabled and leave the tab open for a long time, it will eventually exhaust memory.", "priority": "high", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Well, this is a bigger task than originally hoped. Seems like more can be blamed for runaway memory usage with AJAX refreshes:\n- Modals and randomly named global variables related to them get created and persisted\n- Select2 elements remain in memory even when they no longer exist in the DOM, probably because select2 JS still holds references\n- Our own 'select2_configs' global variable keeps adding \"new\" configs without old ones being removed\n- Other elements are detached but still in memory like loading spinners\n\nI'm fairly certain these kinds of issues exist in other parts of GLPI, just to a lesser degree.\nMy opinion is that it will take a lot of time to fix and may not even be feasible without a rewrite (Vue) and removing some dependency usage like select2 or at least a more controlled disposal/refresh process.\n\nA short-term fix is probably keeping track of the number of AJAX refreshes the search results does and forcing a full-page reload after around 100 which is higher than most non-automated refreshes and before the extra memory usage becomes problematic.\n\nOriginal response date: 2025-11-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3568074227, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22031#issuecomment-3568074227", "createdAt": "2025-11-23T15:22:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22031, "url": "https://github.com/glpi-project/glpi/issues/22031", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "performance", "task" ], "state": "open", "stateReason": null, "createdAt": "2025-11-23T01:26:24Z", "updatedAt": "2025-11-23T15:22:25Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Problem with recurring calls (duplicating, multiplying several of the same) 9.5.6 latest version.", "detail": "Affected version:\n9.5.6\n\nIssue description:\nHello friends,\nI detected a bug in version 9.5.6 , it is infinitely multiplying the recurring calls.\nex: if I have a recurring call to be opened at 10 am, it creates infinitely several calls of the same.\n\nanyone with this problem? already have correction?\n\nI noticed that even creating the call, it makes a new schedule and when it runs, it makes a new schedule, with a difference of a few minutes.\n\nReproduction steps:\n1. create a ticket template\n2. make the same call a recurrence, add a start and end date and a time to open the recurring call.\n3. Note that after he creates the ticket, he will schedule a new creation in a few minutes and this is repeated (polluting the dashboard of the tickets)\n\nEnvironment details:\nversão 9.5.6", "priority": "medium", "type": "support", "createdByEmail": "avery.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 9913, "url": "https://github.com/glpi-project/glpi/issues/9913", "author": "bmarquinhoss", "anonymizedAuthorEmail": "avery.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2021-11-22T11:37:06Z", "updatedAt": "2025-12-04T11:22:07Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI 10.0.0: GLPI with LDAP and SSO adds \"&noAUTO=1\" in notification links leading to break SSO", "detail": "Affected version:\nGLPI 10.0.2\n\nIssue description:\nHi, we’re using GLPI with LDAP and SSO. There has been a change where a link in notifications now behaves differently:\n\nExample:\n\nIn our case the “&noAUTO=1” was not really interpreted in the past with previous versions (when an SSO-session did not take place _before_ opening the link one had to refresh and SSO took place again) – _what it does now_ is breaking the SSO-experience (login-site shows up). The whole issue seems not be be new and was already fixed in the past with GLPI 9.1.2:\n\n and\n\n* “Added Auth::LDAP to prevent adding of noAuto=1” (Fixes #1744)\n\nBest,\nCarsten", "priority": "medium", "type": "support", "createdByEmail": "emerson.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 11478, "url": "https://github.com/glpi-project/glpi/issues/11478", "author": "kodicd", "anonymizedAuthorEmail": "emerson.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2022-05-03T06:41:13Z", "updatedAt": "2025-12-04T11:45:15Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI 11 - unable to list plugins (without marketplace)", "detail": "Affected version:\n11.0.0-dev (nightly)\n\nIssue description:\nI cloned my test server to migrate it to GLPI 11, so I can start testing.\nThe migration seems to have gone well, but when I want to reactivate the plugins, I have an error :\n\nMy server does not have internet access. So I do not use the marketplace.\n\nif I click on marketplace I have the list of plugins (and a message to say that I don't have internet) and it is indicated that the majority of plugins are not compatible with GLPI 11 ;)\n\nAffected page:\n/front/plugin.php\n\nReproduction steps:\n1. have v10 plugins in the plugins directory\n2. go to configuration / plugins\n\nAdditional context:\nthank you :)", "priority": "high", "type": "support", "createdByEmail": "rowan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18695, "url": "https://github.com/glpi-project/glpi/issues/18695", "author": "TheRoby", "anonymizedAuthorEmail": "rowan.adler@peppermint.local", "assignees": [], "labels": [ "complex issue" ], "state": "open", "stateReason": "reopened", "createdAt": "2025-01-09T15:48:52Z", "updatedAt": "2025-12-04T11:45:20Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "LDAP: impossible to import the same login user from multiple AD", "detail": "Affected version:\n10.0.18\n\nIssue description:\nI am not able to import the same login user from different domain\n\nReproduction steps:\n1. Administration\n2. Users\n3. LDap directory link\n4. Import new user\n5. Select \"LDAP directory choice\"\n\n6. \"Select the desidered entity\"\n\n7. push \"search\"\n\n8. The same for the oder Domain\n\n9. Import the user from the first domain (for example CMSR)\n\n10. Try to import the same user from an other domain (for example VillaBerica) this is the result", "priority": "high", "type": "support", "createdByEmail": "jesse.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 19930, "url": "https://github.com/glpi-project/glpi/issues/19930", "author": "sercasbh", "anonymizedAuthorEmail": "jesse.adler@peppermint.local", "assignees": [], "labels": [ "complex issue" ], "state": "open", "stateReason": null, "createdAt": "2025-06-05T17:33:12Z", "updatedAt": "2025-12-04T10:59:42Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "10.0.6 Bug notification with new group assigned", "detail": "Affected version:\n10.0.6\n\nIssue description:\nnotifications \"New attribution\" are send to the new group but also to the deleted groupe!..\n\nI have a notification for new attribution group based on new responsable group\non a ticket, I delete the current group and assign a new group\n\nnotifications \"New attribution\" are send to the new group but also to the deleted groupe!..\n\nReproduction steps:\nthe third notifications are send to the delete group\nand the second last are send to the new group", "priority": "medium", "type": "support", "createdByEmail": "quinn.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 14704, "url": "https://github.com/glpi-project/glpi/issues/14704", "author": "EmilieBy", "anonymizedAuthorEmail": "quinn.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-05-12T11:12:07Z", "updatedAt": "2025-12-04T11:45:17Z", "closedAt": null } }, { "title": "Ticket hover preview loads remote content", "detail": "Affected version:\n10.0.6\n\nIssue description:\nIf there's a ticket with content from an email, the remote content will be loaded. I've stumbled upon this issue, as a request has been blocked by my browser due to mixed content.\n\nThis looks like a potential leak of data to some third party, if there are tickets created by mail.\n\nAffected page:", "priority": "high", "type": "incident", "createdByEmail": "harper.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 13975, "url": "https://github.com/glpi-project/glpi/issues/13975", "author": "saz", "anonymizedAuthorEmail": "harper.adler@peppermint.local", "assignees": [], "labels": [ "security" ], "state": "open", "stateReason": null, "createdAt": "2023-02-01T10:39:24Z", "updatedAt": "2025-12-04T11:45:16Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Some local users are unable to log-in after GLPI TIMEZONE migration", "detail": "Affected version:\n10.0.7\n\nIssue description:\nAfter migrating from GLPI 9.5.2 to GLPI 10.0.7 to a MySQL server without timezone table access, I was able to login the first time but unable to login after glpi:migration:timestamps migration.\n\nBefore migration, the user has the following entry on glpi_users table (the password hash was changed to 'glpi' password to avoid data leak):\n\nAfter migration:\n\nAfter issue the glpi:migration:timestamps command:\n\nFollowing the troubleshoots steps available at I was able to identify that the end_date column value changed from 2050-01-01 00:00:00 to 0000-00-00 00:00:00. After changing the 2050-01-01 00:00:00 end_date user value to NULL I was able to login as expected.\n\nMaybe it's changing the value the end_date column value of the user to 0000-00-00 00:00:00 because our host doesn't support MySQL timezones? Most hosting services based on CPanel do not offer access to the mysql.time_zone_name table and GLPI installer allows to continue the GLPI installation/migration just fine. If it's required, this installation check should be changed to enforce it. If it isn't a requirement, maybe there's a bug on TIMEZONE migration or GLPI end_date verification logic should be changed to handle the 0000-00-00 00:00:00 value with the same treatment that the NULL value has.\n\nDiagnostic information:\nsql-errors.log:\n\nAffected page:\n\nReproduction steps:\n1. Migrate from GLPI 9.5.2 to GLPI 10.\n2. Login at GLPI (it works as expected).\n3. Do the TIMEZONE migration.\n4. Some local users are unable to login.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 14842, "url": "https://github.com/glpi-project/glpi/issues/14842", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-06-01T13:40:49Z", "updatedAt": "2025-12-04T10:54:26Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Observer is not added to ticket after update to 10.0.5", "detail": "Affected version:\n10.0.5\n\nIssue description:\nSince updating from 10.0.3 to 10.0.5, when a user adds someone in CC, that 'CC user' is not added to Observer field in tickets.\nThat also means when a technician replies to a ticket, 'CC user' will not receive this reply because 'CC user' is not in Observer.\n\nThis worked just fine in version 10.0.3 and earlier versions.\n\nReproduction steps:\n1. User sends an email and creates new ticket\n2. Ticket is assigned to a technician\n3. User adds someone new in CC and sends new reply (new followup)\n\nNormally, that 'CC user' should be added as Observer ... but it is not.\n\nEnvironment details:\nGLPI 10.0.5 ( => /var/www/html)\nInstallation mode: TARBALL\nCurrent language:en_US\n\nOperating system: Linux 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64\nPHP 8.1.9 apache2handler (Core, FFI, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, bz2, calendar, ctype,\n curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, intl, json, libxml, mbstring, mysqli, mysqlnd, openssl,\n pcre, pdo_mysql, posix, readline, session, shmop, sockets, sodium, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml,\n xmlreader, xmlwriter, xsl, zip, zlib)\nSetup: max_execution_time=\"30\" memory_limit=\"128M\" post_max_size=\"8M\" safe_mode=\"\" session.save_handler=\"files\"\n upload_max_filesize=\"2M\"\nSoftware: Apache/2.4.54 (Debian) (Apache/2.4.54 (Debian) Server at helpdesk.tvz.hr Port 443\n)\n Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36 Edg/107.0.1418.35\nServer Software: Debian 11\n Server Version: 10.5.15-MariaDB-0+deb11u1\n Server SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n Parameters: glpi@localhost/glpi\n Host info: Localhost via UNIX socket\n\nPHP version (8.1.9) is supported.PHP version (8.1.9) is supported.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nmysqli extension is installed.mysqli extension is installed.\nFollowing extensions are installed: dom, fileinfo, json, simplexml.Following extensions are installed: dom, fileinfo, json, simplexml.\ncurl extension is installed.curl extension is installed.\ngd extension is installed.gd extension is installed.\nintl extension is installed.intl extension is installed.\nlibxml extension is installed.libxml extension is installed.\nzlib extension is installed.zlib extension is installed.\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nDatabase engine version (10.5.15) is supported.Database engine version (10.5.15) is supported.\nNo files from previous GLPI version detected.No files from previous GLPI version detected.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/www/html/files/_cache has been validated. Write access to /var/www/html/config has been validated. Write access to /var/www/html/files/_cron has been validated. Write access to /var/www/html/files has been validated. Write access to /var/www/html/files/_dumps has been validated. Write access to /var/www/html/files/_graphs has been validated. Write access to /var/www/html/files/_lock has been validated. Write access to /var/www/html/files/_pictures has been validated. Write access to /var/www/html/files/_plugins has been validated. Write access to /var/www/html/files/_rss has been validated. Write access to /var/www/html/files/_sessions has been validated. Write access to /var/www/html/files/_tmp has been validated. Write access to /var/www/html/files/_uploads has been validated.Write access to /var/www/html/files/_cache has been validated.\nWrite access to /var/www/html/config has been validated.\nWrite access to /var/www/html/files/_cron has been validated.\nWrite access to /var/www/html/files has been validated.\nWrite access to /var/www/html/files/_dumps has been validated.\nWrite access to /var/www/html/files/_graphs has been validated.\nWrite access to /var/www/html/files/_lock has been validated.\nWrite access to /var/www/html/files/_pictures has been validated.\nWrite access to /var/www/html/files/_plugins has been validated.\nWrite access to /var/www/html/files/_rss has been validated.\nWrite access to /var/www/html/files/_sessions has been validated.\nWrite access to /var/www/html/files/_tmp has been validated.\nWrite access to /var/www/html/files/_uploads has been validated.\n\nAdditional context:\nAddition info: I'm using Oauth IMAP plugin for sending/receiving emails connected to Azure.", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 13269, "url": "https://github.com/glpi-project/glpi/issues/13269", "author": "oneill2john", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2022-11-10T09:55:19Z", "updatedAt": "2025-12-04T07:32:56Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "[DomainsAlert] Expiring domains sets only one email in notification queue by automatic action/crontask", "detail": "Affected version:\n10.0.3\n\nIssue description:\nI have installed latest glpi 10.0.3.\n\nA domain (example.com) expiring prior to 30 days is found by DomainsAlert crontask only one time and an email is get queued in notification queue. after that even if i manually execute DomainsAlert automatic action, email is not queuing in the notification queue menu under Administration.\n\nRoot Entity is configured with notifications 30 days before expiration.\n\nI want whenever cron will run or execute it manually, the respective email should be queued for domain alert action every time for each call .\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "dakota.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 12984, "url": "https://github.com/glpi-project/glpi/issues/12984", "author": "abhishek-rajput-44", "anonymizedAuthorEmail": "dakota.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2022-10-14T11:43:21Z", "updatedAt": "2025-12-04T11:45:15Z", "closedAt": null } }, { "title": "MSG attachment in an email that is imported via the POP3 Connector, the content is changed or converted into an EML file that is no longer fully readable", "detail": "Affected version:\n10.0.15\n\nIssue description:\nWe sometimes receive MSG files from users sent to the ticket system by email.\n\nIf we create a ticket manually and add a MSG file, it is displayed identically. The situation is different with email imports. There are several problems here.\nThe MSG file attachment is converted into an EML file. This is then unusable.\nFor unknown reasons, the MSG is sometimes imported, but due to a change within the file, the display no longer works. German umlauts and special characters are displayed strangely.\nIs it possible to set GLPI so that MSG files are saved exactly as they are sent?\n\nExamples are: \"&nbs=;\" or \"Datenschutzb=stimmungen\" (correct Datenschutzbestimmungen)\n\nReproduction steps:\n1. create an email to the ticket system with Outlook\n2. add another email from Outlook as an attachment (is then automatically a MSG file)\n3. GLPI imports this email and creates a ticket from it with an EML file that was originally the MSG file\n4. open EML file from the ticket system", "priority": "medium", "type": "support", "createdByEmail": "hayden.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 17464, "url": "https://github.com/glpi-project/glpi/issues/17464", "author": "schieffahrer", "anonymizedAuthorEmail": "hayden.adler@peppermint.local", "assignees": [], "labels": [ "help wanted" ], "state": "open", "stateReason": null, "createdAt": "2024-07-07T15:20:52Z", "updatedAt": "2025-12-04T11:27:22Z", "closedAt": null } }, { "title": "Ability to assign a profile to a user in his own entity", "detail": "Affected version:\n10.0.3\n\nIssue description:\nIn a sub-entity (not root), a user with Admin or Super-Admin profile can not attach a profile to another user in its entity or sub-entities. Sub-entities admins should be able to assign a profile in their own entity or sub-entities.", "priority": "medium", "type": "support", "createdByEmail": "jordan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 13029, "url": "https://github.com/glpi-project/glpi/issues/13029", "author": "paidge", "anonymizedAuthorEmail": "jordan.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": "reopened", "createdAt": "2022-10-19T11:42:46Z", "updatedAt": "2025-12-04T11:29:00Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Public and integrated dashboard uses session filters without being able to change it", "detail": "Affected version:\n10.0.14\n\nIssue description:\nWe want to use the direct link to dashboard in our plants for each team to be able to display per technician group some statistics and testing the behaviors of direct / integrated dashboards.\n\nI've identified a _functionnal_ issue\n\nFeatures / bugs identified :\n- _Embed_ dashboard by-pass all security to display a dash but do not integrate or show filters : as the filters are parts of how a dash is working, this is a missing feature (so not the purpose of this ticket)\n- _Embed_ dashboard by-pass all security to display a dash independently of a logged context but uses the actual session attributes to apply current filters which make it inconsistent depending on user cases\n\nWith these two points, in _embed_ mode, the view of dashboard in direct link is non-functional.\n\nExpected behavior:\n- Embed mode dashboard should use its own filter context as the security is totaly by-passed in this mode. In the futur, it may expose things we don't want to\n- nice to have : being able to use / apply filters in this mode as it's part of the dashboard feature\n\nReproduction steps:\n1. create a dashboard with filters\n2. [UC-A] open a window with the public link\n3. [UC-B] open a window with the public link in private mode (to have a clean session)\n4. apply a filter in GLPI on the dashboard\n5. refresh UC-A : filter is applied and not manageable\n6. refresh UC-B : filter is not applied (and not manageable)", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 16967, "url": "https://github.com/glpi-project/glpi/issues/16967", "author": "keguira", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-04-22T07:17:38Z", "updatedAt": "2025-12-04T11:24:48Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "NotificationTarget inheretance broken", "detail": "Affected version:\n10.0.16\n\nIssue description:\nCompany\nCompany > Departement 1\nCompany > Departement 2\nCompany > Departement 3\nCompany > Departement 4\n\nWhile the inheritance (overwriting) of templates works fine it doesn't work for the assigned targets.\nCreate a notification on company level. All departments have the same notification.\nNow, one department decided that they don't want notifications for \"added followup\" event. So I recreated it in department 3 and changed who is receiving the notification.\nHowever, they are still receiving notifications as set in the company level (if I disable it at company level there is no notification send) but this adds a lot of maintenance work as you have to remember this each time a new entity is created. Also the GUI is misleading thinking you can control / manage it for each entity separately.", "priority": "medium", "type": "support", "createdByEmail": "rowan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 17913, "url": "https://github.com/glpi-project/glpi/issues/17913", "author": "blippercop", "anonymizedAuthorEmail": "rowan.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2024-09-23T15:45:44Z", "updatedAt": "2025-12-04T11:24:13Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "A technician is appointed, but OLA time is running out.", "detail": "Affected version:\n10.0.6\n\nIssue description:\nWhen creating a Ticket from a page /front/ticket.php from the central interface and immediately the appointment of a technician in it, when applying the rule, OLA is assigned and the time passes before the Ticket is taken, although the technician is assigned.\n\nCreating a Ticket from the central interface. Assigning a technician to a ticket.\nWe put ourselves as the Requester and another user as the Technician.\n\nIn the history of the ticket, we see that there is no mark about taking the Ticket (Take into account time).\n\nWe see that the time of OLA is coming.\n\nCreating the same Ticket, in the same category.\nWe appoint another user as the Requester and his/her ticket Technician.\n\nIn the history of the ticket, we see that there is mark about taking the Ticket (Take into account time).\n\nWe see that OLA was also assigned, but time is not running out.\n\nJust a rule.\n\nAlso, the OLA assignment is not visible in the logs when it is assigned through the rules.", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 14026, "url": "https://github.com/glpi-project/glpi/issues/14026", "author": "kofe88", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-02-08T08:27:03Z", "updatedAt": "2025-12-04T11:17:20Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Dropdown menu is still shown when selecting \"Add to transfer list\"", "detail": "Affected version:\n10.0.16\n\nIssue description:\nWhen selecting the box at the side of an agent to move it to a new Entity, if I select \"Update\" (or any other menu, I believe), clicking on the sub dropdown and select on the main dropdown the \"Transfer list\" option, the sub dropdown is still shown, as can be seen on the animation below.\n\nAffected page:\n\nReproduction steps:\n1. Select a checkbox in an item.\n2. Select \"Update\" on main dropdown.\n3. Click on sub dropdown.\n4. Select \"Add to transfer list\" on main dropdown.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 17504, "url": "https://github.com/glpi-project/glpi/issues/17504", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "open", "stateReason": null, "createdAt": "2024-07-12T13:35:57Z", "updatedAt": "2025-12-04T06:52:08Z", "closedAt": null } }, { "title": "SMTP Oauth authentication error (Azure)", "detail": "Affected version:\n10.0.15\n\nIssue description:\nTL;DR: smtp username might not be the same as email, and SMTP XOAUTH2 flow will fail. GLPI would autodisolver this using UPN, or populated by user in frontend, like it is done with SMTP Auth (BASIC)\n\nGLPI 10.0.15, On-prem AD, and Entra ID Synchronized\n\nOur support account’s username and primary SMTP address are not the same. I logged in successfully via browser, but then test SMTP fails.\n\nI tested the equivalent configuration (SMTP+OAUTH) with my individual company user account, which has identical UPN and email, and it worked successfully. This corner case is handled correctly by GLPI SMTP AUTH (Basic), where you can specify login and email information separately. However, it seems that SMTP OAUTH might be using the email as the username (i.e. UPN), which would be incorrect.\n\nIf this is reproduced, it will be an issue for a lot of users when migrating to SMTP OAUTH this fall. If this is a no-fix, docs will have to be updated to require UPN and email to hold the same value.\n\nFor example:\n\nFrom the code above, the refresh_token will be correct, but smtp_username may not, as in our case. Here’s an example of a message exchange between a client and an SMTP server using OAuth 2.0 for authentication. In this scenario, the UPN is [email redacted], the email address is [email redacted], and the OAuth access token is AAAA:\n\nThe base64-encoded string is:\n\nHere user needs to be the id (UPN in Azure) and not email. Another openid field that may work is preferrred_username, still don't know if it contains org '@contoso.com'.\n\nReproduction steps:\nYou may try to set up SMTP+OAUTH mail with an Azure account like:\n\nuser (UPN): [email redacted]\nprimary email: [email redacted]\n(we still had [email redacted], UPN, as secondary email/alias)", "priority": "medium", "type": "support", "createdByEmail": "rowan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18796, "url": "https://github.com/glpi-project/glpi/issues/18796", "author": "gabrielgbs97", "anonymizedAuthorEmail": "rowan.adler@peppermint.local", "assignees": [ { "sourceLogin": "Otijom", "anonymizedEmail": "skyler.adler@peppermint.local" }, { "sourceLogin": "orthagh", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "help wanted" ], "state": "open", "stateReason": null, "createdAt": "2025-01-23T08:02:39Z", "updatedAt": "2025-12-04T11:45:20Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "ERROR_GLPI_LOGIN_USER_TOKEN", "detail": "Affected version:\n10.0.16\n\nIssue description:\nI encountered a problem with the impossibility of obtaining a session token via user_token. I always got a response with the code ERROR_GLPI_LOGIN_USER_TOKEN. I found and solved the problem only by analyzing Apache logs. The error sounded like this: \"PHP Warning: getFromDBByCrit expects to get one result, 3 found in query \"SELECT id FROM glpi_users WHERE name = 'MY_USER_NAME' in /var/www/html/src/CommonDBTM.php on line 393\".\nIt turns out I had two old inactive accounts and an active one. As soon as I moved the inactive accounts to the trash and deleted them forever, the original request to get a session token by user_token started working as expected and I got a session_token.\n\nIs it possible to add to the condition for getting accounts only with the active flag? This would save time for other users who will encounter a similar problem in the future.", "priority": "medium", "type": "bug", "createdByEmail": "jesse.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20073, "url": "https://github.com/glpi-project/glpi/issues/20073", "author": "Gizmodo", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [ "api", "bug" ], "state": "open", "stateReason": null, "createdAt": "2025-06-19T11:49:29Z", "updatedAt": "2025-11-27T15:20:39Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "CSRF check failed for permanent delete of domains above 250 records", "detail": "Issue description:\n- I agree to follow this project's Code of Conduct\n- I have searched the existing issues\n\nAffected version:\n10.0.7 with MainAsset.php modified\n\nIssue description:\nFollowing the issue #14489 I have 5k domain records to delete.\n\nFirst, to delete them, it can only be done 1000 per 1000. If trying to select more, there is no error message but it will not work.\nI remember in previous GLPI version there was a limitation to forbid mass action above 1k records, maybe this should be added again ?\n\nBut the main issue is not here but for the permanent delete. I can delete 250 records but if I try to delete 500 or more at once, I have the error message \"The action you have requested is not allowed.\"\nIn access-errors.log I can see the message \"CSRF check failed for User ID: XX at /front/massiveaction.php\"\n\nKnowing it works for the normal delete and for permanenent delete of 250 records, is it really a CSRF issue ?", "priority": "medium", "type": "support", "createdByEmail": "riley.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 14863, "url": "https://github.com/glpi-project/glpi/issues/14863", "author": "MarcSamD", "anonymizedAuthorEmail": "riley.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-06-06T02:09:09Z", "updatedAt": "2025-12-04T11:45:17Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Entity Option 'Enable notifications by default' not working correctly", "detail": "Affected version:\n10.0.14\n\nIssue description:\nThe Value of the Entity Setting 'Enable notifications by default' under Notifications does not affect the Actors in a newly created or updated ticket.\nIf \"No\" is selected, Notifications via E-Mail/Browser still get send to the Actors of the Ticket, for example the Requester.\n\nAffected page:\n/front/entity.form.php\n\nReproduction steps:\n1. Change the 'Enable notifications by default' of an entity to \"No\" (Default is No)\n2. Have a notification set up for Type \"Tickets\" - Event \"New Ticket\"\n3. Create a ticket and assign a requester with a valid email to receive notifications\n4. Notification gets send out => Expected behaviour is that no notification is send\n\nCan be reproduced for any Notification for Type \"Tickets\" (New Followup, New Mention, etc.)", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 16829, "url": "https://github.com/glpi-project/glpi/issues/16829", "author": "SimonTheIman", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-03-26T13:46:06Z", "updatedAt": "2025-12-04T11:26:53Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Mail receiver refuse mail when \"To email header\" is not in first position", "detail": "Affected version:\nGLPI 10.0.19\n\nIssue description:\nContext:\nReceveir set to get email from O365 box every minute. Rule set to create a ticket if \"User featuring the profile is Self-Service\" and \"To email header contains [email redacted]\"\nIssue:\nWhen a mail from an existing user is send to multiple recipients, it is refused if [email redacted] is not in first position (ex: [email redacted];[email redacted]).\nIt works fine when [email redacted] is set first (ex: [email redacted]; [email redacted])\n\nSame as", "priority": "medium", "type": "support", "createdByEmail": "parker.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20892, "url": "https://github.com/glpi-project/glpi/issues/20892", "author": "lscotte", "anonymizedAuthorEmail": "parker.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-09-02T13:38:55Z", "updatedAt": "2025-12-04T10:58:58Z", "closedAt": null } }, { "title": "Unable to merge tickets without spamming clients", "detail": "Contribution description:\nWhen I create a non private followup an email gets automatically sent to the Requester, as expected.\n\nWhen I merge a ticket the Requester gets sent an email for the ticket itself and for each unlocked followup on the ticket. I can mark the source followups as private prior to merging to stop these emails however I am unable to stop the main ticket being sent as an email to the client.\n\nIs there a better way to manage this followup process as our clients are complaining about being spammed with emails?", "priority": "medium", "type": "support", "createdByEmail": "jesse.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20620, "url": "https://github.com/glpi-project/glpi/issues/20620", "author": "Dercni", "anonymizedAuthorEmail": "jesse.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-08-11T02:05:59Z", "updatedAt": "2025-09-23T07:26:59Z", "closedAt": null } }, { "title": "Very slow Global Search (5 minutes)", "detail": "Affected version:\n10.0.18\n\nIssue description:\nHey,\n\nWe have noticed that the global search is very slow on our server, taking up to 5 minutes to load. We have a fairly well-stocked database because we've been using it for a while for several clients.\n\nIn debug mode, I've identified the request that seems to be causing the problem. Do you know how to fix it?\nThe SQL query takes about 5 minutes and 30 seconds to complete\n\n[Image omitted]\n\nSQL Query :\n\nI've found a similar ticket with a pull request but I don't know if it can fix the problem we're having because an EXPLAIN gives me a different result\n\nOptimize(Search): Handle LEFT JOIN which concern counting operatio lastly #16997\n\nThanks you for your help\nRichard\n\nReproduction steps:\nSearch in Global search", "priority": "high", "type": "support", "createdByEmail": "bailey.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20264, "url": "https://github.com/glpi-project/glpi/issues/20264", "author": "richardlg-pro", "anonymizedAuthorEmail": "bailey.adler@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "open", "stateReason": null, "createdAt": "2025-07-09T20:26:57Z", "updatedAt": "2025-12-04T11:45:21Z", "closedAt": null } }, { "title": "Problem with HTML mail signatures", "detail": "Affected version:\n10.0.7\n\nIssue description:\nWhen I configure a mail signature, in Configuration>Notifications, I try to enter HTML text.\n\nFirst, the input text box is only text, not Rich-Text input box (perhaps this is the problem).\n\nI try the next signature (for example):\nMy name, My company\n\nOnce changed the signature to an HTML text, with bolds, cursives... I try to send a test email to the administrator email.\n\nBut the mail I receive is the conversion of the sitnature to HTML symbols:\nMy nameMy company\n\nI think the problem is the type of the email signature input box: perhaps it filters all the data before insert in the database, into the table of configurations.\n\nIs any way to solve this? Perhaps am I having a bad configuration?\n\nThanks in advance, and congratulations for your fantastic tool!!!", "priority": "medium", "type": "support", "createdByEmail": "hayden.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 14500, "url": "https://github.com/glpi-project/glpi/issues/14500", "author": "darthjuanan", "anonymizedAuthorEmail": "hayden.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-04-09T10:30:45Z", "updatedAt": "2025-12-04T11:45:16Z", "closedAt": null } }, { "title": "Input variables exceeded", "detail": "Affected version:\n10.0.5\n\nIssue description:\n$_POST['used'] in Dropdown class may have thousands of elements, all other variables (e.g. searchText) exceeding max_input_vars limit are left out.\nConsider increased max_input_vars a requirement for Glpi.\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "quinn.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 13513, "url": "https://github.com/glpi-project/glpi/issues/13513", "author": "po1vo", "anonymizedAuthorEmail": "quinn.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2022-12-02T15:23:48Z", "updatedAt": "2025-12-04T11:45:16Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Asset Transfering removes license", "detail": "Affected version:\n10.0.17\n\nIssue description:\nThe problem has already been described here\n\nWhen transfers computers, if the number of licenses = 1, the license is sent to the trash bin. This happens with BOX, OEM licenses, the number of which is always = 1. Because of this, there is a danger of losing data on these licenses if you empty the trash.\nThis is likely due to the fact that during migration the old license is deleted and a new one is created in another object.\n\nVideo\n\nReproduction steps:\n1. Go to Assets > Computers\n2. Create a computer in the \"Root entity\"\n3. Add and install softwares/licenses\n4. Choose a transfer template (standart rule \"complete\") and an entity (\"Root entity\") to transfer the PC\n5. Go to Management>Licenses, сhoose a trash. There will be a license in the trash and the \"Number\" field will increase by 1\n6. If you empty the trash, the license information will be lost\n\nEnvironment details:\nGLPI 10.0.17 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language:en_GB\n\nAdditional context:\nSorry, I am writing through a translator", "priority": "medium", "type": "support", "createdByEmail": "casey.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18506, "url": "https://github.com/glpi-project/glpi/issues/18506", "author": "ke029ke", "anonymizedAuthorEmail": "casey.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-12-09T09:17:39Z", "updatedAt": "2025-12-04T11:26:21Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Some ticket rules are not working when ticket is collected by mail while it works by interface", "detail": "Affected version:\n10.0.17\n\nIssue description:\nWe got an issue, we got a set of rules to extract ticket category from subject by using a regex.\nThen we got a set of rules to assign a technician based on the previously extracted category.\nTo finish we got a set of rules to assign SLA based on the category and the priority or type of the ticket.\n\nAll rules are in \"add/update\" mode.\n\nWhen we use the rule tester, all rules are evaluated and we end up with the result we want.\nWhen we create a ticket directly from GLPI it works.\n\nBut when a ticket is created by the mailgate some rules are not evaluated.\n\nAfter troubleshooting it, it looks like the ticket type is not available when creating a ticket from mailgate while evualuating rules the first time.\nIf we manually set it in the first matching rule it works.\n\nReproduction steps:\n1. Create a rule to extract category from title with 'add/update'\n2. Create a rule to set SLA based on ticket based on category and ticket type.\n\nIf you manually set a type in the rule 1 it works otherwise it doesn't.", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18368, "url": "https://github.com/glpi-project/glpi/issues/18368", "author": "SteadEXE", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-11-21T08:10:01Z", "updatedAt": "2025-12-04T11:22:35Z", "closedAt": null } }, { "title": "Asset access right problem", "detail": "Affected version:\n10.0.18\n\nIssue description:\nI create a profile with only computer and financial management read right.\nThen associate an user with this profile.\nAfter test, the user still can modify operating system and financial management fields.\nis that a bug ?", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 19601, "url": "https://github.com/glpi-project/glpi/issues/19601", "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-04-30T08:39:40Z", "updatedAt": "2025-12-04T10:56:01Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Projects tasks states don't show the state of each task", "detail": "Affected version:\n10.0.18\n\nIssue description:\nIn the projects tab, the \"project task state\" entry is only showing a list of all state, and not the state of each project task.\n\nFor example, here :\n\nWe should have two line for 113 because there is two project task.\n\nAffected page:\n/front/project.php\n\nReproduction steps:\n1. In GLPI 10.0.18\n2. Navigate to Tools -> Projects\n3. Search for a project with multiple project tasks with states\n4. Compare the project task state list under the \"project task - state\" entry with the actual project tasks state", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 19296, "url": "https://github.com/glpi-project/glpi/issues/19296", "author": "CsroDev", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-03-27T10:53:31Z", "updatedAt": "2025-12-04T07:20:39Z", "closedAt": null } }, { "title": "Consider moving our own sass file to native css", "detail": "Issue description:\nWith:\n-\n-\n-\n\nAll avaible in baseline (2023) or widely (for the rest), it may already cover all our need for our own sass files. And so we may remove compilation at runtime..\n\nI target 12.0 for the moment, but the required work may be simple to be included in 11.0\nSo let's discuss about that.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18878, "url": "https://github.com/glpi-project/glpi/issues/18878", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-02-01T09:07:33Z", "updatedAt": "2025-12-04T11:45:21Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Problem with daily Cartridge Alarms", "detail": "Affected version:\n10.0.12\n\nIssue description:\nFor some weeks now, we have the problem that the emails for the cartridge alarm are sent separately. For example, the 2 alarms are sent on 31.01:\n[Image omitted]\n\nand on 01.02. there are these 2 alarms:\n[Image omitted]\n\nalthough all 4 are set to alarm. Why do the alarms come separately? Before, the cartridge alarms were actually sent together every day.", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 16579, "url": "https://github.com/glpi-project/glpi/issues/16579", "author": "FreeMacs", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-02-19T07:53:47Z", "updatedAt": "2025-12-04T11:45:19Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Request to enhance automatic inventory of monitors", "detail": "Affected version:\n10.0.0\n\nIssue description:\nSometime automatic inventory of monitors turns people in trouble. This happens when monitors manufacturers have no respect to established standards and the agent fails to report the expected monitor serial after reading a poorly designed monitor EDID bloc.\nFor such kind of manufacturer, we started to develop the reporting of an ALTSERIAL entry in the inventory. Actually FusionInventory agent and GLPI agent supports this reporting. We can easily modify the agent to exchange SERIAL and ALTSERIAL inventory entries but, as we can't trust manufacturers, this is actually done for only few manufacturers and even only on some models.\nA nice feature for GLPI 10 would be to also show the ALTSERIAL entry when it is available in an inventory.\nBut it would also be nice to have the availability for GLPI admin users to decide the ALTSERIAL for a given model of a given manufacturer if the right serial to use when linking a monitor to a computer.\nIf such a feature is developed in GLPI, the agent wouldn't have to be updated to switch SERIAL and ALTSERIAL.\n\nFeature request summary:\n1. Show \"altserial\" of monitor when available as \"Other serial\" or \"Alternate serial\"\n2. Add an option on monitor model to:\n 1. select \"serial\" or \"altserial\" as serial to link monitor to computer,\n 2. automatically exchange \"serial\" and \"altserial\" when displaying so the expected serial is also shown", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 10165, "url": "https://github.com/glpi-project/glpi/issues/10165", "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2021-12-17T13:17:24Z", "updatedAt": "2025-12-04T11:31:48Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Performance problems with default search on tickets", "detail": "Affected version:\n10.0.7\n\nIssue description:\nPreviously, this problem was discussed on the community form:\n\nI observe severe performance problems in one place:\nI have a lot of closed tickets, about 40K. When loading a tickets page with \"closed\" status with any number of rows, it takes about 30 seconds. When switching to the second page it loaded 30 seconds again.\n\nThe standard search filter is used. I was told on a community forum that a limit should be used at the end of the SQL query, but that doesn't happen.\n\nI did some tests:\nGot a slow SQL expression from Debug mode and send direct SQL query in DB. In the case where I explicitly set the limit by 5 rows at the end of the query, the data fetch is 7.7 seconds faster, which is a significant performance improvement.\n\nGet tickets without LIMIT:\n\nResult:\n32.355 seconds\n\nGet tickets with LIMIT 0, 5:\n\nResult:\n24.618 seconds\n\nPlease, add a limit to the SQL query when receiving tickets with default search filter.\n\nAffected page:\n\nReproduction steps:\n1. Have a large number of tickets in your database (about 40K)\n2. Make a default search for tickets. Try to set different \"rows / page\". Make sure it doesn't affect performance at all.\n\nEnvironment details:\nGLPI 10.0.7 ( => /var/www/html)\nInstallation mode: TARBALL\nCurrent language:en_GB\n\nOperating system: Linux glpi.sample.com 3.10.0-1160.76.1.el7.x86_64 #1 SMP Wed Aug 10 16:21:17 UTC 2022 x86_64\nPHP 8.0.23 apache2handler (Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, apcu, bcmath, bz2,\n calendar, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, imap, intl, json, ldap, libxml,\n mbstring, mcrypt, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, session, shmop, sockets,\n sodium, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib)\nSetup: max_execution_time=\"60\" memory_limit=\"1000M\" post_max_size=\"8M\" safe_mode=\"\" session.save_handler=\"files\"\n upload_max_filesize=\"32M\"\nSoftware: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips mod_auth_kerb/5.4 PHP/8.0.23 ()\n Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36\nServer Software: MariaDB Server\n Server Version: 10.8.4-MariaDB-log\n Server SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n Parameters: glpi@localhost/glpi\n Host info: Localhost via UNIX socket\n\nPHP version (8.0.23) is supported.PHP version (8.0.23) is supported.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nmysqli extension is installed.mysqli extension is installed.\nFollowing extensions are installed: dom, fileinfo, json, simplexml.Following extensions are installed: dom, fileinfo, json, simplexml.\ncurl extension is installed.curl extension is installed.\ngd extension is installed.gd extension is installed.\nintl extension is installed.intl extension is installed.\nlibxml extension is installed.libxml extension is installed.\nzlib extension is installed.zlib extension is installed.\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nDatabase engine version (10.8.4) is supported.Database engine version (10.8.4) is supported.\nNo files from previous GLPI version detected.No files from previous GLPI version detected.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/www/html/files/_cache has been validated. Write access to /var/www/html/config has been validated. Write access to /var/www/html/files/_cron has been validated. Write access to /var/www/html/files has been validated. Write access to /var/www/html/files/_dumps has been validated. Write access to /var/www/html/files/_graphs has been validated. Write access to /var/www/html/files/_lock has been validated. Write access to /var/www/html/files/_pictures has been validated. Write access to /var/www/html/files/_plugins has been validated. Write access to /var/www/html/files/_rss has been validated. Write access to /var/www/html/files/_sessions has been validated. Write access to /var/www/html/files/_tmp has been validated. Write access to /var/www/html/files/_uploads has been validated.Write access to /var/www/html/files/_cache has been validated.\nWrite access to /var/www/html/config has been validated.\nWrite access to /var/www/html/files/_cron has been validated.\nWrite access to /var/www/html/files has been validated.\nWrite access to /var/www/html/files/_dumps has been validated.\nWrite access to /var/www/html/files/_graphs has been validated.\nWrite access to /var/www/html/files/_lock has been validated.\nWrite access to /var/www/html/files/_pictures has been validated.\nWrite access to /var/www/html/files/_plugins has been validated.\nWrite access to /var/www/html/files/_rss has been validated.\nWrite access to /var/www/html/files/_sessions has been validated.\nWrite access to /var/www/html/files/_tmp has been validated.\nWrite access to /var/www/html/files/_uploads has been validated.\nFor security reasons, SELinux mode should be Enforcing.For security reasons, SELinux mode should be Enforcing.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nexif extension is installed.exif extension is installed.\nldap extension is installed.ldap extension is installed.\nopenssl extension is installed.openssl extension is installed.\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2, Phar, zip.\nZend OPcache extension is installed.Zend OPcache extension is installed.\nFollowing extensions a\n\n[Content truncated.]", "priority": "high", "type": "support", "createdByEmail": "logan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 15246, "url": "https://github.com/glpi-project/glpi/issues/15246", "author": "Dmtrkozl", "anonymizedAuthorEmail": "logan.adler@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "open", "stateReason": null, "createdAt": "2023-07-19T07:17:07Z", "updatedAt": "2025-12-04T11:31:16Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "\"Item type\" business rule criteria won't work", "detail": "Affected version:\n10.0.7\n\nIssue description:\nBasically, I'm trying to create a rule for auto adding a follow-up to the ticket when I assign a computer to a ticket. I'm trying to use \"Item type\" for the criteria, and the rule pass testing, but it never applies. Tried to use another criteria for adding the follow-up and it worked. It just won't work with the \"item type\" criteria.\n\nAfter some time, I noticed that the rule applies only when you select an item in the ticket screen but don't actually add it to the ticket (i.e. choose it on the list but don't click \"+ Add\" button, then save the ticket).\n\nThis is obviously useless, because although the rule is processed, the item is not added to the ticket.\n\nReproduction steps:\n1. Create a business rule for tickets\n2. Use \"Item type\" as criteria\n3. Set item type to \"Computer\"\n4. Add desired action\n5. Test it by adding a computer to a ticket. The rule won't apply.\n6. Try it again by selecting a computer in the item list, but don't actually add it to the ticket (just select it on the list and don't click \"+\")\n7. Rule applies but item is not linked to the ticket", "priority": "medium", "type": "support", "createdByEmail": "riley.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 14760, "url": "https://github.com/glpi-project/glpi/issues/14760", "author": "redddcyclone", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-05-23T13:02:16Z", "updatedAt": "2025-12-04T11:30:29Z", "closedAt": null } }, { "title": "Unable to open images via email with an anonymous user", "detail": "Issue description:\nHello\nI don't know if this situation is a BUG or a feature to be improved.\n\nI allow you to open calls via email (anonymously) for my customers. When a Service Analyst inserts a follow-up and includes an image in the text area, the email is sent with a thumbnail on the print screen\n\nImage is compressed and presented in a small size in the email. This makes the customer click on the image to view the image in its original size, to view the image in its original size\n\nHowever, as the user does not have access to the GLPI, displays the error message of file not found\n\nIn this case we have a nonsense. GLPI allows sending the image to the user, but does not allow him to view the image.\n\nPs: The functionality of sending files by attachment is disabled, since it cannot understand and send only the image or file inserted in the last follow-up, a fact that makes the use of the functionality even more difficult.\n\nGLPI 9.4.6", "priority": "medium", "type": "support", "createdByEmail": "lane.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 7872, "url": "https://github.com/glpi-project/glpi/issues/7872", "author": "phamorais", "anonymizedAuthorEmail": "lane.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2020-08-21T02:14:18Z", "updatedAt": "2025-12-04T11:26:32Z", "closedAt": null } }, { "title": "Event \"Not Solved Tickets\" not parsing tags", "detail": "Affected version:\n10.0.17\n\nIssue description:\nUsing version 10.0.15, the notification for tickets not solved in X days had been working fine on our weekly notification schedule for this item. After upgrading to 10.0.17, our alert for tickets not closed quick parsing the tags correctly.\n\nPrior to 10.0.17, our code block in the HTML notification template translation looked like this:\n\n\\\n\\\n\\##ticket.title##\n\\##ticket.authors##\n\\##ticket.priority##\n\\##ticket.status##\n\\##IFticket.assigntousers####ticket.assigntousers####ENDIFticket.assigntousers####IFticket.assigntogroups####ticket.assigntogroups## ##ENDIFticket.assigntogroups####IFticket.assigntosupplier####ticket.assigntosupplier## ##ENDIFticket.assigntosupplier##\n\\##ticket.creationdate##\n\\\n\\\n\nAfter updating to 10.0.17, the only way I can get the tags to parse in the above code block is to remove the ##IFticket.status=Pending## and related tags, making the above code block look like this:\n\n\\\n\\\n\\##ticket.title##\n\\##ticket.authors##\n\\##ticket.priority##\n\\##ticket.status##\n\\##IFticket.assigntousers####ticket.assigntousers####ENDIFticket.assigntousers####IFticket.assigntogroups####ticket.assigntogroups## ##ENDIFticket.assigntogroups####IFticket.assigntosupplier####ticket.assigntosupplier## ##ENDIFticket.assigntosupplier##\n\\##ticket.creationdate##\n\\\n\\\n\nI have tried various combinations of the above, and also tried switching to ##IFticket.storestatus=4## in place of the ##IFticket.status=Pening##, but nothing seems to work at this point. It seems related to the fact that I'm embedding it within a FOREACH block, and I have ran into \"embedding\" issues in some of our other templates that forced me to be creative on how I built out our templates.\n\nBasically, just need a way for the alertnotclosed notification to allow for excluding pending tickets, or for specifying the ticket status to include. This could be an alert configuraiton option on the automatic action, or it could be a \"code\" solution in my HTML.....which is what was working prior to 10.0.17.\n\nReproduction steps:\n1. Upgrade or install 10.0.17\n2. Make the HTML code for the notification fired by the automatic action \"alertnotclosed\" like the attached code.\n3. Run the alertnotclosed notification\n\nalertnotclosed-ticketnotification.txt", "priority": "medium", "type": "support", "createdByEmail": "robin.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18315, "url": "https://github.com/glpi-project/glpi/issues/18315", "author": "raregtp", "anonymizedAuthorEmail": "robin.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-11-14T15:58:27Z", "updatedAt": "2025-12-04T11:26:02Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Expired License notification - unable to select 'Group in charge of the Hardware' as notification recipient", "detail": "Affected version:\n10.0.2\n\nIssue description:\nUnable to select the 'Group in charge of the hardware' and 'Technician in charge of the hardware' as notification recipient for the license expiration.\nThis is currently possible to configure\n\nLicense example\n\nNotification\n\nRecipient selection, unable to select in this notification\n\nRecipient selection for certificate notification:", "priority": "medium", "type": "support", "createdByEmail": "cameron.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 13774, "url": "https://github.com/glpi-project/glpi/issues/13774", "author": "Geo-Ron", "anonymizedAuthorEmail": "cameron.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-01-11T13:18:24Z", "updatedAt": "2025-12-04T11:21:35Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Timeout with external proxies (cloudflare)", "detail": "Affected version:\n10.0.10\n\nIssue description:\nWhen performing a large export (csv, pdf, slk) I get timeouts from cloudflare (probably happens the same with similar products).\n\nThe problem is similar to apache/php timeouts (max_execution_time + memory_limit) but with an external proxy, so I can't configure or modify anything.\n\nIf I circumvent cloudflare and I access the server directly (internal IP) I get the export without any problem.\n\nAffected page:\n\nThis URL is using a tunnel to the web server.\n\nAdditional context:\nI can see some similar problems but always related to self hosted proxies, not external (unmanaged) ones.\n\nMy proposal is to implement a waiting page with http status code 102 so the client knows something is taking some time to process:\n\nWith this addition there'll be no need to increase max_execution_time. This is used in other projects that generate reports.", "priority": "medium", "type": "support", "createdByEmail": "emerson.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18689, "url": "https://github.com/glpi-project/glpi/issues/18689", "author": "muzzol", "anonymizedAuthorEmail": "emerson.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-01-09T12:09:44Z", "updatedAt": "2025-12-04T11:20:35Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Too many actions possible on templates?", "detail": "Issue description:\nIt seems there is a lot of possible actions on templates:\n\n[Image omitted]\n\nMore a quesiton than a bug, I do not know exactly what should be possible. In v10, there were already some possible actions; but there are much more on v11.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "needs_support", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20316, "url": "https://github.com/glpi-project/glpi/issues/20316", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "question" ], "state": "open", "stateReason": null, "createdAt": "2025-07-16T08:04:05Z", "updatedAt": "2025-12-04T07:33:55Z", "closedAt": null } }, { "title": "Contribution: Add items counter to Budget Items tab", "detail": "Contribution description:\nRequest to add a counter to the Items tab of Budget in GLPI.\n\nContribution description:\nImplement a counter that displays the total number of items listed within the Items tab when viewing a specific Budget. This enhancement aims to improve usability for users managing Budget items by making it easy to quickly assess volume at a glance.\n\nKey points:\n- Place the counter near the Items tab label or the tab content header.\n- The counter should update dynamically as items are added or removed.\n- Ensure visibility for users across permission levels.\n- Ideally, structure the solution for possible reuse in similar tabular UI contexts throughout GLPI.", "priority": "low", "type": "feature", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22873, "url": "https://github.com/glpi-project/glpi/issues/22873", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "eduardomozart", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "feature suggestion" ], "state": "open", "stateReason": "reopened", "createdAt": "2026-01-28T14:28:45Z", "updatedAt": "2026-05-31T00:28:40Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Multiple issues with planning", "detail": "Affected version:\n10.0.6\n\nIssue description:\n1\\) Datepickers modal do not follow the content when scrolling\n\nIt seems that flatpicker has an positionElement option to fix this but I haven't been able to use it correctly.\nAs we saw this together earlier Taylor Adler, what this parameter the solution you had in mind ?\n\n2\\) Dropdowns open in the wrong positions after scrolling\n\n3\\) If I scroll down then click on the \"Percent done\" dropdown, the modal closes itself 90% of the time.\n\n4\\) Some js error when closing and reopening the event's edit form.\nProbably need to isolate the variables with some self invoking functions around the scripts of project_task.html.twig.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 13943, "url": "https://github.com/glpi-project/glpi/issues/13943", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2023-01-31T16:16:07Z", "updatedAt": "2026-01-09T09:17:16Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "LDAP - time zones selection not applied", "detail": "Affected version:\n10.0.5\n\nIssue description:\nAfter activating the time zone in database all of the application take it into account (users, general configuration, etc) except of the LDAP configuration.\n\nIn the following elements, the selector still indicates GMT offsets in place of timezone selection :\n\n- Setup > Authentication > Setup\n- Setup > Authentication > LDAP directories > \"an element\" > Advanced information\n\nFor information : I also raised a ticket on documentation to further the impacts of these configurations and how they interact with everything else as time handling can be hard to understand.\n\nReproduction steps:\n1. create a new instance of GLPI\n2. Activate timezones like asked in documentation\n3. Create a new LDAP configuration\n\nAdditional context:\nI use a single instance of GLPI with multiple LDAP directories located around the world. Users have their own timezone, Active directories servers have their own time zone (north america, north africa, multiple countries in europe).", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 13682, "url": "https://github.com/glpi-project/glpi/issues/13682", "author": "keguira", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2022-12-29T13:37:27Z", "updatedAt": "2025-12-04T11:31:39Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "no api token logging", "detail": "Affected version:\n10.0.9\n\nIssue description:\nI have logging set to 'complete' and there is no logging for APP Token access, including failed nor is there any logging including failed attempts using a user token. this includes a shear lack of API access logging for any invalid parameter.\n\nWithin the event log you can't see a failed login, however no username nor mention of app token, including if the user details are corrent and the token invalid. in this failed login, HTTP/400 is returned as is a JSON response telling the user what is wrong, invalid app-token. any access to an app token must be logged so it can be audited and the user attempting to access the api with an invalid app token should not be notified that the APP token is incorrect as now a valid user token is known. However unlikely, this presents an opportunity however so small (62^40, assuming tokens only use a-zA-Z0-9) that an app token can be brute forced. this goes par in par with the other tokens, adjusting for their char set, which for auth username and password being shorter.\n\nin all cases within the apache access log there is either HTTP/401 and HTTP/400 logged along with the request with the latter however not specifically isolated to login attempts.\n\nDiagnostic information:\nValid User Token invalid auth token: none\n\nInvalid user token, valid app token:\n\nValid auth token, invalid app token: none\n\nInvalid session token, valid app token:\n\ninvalid app token, invalid session token: none\n\nAffected page:\napirest.php\n\nReproduction steps:\nno steps required, this is on a fresh install of glpi, with the exception of a few plugins.\n\nAdditional context:\n#1253 - Limit API failed login attempts, is noted and may be related, however nothing in that issue seems to have been implemented\n\nEdit: fix code blocks", "priority": "high", "type": "incident", "createdByEmail": "rowan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 15268, "url": "https://github.com/glpi-project/glpi/issues/15268", "author": "jon-nfc", "anonymizedAuthorEmail": "rowan.adler@peppermint.local", "assignees": [], "labels": [ "security" ], "state": "open", "stateReason": null, "createdAt": "2023-07-22T03:59:16Z", "updatedAt": "2025-12-04T11:31:06Z", "closedAt": null } }, { "title": "Right to update priority & reload ticket", "detail": "Affected version:\n[GLPI 10 Bugfixes]\n\nIssue description:\n1. Use a profile without the right to change the ticket priority\n2. Launch ticket creation\n3. Select Urgency & Impact -> the priority is defined\n\n4. Change category of the ticket\n5. the priority has been reset :", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 13603, "url": "https://github.com/glpi-project/glpi/issues/13603", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2022-12-14T09:39:14Z", "updatedAt": "2025-12-04T11:29:23Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "GLPI_10.0.15 : No history if I give a consumable to a user.", "detail": "Affected version:\n10.0.15\n\nIssue description:\nHello,\n\nIf I give one consumable , i dont have history\n\nI see the addition or delete of stock but when I give it there is no trace\n\nits ok in the section\n\nAffected page:\n/glpi/front/consumableitem.form.php?id=\n\nReproduction steps:\n1. go to /glpi/front/consumableitem.php\n2. Click name consumable\n3. Give one consumable\n4. look history", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 17251, "url": "https://github.com/glpi-project/glpi/issues/17251", "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-06-05T06:47:48Z", "updatedAt": "2025-12-04T11:17:53Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Solutions types dropdown not loaded on sub-entities", "detail": "Affected version:\n10.0.17\n\nIssue description:\nHere is a change at the root, and reccursive.\nHere are reccursive types of solution.\n\nWhen logged at the root with arborescence : adding a type of solution on the change is ok\nWhen logged at an other entity : no type of solution are shown to close the change : ko\n\nReproduction steps:\n1. Create a reccursive change\n2. Having reccursive 'type of solution'\n3. logged on the root itself : the type of solutions are listed : OK\n4. logged on a different entity (on which the change is visible , as it is reccursive) : the type of solutions are empty : KO", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18847, "url": "https://github.com/glpi-project/glpi/issues/18847", "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-01-30T07:16:02Z", "updatedAt": "2025-12-04T11:13:08Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Notifications only send the first Email Template but it has multiples assigned", "detail": "Affected version:\n10.0.9\n\nIssue description:\nI have setup Notification For \"New Ticket\", and assigned 2 templates both of them in \"Email\" Mode, but when it triggers and sends the email, just the first template is used, and not the second one too.\n\nReproduction steps:\n1. Setup the Notification and assig 2 templates with \"Email\" mode:\n\n2. Trigger the Notification, in my case is \"New Ticket\" so I created a new ticket:\n\n3. In \"Notification queue\" only shows the first Notification Template, in this case is \"Tickets\" or the Template ID = 394\n\n4. If I deleted the relation of the first Template with the Notification:\n\n5. And repeat the process, it trigger correctly, so the problem is that 2 notification template with the same Email mode, cannot be associated with a Notification:", "priority": "medium", "type": "support", "createdByEmail": "micah.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 15608, "url": "https://github.com/glpi-project/glpi/issues/15608", "author": "jairockman", "anonymizedAuthorEmail": "micah.adler@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-09-19T15:12:29Z", "updatedAt": "2025-12-04T11:12:21Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "Add 'Matches' Search Option for Better Usability", "detail": "Contribution description:\nThis contribution request is to introduce a new matches search operator to improve ticket filtering by allowing direct text input.\nUnlike the existing \"is\" operator, which depends on dropdowns, matches enables users to type known values directly—bypassing dropdown loading delays.\nThis makes searches faster, especially when dealing with large datasets or slow-loading UI components, and improves overall usability.\n\nThe Difference between is and match:\nSearch with is option\n[Image omitted]\n\nSearch with match option\n[Image omitted]\n\nThe match option allows searching without using the list\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20713, "url": "https://github.com/glpi-project/glpi/issues/20713", "author": "HyunahJang", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-08-20T07:34:04Z", "updatedAt": "2025-12-04T11:09:32Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "ITIL templates not handled properly once created", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nCommonITILObject::checkRequiredFieldsFilled is being used to see if all fields that are required by the template are filled. This calls CommonITILObject::handleTemplateFields which ignores the template already set in the object's template field (tickettemplates_id). So, it will only every check the fields that are required by the computed template based on entity/profile/category which isn't relevant once created.\n\nProbably a consequence of using templates to restrict the statuses that can be used now.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20678, "url": "https://github.com/glpi-project/glpi/issues/20678", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-08-14T15:10:11Z", "updatedAt": "2025-12-04T09:43:48Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Add comment field to type object in webhook payload", "detail": "Contribution description:\nCurrently, the type object in webhook payloads only returns the following:\n\n\"type\": {\n \"id\": \"{{ item.type.id }}\",\n \"name\": \"{{ item.type.name }}\"\n}\n\nIt would be helpful to also retrieve the comment field, which is available in the GLPI database for types.\n\nThis would avoid having to make an additional request to retrieve the comment since there are only two fields: \"name\" and \"comment\".\n\nI await your opinion on this need. It may not be in line with your vision.\n\nThanks", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20917, "url": "https://github.com/glpi-project/glpi/issues/20917", "author": "Yann843", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2025-09-05T10:30:48Z", "updatedAt": "2025-12-04T09:41:38Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Non-matching number of items and entries of items for components", "detail": "Affected version:\n10.0.6 and nightly build\n\nIssue description:\nWhen a component is assigned to the root entity, \"child entities\" is active and an item from a sub entity is assigned to this component the number of items and the list vom items does not match for a user from another subentities.\n\nReproduction steps:\n1. create two subentities where each is a child of the root entity\n2. Import an inventory for a computer to the first subentity\n3. Merge and assign all components to the root entity (massive action for the component) so each component is assigned to the root entity and has \"child entites\" active\n4. create a user with profile Admin and assign the user to the second subentity\n5. go to Setup > Components > Processors\n6. Choose the processor\n7. go to items", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 14396, "url": "https://github.com/glpi-project/glpi/issues/14396", "author": "AndiMb", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-03-27T07:15:16Z", "updatedAt": "2025-12-04T07:31:48Z", "closedAt": null } }, { "title": "Installations sublist for Software uses legacy UI", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nThe list of installations on the Installations tab of a Software/Software Version still shows the list using the legacy UI instead of a datatable.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20529, "url": "https://github.com/glpi-project/glpi/issues/20529", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "open", "stateReason": null, "createdAt": "2025-08-04T22:06:47Z", "updatedAt": "2025-12-04T07:19:43Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Improve illustration manager tests", "detail": "Issue description:\nIllustrations tests on GLPI side were depending on changes made on the lib. Therefore, tests were often failing on lib update; this should be avoid.\nThis affects both PHP and e2e tests (while the second one is less affected because of a different logic as far as we saw).\n\nSee #20064", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20067, "url": "https://github.com/glpi-project/glpi/issues/20067", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-06-19T08:06:34Z", "updatedAt": "2025-12-04T07:08:48Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Setup: too much weight on labels", "detail": "Issue description:\n11.0:\n\n10.0:\n\nNote, that we use the default style as used in Assets (and it's fine here, but we may test also with bold).\nFor setup, I think we should have normal weight for labels", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18168, "url": "https://github.com/glpi-project/glpi/issues/18168", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "open", "stateReason": null, "createdAt": "2024-10-31T08:53:31Z", "updatedAt": "2025-12-04T06:53:39Z", "closedAt": null } }, { "title": "LDAP user import fails when sAMAccountName starts with \"!\"", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nGLPI version: 11.0.7\n\nEnvironment:\n- Official Docker image\n- Active Directory authentication\n- LDAP synchronization configured and working\n\nProblem:\nUsers whose sAMAccountName starts with \"!\" cannot be imported from the LDAP import interface.\n\nExample:\n\nsAMAccountName = !username\n\nThe user:\n- exists in Active Directory\n- is enabled\n- is member of LDAP synchronization groups\n- is returned by LDAP queries\n\nWhen importing the user from:\nAdministration > Users > LDAP directory > Import new users\n\nGLPI returns HTTP 500.\n\nLogs show a SessionException after the import attempt.\n\nAs a test, changing the same account from:\n\n!username\n\nto\n\nadm-username\n\nallows immediate import without any other changes.\n\nLDAP synchronization from CLI works:\n\nphp bin/console ldap:synchronize_users\n\nThis suggests that the \"!\" character is not correctly handled or escaped during LDAP user import through the web interface.", "priority": "medium", "type": "support", "createdByEmail": "jordan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24924, "url": "https://github.com/glpi-project/glpi/issues/24924", "author": "hakd0c", "anonymizedAuthorEmail": "jordan.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-22T10:48:01Z", "updatedAt": "2026-07-22T10:48:44Z", "closedAt": null } }, { "title": "Mail Collector setup : login field not displayed", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.26\n\nIssue description:\nWhen creating a mail collector (with Oauth Imap connexion), the login field is not visible ( only the caption is visible)\n\n[Image omitted]\n\nAffected page:\nglpi/front/mailcollector.form.php\n\nReproduction steps:\n1. create a an application with plugin OAUTH IMAP and give autorizations\n2. create a collector and select connexion IMAP=> OK\n3. Change connexion to the one created with the auth IMAP\n4. the field login is not more visible ( but the caption is still there)\n\nin the file /src/MailCollector.php line 308\n\nchange\n echo Html::input('login', ['value' => $this->fields['login']]);\n\ninto\n\n echo Html::input('Login', ['value' => $this->fields['login']]);\n\nthe login field is back.\n\nEnvironment details:\nGLPI 10.0.26 ( => /var/www/glpi)\nInstallation mode: TARBALL\nCurrent language:fr_FR\n\nPlugin Oauth IMAP 1.4.5", "priority": "medium", "type": "support", "createdByEmail": "jamie.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24917, "url": "https://github.com/glpi-project/glpi/issues/24917", "author": "ladenree76000", "anonymizedAuthorEmail": "jamie.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-21T14:51:34Z", "updatedAt": "2026-07-21T14:51:55Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Firefox does not display all columns or a scrollbar", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nHi,\n\nIn GLPI, when I search for computers, I cannot see all the columns, and there is no horizontal scrollbar to scroll to the right.\n\nFor example, in Chrome, the layout is automatically adjusted so that all columns are visible.\n\nWould it be possible to make Firefox behave the same way?\n\nAffected page:\n/front/computer.php\n\nReproduction steps:\n1. With Firefox\n2. On GLPI Search all computers and add for example 12 columns\n2. We can't see all columns", "priority": "medium", "type": "support", "createdByEmail": "reese.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24906, "url": "https://github.com/glpi-project/glpi/issues/24906", "author": "flagoda", "anonymizedAuthorEmail": "reese.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-21T11:54:19Z", "updatedAt": "2026-07-21T11:54:19Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "cannot persist group field for computer assets using GLPI 11 new REST api", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI cannot persist group field for computer assets using GLPI 11 new REST api\n\nAPI api.php/v2.3 command is PATCH on an existing asset via\n\nbody is\n\"{'name': 'DXCDC22AWS001', 'comment': 'Instance type:t3a.medium Client:ITO OS:Win2022 Zone:Production Creator:Stephan.Krause\nCPU/MEM: 2/4 Scheduler: AlwaysOn', 'group': [{'id': 114, 'name': 'dxc_aws'}], 'group_tech': [{'id': 114, 'name': 'dxc_aws'}], 'location': {'id': 37}, 'serial': 'i-0177553aac05d986f', 'type': {'id': 458}, 'manufacturer': {'id': 5785}, 'status': {'id': 3}, 'autoupdatesystem': {'id': 449}, 'is_template': False, 'id': 7737}\"\n\nreturn response is\n'b\\'{\"id\":7737,\"name\":\"DXCDC22AWS001\",\"comment\":\"Instance type:t3a.medium Client:ITO OS:Win2022 Zone:Production Creator:xxxxx\nCPU\\\\\\\\/MEM: 2\\\\\\\\/4 Scheduler: AlwaysOn\",\"is_recursive\":false,\"contact\":null,\"contact_num\":null,\"serial\":\"i-0177553aac05d986f\",\"otherserial\":\"\",\"is_deleted\":false,\"date_creation\":\"2024-03-04T08:47:00+01:00\",\"date_mod\":\"2026-07-17T13:49:56+02:00\",\"uuid\":\"\",\"is_template\":false,\"template_name\":null,\"is_dynamic\":true,\"ticket_tco\":0,\"last_inventory_update\":\"2024-03-18T10:28:02+01:00\",\"last_boot\":\"2024-02-21T03:21:36+01:00\",\"status\":{\"id\":3,\"name\":\"ACTIVE\"},\"entity\":{\"id\":0,\"name\":\"Root entity\",\"completename\":\"Root entity\"},\"manufacturer\":{\"id\":5785,\"name\":\"AWS\"},\"user\":null,\"user_tech\":null,\"location\":{\"id\":37,\"name\":\"AWS Region Frankfurt\"},\"type\":{\"id\":458,\"name\":\"EC2\"},\"model\":{\"id\":454,\"name\":\"t3a.medium\"},\"group\":[],\"group_tech\":[],\"network\":null,\"autoupdatesystem\":{\"id\":449,\"name\":\"Replication\"}}\\''\n\nstatus code is 200\n\nI am using the PATCH API as documented in\n\nbtw:\ninsert POST command with same body is also not inserting the groups.\nand: updating the location IS WORKING !", "priority": "medium", "type": "support", "createdByEmail": "micah.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24899, "url": "https://github.com/glpi-project/glpi/issues/24899", "author": "LordVader4711", "anonymizedAuthorEmail": "micah.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-21T07:26:33Z", "updatedAt": "2026-07-21T11:49:58Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "hasSessionMessageThatContains do not fail the test if the message is missing.", "detail": "Issue description:\n(At least on main, didn't test elsewhere).\n\nIt mean you can call $this->hasSessionMessageThatContains($with_message, ERROR); with any message and your test will never fail.\n\nI am almost sure that this wasn't the case before and that the base test case is supposed to fail if a message remains in the session.\n\nIt never happens because a missing message will set $this->has_failed to true and the teardown skip the check in this case:\n\n[Image omitted]\n\nI think hasSessionMessageThatContains should probably trigger a failure immediately rather than set has_failed.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24903, "url": "https://github.com/glpi-project/glpi/issues/24903", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-21T09:37:29Z", "updatedAt": "2026-07-21T09:37:29Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Old technician still receives \"a ticket has just been assigned to you\" email when reassigning a ticket to another technician in a single save", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nWhen a ticket is reassigned from one technician to another in a single save — removing the currently assigned technician and adding a new one before saving — GLPI sends the \"a ticket has just been assigned to you\" email (event: *New user responsible* / assign_ticket) to both the old technician and the new one, instead of only the new technician.\n\nThe old technician has just been removed from the \"Assigned to\" field and should not receive an assignment notification.\n\nExpected behavior:\nOnly the new assignee (Technician B) receives the \"a ticket has just been assigned to you\" email.\n\nObserved behavior:\nBoth the old (removed) technician and the new technician receive the assignment email, using the same \"Ticket -> Technician\" template on the \"New user responsible\" event.\n\nEvidence (notification queue):\nTwo assignment emails are generated for the same ticket, same template, on the single reassignment save:\n\n| Subject | Recipient | Template | Event |\n|---|---|---|---|\n| A ticket has just been assigned to you | Technician B (new) — OK | Ticket -> Technician | New user responsible |\n| A ticket has just been assigned to you | Technician A (old, removed) — WRONG | Ticket -> Technician | New user responsible |\n\nThe notification itself is correctly configured with a single recipient (\"Technician in charge of the ticket\") and no exclusion (see screenshots). The problem is in how the \"assign\" recipients are resolved during the update transaction: the just-removed actor is still present in the in-memory ticket actors when the assignment notification targets are computed, so the old technician is notified too.\n\n[Image omitted]\n\nAffected page:\n/front/ticket.form.php?id= (reassignment) — evidence in /front/queuednotification.php\n\nReproduction steps:\n1. Create a ticket and assign it to Technician A (Assigned to = Technician A). Save.\n2. Open the ticket. In the \"Assigned to\" field, remove Technician A and add Technician B.\n3. Save the ticket (single save — removal and addition in the same update).\n4. Go to Administration > Notifications queue (or check the technicians' mailboxes).\n5. Observe that the \"a ticket has just been assigned to you\" email (Ticket -> Technician template, \"New user responsible\" event) is queued for BOTH Technician A (old, removed) and Technician B (new), instead of only Technician B.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "harper.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24901, "url": "https://github.com/glpi-project/glpi/issues/24901", "author": "Neu-Maximilian", "anonymizedAuthorEmail": "harper.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-21T09:01:36Z", "updatedAt": "2026-07-21T09:01:36Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Hidden fields in self-service ticket template remain hidden for technicians after ticket creation", "detail": "Issue description:\nDescribe the bug\n\nWhen a self-service user creates a ticket using a ticket template where fields such as Impact and Urgency are hidden, those fields are also hidden when the ticket is later viewed by a technician or administrator.\n\nTo reproduce\n\n1. Create a ticket template for self-service users.\n2. Hide fields such as Impact and Urgency.\n3. Assign the template to a self-service profile.\n4. Create a ticket as a self-service user.\n5. Open the ticket as a technician or administrator.\n\nCurrent behavior\n\nThe hidden fields are not visible to technicians or administrators on the created ticket.\n\nExpected behavior\n\nThe template should only affect the ticket creation form for self-service users. After the ticket is created, technicians and administrators should see all fields according to their permissions so they can complete information such as Impact and Urgency.", "priority": "medium", "type": "support", "createdByEmail": "morgan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24888, "url": "https://github.com/glpi-project/glpi/issues/24888", "author": "loulouontop", "anonymizedAuthorEmail": "morgan.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-19T22:26:42Z", "updatedAt": "2026-07-19T22:26:42Z", "closedAt": null } }, { "title": "GLPI 11 - genericobject_plugin_to_core migration fails with \"Unable to find the target itemtype for PluginGenericobjectType\"", "detail": "Affected version:\n11.0.6\n\nIssue description:\nRunning the GenericObject plugin migration command fails partway through with a generic\n\"Une erreur est survenue\" (An error occurred) message. Running with -vvv and checking\nfiles/_log/php-errors.log reveals the underlying exception:\n\nThe migration is transactional and rolls back completely on failure, so no partial data\nis left in the database — but this also makes the failure hard to diagnose after the fact,\nsince the offending record no longer exists once the command exits.\n\nBefore this specific error, the command also required two earlier workarounds to get this far:\n1. Had to add --allow-superuser (running the console as root).\n2. Had to disable \"Enable the financial and administrative information by default\" in\n Setup > General > Assets, otherwise the migration failed earlier with\n Unable to copy Informations financières et administratives \"N/A\".\n\nReproduction steps:\n1. Instance heavily using the GenericObject plugin: 31 custom object types (families\n configured for several of them), custom fields.\n2. Migrated database from GLPI 10 to GLPI 11.\n3. Installed GenericObject plugin v3.0.0 (EOL/migration version).\n4. Disabled \"Enable the financial and administrative information by default\" (Setup >\n General > Assets) to work around a prior blocking error.\n5. Ran: sudo -u www-data php bin/console migration:genericobject_plugin_to_core --allow-superuser -vvv\n6. Migration progresses through dropdown definitions import, creates ~31 custom assets and\n several custom fields (last successfully logged: a ticket_tco-named custom field), then\n fails with the error above and rolls back all changes.\n\nAdditional context:\n- The instance has 31 GenericObject types configured, several of them grouped into\n \"families\" (which are already known to be unsupported/dropped during migration —\n this is reported as an info notice, not an error, and is expected).\n- Checked glpi_plugin_fields_containers / glpi_plugin_fields_fields (old Fields\n plugin tables) — none reference PluginGenericobjectType or any GenericObject\n itemtype directly; all container itemtypes already point to the new\n Glpi\\CustomAsset\\Asset classes (the Fields plugin's own migration to core\n had already run successfully beforehand). Ran\n SELECT ... WHERE itemtypes LIKE '%PluginGenericobject%' — zero rows, confirming\n no leftover old-format reference exists in this table.\n\nIsolation testing performed (to narrow down the cause):\n- Temporarily removed 28 of the 31 rows from glpi_plugin_genericobject_types,\n keeping only 3 unrelated, simple types (no custom fields beyond the plugin\n defaults): gp, videoprojecteur, duplicopieur.\n- Re-ran the migration with only these 3 types present. The exact same failure\n occurs, at the exact same point (immediately after a ticket_tco custom field\n is logged as created), even though only 3 (out of 31) types are now being\n processed.\n- Also tested detaching these 3 types from their shared \"family\" (id 8) by setting\n plugin_genericobject_typefamilies_id = 0 — same failure persisted, ruling out\n families as the cause too.\n- This strongly suggests the failure is not specific to any particular\n GenericObject type, family, or Fields-plugin container in this dataset, but is\n triggered by something processed unconditionally/globally during\n getCustomFieldSpecs() — possibly a core custom field (ticket_tco itself, which\n is a reserved/native Ticket TCO field per src/Ticket.php) being picked up by the\n migration's field-scanning logic and mishandled when it tries to resolve a target\n itemtype for whatever field is processed right after it.\n- Because the migration is wrapped in a transaction, I cannot inspect the specific\n field/record that triggers getTargetItemtype() failure after the fact — happy to\n add temporary debug logging or run a patched build if that would help pinpoint it.\n\nEnvironment:\n- GLPI version: 11.0.6\n- PHP version: 8.2.30 (cli) (NTS), Zend Engine v4.2.30\n- Database: MariaDB 10.6.23 (Ubuntu 22.04 build)\n- GenericObject plugin version: 3.0.0\n- Number of GenericObject types: 31 (several grouped in families)\n- Migrated from: GLPI 10.0.x", "priority": "medium", "type": "support", "createdByEmail": "devon.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24887, "url": "https://github.com/glpi-project/glpi/issues/24887", "author": "absita07", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-19T17:17:21Z", "updatedAt": "2026-07-19T17:17:21Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Error in Observer email response", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nWhen an Observer replies to an email, the message is not added to the ticket.\nI identified that the MailCollector processes the message and places it in the Refused folder.\nThe following can be seen in the PHP log:\n\n[2026-07-15 17:52:10] glpi.ERROR: * Caught TypeError: Safe\\base64_decode(): Argument #1 ($string) must be of type string, null given, called in ./src/MailCollector.php on line 2445\n Backtrace :\n .../thecodingmachine/safe/generated/8.4/url.php:20\n ./src/MailCollector.php:2445 Safe\\base64_decode()\n ./src/MailCollector.php:1749 MailCollector->getDecodedContent()\n ./src/MailCollector.php:1064 MailCollector->getBody()\n ./src/MailCollector.php:732 MailCollector->buildTicket()\n ./src/MailCollector.php:1886 MailCollector->collect()\n ./src/CronTask.php:887 MailCollector::cronMailgate()\n ./front/cron.php:136 CronTask::launch()\n\n[RES_ \\[GLPI #0000701\\] \\[Suporte # 0000701\\] Solicitação de acesso..eml](", "priority": "medium", "type": "support", "createdByEmail": "remy.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24859, "url": "https://github.com/glpi-project/glpi/issues/24859", "author": "supermozzi", "anonymizedAuthorEmail": "remy.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-15T18:27:11Z", "updatedAt": "2026-07-15T18:27:11Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "KB Rework issues/review", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nmain\n\nIssue description:\nI don't want to complain too much if the KB editor work is still early, but my list keeps growing and we are getting close to the end of the development cycle of this version (hopefully) and a lot of people have a lot of time off coming up.\n\nTiptap/Editor Usage Related:\n- Slash menu not discoverable when editing an existing article unless you go to a new line.\n- No keyboard control of the bubble menu. Some actions may have intuitive shortcut like ctrl+b for bold, but I don't know what the other shortcuts are or if shortcuts even exist for the other actions.\n- No way clear to configure tables. Always inserts a 3x3 table. Tabbing past the last body cell adds another row, but this is not discoverable and I haven't found any way to add new columns.\n- Impossible to click to focus the body cells in tables.\n- Ability to resize table columns not discoverable because the cursor doesn't change when hovering over the column border.\n- No way to delete table rows/columns? No way to quickly delete the entire table except selecting the entire thing?\n\nMisc Bugs/UX:\n- Add to favorites actions shows for Self-Service profile users but the request causes a 403 response.\n- Add to favorites action does not update the toggle control state even when the action is successful and the sidebar is updated.\n- Viewing an article as Self-Service does not show article list. FAQ link -> Old UI showing Search/Browse tabs -> Click article -> new UI showing only the article content. User is forced to go all the way back to the FAQ link/old UI instead of just seeing the list of articles they have access to see like the standard interface users.\n- Links open a basic browser text input prompt dialog. No option to configure links to open in new tabs, title or text. Not a big deal but it looks weird/unfinished.\n- Trying to scroll the list of articles in the sidebar scrolls the entire page because there is no max height on it and it looks broken. The article list and article should be independent scroll containers and not overflow the viewport.\n- Old Search and Browse tabs views seem out of place now, but I assume they are planned to be removed? The new UI doesn't cover all functionality of the old tabs yet like filtering and viewing recent/last updated/popular article lists.\n- Adding comment to an article scrolls the entire page down. Scroll seems based on the comment text, not the comment container itself and forces it to the top of the viewport instead of just ensuring it is scrolled into view.\n[Image omitted]\n- Daring to leave the KB page idle for 24 minutes (PHP session lifetime) spams \"An unexpected error occurred\" toasts when hovering over articles in the list and causes CPU spikes if constantly moving over the articles as these requests get repeated and are not throttled. This is mostly a PHP/GLPI annoyance but the KB itself can do better by not showing a toast for such a passive action and throttling the requests (also see related item under performance/optimization issues).\n\nMisc A11Y:\n- \"X translations\" text in self-service view is a link and focusable but not clickable and focus + enter changes the URL without doing anything else.\n\nTheme/Style Related:\n- Article actions dropdown in article list looks wrong (pseudo elements on the list items don't line up and look out of place even if they did).\n[Image omitted]\n- Too much space at top of the tab contents in sharing modal\n- Create/Checkmark button when creating a new sharing link looks wrong with the primary background\n[Image omitted]\n- Current/selected slash menu item colors not dark theme friendly\n- Table header colors not dark theme friendly.\n- Article list not dark mode friendly\n- Related items chips/badges not dark mode friendly\n- Documents/Related items tab names text color not dark mode friendly\n[Image omitted]\n\nPerformance/optimization related:\n- Sending the entire list of articles and categories to the client immediately as HTML is not efficient or needed. Loading my KB sends 0.5 MB of HTML for 3 categories and 251 articles. IMO only the top-level categories need to be in the DOM, and any then any categories and articles along the path to the current article. The other data could be lazy loaded when the user expands a category. If the delay is too much you could load the top level + the second level data initially, and then each time a category is expanded, you load one step ahead in the background without blocking the UI. Honestly even that isn't sufficiently efficient on its own when the articles are mostly uncategorized or in a few top-level categories. Would reduce a lot of data transferred if you only sent the raw data needed, not HTML.\n- Spams AJAX requests when hovering over articles in the sidebar which return 2.7kb of HTML each. Only seems to be for the actions dropdowns but triggers even when hovering over the article name. No reason this couldn't be client-side based on already known data about the user and articles sent as part of the tree. Or,\n\n[Content truncated.]", "priority": "high", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24852, "url": "https://github.com/glpi-project/glpi/issues/24852", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "beta / rc", "performance", "ui", "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-07-15T11:43:05Z", "updatedAt": "2026-07-15T12:47:05Z", "closedAt": null } }, { "title": "API schema validation fails on main branch", "detail": "Issue description:\nTests are failing on the main branch on the CI env, but are passing on my local machine.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24853, "url": "https://github.com/glpi-project/glpi/issues/24853", "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-15T11:47:13Z", "updatedAt": "2026-07-15T11:47:13Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "ValueError: imagecreatetruecolor() must be greater than 0 in Toolbox::resizePicture() with extreme aspect-ratio images (mail collector signatures)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nAffected version:\n11.0.x\n\nIssue description:\nToolbox::resizePicture() throws a fatal ValueError when it processes an\nimage with an extreme aspect ratio (very wide and short, or very tall and\nnarrow). Such images are commonly injected through the mail collector: sender\nsignature banners, spacer/tracking images (e.g. a GIF of 1600x5 px).\n\nFor an image where width / height (or the inverse) is large enough, the\nceil() computation of the target dimension still yields a valid value, but\nwhen $max_size is small or a source dimension is degenerate, one of\n$new_width / $new_height is rounded to 0. The subsequent call to\nimagecreatetruecolor($new_width, $new_height) then throws.\n\nBecause this happens inside the notification pipeline\n(NotificationEventMailing::attachDocuments() -> Document::getImage() ->\nToolbox::resizePicture()), a single such image blocks the whole\nqueuednotification cron / mail sending for the affected ticket. This is a\nlong-standing issue previously reported on 9.5.x (#8795, #9431, #10109) that\nstill reproduces on 11.x, as the affected code path never received a\ndimension clamp.\n\nReproduction steps:\n1. Create a ticket via the mail collector from an email whose HTML body / signature\n contains an image with an extreme aspect ratio (e.g. a 1600x5 GIF tracking pixel).\n2. Trigger a notification for that ticket (new ticket / followup).\n3. The queuednotification cron fails; the mail is not sent.\n\nExpected behavior:\nImages with extreme aspect ratios should be resized without crashing. The\nresulting thumbnail dimensions should never be less than 1 px.", "priority": "medium", "type": "support", "createdByEmail": "quinn.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24849, "url": "https://github.com/glpi-project/glpi/issues/24849", "author": "jeromeroseaueslc", "anonymizedAuthorEmail": "quinn.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-15T10:30:49Z", "updatedAt": "2026-07-15T10:30:49Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Remove sudo mode bypass", "detail": "Issue description:\nWhen introducing reauthentication process, we decided to provide a temporary bypass feature to disable reauthentication to provide a quick way to disable reauth.\n\nIt's temporary, it should be removed in a glpi 12.x release.\n\nOriginal pr :", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24844, "url": "https://github.com/glpi-project/glpi/issues/24844", "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-15T08:45:00Z", "updatedAt": "2026-07-15T08:46:47Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Allow configuring default sort strategy for Service Catalog (currently hardcoded to \"popularity\")", "detail": "Contribution description:\nContext\nIn GLPI 11.x, the Service Catalog displays items (forms, categories, knowledge base articles)\nsorted by a \"sort strategy\" (SortStrategyEnum: ALPHABETICAL, REVERSE_ALPHABETICAL, POPULARITY).\n\nUsers can manually change the sort order via the dropdown in the UI, but this choice is not persisted\nand resets to the default strategy on every new page load / session.\n\nCurrent behavior\nThe default strategy is currently hardcoded to POPULARITY in three places:\n- src/Glpi/Form/ServiceCatalog/SortStrategy/SortStrategyEnum.php (getDefault() method)\n- src/Glpi/Form/ServiceCatalog/ItemRequest.php (constructor default parameter)\n- public/js/modules/Forms/ServiceCatalogController.js (constructor default parameter)\n\nThere is no administration setting (global config or per-entity) allowing administrators\nto change this default value without patching the core code.\n\nProposed improvement\nAdd a configuration option (e.g. in Setup > General > Assistance or a dedicated\n\"Service Catalog\" settings section) allowing administrators to choose the default\nsort strategy applied to all users, among the existing SortStrategyEnum values\n(alphabetical, reverse_alphabetical, popularity).\n\nThis would avoid administrators having to patch core files (which get overwritten\non every upgrade) just to change a display preference that has no functional impact\non data integrity.\n\nSuggested implementation approach\n- Add a new entry in glpi_configs table (e.g. servicecatalog_default_sort_strategy)\n- Expose it in the general configuration UI\n- Update ItemRequest and ServiceCatalogManager to read this config value instead\n of the hardcoded SortStrategyEnum::POPULARITY\n- Pass the configured value to the JS controller via the Twig template instead of\n the hardcoded 'popularity' default\n\nEnvironment\n- GLPI version: 11.x\n- Impacted files: see above", "priority": "medium", "type": "support", "createdByEmail": "morgan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24843, "url": "https://github.com/glpi-project/glpi/issues/24843", "author": "jcouallier", "anonymizedAuthorEmail": "morgan.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-15T08:42:36Z", "updatedAt": "2026-07-15T08:42:36Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Bug in Reports page: empty dropdown option does not include root_doc", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nHey guys,\n\nI've just updated to 11.0.8 because of a bug you fixed on the Reports page : Commit #1 & Commit #2\n\nI've found another one that's basically the same thing:\n\nThis link ignores the \"root_doc\" variable. It should be an easy fix!\n\nI fixed it like this: 'values' => [$CFG_GLPI['root_doc'] . '/front/report.php' => Dropdown::EMPTY_VALUE] on my GLPI instance, but I guess you could create a variable if you want it to be clean\n\nThank you in advance,\nYou're always working so hard to improve the project and I find it really inspiring!\n\nBARET Yohan\n\nAffected page:\n/front/report.php because my GLPI instance runs at /glpi/\n\nReproduction steps:\nYou need to have a different base url, my GLPI instance runs at /glpi/ so for example, the Reports page would be at /glpi/front/report.php.\n\n1. Go to the Reports page\n2. Select something in the dropdown\n3. Then come back to the empty value \"-----\"\n4. Tadaaaaa!\n\n[Image omitted]\n\nEnvironment details:\nThe only relevant information is that my base URL is changed to something like: \"domain.com/glpi/\"", "priority": "medium", "type": "support", "createdByEmail": "kendall.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24841, "url": "https://github.com/glpi-project/glpi/issues/24841", "author": "Yohan-Baret-st", "anonymizedAuthorEmail": "kendall.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-13T14:20:54Z", "updatedAt": "2026-07-13T14:20:54Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Seemingly corrupt image of a email signature breaks business rule execution", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nHi,\n\nwe've got a customer who seems to fail to create tickets correctly via email due to (probably) it's image signature. This breaks business rule execution, meaning no one get's assigned, no notification is sent, nothing. The ticket get's stale and if no one accesses the platform manually, it gets lost.\n\nWe believe is it's signature because in many of the tickets there are no attachments or screenshots in the body.\n\nRegards,\nDaniel D.", "priority": "medium", "type": "support", "createdByEmail": "hayden.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24840, "url": "https://github.com/glpi-project/glpi/issues/24840", "author": "xBounceIT", "anonymizedAuthorEmail": "hayden.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-13T08:36:16Z", "updatedAt": "2026-07-13T08:36:16Z", "closedAt": null } }, { "title": "Attachments, even if not included in the form's destination response, are attached to the support tickets.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8q\n\nIssue description:\nI created a form with two destinations; in one I added all the questions and answers, and in the other I added all the questions except the attachment. However, the files are being added in all the requests.\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24832, "url": "https://github.com/glpi-project/glpi/issues/24832", "author": "verdanatech-marcio", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-10T11:21:30Z", "updatedAt": "2026-07-10T11:21:30Z", "closedAt": null } }, { "title": "Custom Asset date fields display \"null\" and trigger DateMalformedStringException when empty", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.8\n\nIssue description:\nIn a Custom Asset, I added two custom date fields:\n\n- Date de prêt\n- Date de restitution\n\nWhen these date fields are empty, GLPI displays the value \"null\" instead of leaving the field empty.\n\nThe issue happens on all items of this Custom Asset when the date field has no value.\n\nIf I set a date, save the item, then remove the date and save again, the field still displays \"null\" instead of being empty.\n\nWhen the Custom Asset list is displayed, GLPI tries to format the value \"null\" as a date. This triggers a DateMalformedStringException:\n\nFailed to parse time string (null) at position 0 (n): The timezone could not be found in the database\n\nExpected behavior:\nEmpty date fields should be displayed as empty values, not as the string \"null\".\n\nActual behavior:\nEmpty date fields are displayed as \"null\", and GLPI tries to parse this value as a date, which causes an error in Html::convDate().\n\nReproduction steps:\n1. Use GLPI 11.0.8\n2. Create or use a Custom Asset.\n3. Add one or more custom fields of type date.\nExample:\n- Date de prêt\n- Date de restitution\n4. Create an item in this Custom Asset.\n5. Leave the date fields empty.\n6. Save the item.\n7. Open the Custom Asset list view.\n8. The empty date fields are displayed as \"null\" instead of being empty.\n9. Edit the item again.\n10. Set a valid date in one of the date fields and save.\n11. Edit the item again.\n12. Remove the date value and save.\n13. The field still displays \"null\" instead of being empty.\n14. The list view triggers a DateMalformedStringException because GLPI tries to parse \"null\" as a date.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24817, "url": "https://github.com/glpi-project/glpi/issues/24817", "author": "Yann843", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-09T06:44:34Z", "updatedAt": "2026-07-09T06:44:34Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Global search fails on Custom Assets with linked custom fields due to invalid SQL alias", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.8\n\nIssue description:\nWhen using the global search bar located at the top-right of GLPI, the search fails with a MySQL error on a Custom Asset.\n\nThe issue occurs on this custom asset definition:\nGlpi\\CustomAsset\\SallesinformatiqueAsset\n\nThis Custom Asset contains custom fields linked to other assets. When a global search is performed, GLPI generates an invalid SQL query. The LEFT JOIN clauses correctly create aliases using this pattern:\n\nglpi_assets_assets_custom_fields_[hash]\n\nBut the WHERE clause incorrectly references aliases using this pattern:\n\nglpi_assets_assets_[hash].name\n\nThese aliases do not exist in the query, which causes a MySQL error:\n\nUnknown column 'glpi_assets_assets_[hash].name' in 'WHERE' (1054)\n\nThe problem does not seem to come from the SallesinformatiqueAsset itself. It seems to be triggered by the global search engine when searching inside linked custom fields of a Custom Asset.\n\nThe generated SQL query uses the correct alias in the LEFT JOIN clause, but an incorrect alias in the WHERE clause.\n\nReproduction steps:\n1. Use GLPI 11.x.\n2. Create or use a Custom Asset definition, for example: Glpi\\CustomAsset\\SallesinformatiqueAsset\n3. Add one or more custom fields linked to another asset type.\n4. Make sure these linked custom fields are available in the Custom Asset search/list view.\n5. Use the global search bar located at the top-right of the GLPI interface.\n6. Search for any value, for example: grgrg\n7. The search fails with a MySQL error.\n8. The generated SQL query contains valid aliases in the LEFT JOIN clauses but invalid aliases in the WHERE clause.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24815, "url": "https://github.com/glpi-project/glpi/issues/24815", "author": "Yann843", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-09T06:36:00Z", "updatedAt": "2026-07-09T06:36:00Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Error in anonymous form", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nWhen trying to fill out an anonymous access form, I am receiving some Form/Engine access errors.\n\nAffected page:\n\nReproduction steps:\nCreate an anonymous access form\nAdd questions that are neither Dropdown nor GLPi Objects\nAttempt to answer the form\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24802, "url": "https://github.com/glpi-project/glpi/issues/24802", "author": "verdanatech-marcio", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-07T11:45:04Z", "updatedAt": "2026-07-07T11:45:04Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "pb translation reminders", "detail": "Issue description:\nIn Tools > Reminders, the translations aren't working. I wrote a reminder in English and then translated it into French, but the French version is appearing in English.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24801, "url": "https://github.com/glpi-project/glpi/issues/24801", "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "beta / rc" ], "state": "open", "stateReason": null, "createdAt": "2026-07-07T10:37:59Z", "updatedAt": "2026-07-07T10:38:25Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Missing merged follow-ups and tasks from child into parent ticket", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nSince version 11, adding a follow-up or a task to a child ticket automatically created a merged element within the parent ticket.\n\nThis was great for us, as it allowed all actions taken on child tickets to be visible within the parent ticket—acting as a summary of all work done across various sub-tasks. Our main workflow relied on this to hide child tickets from the requesters and only show them the parent ticket, effectively limiting the number of visible tickets on their end.\n\nHowever, since version 11.0.6 (or 11.0.7), this behavior no longer works.\n\nI found issue #24454, which states that this was considered a bug for follow-ups, so I assume it was \"fixed\" (removed) for tasks as well.\n\nIs there any chance this feature could be brought back, or at least provided as an option that can be enabled via the global settings?\n\nKind regards,\n\nReproduction steps:\n1. create 2 tickets\n2. define 1 as a child of the other\n3. add into child ticket a task or follow-up\n4. nothing appear in parent ticket", "priority": "medium", "type": "support", "createdByEmail": "riley.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24782, "url": "https://github.com/glpi-project/glpi/issues/24782", "author": "JMICob", "anonymizedAuthorEmail": "riley.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-06T13:34:46Z", "updatedAt": "2026-07-06T13:34:46Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Massive action toolbar silently disappears above ~990 displayed rows, no warning message shown (regression of #18341 behavior)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen a search result list displays more rows than max_input_vars (PHP ini setting) allows, GLPI hides the \"Actions\" (massive action) toolbar/button entirely, with no explanatory message shown anywhere on the page. This reproduces on multiple search screens (tested on front/user.php — standard Users list — and front/ldap.import.php — LDAP directory import/sync screen), so it appears to be a general regression in the Search/massive-action display logic, not specific to one page.\n\nThis is the same symptom originally reported in #18341 (\"Selection too large, massive action disabled\" never displayed), which was closed/fixed in milestone 10.0.18. On our 11.0.7 instance the underlying warning message still never appears — the toolbar just vanishes silently, exactly as in the original report — so either the fix did not cover all search contexts (e.g. the interface=simple LDAP import screen), or it has regressed since 10.0.18.\n\nExpected behavior\n\nPer the fix intended in #18341, when the massive action toolbar is disabled because the result set is too large for max_input_vars, GLPI should display the message \"Selection too large, massive action disabled.\" (or its localized equivalent) in place of the toolbar, so users understand what happened and how to work around it (reduce page size, or raise max_input_vars/suhosin.post.max_vars).\n\nActual behavior\n\nThe massive action toolbar simply disappears with zero on-screen explanation. In our testing:\n\n990 displayed rows → \"Ações\" button present and functional.\n991 displayed rows → \"Ações\" button absent, and no \"Selection too large\" (or Portuguese equivalent) message appears anywhere on the page.\n\nThis matches max_input_vars (1000) exactly: the threshold is max_input_vars - 10 (per the logic patched in #18341: disable when max_input_vars 990.\n\nImpact / real-world context\n\nThis was discovered while bulk-importing ~1000 Active Directory users into GLPI via front/ldap.import.php. With the default result set (>1000 candidate users), the \"Ações\" → \"Importar\" action was simply not available anywhere on the page, with no error or hint. It took extensive DOM/network inspection to determine the toolbar was being suppressed due to row count, and the only workaround found was manually paginating the import into batches of ≤990 (we used batches of 100 for safety margin) and repeating the select-all → Ações → Importar → Enviar cycle per batch. A first attempt at importing 500 rows in one batch even returned an \"Access denied\" massiveaction.php error rather than the expected message — suggesting the disabled toolbar can be worked around in ways that still hit hidden validation elsewhere.\n\nAn admin without deep familiarity with GLPI internals would have no way to discover this behavior or its cause.\n\nSuggested fix\n\nEnsure the \"Selection too large, massive action disabled.\" message (from the #18341 fix) actually renders in all search/list contexts that use this display logic, including the LDAP import/sync interface=simple screens, not just the default Search::show() path. Alternatively/additionally, surface the same message (or a link to documentation) whenever the massive action toolbar is omitted, so the behavior is never silent.\n\nReproduction steps:\n1. Go to any search screen with more than ~990 matching results (e.g. Administration > Users, or the LDAP \"Link do diretório LDAP\" import/sync screen at front/ldap.import.php).\n2. Set the page size (\"linhas/página\" / rows-per-page, or the glpilist_limit URL parameter) so that the number of displayed rows is 990 or fewer.\n\n- Result: the \"Ações\" (Actions) button/toolbar is visible and usable above the results table.\n3. Increase the page size (or glpilist_limit) so that 991 or more rows are displayed on the same page, with everything else unchanged.\n- Result: the \"Ações\" button disappears completely. No message, warning, or any other on-page indication explains why.", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24772, "url": "https://github.com/glpi-project/glpi/issues/24772", "author": "montelocso", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-03T13:38:26Z", "updatedAt": "2026-07-03T13:38:26Z", "closedAt": null } }, { "title": "Automatic approval reminder sends notifications for deleted (trashed) tickets", "detail": "Issue description:\nTitle\n\nAutomatic approval reminder sends notifications for deleted (trashed) tickets\n\nEnvironment\n\nGLPI Info:\n\nParameters:\n\nHost info:\n\nSteps to reproduce\n\n1. Create a ticket.\n2. Add an approval request.\n3. Leave the approval status as \"Waiting for approval\".\n4. Configure the Automatic Approval Reminder notification.\n5. Move the ticket to the Trash (Delete the ticket).\n6. Wait for the reminder automatic action to execute (or run it manually).\n\nCurrent behavior\n\nThe approver still receives the Automatic Approval Reminder email for the deleted/trashed ticket.\n\nExpected behavior\n\nDeleted (trashed) tickets should not be considered by the Automatic Approval Reminder.\n\nOnly active tickets should generate reminder emails.\n\nAdditional information\n\nThe Notification Filter UI does not expose any \"Deleted\" or \"is_deleted\" criterion.\n\nTherefore, administrators have no configuration option to exclude deleted tickets from reminders.", "priority": "medium", "type": "support", "createdByEmail": "casey.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24767, "url": "https://github.com/glpi-project/glpi/issues/24767", "author": "abhi0698", "anonymizedAuthorEmail": "casey.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-03T05:34:36Z", "updatedAt": "2026-07-03T05:36:15Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Kanban display issue", "detail": "Issue description:\nWhen a project status is translated (e.g., from English to French), the Kanban view no longer displays.\nI see this error message in the logs, but nothing appears in debug mode.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24763, "url": "https://github.com/glpi-project/glpi/issues/24763", "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-02T12:29:57Z", "updatedAt": "2026-07-02T12:30:09Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Mail receiver repeatedly creates duplicate tickets from reply to closed ticket notification", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen a user replies by email to a notification for an already closed ticket, GLPI detects the original ticket reference but does not import the message as a follow-up to the existing ticket.\n\nInstead, GLPI creates a new ticket from the reply. However, the original email is not moved from the mail receiver inbox to the configured processed folder, for example accepted. As a result, the same email remains in the inbox and is processed again on every mailgate / receiver cron run.\n\nThis causes a loop where a new duplicate ticket is created repeatedly from the same email message.\n\nThe issue is not caused by an IMAP move permission problem, because normal new ticket emails are correctly moved to the accepted folder after successful import. The problem appears only when replying to a notification related to a closed ticket.\n\nExpected behavior:\n\nGLPI should not repeatedly process the same email. If a reply to a closed ticket cannot be imported as a follow-up, GLPI should either:\n\n- reject the email and move it to the refused / not imported folder,\n- or create one new ticket and mark the email as processed,\n- or reopen the original ticket if the configuration allows it.\n\nBut the email should not remain in the inbox and be processed again on each cron execution.\n\nObserved behavior:\n\n- The reply email is detected by the receiver.\n- GLPI creates a new ticket instead of importing it as a follow-up.\n- The original email remains in the inbox.\n- On the next mailgate run, GLPI processes the same email again.\n- A new duplicate ticket is created every time.\n\nThe email contains a valid GLPI ticket reference in the subject and also contains In-Reply-To / References headers pointing to the original closed ticket notification.\n\nExample headers:\n\nThe same Message-ID is processed repeatedly.\n\nReproduction steps:\n1. Configure a mail receiver in GLPI.\n2. Configure the receiver to move successfully processed emails to an accepted folder.\n3. Verify that the receiver works correctly for normal new ticket emails:\n - send a new email to the receiver address,\n - run the mailgate / receiver cron,\n - confirm that a new ticket is created,\n - confirm that the email is moved from INBOX to accepted.\n4. Create a ticket by email through the same mail receiver.\n5. Close the created ticket in GLPI, so the ticket status becomes Closed.\n6. Make sure the requester receives the GLPI notification email about the closed ticket.\n7. From the requester mailbox, reply to the closed ticket notification email.\n\nExample subject:\nRe: [GLPI #0000118] Closing of the ticket Test loop 02\n\n8. Run the mail receiver / mailgate cron.\n9. Observe that GLPI creates a new ticket from the reply instead of importing the message as a follow-up to the original closed ticket.\n10. Check the mail receiver inbox.\n11. Observe that the original reply email is still present in the inbox and was not moved to the configured accepted folder.\n12. Run the mail receiver / mailgate cron again.\n13. Observe that GLPI processes the same email again and creates another duplicate ticket.\n14. Repeat the cron execution and observe that a new duplicate ticket is created on every run from the same email message.\n\nExpected result\n\nAfter the first processing attempt, the email should not remain in the inbox for repeated processing.\n\nGLPI should either:\n\n- import the reply as a follow-up and reopen the closed ticket if allowed,\n- reject the email and move it to the refused / not imported folder,\n- or create a new ticket once and move the email to the accepted / processed folder.\n\nActual result\n\nGLPI creates a new ticket from the reply, but the email remains in the inbox. The same email is processed again on every mailgate cron run, creating duplicate tickets repeatedly.\n\nEnvironment details:\nGLPI: 11.0.7 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\n\nAdditional context:\nAs a temporary workaround, we changed the ticket closing workflow and added a mail receiver rule to prevent this loop.\n\nCurrent workaround:\n\n1. Technicians should not close tickets directly.\n2. Tickets should be moved only to the Solved status.\n3. GLPI should automatically close solved tickets after X days.\n4. A mail receiver rule was added to reject replies to closed ticket notifications.\n\nThe mail receiver rule catches replies to closed ticket notifications, for example messages with a subject like:\n\nThe rule checks the email subject for the GLPI ticket reference and the closing notification text, for example:\n\nAction:\n\nThis prevents GLPI from creating a new ticket from a reply to an already closed ticket notification and prevents the same email from being imported repeatedly.\n\nThis workaround avoids the mail import loop, but it is not an ideal solution because the system should not repeatedly process the same email even without a custom rule.", "priority": "medium", "type": "support", "createdByEmail": "cameron.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24760, "url": "https://github.com/glpi-project/glpi/issues/24760", "author": "KamikX", "anonymizedAuthorEmail": "cameron.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-02T09:57:14Z", "updatedAt": "2026-07-02T10:02:53Z", "closedAt": null } }, { "title": "SamAccountName is not used to link Computer to user if user authenticates using UPN", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nNot sure it is a bug or a \"Keyboard/chair interface issue\".\n\nIf a user is authenticated by UserPrincipalName against LDAP, the User-Computer link is not made.\nIf a user is authenticated by SamAccountName against LDAP, the User-Computer link is made.\nWhat am I missing here ?\n\nReproduction steps:\nAdd an LDAP authentication using the UserPrincipalName as \"Login field\", it works as expected. User is able to connect to GLPI and all LDAP fields are synced from LDAP to GLPI, including the SamAccountName.\nThen, when Glpi-Agent makes its thing, the \"Alternate username\" field is SamAccountName@DOMAIN and the link is not made between the Computer and the LDAP authenticated user.\n\nAdditional context:\nIf I authenticate using the SamAccountName as \"Login field\", the user-computer link is established as expected.", "priority": "medium", "type": "support", "createdByEmail": "bailey.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24749, "url": "https://github.com/glpi-project/glpi/issues/24749", "author": "J-C-P", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-07-01T13:33:14Z", "updatedAt": "2026-07-01T13:35:25Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "[API] Undefined array key warning when using forcedisplay with additionalfields in searchItems() glpi.WARNING: * Warning: Undefined array key \"ITEM_Ticket_62_TABLE.entities_id\" at API.php line 1817", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen calling the REST API endpoint GET /apirest.php/search/Ticket with a forcedisplay parameter that references a search option containing additionalfields (e.g. field 62 — entities_id), a PHP warning is thrown for every result row where the additional field key is absent from the raw SQL result array.\n\nThis generates massive log pollution — we observed over 3 million warnings in a single month on a production instance, saturating the php-errors.log file (2.7 GB for one rotation period).\n\nReproduction steps:\n1. Authenticate via REST API (GET /apirest.php/initSession)\n2. Call the search endpoint with forcedisplay referencing field 62:\n\nGET /apirest.php/search/Ticket?forcedisplay[0]=62&expand_dropdowns=true&is_deleted=0\n\n3. Observe php-errors.log:\n\n[2026-06-26 13:19:18] glpi.WARNING: * Warning: Undefined array key\n\"ITEM_Ticket_62_TABLE.entities_id\" at API.php line 1817\n\nAdditional context:\nProposed Fix : Replace direct array access with null coalescing operator:\n\n// Before\n$tmp_fields[$field_name] = $raw[$field_value_key];\n\n// After\n$tmp_fields[$field_name] = $raw[$field_value_key] ?? null;", "priority": "medium", "type": "support", "createdByEmail": "jesse.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24699, "url": "https://github.com/glpi-project/glpi/issues/24699", "author": "laurentbarre1985", "anonymizedAuthorEmail": "jesse.adler@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2026-06-29T11:58:36Z", "updatedAt": "2026-07-01T02:16:33Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Align dashboard card generation with relations exposed by asset type search options", "detail": "Contribution description:\nI would like to propose an improvement to dashboard card generation in GLPI core.\n\nGLPI already relies on common mechanisms such as CommonDBTM and rawSearchOptions() to integrate and expose itemtype capabilities in a generic way. In that context, dashboard card generation could be made more robust and easier to maintain by deriving available relations from the asset type search options instead of relying on a fixed list of assumed foreign key relations.\n\nCurrently, in src/Glpi/Dashboard/Grid.php, dashboard cards are generated for all asset types listed in $CFG_GLPI['asset_types'], using a predefined set of relations such as State, Entity, Manufacturer, Location, and conditionally Type and Model.\n\nCurrent behavior:\ngetAllDashboardCards() creates cards for every asset type / foreign key combination without checking whether the corresponding relation is actually exposed by the current asset type in its rawSearchOptions().\n\nFor asset types that do not expose some of these relations, this can generate dashboard cards that are irrelevant, empty, or inconsistent at runtime.\n\nExpected behavior:\nDashboard cards should only be generated for relations that are actually exposed by the current asset type in its rawSearchOptions().\n\nProposed solution:\nBefore creating a card, inspect the asset type search options and only generate cards for relations that are effectively available.\n\nExample:\n\nThis would make dashboard card generation follow the same declarative logic already used elsewhere through search options, while improving robustness and maintainability.\n\nAdditional fix:\nWhile reviewing the same block, I also noticed that the generated card definition currently contains a hardcoded itemtype:\n\nThis should probably use the current $itemtype instead:\n\nBenefits:\nImproves the robustness of dashboard card generation in core\nMakes the implementation easier to maintain by relying on declared search options\nAvoids generating irrelevant cards for unsupported relations\nReduces empty or inconsistent dashboard results at runtime\nKeeps dashboard behavior aligned with the generic itemtype integration model already used in GLPI", "priority": "medium", "type": "support", "createdByEmail": "hayden.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24708, "url": "https://github.com/glpi-project/glpi/issues/24708", "author": "krysleo", "anonymizedAuthorEmail": "hayden.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-30T07:26:06Z", "updatedAt": "2026-06-30T07:26:06Z", "closedAt": null } }, { "title": "GUI: Impact analysis impossible to identify groups", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nWe have severals groups called \"Desarrollo\" under differents entities\nSearching groups don't show entity, so is not easy to determine what grup must be selected:\n\n[Image omitted]\n\nReproduction steps:\nHave groups with same name in different entities levels.\nSelect asset\nTry search and add group node on Impact analysis\n\nEnvironment details:\nGLPI 11.0.8", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24705, "url": "https://github.com/glpi-project/glpi/issues/24705", "author": "ftoledo", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-06-30T01:08:39Z", "updatedAt": "2026-06-30T01:10:31Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Undefined array key \"name\" in /usr/share/glpi/src/Search.php at line 7934", "detail": "Issue description:\nHi,\n\nWhen I create (10.0.26) a new contract with minimal data (only \"TestContrat1\" as name), this newly created contract triggers:\nPHP Warning (2): Undefined array key \"name\" in /usr/share/glpi/src/Search.php at line 7934\nAre you able to reproduce or do you need more debug information?", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24697, "url": "https://github.com/glpi-project/glpi/issues/24697", "author": "kabassanov", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-29T09:57:13Z", "updatedAt": "2026-06-29T10:01:26Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Massive random 401 \"unauthorized\" response from system", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nFresh installation on nazwa.pl shared hosting provider, all requirements met.\n\nOn every page refresh there are numbers of 401 responses for random resourses: scripts, files, images. Even on login page. After few retries I can login and use a system, but get 401 response \"unauthorized\" randomly.\n\nFor these 401 requests there are new empty session files created.\n\nServer runs multiple php applications, from standard wp sites to comples php apps.\n\nPlease adivice.", "priority": "medium", "type": "support", "createdByEmail": "jesse.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24690, "url": "https://github.com/glpi-project/glpi/issues/24690", "author": "astwinioenergy", "anonymizedAuthorEmail": "jesse.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-26T19:36:34Z", "updatedAt": "2026-06-26T19:36:34Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Ldap users deleted when moved in AD", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nHi, i have problem with user sync with ours Active directory. Since many years we haven't set any sync filed. we have come in trouble recently with some OU renaming and users moved, and a lot of then ended in user trash.\n\nReproduction steps:\nAfter cleaning DB, set sync field to objectguid, re enabled all users and moved then all out of trash we start resynch everything with console.\nTo get objectguid is glpi only the mass option 'Clean LDAP fields and force synchronisation' as imported the sync field.\nNow, use renaming ,deleted or restored from ad are working correctly.\nOption are set like this in glpi:\n\n[Image omitted]\n\nonly problem is that when i mode a user in AD it's moved in trash and set as deleted from ldap with console:\nsudo -u www-data /usr/bin/php /var/www/glpi/bin/console -n --lang=fr_FR glpi:ldap:synchronize_users -s 2\n\nif i use 'Clean LDAP fields and force synchronisation' from glpi user dn is updated and not moved to trash.", "priority": "medium", "type": "support", "createdByEmail": "robin.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24686, "url": "https://github.com/glpi-project/glpi/issues/24686", "author": "Blank-Vcf", "anonymizedAuthorEmail": "robin.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-26T09:42:10Z", "updatedAt": "2026-06-26T09:50:56Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "feat(Change): Add change type classification (Standard / Normal / Emergency) per ITIL v4", "detail": "Contribution description:\nContext\n\nITIL v4's Change Enablement practice defines three distinct change types that require different authorization and workflow paths:\n\n- Standard — pre-authorized, low risk, well-understood procedure. Should bypass manual validation and be auto-approved when created.\n- Normal — follows the standard assessment and CAB approval workflow. Covers the current default behaviour in GLPI.\n- Emergency — unplanned, urgent. Requires an expedited but still traceable approval process (e-CAB).\n\nCurrently, the glpi_changes table has no change_type field. Every RFC — regardless of risk or urgency — goes through the same workflow. This makes it impossible for organizations running ITIL v4 to implement compliant change authorization using GLPI core alone.\n\nProposed change\n\nAdd a change_type integer column to glpi_changes and the corresponding constants to Change.php:\n\n// Change.php\npublic const STANDARD_CHANGE = 1;\npublic const NORMAL_CHANGE = 2;\npublic const EMERGENCY_CHANGE = 3;\n\nDefault value: NORMAL_CHANGE (preserves current behaviour for all existing records and upgrades).\n\nBehaviour per type:\n\n┌───────────┬───────────────────────────────────────────────────┬──────────────────────┬─────────────────────────────────────┐\n│ Type │ Validation steps │ time_to_resolve │ Notes │\n├───────────┼───────────────────────────────────────────────────┼──────────────────────┼─────────────────────────────────────┤\n│ Standard │ Skipped (auto-accepted) │ Inherited from │ Optionally tied to a pre-approved │\n│ │ │ template │ ChangeTemplate │\n├───────────┼───────────────────────────────────────────────────┼──────────────────────┼─────────────────────────────────────┤\n│ Normal │ Current ChangeValidationStep flow │ Standard TTR │ No change to existing logic │\n├───────────┼───────────────────────────────────────────────────┼──────────────────────┼─────────────────────────────────────┤\n│ Emergency │ ChangeValidationStep flow, but validation percent │ Shorter TTR │ Adds is_emergency flag visible in │\n│ │ threshold reduced │ │ list views │\n└───────────┴───────────────────────────────────────────────────┴──────────────────────┴─────────────────────────────────────┘\n\nWhat this touches:\n- install/mysql/glpi-empty.sql — new column + index on glpi_changes\n- A migration file under install/migrations/ for existing installations\n- src/Change.php — constants, getAllStatusArray()-equivalent for types, rawSearchOptions(), pre-add/pre-update logic to skip validation for Standard\n- src/RuleChange.php / src/RuleChangeCollection.php — add change_type as available criterion and action\n- Twig templates for the Change form — type selector field\n- src/NotificationTargetChange.php — expose type in notification data\n\nWhat this does NOT touch:\n- Ticket.php — already has INCIDENT_TYPE / DEMAND_TYPE; the same pattern is followed here\n- ChangeValidationStep.php — no changes to the validation step logic itself; Standard changes simply never create steps\n- Any plugin API surface\n\nBackward compatibility\n\n- Existing changes keep change_type = NORMAL_CHANGE after migration — zero behaviour change on upgrade.\n- The field is nullable-with-default in the schema; no mandatory field introduced in templates by default.\n\nScope question for maintainers\n\nThe plugin-first policy in CONTRIBUTING.md is noted. However, change_type belongs on the shared glpi_changes schema, which a plugin cannot alter portably without core support. We believe this qualifies as shared infrastructure. If the team prefers a plugin approach first, we would need a hook or override point in Change::prepareInputForAdd() / Change::post_getEmpty() — which does not currently exist for this purpose. We are happy to discuss either path.\n\nTests\n\n- Unit tests for the new constants and type-label methods in Change.php\n- Integration tests asserting that a Standard change skips ChangeValidationStep creation\n- Integration tests asserting that a Normal change follows the existing validation flow unchanged\n- Search/filter tests for change_type via rawSearchOptions()\n\nTarget branch\n\nmain (new feature, per contribution guidelines).", "priority": "medium", "type": "support", "createdByEmail": "devon.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24681, "url": "https://github.com/glpi-project/glpi/issues/24681", "author": "giovanny07", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-25T20:52:15Z", "updatedAt": "2026-06-25T20:52:15Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "IFticket.action condition fails for \"Mise à jour d'une tâche\" and \"Mise à jour d'un suivi\" notifications", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.8\n\nIssue description:\nWhen using notification templates, conditional blocks based on ticket.action work correctly for some actions such as:\n\n##IFticket.action=Nouvelle tâche##\n...\n##ENDIFticket.action##\n\nand\n\n##IFticket.action=Nouveau suivi##\n...\n##ENDIFticket.action##\n\nHowever, similar conditions do not work for update actions:\n\n##IFticket.action=Mise à jour d'une tâche##\n...\n##ENDIFticket.action##\n\nand\n\n##IFticket.action=Mise à jour d'un suivi##\n...\n##ENDIFticket.action##\n\nThe content inside the conditional block is never rendered.\n\nReproduction steps:\nCreate or edit a notification template.\nAdd the following content:\n##IFticket.action=Mise à jour d'une tâche##\nTEST\n##ENDIFticket.action##\nTrigger a task update on a ticket.\nReceive the notification email.\n\nAdditional context:\nExpected behavior\n\nThe text:\n\nTEST\n\nshould be displayed because the action is \"Mise à jour d'une tâche\".\n\nActual behavior\n\nNothing is displayed.\n\nAdditional investigation\n\nUsing:\n\nAction détectée : [##ticket.action##]\n\ninside the same notification produces:\n\nAction détectée : [Mise à jour d'une tâche]\n\nwhich confirms that the ticket.action variable contains the expected value.\n\nHowever, the condition:\n\n##IFticket.action=Mise à jour d'une tâche##\n\ndoes not evaluate to true.\n\nThe same issue occurs with:\n\n##IFticket.action=Mise à jour d'un suivi##\n\nwhile conditions for:\n\n##IFticket.action=Nouvelle tâche##\n\nand\n\n##IFticket.action=Nouveau suivi##\n\nwork correctly.\n\nNotes\n\nThis may be related to:\n\nstring comparison in notification templates,\nhandling of accented characters,\nhandling of apostrophes ('),\nor a specific issue with update actions in the template engine.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24676, "url": "https://github.com/glpi-project/glpi/issues/24676", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-25T11:29:03Z", "updatedAt": "2026-06-25T11:29:03Z", "closedAt": null } }, { "title": "Infinite loop when displaying contract detail", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.25\n\nIssue description:\nAfter installed a new fresh version of GLPI 10.0.25.\n\nGo to contract. Add a new contract with this value :\nName : FREECAD (for example)\nStart date : 2020-01-01\nNotice : 3 months\nRenewal : Tacit\nInitial contract period : -----\nInvoice period ; 12 months\n\nSave the contract.\nReturn to the contract list (If you have many contract it can be not display, For my case I have only 1 contract \"FREECAD\")\nDisplay the detail of the contract by clicking on the name.\n\nExpected :\nDetail of the contract must be displayed\n\nCurrent :\nThe detail is not displayed only the loader gift turn.\n\nAffected page:\n/front/contract.form.php?id=1\n\nReproduction steps:\nCreate a contract with this data :\nName : FREECAD (for example)\nStart date : 2020-01-01\nNotice : 3 months\nRenewal : Tacit\nInitial contract period : -----\nInvoice period ; 12 months\n\nAfter the save, display the detail of the contract.\n\nEnvironment details:\nA fresh install of the GLPI version 10.0.25 :\nGLPI 10.0.25 ( => C:\\xampp_8.2\\htdocs\\glpi-10.0.25)\nInstallation mode: TARBALL\nCurrent language:en_GB\n\nAdditional context:\nNot reproduce in GLPI 10.0.18.", "priority": "medium", "type": "support", "createdByEmail": "elliot.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24660, "url": "https://github.com/glpi-project/glpi/issues/24660", "author": "cuicui86", "anonymizedAuthorEmail": "elliot.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-24T09:42:21Z", "updatedAt": "2026-06-24T09:42:21Z", "closedAt": null } }, { "title": "better handle form import errors", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nImporting a form from one GLPI instance to another fails.\nThere might be some question data (category, etc.) that isn't available in the destination instance. But beyond that, GLPI should provide more detailed information, at least some reference to which question or target is causing the problem, so it can be corrected. As it is, the reason for the import failure is unclear.\n\nexamples:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24644, "url": "https://github.com/glpi-project/glpi/issues/24644", "author": "ftoledo", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-22T16:23:37Z", "updatedAt": "2026-06-22T16:23:37Z", "closedAt": null } }, { "title": "Windows IIS + PHP + LDAPS returns \"Can't contact LDAP server (-1)\" until TLS options are initialized before first LDAP connection", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.25 e 11.x\n\nEnvironment:\n- GLPI 10.0.25 and 11.x\n- Windows Server\n- IIS\n- PHP 8.3.31 and 8.5.7\n- Active Directory\n- LDAPS (636 ou 3269)\n\nSymptoms:\nLDAP tests fail with:\n\nCan't contact LDAP server (-1)\n\nThe same LDAP server works correctly with:\n\n- LDP.EXE\n- Standalone PHP scripts using ldap_connect() and ldap_bind()\n- Valid certificates and trusted CA\n\nRoot Cause:\nThe OpenLDAP client used by PHP does not appear to apply TLS settings early enough when GLPI creates the LDAP connection under IIS.\n\nWorkaround:\nA PHP bootstrap file loaded through auto_prepend_file was used to initialize TLS options before the first LDAP connection:\n\nshell", "priority": "medium", "type": "support", "createdByEmail": "kendall.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24640, "url": "https://github.com/glpi-project/glpi/issues/24640", "author": "sidneyveroneze", "anonymizedAuthorEmail": "kendall.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-22T13:54:43Z", "updatedAt": "2026-06-22T13:55:13Z", "closedAt": null } }, { "title": "OpenAPI json issue", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nThe Swagger OpenAPI json seems to contain issues. I get the json document from swagger using\nI get errors on the DashboardItem when generating code using OpenAPI generator or NSwag.\nBelow is some output the editor.swagger.io:\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "remy.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24610, "url": "https://github.com/glpi-project/glpi/issues/24610", "author": "jhermsen", "anonymizedAuthorEmail": "remy.adler@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2026-06-19T06:22:04Z", "updatedAt": "2026-06-19T23:06:13Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Uploaded images not visible for users", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWe have sometimes images in our forms, they are not displayed for the users and if they access it by a direct link, the following errors occur.\nThe user has the \"simplified interface\" in the profile set.\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24487, "url": "https://github.com/glpi-project/glpi/issues/24487", "author": "SimonTheIman", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-05T09:01:36Z", "updatedAt": "2026-06-17T20:16:11Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Duplicate entry SQL error when creating an existing Knowledge Base category from article form", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen writing a new Knowledge Base article, if a user attempts to create a new Category via the \"New item\" modal window (the plus icon) using a name that already exists in the database, the system does not validate the input. Instead of showing a user-friendly validation message, it attempts the INSERT and throws a fatal MySQL 1062 Duplicate entry error.\n\nAffected page:\n/front/knowbaseitem.form.php\n\nReproduction steps:\n1. Go to Tools > Knowledge Base and start writing a New Article.\n2. Next to the Category dropdown field, click the \"New item\" (plus + icon) to open the creation modal.\n3. In the Name field, input a category name that already exists in the system (e.g., Grafana).\n4. Click Add.\n5. Observe the fatal SQL error.\n\nAdditional context:\nThe system should catch the duplicate entry and return a standard warning message (e.g., \"Item already exists\" or \"Duplicate entry\") inside the modal or UI, allowing the user to correct their input without crashing the application flow.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24559, "url": "https://github.com/glpi-project/glpi/issues/24559", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-14T21:36:24Z", "updatedAt": "2026-06-17T18:49:19Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Cannot change active pending reason from a new task when ticket is already in Pending status", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.25 and 11.0.7\n\nIssue description:\nWhen a ticket is already in Pending status and has an active pending reason, it is currently not possible to change that pending reason while creating a new task from the ticket timeline.\n\nIn this scenario, the pending reason selector/actions are hidden in the new task form when the ticket already has an active pending reason.\n\n[Image omitted]\n\nHowever, the same operation is possible when creating a new follow-up: the pending reason fields are displayed, allowing the active pending reason to be changed.\n\n* This behavior was corrected for follow-ups in #15715\n\n[Image omitted]\n\nAs a result, the behavior is currently inconsistent between the task and follow-up forms.\n\nReproduction steps:\n1. Create or open a ticket.\n2. Add a new follow-up/task with a pending reason.\n3. Try to add a new task and change the active pending reason from the new task form.\n4. Notice that the pending reason selector/actions are not available.\n5. Add a new follow-up instead.\n6. Notice that the pending reason can be changed from the follow-up form.\n\nAdditional context:\nIn GLPI 10.0.25, the task form template seems to hide pending reason controls when the ticket already has an active pending reason.\n\nFile:\ntemplates/components/itilobject/timeline/form_task.html.twig\n\nRelevant logic observed:\n\nThe behavior seems inconsistent because the follow-up form allows updating the pending reason.\n\nAlso, the backend seems to support updating pending reason details when adding a new task or follow-up.\n\nFile:\nsrc/PendingReason_Item.php\n\nRelevant comment observed:\n\n\"This method update the latest pending timeline item if the user has edited the pending details while adding a new task or followup\"", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24567, "url": "https://github.com/glpi-project/glpi/issues/24567", "author": "serviceticst", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-15T14:05:24Z", "updatedAt": "2026-06-15T14:05:24Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Drop jQuery File Upload", "detail": "Issue description:\nSince the KB rework, there is now a custom file upload component. There is no known reason to keep jquery-file-uploader around, and after my PRs to remove FancyTree and RateIt get merged, this is the last dependency that is keeping the ancient jQuery UI dependency around and therefore the only thing left keeping me from finalizing the migration away from Webpack to Vite.\n\nThen, the long-abandoned qTip2 dependency remains as the only dependency that requires jQuery AFAIK.\n\nFurther, It would look more professional if every file input looked the same.\n\nI already tried looking at this but there are more changes needed with it than I want to do at the moment; I don't want to mess too much with the new KB code at this point.\nAt least:\n1. The component is not fully independent of the new KB code. Some of the file upload functionality seems to only exist for the KB.\n2. The template does not initialize the JS for the component.\n3. There is no compatibility with the existing file handler code on the server side.\n4. Component styles are only built with its use in a modal in mind (too large). The component would need to at least support a \"small\" variant with less padding and adjusting the upload list to be more compact.\n5. No support for an \"onlyimages\" option.", "priority": "low", "type": "feature", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24552, "url": "https://github.com/glpi-project/glpi/issues/24552", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "enhancement", "task" ], "state": "open", "stateReason": null, "createdAt": "2026-06-12T19:16:22Z", "updatedAt": "2026-06-12T19:16:22Z", "closedAt": null } }, { "title": "Self-Service users can edit technician comments in assigned approval requests", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen a technician creates an approval request for a ticket and includes a comment/instruction for the approver, the assigned user (with a Self-Service profile) is able to edit or modify the technician's original text within that validation request. An approver should only be able to approve, reject, or add their own feedback, but never alter the description or comments written by the technician who initiated the request.\n\nReproduction steps:\n1. Log in as a Technician or Admin\n2. Create a new approval request assigned to a standard Self-Service user, and add a text in the comment/description field\n3. Log in as the assigned Self-Service user\n4. Open the ticket\n5. Notice that the text field containing the technician's original comment is editable, allowing the user to change the context of what they are actually approving.", "priority": "medium", "type": "support", "createdByEmail": "emerson.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24534, "url": "https://github.com/glpi-project/glpi/issues/24534", "author": "Werneschoenholz", "anonymizedAuthorEmail": "emerson.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-10T14:05:45Z", "updatedAt": "2026-06-10T14:05:45Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Public FAQ ignores knowledge base item's settings", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nPrerequisite: Public FAQ enabled.\nOnce a knowledeg base item is created and selected to be in FAQ, the item is displayed in the public FAQ regardless of Targets, Visible since, Visible until settings.\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\n/front/helpdesk.faq.php\n\nReproduction steps:\n1. Enable public FAQ under Setup > General > General setup > Allow FAQ anonymous access\n2. Add new item to knowledge base, with Put this item to the FAQ = Yes\n3. Play with the settings of Targets, Visible since, Visible until, they're ignored anyway\n4. Open the FAQ when not logged in, the item is there", "priority": "medium", "type": "support", "createdByEmail": "remy.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24532, "url": "https://github.com/glpi-project/glpi/issues/24532", "author": "MadBeango", "anonymizedAuthorEmail": "remy.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-10T13:18:41Z", "updatedAt": "2026-06-10T13:18:41Z", "closedAt": null } }, { "title": "Feature Request: Enable Network Port Metrics for Computer Assets", "detail": "Issue description:\nCurrently, vital network port statistics such as the number of I/O bytes (ifinbytes, ifoutbytes, ifinerrors, ifouterrors) and Port Number (logical_number / ifnumber) are primarily associated with Network Equipment (like manageable switches).\n\nI propose adding support to map these network port telemetry metrics directly to Computer assets (and other non-NetworkEquipment assets).\n\n[Image omitted]\n\nWhy is this useful:\nBringing host-level network monitoring parity to computer assets provides direct insight into the actual traffic processed by a server's or workstation's OS. This is highly valuable because:\n* It allows tracking traffic and interface errors regardless of the upstream network topology.\n* It does not conflict with or affect switch metrics. Computer network ports and switch network ports remain separate entities in the database, meaning each retains its own independent telemetry data.\n\nProposed Solution:\nThe inventory format already technically allows a NETWORK_PORTS section in the schema. I propose updating GLPI's server-side inventory logic to process this section for Computer assets, mapping the metrics to their respective NetworkCard and NetworkPort records by correlating MAC addresses and interface names.\n\nA working proposed solution for GLPI is available here:\n👉\n\nCompanion Agent Implementation:\nTo collect and send this data, the GLPI-Agent also requires an update. The implementation for the agent is proposed here:\n👉\n\n---\n\n⚠️ Important Backward Compatibility Notice:\nWhile sending NETWORK_PORTS for computers is valid according to the inventory schema, older versions of GLPI do not expect to receive this data for non-NetworkEquipment assets.\n\nIf an updated agent sends this payload to a current/older GLPI server, GLPI throws a fatal 500 error:\n\n*(A similar error also occurs with isStackedSwitch() when processing this section).*\n\nBecause of this limitation in older GLPI versions, the GLPI-Agent (in PR glpi-project/glpi-agent#1184) will need to perform a version check and only transmit the NETWORK_PORTS payload to GLPI versions that include the feature proposed in PR #24508.\n\nFeedback:\nI would love to hear the maintainers' thoughts on this feature and the proposed implementation.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24509, "url": "https://github.com/glpi-project/glpi/issues/24509", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-08T18:31:24Z", "updatedAt": "2026-06-08T18:35:13Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Closing Ticket", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nThe automatic action \"closeticket\" is not calculating times right when you have a calendar with Time Ranges.\nThe only way for the action to work is removing Time Ranges of calendar.\n\nReproduction steps:\nCreate 2 types of calendars, where one you fill the Time Ranges and other you don't\nSetup your Assistance Tab in Entities section:\nAutomatic Closing Configuration\n\"Automatic closing of solved tickets after\"\nTicket Configuration\n\"Calendar\" - Select the one with Time Ranges\nTest with a ticket and solve it\nEnforce automatic action with both calendars.", "priority": "medium", "type": "support", "createdByEmail": "robin.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24489, "url": "https://github.com/glpi-project/glpi/issues/24489", "author": "joao-panao", "anonymizedAuthorEmail": "robin.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-05T11:18:49Z", "updatedAt": "2026-06-05T11:18:49Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI 11 PHP exception on translated asset types (custom asset definitions)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen using a custom asset definition with asset types that has translation (in our case english to german) opening the asset definition in the left side menu ends in an PHP exception when using said translation as system language.\n\nAffected page:\n\nReproduction steps:\n1. Set system language to english\n2. create asset definition\n3. create dropdown > asset type for this asset definition\n4. add translation to the asset type (for example german)\n5. set system language to german (or selected translation)\n6. try to open asset definition on left side menu", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24479, "url": "https://github.com/glpi-project/glpi/issues/24479", "author": "whoiswhoami", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-04T12:52:08Z", "updatedAt": "2026-06-04T12:56:03Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Error on anonymous/public forms related to notification enable", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nglpi 11.0.7\n\nIssue description:\nHello,\n\nI'm using forms accessible in anonymous mode. When browser notifications are enabled in GLPI, I get an error message when I start filling out the form, and I can't submit it afterward. If I disable browser notifications in GLPI or block/refuse notifications from my Chrome browser, everything works.\n\n[Image omitted]\n\nReproduction steps:\n1. Created a form accessible anonymously.\n2. Enabled browser notifications in GLPI.\n3. Tried accessing the anonymous form in private browsing mode.\n4. Allowed/Accepted the notification permission message in my browser.\n5. Filled out the form, and the message appeared.\n6. The form's submit button doesn't work.\n\nEnvironment details:\nI'm using the Chrome browser.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24470, "url": "https://github.com/glpi-project/glpi/issues/24470", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-03T21:05:04Z", "updatedAt": "2026-06-03T21:06:50Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Clear inventory file when asset definition is deleted", "detail": "Issue description:\nSee", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24410, "url": "https://github.com/glpi-project/glpi/issues/24410", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-06-01T09:34:47Z", "updatedAt": "2026-06-01T09:35:02Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Update fails with Safe\\flock() when GLPI_TMP_DIR is on NFS PVC (prod/staging only)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWe consistently hit the same crash during every GLPI update in production/staging environments where files are mounted on an NFS-backed PVC.\n\nThis is not an intermittent issue for us: it has happened in all update attempts in these environments.\n\nThe failure happens in progress storage file locking (flock) and aborts the update flow.\n\nReproduction steps:\nDeploy GLPI in Kubernetes.\nMount GLPI runtime files/temp path on an NFS-backed PVC.\nExecute a GLPI update.\nDuring progress checks, GLPI throws the Safe\\flock() exception and update fails.\n\nEnvironment details:\nKubernetes deployment\nPHP 8.3\nProduction/Staging:\nfiles (including runtime temp path) on NFS PVC\nmultiple replicas/pods may access shared storage\nDevelopment:\ndoes not reproduce (different storage backend, no NFS for runtime temp)\n\nGLPI information\nGLPI: 11.0.7 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: pt_BR\nSource Integrity: OK\n\nServer\nOperating system: Linux k0669-hom-glpi-5bcccc97bd-xfz22 4.18.0-553.124.4.el8_10.x86_64 #​1 SMP Fri May 15 04:14:14 EDT 2026 x86_64\n\nPHP: 8.3.24 fpm-fcgi\n\nPHP extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, ctype, curl, dom, fileinfo, filter, hash, iconv, json, mbstring, SPL, session, PDO, pdo_sqlite, bz2, posix, random, readline, Reflection, standard, SimpleXML, tokenizer, xml, xmlreader, xmlwriter, mysqlnd, cgi-fcgi, oneagentphp, bcmath, Phar, exif, gd, imap, intl, ldap, mysqli, pdo_mysql, redis, sodium, zip, ionCube Loader, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"600\" max_input_vars=\"5000\" memory_limit=\"1024M\" post_max_size=\"100M\" session.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"Strict\" session.save_handler=\"files\" upload_max_filesize=\"100M\"\n\nWeb server: nginx/1.27.5 ()\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 Edg/148.0.0.0\n\nDatabase:\n\nServer Software: MariaDB Server\n\nServer Version: 10.6.20-MariaDB-log\n\nServer SQL Mode: STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: [email redacted]/k0669_hom_glpi\n\nHost info: s1915.ms via TCP/IP\n\nRequirements:\nPHP version (8.3.24) is supported.PHP version (8.3.24) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader, xmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (10.6.20) is supported.Database engine version (10.6.20) is supported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated. Write access to /var/www/html/glpi/files/_cron has been validated. Write access to /var/www/html/glpi/files has been validated. Write access to /var/www/html/glpi/files/_graphs has been validated. Write access to /var/www/html/glpi/files/_lock has been validated. Write access to /var/www/html/glpi/files/_pictures has been validated. Write access to /var/www/html/glpi/files/_plugins has been validated. Write access to /var/www/html/glpi/files/_rss has been validated. Write access to /var/www/html/glpi/files/_sessions has been validated. Write access to /var/www/html/glpi/files/_tmp has been validated. Write access to /var/www/html/glpi/files/_uploads has been validated.Write access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2, Phar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed: ctype, iconv, sodium.\nWrite access to /var/www/html/glpi/marketplace has been validated.Write access to /var/www/html/glpi/marketpl\n\n[Content truncated.]\n\nAdditional context:\nExpected Behavior\nGLPI update should complete without crashing, even when running on NFS-backed shared storage, or provide a robust fallback/clear diagnostic if advisory locks a\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24349, "url": "https://github.com/glpi-project/glpi/issues/24349", "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-27T18:58:53Z", "updatedAt": "2026-05-31T00:05:37Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Disassociating item from Network Name form redirects to the old item, not Network Name", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0/bugfixes\n\nIssue description:\nClicking the \"Disassociate\" button in the main Network Name form to disconnect the item results in GLPI sending the user to the old item's form instead of back to the Network Name form.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24406, "url": "https://github.com/glpi-project/glpi/issues/24406", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "open", "stateReason": null, "createdAt": "2026-05-30T23:02:29Z", "updatedAt": "2026-05-30T23:02:29Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Namespaced RuleCollection classes break Massive Actions UI (\"No selected items\" error)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI: 11.0.7 ( => /var/www/glpi-dev_quinquies_nl) Installation mode: TARBALL Current language: en_GB Source Integrity: OK\n\nIssue description:\nWhen using a namespaced RuleCollection subclass (typical for all GLPI 10.0+ / 11.0+ plugins following modern PSR-4 namespacing standards), checking rules in the rules list view and clicking Actions fails with a \"No selected items\" warning modal. This prevents massive actions (like deleting or activating rules) from being executed.\n\nReproduction steps:\n1. Create a plugin with a namespaced rule collection class, e.g. \\GlpiPlugin\\Myplugin\\RuleMypluginCollection.\n2. Go to the rules list page in the GLPI administration panel.\n3. Check the checkbox next to any rule.\n4. Click on the Actions dropdown or button at the bottom of the table.\n5. A modal stating \"No selected items\" is displayed, even though rules were checked.\n\n---\n\nRoot Cause Analysis:\nIn the GLPI core file src/RuleCollection.php, the HTML container ID for the massive actions checkboxes is generated using static::class (which leverages Late Static Binding):\n\nsrc/RuleCollection.php (L627-L635)\n\nBecause the plugin is properly namespaced, static::class resolves to GlpiPlugin\\Myplugin\\RuleMypluginCollection, resulting in an HTML ID containing backslashes (e.g., id=\"massGlpiPlugin\\Myplugin\\RuleMypluginCollection123456\").\n\nIn the template templates/components/datatable.html.twig, this container ID is passed directly to Javascript:\n\ntemplates/components/datatable.html.twig (L162)\n\nWhen GLPI's massive action Javascript or jQuery runs selectors on this ID (e.g., $('#' + container)), it fails because backslashes (\\) are interpreted by jQuery and CSS selectors as escape characters. As a result, the element is not found, and jQuery determines that 0 items are selected.\n\n---\n\nSuggested Fix:\nThe backslashes in namespaced class names must be sanitized (e.g., replaced with underscores) before using them as HTML ID attributes.\n\nModify the container key generation in src/RuleCollection.php:", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24400, "url": "https://github.com/glpi-project/glpi/issues/24400", "author": "DonutsNL", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-29T20:52:05Z", "updatedAt": "2026-05-29T20:52:57Z", "closedAt": null } }, { "title": "Template pre-filled value are not applied with the new helpdesk/service catalog form", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI created a template for a ticket with a pre-fill field (description).\nWhen I use the new ticket form in my admin interface, and choose the related category it works fine. The forms is refreshed and the description content appears.\nIf I use the service catalog, and new demand forms, it doesn't work. The description field is empty when I choose the category. Nothing happens.\nThank you in advance.\n\nAffected page:\n/Helpdesk\n\nReproduction steps:\nNew template associated with a category\nPre-filled value. Add description field, and enter a content.\nUse the helpdesk page, with the new ask form.\nSelect the category and enjoy.\n\nAdditional context:\nCongratulation for your work!", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24384, "url": "https://github.com/glpi-project/glpi/issues/24384", "author": "yberteaux", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-29T07:19:55Z", "updatedAt": "2026-05-29T07:19:55Z", "closedAt": null } }, { "title": "Satisfaction Survey Should Follow Ticket Timeline Order Configuration", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nDescription:\nCurrently, when configuring the ticket timeline display order as reverse chronological order, the Satisfaction Survey section still remains fixed at the end of the timeline instead of following the configured order.\n\nThis behavior causes many end users to overlook or forget the satisfaction survey, since it becomes hidden after all ticket activities and updates.\n\nExpected behavior:\nThe Satisfaction Survey should respect the same timeline ordering configuration applied to the ticket timeline, appearing according to the selected chronological order.\n\nAlternative suggestion:\nProvide a dedicated configuration option under Setup > Default values (or similar settings area) allowing administrators to define the position of the Satisfaction Survey within the ticket timeline, for example:\n\nTop of timeline\nBottom of timeline\nFollow timeline order automatically\n\nThis would improve visibility and increase the likelihood of users completing the satisfaction survey.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24376, "url": "https://github.com/glpi-project/glpi/issues/24376", "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-28T15:10:01Z", "updatedAt": "2026-05-28T15:10:01Z", "closedAt": null } }, { "title": "KB Comments Timeline Line Exceeds Avatar and Overlaps Edit/Reply Forms", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nIn GLPI's Knowledge Base (KB), when a user opens the Reply form or Edit form on a comment, the vertical timeline line (.comments::before and ul::before) exceeds its expected bounds. Instead of terminating neatly at the last comment's avatar, it draws straight down through the avatar and enters the newly opened form container, creating a broken and cluttered UI layout.\n\n[Image omitted]\n\nActual Behavior\n\n- Vertical Line Overflow: The vertical timeline line goes straight down past the last active avatar, slicing through the avatar of the reply/edit form and extending deep into the light grey form card.\n- Toggle Misalignment: When a comment is being edited, the [-] (collapse/expand toggle) for its subcomments stays fixed near the top of the enlarged edit form rather than aligning dynamically right above the second comment/subcomment.\n- Collapsed Line Break: When the toggle is collapsed (not(:checked)), the ... pseudo-element breaks the timeline line unexpectedly on smaller screens.\n\nAffected page:\n/front/knowbaseitem.form.php\n\nReproduction steps:\n1. Navigate to Tools > Knowledge Base and select any article with comments.\n2. In the comments section:\n- Click the Reply icon (arrow) on a comment, OR\n- Click the Edit icon (pencil) on an existing comment.\n3. Observe the vertical grey timeline line on the left.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24320, "url": "https://github.com/glpi-project/glpi/issues/24320", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-27T00:32:00Z", "updatedAt": "2026-05-27T00:35:39Z", "closedAt": null } }, { "title": "Socket dropdown in Cable form not populated on Asset change when Socket model is not set", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nThe \"Socket\" dropdown in Cable form (/front/cable.form.php?id=1) for both endpoints seems to stay empty: it .does not get populated with asset's Sockets.\n\nAffected page:\n\nReproduction steps:\n1. With a computer \"computer1\" having a socket \"Ethernet\" of model \"RJ45\"\n1. Go to Assets > Cable > Add (/front/cable.form.php?id=-1)\n1. Under Endpoint A (or B):\n 1. Select \"Computers\" in Asset dropdown\n 1. Select \"computer1\" in sub-dropdown\n 1. Select \"RJ45\" in Socket model dropdown\n\n\"Socket\" dropdown is empty, while it should list \"Ethernet\".\n\nWorkarounds:\n\n* Two-steps save:\n 1. Save the form without selecting \"Socket\".\n 1. On the refreshed page, the \"Socket\" dropdown now lists the \"Ethernet\" Socket.\n 1. Select \"Ethernet\" in Socket dropdown\n 1. Save the form.\n* Change form-filling order:\n 1. With a computer \"computer1\" having a socket \"Ethernet\" of model \"RJ45\"\n 1. Go to Assets > Cable > Add (/front/cable.form.php?id=-1)\n 1. Under Endpoint A (or B)\n 1. Select \"RJ45\" in Socket model dropdown\n 1. Select \"Computers\" in Asset dropdown\n 1. Select \"computer1\" in sub-dropdown\n The \"Socket\" dropdown will be populated with the \"Ethernet\" Socket.\n\nAdditional context:\nI guess the SQL query to fetch Asset's Socket uses the \"Socket model\" field to filter obtained Sockets.\n\nChanging the \"Socket model\" field does not trigger a new \"Socket\" field populating, only changing the \"Asset\" field does it.", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24277, "url": "https://github.com/glpi-project/glpi/issues/24277", "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-21T18:25:52Z", "updatedAt": "2026-05-21T20:49:26Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Plugin update issue after GLPI 10 → 11 migration", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nHello,\n\nI recently migrated from GLPI 10 to GLPI 11 and I'm experiencing an issue with plugin updates.\n\nEnvironment:\n\nGLPI 10 → 11 migration completed\n\nAll plugins show \"To update\" status in the interface\n\nPlugin files are up to date (e.g., activity plugin shows version 3.2.7 in setup.php)\n\nWhat I have done:\n\nphp bin/console marketplace:upgrade → downloads OK\n\nphp bin/console plugin:install activity --force → \"installed and can be activated\"\n\nphp bin/console plugin:activate activity → \"activated\"\n\nphp bin/console plugin:list shows the correct version (3.2.7) and \"Activated\"\n\nThe problem:\nAfter a few seconds (or minutes), the version reverts to the old one (3.2.6) and the status goes back to \"To update\". This happens even after:\n\nDisabling all crons\n\nAdding define('GLPI_SYSTEM_CRON', false); in inc/downstream.php\n\nClearing all caches (Memcached via cPanel, OPcache via GLPI Performance page)\n\nVerifying no triggers or events exist in the database\n\nThe database contains the correct version (3.2.7) with state = 1, but php bin/console plugin:list keeps showing the old version (3.2.6).\n\nAdditional info:\n\nRunning on O2switch hosting\n\nPHP 8.2\n\nMemcached and OPcache are enabled\n\nWhat could be forcing this automatic rollback? Any help would be greatly appreciated.\n\nThank you.", "priority": "medium", "type": "support", "createdByEmail": "logan.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24275, "url": "https://github.com/glpi-project/glpi/issues/24275", "author": "informatiquemagny78114-sys", "anonymizedAuthorEmail": "logan.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-21T14:47:10Z", "updatedAt": "2026-05-21T14:47:10Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Add entity field in event planning form", "detail": "Contribution description:\nIn this PR we have the code to add an entity field in planning form.\nThis field follows all the necessary rules to prevent the user from selecting an unauthorized entity.\nThe form is also updated when the field value changes to reflect the changes in other fields.", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24244, "url": "https://github.com/glpi-project/glpi/issues/24244", "author": "Axel35000-tech", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-18T10:35:01Z", "updatedAt": "2026-05-18T10:35:01Z", "closedAt": null } }, { "title": "Can not template child entities for ITILObjects", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nThe field child entities can not be templated for ITILObjects.\nIt appears to be related to .\n\nThis affects the use of child entities as changes and problems can not be made to automatically apply to all sub entities.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24239, "url": "https://github.com/glpi-project/glpi/issues/24239", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-18T08:33:06Z", "updatedAt": "2026-05-18T08:33:22Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "ProjectTask: autoSetDate() overwrites manually entered effective_duration when real dates are set", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen a project task has both real_start_date and real_end_date defined,\n the autoSetDate() method in ProjectTask.php automatically overwrites\n effective_duration with the raw calendar difference between the two\n timestamps (in seconds), regardless of any value the user manually entered\n in the \"Effective duration\" field.\n\n ## Steps to reproduce\n\n 1. Create a project task with a real start and end date set.\n 2. Manually enter a value in the \"Effective duration\" field (e.g. 8 hours).\n 3. Save the task.\n 4. Reopen the task — \"Effective duration\" shows the calendar diff between\n dates (e.g. 3 days if the dates span a weekend), not the 8 hours entered.\n 5. The project's \"Total Duration\" reflects the wrong value.\n\n ## Expected behavior\n\n If the user explicitly submits a value for effective_duration, it should\n be respected. The auto-calculation from dates should only apply when the\n field is left empty.\n\n ## Actual behavior\n\n autoSetDate() unconditionally overwrites effective_duration:\n\nshell", "priority": "medium", "type": "support", "createdByEmail": "devon.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24234, "url": "https://github.com/glpi-project/glpi/issues/24234", "author": "giovanny07", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-15T17:13:51Z", "updatedAt": "2026-05-15T17:13:51Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "recurring ticket creation error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.25\n\nIssue description:\nHello team, I hope you are all doing well.\n\nSince update 10.0.25 I have noticed an error in the creation of recurring tickets in our configuration, as they are being created when they shouldn't be, sharing the following screenshots:\n\n[Image omitted]\n[Image omitted]\n\n---------------------------------------------------------------------------------------------\n\n[Image omitted]\n[Image omitted]\n\nThe GLPI update in production was carried out on Saturday, which is why these two anomalies were detected this week. There are currently 28 recurring tickets, which are created on different days and at different times. Before the update, the creation of recurring incidents was managed correctly.\n\nRegards!\n\nAdditional context:\nmigration from 10.0.22 => 10.0.25", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24220, "url": "https://github.com/glpi-project/glpi/issues/24220", "author": "german-giraldom", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-13T20:52:23Z", "updatedAt": "2026-05-13T20:53:35Z", "closedAt": null } }, { "title": "[HLAPI] Context-aware data fetching", "detail": "Contribution description:\nI have been trying to come up with ideas for specs for context-aware data fetching in the High-Level API for a while now without being able to fully settle on any specifics, so I am looking for other people's opinions/suggestions to try to unblock this as it may be required for an official client using the HLAPI and makes it easier for non-official API uses to submit correct/expected data.\n\nA little background,\nIn GLPI we have resource-level permissions like READ for Users. A self-service user has no permission to read users normally, but they are able to see them as options in a dropdown in some circumstances. Additionally, specific contexts like the actor fields in a ticket require additional filtering like only showing users that could be assigned to the ticket.\n\nCurrently, when calling /Administration/User or GraphQL User query, only the READ permission and entity restrictions are taken into account. There are no exceptions for a dropdown context.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24218, "url": "https://github.com/glpi-project/glpi/issues/24218", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "api", "help wanted" ], "state": "open", "stateReason": null, "createdAt": "2026-05-13T13:29:43Z", "updatedAt": "2026-05-13T13:29:43Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Forms ITIL category selection shows ITIL categories from all entities (regression?)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nDescription\nSince upgrading to GLPI 11, category selection in forms no longer respects entity boundaries.\n\nContext\nUsing entities with separate ITIL categories\nForms are assigned to specific entities\nPreviously (with GLPI + Forms plugin), forms only displayed ITIL categories belonging to their own entity\nCurrent behavior\n\nWhen creating or submitting a form, the category selection field displays all ITIL categories from all entities, instead of being restricted to the form’s entity.\n\nExpected behavior\nForms should only display ITIL categories associated with the same entity as the form (as in previous versions).\n\nSteps to reproduce\nCreate multiple entities\nDefine different ITIL categories for each entity\nCreate a form assigned to one entity\nOpen the form and check the category dropdown\n\nImpact\nConfusing for users (too many irrelevant categories)\nRisk of assigning tickets to incorrect categories/entities\n\nThis behavior looks like a regression compared to earlier versions with the Forms plugin\n\nQuestion\nIs this an intended change in GLPI 11, or a bug/regression?\nOr I make it wrong ?\n\nBest regards", "priority": "medium", "type": "support", "createdByEmail": "micah.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24150, "url": "https://github.com/glpi-project/glpi/issues/24150", "author": "dsiens", "anonymizedAuthorEmail": "micah.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-06T09:17:40Z", "updatedAt": "2026-05-06T10:05:57Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Flaky E2E test", "detail": "Issue description:\n2. [chromium] › tests/e2e/specs/Knowbase/translations.spec.ts:73:5 › Can create a new translation\n\n Error: expect(locator).toHaveText(expected) failed\n\n Locator: getByTestId('subject')\n Expected: \"Article Traduisible\"\n Received: \"ticle TraduisibleTranslatable Article\"\n Timeout: 5000ms\n\n Call log:\n - Expect \"toHaveText\" with timeout 5000ms\n - waiting for getByTestId('subject')\n 9 × locator resolved to ticle TraduisibleTranslatable Article\n - unexpected value \"ticle TraduisibleTranslatable Article\"\n\n 114 | // Verify saved content is displayed\n 115 | await expect(page.getByTestId('content')).toContainText('Contenu en français');\n > 116 | await expect(subject).toHaveText('Article Traduisible');\n | ^\n 117 | });\n 118 |\n 119 | test('Can switch between languages in translation mode', async ({ page, profile, api }) => {\n at /app/tests/e2e/specs/Knowbase/translations.spec.ts:116:27\n\n Error Context: tests/e2e/output/Knowbase-translations-Can-create-a-new-translation-chromium/error-context.md", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24004, "url": "https://github.com/glpi-project/glpi/issues/24004", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-24T12:09:47Z", "updatedAt": "2026-05-06T07:34:11Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "Duplicate search entries in Knowledge Base tree view keep increasing", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6 (also 11.0.7, earlier versions unknown)\n\nIssue description:\n[Image omitted]\n\n- In Knowledge Base Browse (Tree view), clicking the filter button initially shows two filter fields.\n- After executing a search, a third filter field appears.\n- This issue does not occur in List view.\n\nAffected page:\n/front/knowbaseitem.php\n\nReproduction steps:\n- The issue occurs during normal operation, as described in the bug description.\n- This behavior also occurs on a clean installation.", "priority": "medium", "type": "support", "createdByEmail": "robin.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24090, "url": "https://github.com/glpi-project/glpi/issues/24090", "author": "masakazuwatanabe", "anonymizedAuthorEmail": "robin.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-05-01T10:14:42Z", "updatedAt": "2026-05-01T10:21:04Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "SMTP: EHLO sends [127.0.0.1] instead of server hostname (Symfony Mailer local_domain not set)", "detail": "Summary:\nWhen GLPI is deployed in Docker or behind NAT, Symfony Mailer sends EHLO [127.0.0.1] instead of a proper hostname. Strict SMTP relays (e.g. Google Workspace smtp-relay.gmail.com) reject the connection with:\n\nReproduction steps:\n1. Deploy GLPI in Docker (container hostname = random hash or internal IP)\n2. Configure SMTP: smtp-relay.gmail.com:587 (TLS, no credentials — IP-authenticated relay)\n3. Send a test email\n4. Observe connection rejected at EHLO stage\n\nExpected behavior:\nGLPI sends EHLO glpi.example.com (the hostname from url_base config).\n\nRoot cause:\nGLPIMailer::buildDsn() builds the Symfony Mailer DSN string but never sets the local_domain query parameter. Symfony's EsmtpTransport defaults to [127.0.0.1] when no local domain is configured (see symfony/symfony#37300).\n\nProposed fix:\nAdd local_domain to the DSN, derived from $CFG_GLPI['url_base'] (with gethostname() fallback), in src/GLPIMailer.php:\n\nThis fix also cleans up the existing verify_peer logic by collecting all query params before appending them.\n\nEnvironment:\n- GLPI 11.0.6\n- Docker deployment\n- Google Workspace SMTP relay (smtp-relay.gmail.com:587)\n- Symfony Mailer (via GLPI's GLPIMailer class)", "priority": "medium", "type": "support", "createdByEmail": "noel.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 24016, "url": "https://github.com/glpi-project/glpi/issues/24016", "author": "pisarz77", "anonymizedAuthorEmail": "noel.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-26T12:31:35Z", "updatedAt": "2026-04-26T12:31:35Z", "closedAt": null } }, { "title": "[LDAP] Massive action \"sync\" fails silently when authldaps_id is missing from request", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.5\n\nIssue description:\nWhen performing a massive action to synchronize users from Administration > Users,\nthe action fails because the authldaps_id parameter is not included in the request.\n\nExpected behavior: The synchronization should work when only one LDAP server is configured,\nautomatically using it without requiring the parameter to be explicitly passed.\n\nActual behavior: The action fails silently — users disappear from the list\nwithout any error message. The system switches automatically between\n\"Synchronize already imported users\" and \"Import new users\" modes.\n\nRoot cause: In src/AuthLDAP.php, the processMassiveActionsForOneItemtype() method\naccesses $_REQUEST['authldaps_id'] directly without checking if it exists:\n\\\n\nAffected page:\n/front/massiveaction.php\n\nReproduction steps:\n1. Have at least one LDAP server configured (Administration > Authentication > LDAP)\n2. Go to Administration > Users\n3. Select multiple users that were imported from LDAP\n4. In the massive action dropdown, select \"Synchronize\"\n5. Confirm the action\n\nAdditional context:\nSuggested fix: Check if authldaps_id is present in the request.\nIf not, and only one LDPI server is configured, use it automatically:\n\n\\\n\nTested and confirmed working on GLPI 11.0.5.", "priority": "medium", "type": "support", "createdByEmail": "casey.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23989, "url": "https://github.com/glpi-project/glpi/issues/23989", "author": "RobyellMartins", "anonymizedAuthorEmail": "casey.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-22T14:48:15Z", "updatedAt": "2026-04-22T14:48:15Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "The ‘Actions’ feature under Assets > Computers allows licenses to be added improperly", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.24\n\nIssue description:\nWhile testing the license creation process, I noticed the following:\n\nWhen you create a license and set its connection limit, if you add computers one at a time within the license itself > Items, once the limit is reached, the Add button disappears so the user can’t add any more.\n\nBut if you select the list of all active computers, click Actions > Add License, and choose the same license, it allows you to add computers, even if the license is already close to its limit.\n\nI believe this must be a bug; it should either block the addition because the limit has been exceeded or allow adding only a portion from the list (if there are still available license slots).\n\nEnvironment details:\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23963, "url": "https://github.com/glpi-project/glpi/issues/23963", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-19T16:16:38Z", "updatedAt": "2026-04-19T16:16:38Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Encryption issue on upgrade from 10.0.7 to 11.0.6 - glpicrypt.key - symfony bug", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nUpgrading from 10.0.7 to 11.0.6 shows unexpected error and progress incomplete progress, but after the screen shows that the system has been upgraded to 11.0.6\n\nApplication cannot be used after upgrade. Tried it two times, same outcome.\n(second time with all plugins disabled)\n\nThe string shown in the output error is part of the key string from the glpicryp.key file. (K_–²A•}¶Ö)\n\nIf i try to access the application after the failed installation, i get the symfony parameter bug error, related to the glpicrypt file\n\nAffected page:\n/install/update.php\n\nReproduction steps:\n- unpacked glpi 11.0.6 to project root\n- copied config, files, marketplace, plugins dirs from old application (10.0.7) to the new one\n- copied the database\n- - prepared the database connection\n- accessed the application where the upgrade page was loaded with no warning\n- everything goes well up to Update to 11.0.6 version completed message\n- right afte the upgarde completed message i get An unexpected error occurred\n\n[Image omitted]\n\nSource Sever:\n==============================\n\n==============================\n\nDestination server:\n=========================================\n\n=========================================\n\nAdditional context:\nI had to remove the source cryptkey altogether to make it work - that implies resetting all credentials, LDAP included.", "priority": "medium", "type": "support", "createdByEmail": "emerson.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23757, "url": "https://github.com/glpi-project/glpi/issues/23757", "author": "valentindragan", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-02T20:10:58Z", "updatedAt": "2026-04-17T13:31:17Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Custom Asset Definitions: Items search on Ticket/Change does not search recursively in child entities", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nCustom asset types (Asset Definitions) are not searchable recursively from parent entities when linking Items to Tickets or Changes. Standard asset types (Computer, Monitor, etc.) work correctly with recursive entity search.\n\nExpected behavior\nCustom assets should be searchable from parent entity with recursive view, same as standard asset types (Computer, Network Equipment, etc.).\n\nActual behavior\nFrom root entity: search field is disabled/greyed out, no results\nFrom child entity (where assets are saved): search works, assets appear\nCreating a Ticket/Change from the asset's own tab (e.g. Cloud VM > Changes > \"New Change for this item\") works correctly and links the item\nAdditional context\nStandard asset types work recursively from any parent entity\nAll profile permissions (Super-Admin) are set with full rights on the custom asset definition\nAsset list view (Assets > Cloud VM) correctly shows assets recursively\n\nReproduction steps:\nCreate a Custom Asset Definition (e.g. \"Cloud VM\") with all capacities and profile permissions enabled\nCreate custom assets in a child entity (e.g. \"Root > Public Cloud Customers > tenant1\")\nSwitch to root entity with \"tree structure\" view\nVerify: Assets > Cloud VM list shows all assets from child entities (recursive works here)\nCreate or edit a Ticket or Change > Items section > select \"Cloud VM\" from type dropdown\nSearch field is greyed out / disabled — cannot search or select any custom asset", "priority": "medium", "type": "support", "createdByEmail": "avery.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23949, "url": "https://github.com/glpi-project/glpi/issues/23949", "author": "mciobanu1", "anonymizedAuthorEmail": "avery.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-17T08:38:51Z", "updatedAt": "2026-04-17T08:38:51Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Add target on ITIL templates", "detail": "Contribution description:\nThis feature is to add target on ITIL template. Only are concerned : ITILFollowup Template, TaskTemplate, SolutionTemplate.\nYou can add several target (Entity, group, users, profil). Each can be restricted on only one entity on much more with the recusive fields.\nYou can see the code here", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23813, "url": "https://github.com/glpi-project/glpi/issues/23813", "author": "Axel35000-tech", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-09T06:53:51Z", "updatedAt": "2026-04-09T06:53:51Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "[Native Forms] Hidden questions are included in ticket description when \"Auto config\" is disabled", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen using native forms in GLPI 11.0.6, if \"automatic configuration\" is disabled in ticket destinations, sections and questions that were hidden in the form are inserted into the ticket description. However, when using automatic configuration, the conditions of the hidden items are respected.\n\nIn GLPI 10, using the Form Builder, questions and sections remained hidden when opening the ticket, even without using the \"FULL FORM\" option.\n\nReproduction steps:\n1. Create a form with 2 sections. In Section 1, add a conditional question. In Section 2, add any question and configure the display of Section 2 according to the conditional question of Section 1.\n\n2. In \"Destinations\", add another ticket and disable \"Auto config\" and save the changes. Keep two tickets in the destination with auto config enabled in one and disabled in the other.\n\n3. Submit the new form keeping Section 2 hidden.\n\n4. Open the generated tickets and check the difference in the description.\n\nExpected behavior:\nOnly questions that received an answer should appear in the ticket description. Unanswered questions should be omitted, following the FormCreator behavior in GLPI 10.\n\nCurrent Behavior:\nAll questions are listed in the ticket description, including those with empty answers. In a lengthy form, this makes it difficult to understand and organize the ticket.\n\nEnvironment:\n- GLPI Version: 11.0.6\n- PHP Version: (8.3.6)\n- Operating System: Ubuntu 24.04\n- Database: (MariaDB 10.11)", "priority": "medium", "type": "support", "createdByEmail": "elliot.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23788, "url": "https://github.com/glpi-project/glpi/issues/23788", "author": "almeidaddiego", "anonymizedAuthorEmail": "elliot.adler@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "open", "stateReason": null, "createdAt": "2026-04-07T18:41:37Z", "updatedAt": "2026-04-07T20:25:33Z", "closedAt": null } }, { "title": "Custom notification tag not handled or displayed", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nI want to add new notifications tags to be used in templates. To avoid \"touching directly\" the code i build a plugin. The tag is not handled when used in a template and not displayed in the list of tags.\n\nReproduction steps:\n1. Create a new empty plugin\n2. Add these functions in the hook.php:\n\n3. Add this in setup.php:\n\n4. Install and enable the plugin then open the notification templates page.", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23692, "url": "https://github.com/glpi-project/glpi/issues/23692", "author": "Asmitta-01", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-31T10:46:48Z", "updatedAt": "2026-04-07T11:29:39Z", "closedAt": null } }, { "title": "Flatpickr start time picker ignores \"Step for the hours\" setting (regression from 10.x)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello GLPI team!\n\nBug Report:\nVersion: 11.0.6\n\nIssue description:\nWhen planning a task, the duration dropdown correctly uses the configured step (e.g. 30min intervals). However, the start time picker (flatpickr) always uses 5-minute steps, ignoring the \"Step for the hours (in minutes)\" setting (Setup → General → Assistance).\n\nThis is a regression from GLPI 10.x. In GLPI 10, Html::showDateTimeField() passed minuteIncrement to flatpickr using $CFG_GLPI['time_step'] (see src/Html.php around line 2995):\n\nIn GLPI 11, datetime rendering was migrated from PHP to the Twig date macro in templates/components/form/basic_inputs_macros.html.twig. The minuteIncrement property was not carried over, flatpickr defaults to 5.\n\nAffected: All datetime pickers rendered via the Twig date/datetime macro (e.g. task planning start time).\n\nNot affected: Datetime pickers still rendered via Html::showDateTimeField() in PHP (these still work correctly).\n\nFix:\nAdd one line in templates/components/form/basic_inputs_macros.html.twig, in the flatpickr init block after enableSeconds:\n\nThe config('time_step') function is already used elsewhere in GLPI 11 Twig templates (e.g. config('use_notifications') in the same file).\n\nBest Regards,\nBoris\n\nAffected page:\nAny page with a datetime picker rendered via Twig, e.g. Ticket → Add Task → Plan this task → Start date picker.\n\nReproduction steps:\n1. Set Setup → General → Assistance → \"Step for the hours\" to 30\n2. Open a ticket, add a task, click \"Plan this task\"\n3. Open the start date picker and use the time arrows\n4. Expected: 30-minute increments\n5. Actual: 5-minute increments", "priority": "medium", "type": "support", "createdByEmail": "kendall.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23766, "url": "https://github.com/glpi-project/glpi/issues/23766", "author": "b-o-r-i-s975", "anonymizedAuthorEmail": "kendall.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-03T23:31:17Z", "updatedAt": "2026-04-07T08:51:35Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Add target on private saved search", "detail": "Contribution description:\nOn private saved search, the goal is to add target (user and/or group) to share a saved search whith retricted acces.\nThis feature is to add a step between public saved search (can see by everybody) and a private saved search (can see only by yourself).\nYou can see the code on PR", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23764, "url": "https://github.com/glpi-project/glpi/issues/23764", "author": "Axel35000-tech", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-04-03T13:41:52Z", "updatedAt": "2026-04-03T13:42:04Z", "closedAt": null } }, { "title": "Metadata filtering for GLPI objects", "detail": "Contribution description:\nWhen using a field of the type \"GLPI Objects\", the system currently lists all records or offers basic hierarchical filters (like the Subtree root found in Dropdowns). However, there is no way to restrict the selection based on specific attributes of that object.\n\nWhen adding a \"Supplier\" field to a form, I would like to be able to configure a filter so that only suppliers with a registered _Administrative number_ are displayed to the user, or perhaps filter by a specific email.\n\nSomething like we have when the specified filter is configured as dropdown\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23562, "url": "https://github.com/glpi-project/glpi/issues/23562", "author": "Killink61", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "open", "stateReason": null, "createdAt": "2026-03-20T15:42:03Z", "updatedAt": "2026-04-01T12:04:12Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Impact Analysis Rewrite", "detail": "Contribution description:\nThis may upset some, but there are several clear issues with the current state of Impact Analysis which justify a rewrite. In addition to the technical reasons, Impact is over 6 years years old now so there should have been significant improvement in technical skill since then. I think we can do better now.\n\nThe issues identified:\n- Lack of standard permission management. This is blocking access via the legacy API and the HLAPI.\n- The database layout is not really correct. The “parent_id” column should be named “impactcompounds_id” to match GLPI standards for example.\n- ImpactItem should extend CommonDBChild, not CommonDBTM directly, so it can use the correct permissions from the parent item.\n- Very complex/long JavaScript. There are nearly 4400 lines in direct echos in the PHP code in “js/impact.js”. By comparison the workflows plugin, which has far more complexity and functionality in its workflow editor, has just 4089 lines of JavaScript so far.\n- Performance issues when panning or zooming fast. This seems to be a Cytoscape issue.\n- Clicking a node, rather than dragging between nodes, while in edge creation mode causes a TypeError.\n- Missing undo/redo stack actions and removal of actions? Added and then removed a custom asset from the graph. Clicked undo which properly re-added it. Notice redo button is disabled. Clicking undo again throws error \"Can not create second element with ID [...]\".\n- HTML elements echos directly from PHP code instead of Twig templates.\n\nFor GLPI 11:\n- Attempt to resolve lack of standard permissions to unblock API usage without major rewrites (as much as possible)\n- Try fixing the edge creation mode click error and undo/redo actions.\n\nFor GLPI 12 (separate tasks to complete in listed order):\n- Use Vue for the frontend portion of the feature.\n- Replace Cytoscape with VueFlow like used in the workflows plugin (and n8n if that gives it more credibility). VueFlow is simpler, half the bundle size, and IMO fits the need of Impact better while Cytoscape is more complex than needed.\n- Add a DB migration to correct the schema.\n- Rewrite/refactor the PHP code to align with GLPI standards\n- Extract any remaining HTML in the PHP code to the new Vue code", "priority": "low", "type": "feature", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23656, "url": "https://github.com/glpi-project/glpi/issues/23656", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "enhancement" ], "state": "open", "stateReason": null, "createdAt": "2026-03-27T11:09:51Z", "updatedAt": "2026-03-27T11:09:51Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Cascading dropdowns in GLPI Forms (filter question based on previous answer)", "detail": "Problem:\nIn GLPI 11 (built-in Forms), dropdown questions (Locations, Categories, Items)\nalways display the full tree or full list.\n\nIt is not possible to filter the available values of a question\nbased on the answer of a previous question.\n\nThis makes large hierarchies (Buildings → Departments → Sections)\nhard to use for end users.\n\nCurrent behavior:\n- Question 1: Select building\n- Question 2: Select department\n➡ Question 2 shows departments from ALL buildings\n\nExpected behavior:\nAllow cascading / dependent dropdowns:\n- Question 2 should only show values that are children of the selected value in Question 1\n- Same behavior for multiple levels (tree navigation)\n\nUse cases:\n- Location selection\n- Service catalog forms\n- Large organizations with multiple buildings\n\nBenefits:\n- Better user experience\n- Less user errors\n- Cleaner forms", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22722, "url": "https://github.com/glpi-project/glpi/issues/22722", "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "open", "stateReason": null, "createdAt": "2026-01-18T10:16:37Z", "updatedAt": "2026-03-27T01:14:10Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Entity tree accessibility issues", "detail": "Issue description:\n1\\) ARIA commands must have an accessible name\n\n[Image omitted]\n\n2\\) Table header text should not be empty\n\n[Image omitted]\n\n----\n\nRelevant e2e test:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23554, "url": "https://github.com/glpi-project/glpi/issues/23554", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-03-20T08:39:07Z", "updatedAt": "2026-03-26T19:56:43Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Menu accessibility issues", "detail": "Issue description:\nAccess keys:\n\n[Image omitted]\n\nRelevant e2e test that should be updated:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23550, "url": "https://github.com/glpi-project/glpi/issues/23550", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-03-19T16:20:22Z", "updatedAt": "2026-03-26T19:56:43Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Search panels accessibility issues", "detail": "Issue description:\nThe contrast on the search panel actions is not good enough:\n\n[Image omitted]\n\nIt applies to both the criteria and the sort panels actions.\n\nOnce fixed, these two lines should be removed from the tests/e2e/specs/Search/search_engine.spec.ts test:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23548, "url": "https://github.com/glpi-project/glpi/issues/23548", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-03-19T14:55:10Z", "updatedAt": "2026-03-26T19:56:42Z", "closedAt": null } }, { "title": "TypeError in StencilEditor when removing a port during an active edit", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nA JavaScript Uncaught TypeError occurs when a network port is removed using the delete/remove icon while the editing form for that port is still active. The UI fails to close the editor, and subsequent save attempts reference a destroyed object.\n\nActual Result\nThe form remains open. Clicking \"Save port data\" triggers a crash in the console, and the data is not processed. It appears StencilEditor.saveZoneData expects the Cropper instance to exist. When the port is removed via the \"-\" icon, the DOM elements or the underlying data model for the canvas are cleaned up, but the event listener on the \"Save port data\" button remains active and attempts to call getCropperCanvas on an undefined reference.\n\nExpected Result\nThe editing form should automatically close or be destroyed when the associated port is removed. If the form remains, the \"Save port data\" action should be disabled or handled gracefully.\n\nAffected page:\n/front/networkequipmentmodel.form.php?id=5\n\nReproduction steps:\n1. Navigate to a device or rack where ports are managed visually (using the Stencil/Graphic editor - Setup > Dropdowns > Network Device Models).\n2. Add a new port or select an existing one.\n3. Click to Edit the port to open the configuration/stencil form.\n4. Without saving or closing the form, click the \"-\" (remove) icon to delete the port.\n5. Observe that the editing form remains visible even though the port entry has been removed.\n6. Click the Save port data button within the lingering form.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23613, "url": "https://github.com/glpi-project/glpi/issues/23613", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-25T02:57:15Z", "updatedAt": "2026-03-26T02:41:09Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "APIRest::parseIncomingParams crashes with TypeError when request body is null", "detail": "Issue description:\nGlpi\\Api\\APIRest crashes with a TypeError when json_decode() receives null instead of a string. This happens when an API request is sent with an empty or missing body.\n\nThe API should handle empty/null request bodies gracefully instead of throwing an unhandled exception.\n\nGLPI version:\n11.0.6\n\nPHP version:\n8.2 (CloudLinux/CentOS — Hostinger shared hosting)\n\nReproduction steps:\n1. Send a POST/PUT request to the GLPI REST API with an empty body or Content-Type: application/json with no payload\n2. GLPI crashes with TypeError\n\nExample:\n\nExpected behavior:\nGLPI should check if the body is null/empty before calling json_decode() and return a proper API error response (e.g., HTTP 400 with a message like \"Request body is required\").\n\nSuggested fix:\nIn src/Glpi/Api/APIRest.php around line 555:\n\nImpact:\n- Any API client that accidentally sends an empty body crashes the API instead of getting a proper error response\n- May affect automated integrations, especially those with retry logic where the body might get lost", "priority": "medium", "type": "support", "createdByEmail": "parker.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23605, "url": "https://github.com/glpi-project/glpi/issues/23605", "author": "StbanMc", "anonymizedAuthorEmail": "parker.adler@peppermint.local", "assignees": [], "labels": [ "api", "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-03-24T20:58:10Z", "updatedAt": "2026-03-25T12:55:27Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Unable to insert images in the Ticket Creation fields of Form Destinations in GLPI 11", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6 (11.0.x)\n\nIssue description:\nHello,\nIf this behavior is by design and not a bug, I apologize in advance.\n\n[Image omitted]\n\nIssue Description:\nIn GLPI 11, when editing a Form’s Destination — specifically the screen where you customize the fields of the Ticket that will be created — it is not possible to insert images.\nThe following actions all fail to add an image:\n\n* Selecting an image using the editor’s “Insert image” menu → nothing happens\n* Drag & dropping an image into the editor → nothing happens\n* Adding an [Image omitted] tag whose src points to a previously uploaded Document → the tag appears to be ignored or removed\n\nIn all cases, the editor shows no error and simply refuses to embed the image.\n\nExpected behavior:\nWhen manually creating a normal ticket (outside Forms), the description field supports embedding images — either via drag & drop or by selecting an image in the editor.\nI expected the same capability when customizing the “ticket content” produced by a Form Destination.\n\nReproduction steps:\nThe issue occurs during standard, normal use without any special conditions.\n\nCreate or edit a Form in GLPI 11\nOpen Destinations → Ticket (item to be created)\nAttempt to insert an image using:\n\n* the editor’s “Insert image” menu, or\n* drag & drop, or\n* an [Image omitted] tag referencing an uploaded Document\n\nObserve that the image is not added", "priority": "medium", "type": "support", "createdByEmail": "robin.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23616, "url": "https://github.com/glpi-project/glpi/issues/23616", "author": "masakazuwatanabe", "anonymizedAuthorEmail": "robin.adler@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "open", "stateReason": null, "createdAt": "2026-03-25T08:21:48Z", "updatedAt": "2026-03-25T10:53:42Z", "closedAt": null } }, { "title": "Port mapping inconsistency on dual-image Network Device Models", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen a Network Device Model has both Front and Rear images, the UI allows a user to map the same port to both images. However, upon saving, only the first coordinate set (the first square drawn) is persisted. The second mapping is silently discarded.\n\nActual Result\nOnly the first drawing (e.g., on the Front image) is saved. The coordinates for the Rear image are missing, even though the UI allowed the action without error or warning.\n\nExpected Behavior\nThe system should either:\n\n- Support Dual Mapping: Allow a port to exist on both the front and rear visual planes (common for pass-through panels or specific internal wiring).\n- Enforce Single Mapping: If the database only supports one set of coordinates per port, the UI should prevent drawing a second square or provide a warning that the previous mapping will be overwritten.\n\nAffected page:\n/front/networkequipmentmodel.form.php?id=1\n\nReproduction steps:\n1. Go to Setup > Dropdowns > Network Equipment Models.\n1. Select a model that has both a Front Image and a Rear Image defined.\n1. Go to the Graphical slot definition tab where you define port positions.\n1. Select a specific port (e.g., Port 48).\n1. Draw the mapping square on the Front Image.\n1. While the same port is selected, draw a mapping square on the Rear Image.\n1. Click Save port data.\n\nRefresh the page or navigate away and return.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23608, "url": "https://github.com/glpi-project/glpi/issues/23608", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-25T00:07:56Z", "updatedAt": "2026-03-25T02:11:48Z", "closedAt": null } }, { "title": "Test the anonymous items creation in the mail collector test suite", "detail": "Issue description:\nWe should find a way to have the mail collector tests executed with both anonymous items creation allowed and denied configurations.\n\nAnonymous items creation is not currently tested and we already had issues with tickets/followups created this way.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22426, "url": "https://github.com/glpi-project/glpi/issues/22426", "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-18T10:53:21Z", "updatedAt": "2026-03-18T08:37:43Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Switching entity while in a ticket throws an error page instead of redirecting to all tickets or dashboard view instead.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6.\n\nIssue description:\nSwitching entity while in a ticket throws an error page instead of redirecting to all tickets or dashboard view instead.\n\"The action you have requested is not allowed.\nReturn to previous page\"\n\nAffected page:\n\nReproduction steps:\nOpen a ticket under one Entity (eg. named EntityOne)\nSwitch to another Entity in the top right dropdown menu (eg. named EntityTwo)\nAutomatically shows the error instead of redirecting like before", "priority": "medium", "type": "support", "createdByEmail": "reese.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23434, "url": "https://github.com/glpi-project/glpi/issues/23434", "author": "jglavas-getim", "anonymizedAuthorEmail": "reese.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-03-10T12:00:37Z", "updatedAt": "2026-03-12T14:56:30Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI 11 - \"location\" dropdown disappear in tickets from certain entities", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAfter upgrade from 10 to 11, multiple entities (i'd say 1/3) have the native field \"lieu\" (location) that disappear from the tickets as you can see.\n\n[Image omitted]\n\nIt causes problem because it's a mandatory field and we can't update tickets because it is not completed.\n\nIt was bugged in 11.0.4 and going to 11.0.6 did not resolve the issue.\nWith or without plugins.\n\nOther entitites have no problem.\n[Image omitted]\n\nBugged entities are configured like this\n\n[Image omitted]\nIt's the only template existing anyway\n\nNo errors in the logs.\n\nIt happens when creating a ticket, and even in existing tickets.", "priority": "medium", "type": "support", "createdByEmail": "elliot.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23438, "url": "https://github.com/glpi-project/glpi/issues/23438", "author": "killerwanee", "anonymizedAuthorEmail": "elliot.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-10T13:48:13Z", "updatedAt": "2026-03-10T13:48:13Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "LDAP Sync Group Value saves HTML Entities (Breaks sync for ldap groups with ampersand)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen there is an & in a group name, it gets saved to the database as the HTML entity &, however, when the search is done to match the groups, it does not use the HTML entity version.\n\nExample:\n\nBut when the query is done, it searches this:\n\nIf you sanitize the group name before the query, then it works as expected.\n\nReproduction steps:\n1. Setup LDAP sync\n2. On \"LDAP Directory Link\" page for a group, set attribute value to a group with an & in it\n3. Perform an LDAP sync\n\nAdditional context:\nThis test made it work properly for me", "priority": "medium", "type": "support", "createdByEmail": "emerson.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23339, "url": "https://github.com/glpi-project/glpi/issues/23339", "author": "Goggin", "anonymizedAuthorEmail": "emerson.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-03-03T20:50:45Z", "updatedAt": "2026-03-04T10:32:44Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Date picker month/year change hide search panel and became unusable", "detail": "Issue description:\nWhen searching using the date picker, things goes wrong if we use month or year navigation. Search panels hides; and date picker remains (but is useless, selection is not kept anyway)\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23092, "url": "https://github.com/glpi-project/glpi/issues/23092", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "javascript", "ui" ], "state": "open", "stateReason": null, "createdAt": "2026-02-12T09:31:43Z", "updatedAt": "2026-03-02T14:49:56Z", "closedAt": null } }, { "title": "[Bug] Software license expiration alerts only trigger for already expired licenses (pre-notification fails) on glpi 11.05", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nDescription:\nHello, I am experiencing an issue with the automatic notification system for software license expirations.\nThe feature \"Send alarms on software licenses before X days\" seems to be ignored by the software automatic action.\n\nBehavior: The notification is never sent if the license expires in the future (matching the delay config).\n\nBehavior: The notification is successfully sent only once the license date is passed (expired).\n\nReproduction steps:\nConfiguration:\n\nGo to Administration > Entities > Notifications.\n\nSet \"Alarms on expired licenses\" to Yes.\n\nSet \"Send alarms on software licenses before\" to 1 day (or 30 days, same result).\n\nData:\n\nCreate a Software License with an expiration date set to Tomorrow (Date + 1) (or Date + 30).\n\nEnsure the license is Active and in the correct Entity.\n\nExecution:\n\nGo to Setup > Automatic actions > software.\n\nRun the action manually (or via CLI).\n\nResult:\n\nThe action logs show: 0 Action completed, fully processed.\n\nNo notification is sent.\n\nCounter-test:\n\nModify the license expiration date to Yesterday.\n\nRun the software action again.\n\nResult: The action processes 1 item and the notification is received.\n\nEnvironment details:\nGLPI Version: 11.0.5\n\nPHP Version: 8.2\n\nTimezone: UTC+1", "priority": "medium", "type": "support", "createdByEmail": "lane.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23160, "url": "https://github.com/glpi-project/glpi/issues/23160", "author": "logann-sys", "anonymizedAuthorEmail": "lane.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-18T11:17:17Z", "updatedAt": "2026-02-18T11:17:17Z", "closedAt": null } }, { "title": "cron_mailgate does not update \"Last edit by\"", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHello,\n\nWe use the mail receiver to retrieve an IMAP mailbox. Tickets are created and replies are assigned correctly. However, the “Last edit by” field is not updated.\nIs this a bug or is there a configuration missing?\n\n[Image omitted]\n\nBest regards,\nOliver", "priority": "medium", "type": "support", "createdByEmail": "jesse.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23059, "url": "https://github.com/glpi-project/glpi/issues/23059", "author": "PacGyver", "anonymizedAuthorEmail": "jesse.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-09T15:35:43Z", "updatedAt": "2026-02-09T15:35:43Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "css is not applied in editor", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nThis is the view when not editing:\n\n[Image omitted]\n\nAnd this is the view when editing:\n\n[Image omitted]\n\nIn the example I set the background of the pre element to green, to make the bug obvious and are using my own palette. But the problem does also happen with the default Auror palette:\nWhen not editing the pre element has a border when editing the border is missing. Maybe other elements are effected as well.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 23013, "url": "https://github.com/glpi-project/glpi/issues/23013", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "open", "stateReason": null, "createdAt": "2026-02-04T12:53:40Z", "updatedAt": "2026-02-08T14:52:25Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Mail Collector -> cannot login, user or password wrong", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello,\n\nI'm opening this issue because my email client has stopped working since the 11.0.5 update.\n\nI've attached a screenshot of the logs.\n\nThis happens whether I'm using IMAP or POP3; the username and password are valid and have been tested from another application.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "harper.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22939, "url": "https://github.com/glpi-project/glpi/issues/22939", "author": "DarknessOmbrage", "anonymizedAuthorEmail": "harper.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-02-01T22:17:58Z", "updatedAt": "2026-02-01T22:17:58Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI throws exception when adding a LDAP server without host and port", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen adding a LDAP server only with name, it throws an exception.\n\nAffected page:\n\nReproduction steps:\n1. Go to Setup > Authentication.\n2. Select LDAP Directory.\n3. Add a new LDAP server.\n4. Type only Name and Save.\n5. See error.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22930, "url": "https://github.com/glpi-project/glpi/issues/22930", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-30T21:50:57Z", "updatedAt": "2026-01-30T21:50:57Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "\"Leave site ?\" pop-up only appears for tickets", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen editing a ticket (ex: changing the category of a ticket), and leaving without saving, this browser pop-up comes up asking if I am willing to leave site, losing any unsaved changes :\n[Image omitted]\n\nHowever, when editing an entry, such as a knowledge base item or a supplier, this pop-up does not come up, and it is much easier to loose progress by accident.\n\nExample:\nIn knowledge base item creation, when selecting target groups, because the _i_ to get to list of groups is close to the selection (of course), it's easy to missclick and loose all progress\n\n[Image omitted]\n\nReproduction steps:\n1. Create a new knowledge base item\n2. Write content\n3. Leave the page without saving (by pressing _i_ button in this particular case)", "priority": "medium", "type": "support", "createdByEmail": "cameron.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22917, "url": "https://github.com/glpi-project/glpi/issues/22917", "author": "troncoli", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2026-01-30T10:49:36Z", "updatedAt": "2026-01-30T10:50:07Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 11.0.5: Read-only Mode doesn't work anymore", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHi,\n\nit is no longer possible to open a ticket in read-only mode in GLPI 11.0.5. Our workflow is that technicians open a ticket in read-only mode and only request a lock on the ticket (-> edit) if necessary.\n\nThis option has been removed with the update to 11.0.5. Pull Request #22408 removed this option by setting the variable $autolock = false; in the newly added ‘_else_’ case (lines 136-139).\n\nAfter reading the bug report, it became apparent that there seems to be some misunderstanding regarding the object lock. The fact is that a distinction must be made here between an object lock and read-only mode. The object lock (_Setup->General->General Setup->Use locks_) ensures that the object is locked for other users when it is opened, with all the problems described in ticket #22408. When this is enabled, read-only mode can be enabled or disabled on top (_Setup->General-> Default Values->Auto-Lock-Mode_). If this option is set to ‘_False_’, the ticket is opened in read-only mode and, if necessary, the lock can be obtained using the ‘edit’ button at the top of the ticket. This is how our technicians handle it.\n\nHowever, in Pull Request #22408, the ‘_else_’ case mentioned above overwrites this read-only mode, rendering the entire option obsolete.\n\nOur current workaround is to simply comment out the 4 lines.\n\nBest regards,\nAndreas", "priority": "medium", "type": "support", "createdByEmail": "harper.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22894, "url": "https://github.com/glpi-project/glpi/issues/22894", "author": "andreasmerkel", "anonymizedAuthorEmail": "harper.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-29T12:22:17Z", "updatedAt": "2026-01-29T14:10:31Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Shared Dashboard do not show Filter for other users", "detail": "Issue description:\nAs a super admin, I created a dashboard and added \"Creation date\" filter. This dashboard is visible to Technicians because they have permission to read all dashboards. However, they cannot see the filter I added.\n\nTechnicians have the option to \"Toggle filter mode\" and then \"Add filter\" button appears. But when they click on it no filter options are shown.\n\nGLPI 11.0.4", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22887, "url": "https://github.com/glpi-project/glpi/issues/22887", "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-29T07:38:12Z", "updatedAt": "2026-01-29T07:38:12Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "SLA/OLA (TTO) is automatically closed when ticket is created via Email Collector and assigned by Business Rule", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.22\n\nIssue description:\nWhen a ticket is created through the Email Collector (Request Source: Email), and a TTO SLA/OLA and an assignment group are added via a Business Rule, the TTO is automatically marked as finished after 1 second.\n\nThis behavior does not occur when tickets are created through other sources (e.g., web interface, API, manual creation).\n\n---\n\n✅ Expected Behavior:\nThe TTO SLA/OLA should start normally and respect its configured response time, regardless of the ticket creation source.\n\n---\n\n❌ Actual Behavior:\nWhen the ticket is created via Email Collector, the TTO is automatically marked as completed after approximately 1 second.\n\n---\n\n[Image omitted]\n\nReproduction steps:\n1. Configure an Email Collector.\n2. Create a Business Rule for tickets that:\n\n * Assigns a support group.\n * Applies a TTO SLA/OLA.\n3. Send an email to create a new ticket.\n4. Check the SLA/OLA status after ticket creation.\n\nEnvironment details:\nGLPI Version: 10.0.22\nOperating System: Linux\nDatabase: MariaDB + 11.3.2\nWeb Server: Apache\nPHP Version: 8.3.28\n\n📎 Additional Information:\n* This issue only occurs when the ticket is created via Email Collector.\n* Tickets created via other sources work as expected.\n* The same Business Rule is applied in all cases.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22839, "url": "https://github.com/glpi-project/glpi/issues/22839", "author": "RPGMais", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-26T17:26:28Z", "updatedAt": "2026-01-26T17:26:28Z", "closedAt": null }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Update tests logs are repeating and huge", "detail": "Issue description:\nSee:\n[Image omitted]\n\nWe can see here at least 3 times \"Update to 10.0.1 version completed\".\n\nI guess this also should be avoid in CI output:\n\n[Image omitted]\n\nWhen an update test fail; CI continues; so the error we reach on the CI UI is the last one. We have to manually go to correct error in update part, were we must scroll for a long long time.\nIn my failing test, update from 0.85.5 begins line 33 and error is line 1890.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22809, "url": "https://github.com/glpi-project/glpi/issues/22809", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-23T10:07:37Z", "updatedAt": "2026-01-23T10:07:37Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Use prepared statements in transfer", "detail": "Issue description:\nTransfer is just a succession of many SQL request (like on Software). I guess perfomances could be improved if we rely on SQL prepared statements.", "priority": "high", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22788, "url": "https://github.com/glpi-project/glpi/issues/22788", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "open", "stateReason": null, "createdAt": "2026-01-22T07:20:42Z", "updatedAt": "2026-01-22T07:20:42Z", "closedAt": null } }, { "title": "Can not link tickets and changes across sub entities", "detail": "Affected version:\n11.0.4 and 10\n\nIssue description:\nI have a entities structure like a > b and a ticket belonging to b and a change belonging to a.\nI want to link the ticket and the change however I can not select the ticket or the change in the corresponding tabs.\nHowever if I select \"create a change from this ticket\" and switch the entity to which the change belongs during change creation Change and ticket are linked as expected.\nI suspect the select menu not displaying elements from sub-entities correctly.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22731, "url": "https://github.com/glpi-project/glpi/issues/22731", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-19T09:18:12Z", "updatedAt": "2026-01-19T09:18:35Z", "closedAt": null }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Change and problemas notifications not sent to assigned technician (notification bell disabled on assignment)", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen creating a Change/Problem, the technician is automatically assigned (by template/rule/form), but the notification bell (email follow-up / notifications) for the assigned technician is disabled automatically.\nAs a result, the assigned technician does not receive Change notifications.\nFor Tickets, the same mail setup works correctly (assigned technicians do receive notifications).\n\nConfiguration for the change notification:\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. Configure automatic assignment of a technician when creating a Change.\n2. Configure new notification as image below.\n * Type: Change\n * Event: New change\n * Recipients: Technician in charge of the ticket\n4. Create a new Change.\n5. Observe that the technician is automatically assigned.\n6. Check the assigned technician actor: the notification bell is disabled.", "priority": "medium", "type": "support", "createdByEmail": "noel.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22723, "url": "https://github.com/glpi-project/glpi/issues/22723", "author": "lpgab", "anonymizedAuthorEmail": "noel.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2026-01-18T15:08:58Z", "updatedAt": "2026-01-18T15:08:58Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Creating a group through Rule Action modal redirects to Groups page", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen creating a group through Administration > Rules > Authorizations assignment rules > [+ Add] > Actions > [Add a New Action] > Groups > [+], it opens a modal window that allows you to create groups, but when creating a group, it redirects to the \"Groups\" page of the created group:\n\nThis behavior is different from the other modals on the GLPI, which keeps the same form on modal on Save:\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22627, "url": "https://github.com/glpi-project/glpi/issues/22627", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "javascript", "ui" ], "state": "open", "stateReason": null, "createdAt": "2026-01-12T13:23:50Z", "updatedAt": "2026-01-13T16:18:17Z", "closedAt": null }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Removing the last display preference on an list view silently fails", "detail": "Affected version:\n11.0-dev\n\nIssue description:\nWhen a user removes all display preferences of an itemtype, an exception is raised due to a missing key in $_POST.\n\nAffected page:\n/front/computertype.php\n\nReproduction steps:\nThere are two scenarios\n\n1st scenario:\n- Create a computer type\n- Display the list of computer types\n- Change the display preferences and add one column. Close the display prefs modal to refresh the list\n- Open again the display preferences, remove the additional column, close the modal\n- The list should refresh but the columns remains unchanged; the display preference is still visible\n\n2nd scenario:\n- Create a computer type\n- Display the list of computer types\n- Change the display preferences and add at least 2 columns. Close the display prefs modal to refresh the list\n- Open again the display preferences, remove all additional columns, close the modal\n- The list should refresh but one display preference is still visible; the others are properly deleted", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22286, "url": "https://github.com/glpi-project/glpi/issues/22286", "author": "btry", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "btry", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-08T14:25:51Z", "updatedAt": "2025-12-29T11:27:03Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Cannot transfer assets between entities – “You don't have permission to perform this action”", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWe’re getting the error ‘You don’t have permission to perform this action’ when trying to transfer an asset between entities. From what I know, this started after we switched to 11.0.2 and still persists in 11.0.4.\n\nGLPI version: 11.0.4\nOS: Ubuntu 22.04, PHP 8.5.0, MariaDB\nUser: Super-Admin, full permissions\nPlugins: All disabled\n\nTried:\nDifferent browsers, cleared cache/cookies\nSingle session, no multiple logins\nCreated an empty asset\nChecked PHP session config (session.save_path, gc_maxlifetime, permissions)\nDisabled all plugins\nChecked for duplicate entries in glpi_items_softwareversions (and related tables): no duplicates found\nGLPI cache cleared, Apache restarted\n\nError:\n“You don't have permission to perform this action. Return to previous page.”\nLogs show CSRF/session errors, no ACL errors\n\nEnvironment details:\nGLPI version: 11.0.4\nOS: Ubuntu 22.04, PHP 8.5.0, MariaDB\nUser: Super-Admin, full permissions\nPlugins: All disabled", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22489, "url": "https://github.com/glpi-project/glpi/issues/22489", "author": "femachado", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-28T22:23:47Z", "updatedAt": "2025-12-28T22:23:47Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Dashboard has no entity restriction.", "detail": "Affected version:\n10.0.17\n\nIssue description:\nDashboards in GLPI have no entity restrictions, allowing users to edit them, and everyone sees the same dashboard. This shouldn't be the case; each entity should have different dashboards.\n\nPerhaps there should be personal dashboards, allowing each technician to edit their own instead of a public one.\n\nAffected page:\ndomain/front/ticket.php\n\nReproduction steps:\n1. Have two technicians with the same profile connected to your instance.\n2. Enable dashboards for the shared profile.\n3. Navigate to tickets list page.\n4. Now you can edit the dahsboard, so edit it and remove something.\n5. The other technician will see your changes even if not the same entity is selected.", "priority": "high", "type": "incident", "createdByEmail": "devon.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 18330, "url": "https://github.com/glpi-project/glpi/issues/18330", "author": "rootjog", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [], "labels": [ "security" ], "state": "open", "stateReason": null, "createdAt": "2024-11-18T10:40:09Z", "updatedAt": "2025-12-04T11:45:19Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Review Notes system", "detail": "Issue description:\nCurrently ugly, but we also add title, revisions and comments features", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 16095, "url": "https://github.com/glpi-project/glpi/issues/16095", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2023-11-30T11:26:07Z", "updatedAt": "2025-12-04T11:45:18Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Review config ux for specific options", "detail": "Issue description:\nLot of options are dedicated to a specific behavior not used by so many people.\nWe should move these to an ui like firefox about:config", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 16079, "url": "https://github.com/glpi-project/glpi/issues/16079", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2023-11-28T11:07:01Z", "updatedAt": "2025-12-04T11:45:18Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "modern auth", "detail": "Issue description:\nAt first, we must check customers/user's claims about azure portal closing soon their basic connection supports on smtp.\n\nDo we need a hook for 10.0/bugfixes ?\n\nFor main branch:\n- return of oauth imap plugin in core\n- study/develop the same for smtp\n\ncurrent lib league/oauth-client (MIT)", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 15108, "url": "https://github.com/glpi-project/glpi/issues/15108", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-07-04T13:36:55Z", "updatedAt": "2025-12-04T11:45:18Z", "closedAt": null } }, { "title": "Wizard - discover GLPI", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 15986, "url": "https://github.com/glpi-project/glpi/issues/15986", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "ccailly", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-11-14T09:06:09Z", "updatedAt": "2025-12-04T11:20:53Z", "closedAt": null }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Twig for notification templates", "detail": "Issue description:\nSteps:\n- #15243 Send content in twig rendering engine after processing our own tags\n- Provide tags as twig variables\n- Rewrite existing template with twig syntax", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 15248, "url": "https://github.com/glpi-project/glpi/issues/15248", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2023-07-19T08:05:40Z", "updatedAt": "2025-12-04T11:12:03Z", "closedAt": null } }, { "title": "Mandatory fields not highlighted when changing ticket category to one with a template", "detail": "Affected version:\n11.0.0-beta5 and 10.0.18\n\nIssue description:\nWhen modifying the category of an existing GLPI ticket to a category associated with a ticket template containing mandatory fields, these mandatory fields are not displayed or highlighted. This causes the save operation to fail if any required fields are left unfilled. The validation error occurs only during saving (too late), rather than when the category is selected.\n\nExpected Behavior:\nWhen selecting a new category linked to a template with mandatory fields, GLPI should immediately:\n1. Display all associated mandatory fields\n2. Highlight/indicate required fields (e.g., with red asterisks)\n3. Prevent saving until all requirements are met\n\nCurrent Behavior:\n1. No visual indication of new mandatory fields when changing categories\n2. User only discovers missing fields upon save attempt\n3. Workflow interruption with validation error after form completion\n\nAffected page:\nfront/ticket.form.php?id=X\n\nReproduction steps:\n1. Enter to a previously created ticket\n2. Modify its category to one using a template with mandatory fields\n3. Observe missing field highlighting\n4. Attempt to save without filling new fields\n5. Receive late validation error", "priority": "medium", "type": "support", "createdByEmail": "riley.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 19932, "url": "https://github.com/glpi-project/glpi/issues/19932", "author": "racingfoss", "anonymizedAuthorEmail": "riley.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": "reopened", "createdAt": "2025-06-05T23:01:27Z", "updatedAt": "2025-12-04T11:11:37Z", "closedAt": null } }, { "title": "Improve default dashboard colors", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 17521, "url": "https://github.com/glpi-project/glpi/issues/17521", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-07-16T09:17:00Z", "updatedAt": "2025-12-04T09:44:54Z", "closedAt": null }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "HLAPI timeline users", "detail": "Issue description:\n/Assistance/Ticket/{id]Timeline endpoint answers:\n\nWe missed a few data:\n\n- Important, users information, we may need something like done in team key of Ticket endpoint:\n\nI didn't find any way to retrieve these data with another query, and anyway retrieve them in a single request is probably better.\nTo note, I would like to also have emails in this team/user block.\n- less important, but we miss some keys of the original table: timeline_position, sourceitems_id, sourceof_items_id\n- maybe hard to achieve, but is there a way to retrieve attachments for a timeline entry ?\n\nI highlight these questions and misses because we or people may want to replicate GLPI UI in another homemade application.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 20762, "url": "https://github.com/glpi-project/glpi/issues/20762", "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "open", "stateReason": null, "createdAt": "2025-08-25T08:01:55Z", "updatedAt": "2025-12-04T09:42:27Z", "closedAt": null }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Recursive groups are not taken into account by the search engine", "detail": "Issue description:\nMain group:\n\n[Image omitted]\n\n[Image omitted]\n\nSub group:\n\n[Image omitted]\n\nSearch engine results:\n\n[Image omitted]\n\nThe users should be found here because of the \"Recursive membership: true\" option, which make him part of the group.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 21095, "url": "https://github.com/glpi-project/glpi/issues/21095", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-09-22T14:08:01Z", "updatedAt": "2025-12-04T07:33:28Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Add fields in itilchildtemplate", "detail": "Affected version:\n10.0.10\n\nIssue description:\nHello,\n\nI'd like to suggest an enhancement for GLPI that involves expanding the set of entity fields available for use in templates. Currently, templates support a limited set of fields:\n\n{{ entity.id }}\n{{ entity.name }}\n{{ entity.completename }}\nConsidering the wealth of data available in the GLPI database, including address details, tags, phone numbers, and more, incorporating these additional fields into templates could significantly improve the system's utility.\n\nExample:\n{{ entity.tag}}\n{{ entity.address}}\n{{ entity.phone}}\n\nAffected page:\n/front/contenttemplates/documentation.php?preset=itilchildtemplate#entidade", "priority": "medium", "type": "support", "createdByEmail": "dakota.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 16680, "url": "https://github.com/glpi-project/glpi/issues/16680", "author": "Claonilton", "anonymizedAuthorEmail": "dakota.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2024-03-01T17:55:25Z", "updatedAt": "2025-12-04T07:22:31Z", "closedAt": null } }, { "title": "Encryption key cannot be used when updating after an interruption", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHello!\n\nI upgraded GLPI v10.0.18 to GLPI v11.0.2, following the steps in the official documentation. However, when running the database update from php bin/console database:update, if the user executing the command doesn't have permissions to access glpi/config, the update fails. This is expected and correct. The issue arises because, after this interruption due to permissions, when trying to run php bin/console again, we get the following error:\n\nopensa@ip-private:/var/www/glpi# sudo -u www-data php8.3 bin/console\nSymfony\\Component\\DependencyInjection\\Exception\\ParameterNotFoundException^ {#314\n #message: b\"The parameter \"kernel.secret\" has a dependency on a non-existent parameter \"ù\\x0F\".\"\n #code: 0\n #file: \"/var/www/glpi/vendor/symfony/dependency-injection/ParameterBag/ParameterBag.php\"\n #line: 93\n -key: b\"ù\\x0F\"\n -sourceId: null\n -sourceKey: \"kernel.secret\"\n -alternatives: []\n -nonNestedAlternative: null\n trace: {\n /var/www/glpi/vendor/symfony/dependency-injection/ParameterBag/ParameterBag.php:93 { …}\n /var/www/glpi/vendor/symfony/dependency-injection/ParameterBag/ParameterBag.php:245 { …}\n Symfony\\Component\\DependencyInjection\\ParameterBag\\ParameterBag->Symfony\\Component\\DependencyInjection\\ParameterBag\\{closure}() {}\n /var/www/glpi/vendor/symfony/dependency-injection/ParameterBag/ParameterBag.php:234 { …}\n /var/www/glpi/vendor/symfony/dependency-injection/ParameterBag/ParameterBag.php:205 { …}\n /var/www/glpi/vendor/symfony/dependency-injection/ParameterBag/ParameterBag.php:158 { …}\n /var/www/glpi/vendor/symfony/dependency-injection/Compiler/ResolveParameterPlaceHoldersPass.php:60 { …}\n /var/www/glpi/vendor/symfony/dependency-injection/Compiler/Compiler.php:80 { …}\n /var/www/glpi/vendor/symfony/dependency-injection/ContainerBuilder.php:768 { …}\n /var/www/glpi/src/Glpi/DependencyInjection/PluginContainer.php:139 {\n Glpi\\DependencyInjection\\PluginContainer->initializeContainer(): void^\n ›\n › $container->compile();\n ›\n }\n /var/www/glpi/src/Glpi/Kernel/Listener/PostBootListener/InitializePlugins.php:78 { …}\n /var/www/glpi/vendor/symfony/event-dispatcher/EventDispatcher.php:260 { …}\n /var/www/glpi/vendor/symfony/event-dispatcher/EventDispatcher.php:220 { …}\n /var/www/glpi/vendor/symfony/event-dispatcher/EventDispatcher.php:56 { …}\n /var/www/glpi/src/Glpi/Kernel/Kernel.php:149 { …}\n /var/www/glpi/src/Glpi/Console/Application.php:121 { …}\n /var/www/glpi/bin/console:143 { …}\n }\n}\n\nThis prevented us from continuing the database update. Regenerating the key also prevented us from running php bin/console.\n\nThe solution is to create a new database to restore the GLPI v10 .sql dump and regenerate the encryption key using php bin/console security:change_key.\n\nReproduction steps:\n1. Verify that the config directory has permissions outside the scope of the user who will run the GLPI update. For example, root permissions.\n2. Check the database status with 'php bin/console database:check_schema_integrity'. The status should be ok.\n3. Run the command 'php bin/console database:update' with a user that does not have permissions to access the config directory.\n4. The update will start, but will be interrupted due to a permissions problem in the config directory.\n5. Fix the permissions of the config directory, and GLPI in general to avoid problems during the update.\n6. Try updating the GLPI database again using the command 'php bin/console database:update', this time running it as the recommended user (e.g., www-data).\n7. The previous interruption of the database update will have left a dependency error related to Symfony.", "priority": "medium", "type": "support", "createdByEmail": "riley.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22076, "url": "https://github.com/glpi-project/glpi/issues/22076", "author": "Arkham1997", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-11-26T14:17:30Z", "updatedAt": "2025-12-03T14:34:29Z", "closedAt": null }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "Investigate Ticket item tab criteria", "detail": "Issue description:\nSee comment here:", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22203, "url": "https://github.com/glpi-project/glpi/issues/22203", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-12-03T14:20:58Z", "updatedAt": "2025-12-03T14:22:51Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "API (both versions) still use deprecated Glpi\\Http\\HeaderlessStreamedResponse", "detail": "Issue description:\nHeaderlessStreamedResponse has been deprecated (when it's been added); but API still uses it.\n\nSpotted when trying to remove deprecated classes on main branch. I have no idea how API can be fixed (if it can).", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22092, "url": "https://github.com/glpi-project/glpi/issues/22092", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-11-27T13:59:31Z", "updatedAt": "2025-12-03T13:14:38Z", "closedAt": null } }, { "title": "Confusing notation in impact analysis", "detail": "Affected version:\n11.0.2\n\nIssue description:\nIn the impact analysis diagram I find the arrow notation confusing.\n\nAn example:\n\nSample diagram\n\nIn the attached diagram, blue arrows mean ”Depends on” whilst red arrows mean ”Impacts”. The direction of the Blue arrows are wrong. They should point in the direction of the object that is the source of the dependency, just as the Red arrows points in the direction of the object being impacted.\n\nReproduction steps:\n1. For asset ”A”. In the diagram, add an ”Impacts” arrow from asset ”A” to asset ”B”.\n2. Now switch to asset ”B” and go to the diagram.\n3. You see a blue arrow having the same direction.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22079, "url": "https://github.com/glpi-project/glpi/issues/22079", "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2025-11-26T16:20:19Z", "updatedAt": "2025-11-26T16:27:20Z", "closedAt": null }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "No connection between 2 LLDP ports", "detail": "Affected version:\n10.0.20\n\nIssue description:\nI was exploring port connection failure between TP-Link devices reported here: glpi-project/glpi-agent#1026\n\nGLPI fails to connect 2 TP-Links ports. This may be related to #21285 as second problem there is it seems GLPI fails to handle LLDP ports.\n\nHere are the 2 XMLs generated with nightly build glpi-agent applied on walks provided by @loginone33 on linked and fixed glpi-agent issue:\n 1. SG2218P-2.0.xml\n 2. SG3428XF-1.20.xml\n\nFrom the first device, port \"gigabitEthernet 1/0/18\" is connected to the port \"gigabitEthernet 1/0/7\" of the second device.\n\nOn the first device, connections of port \"gigabitEthernet 1/0/18\" contains:\n\nOn the second device, connections of port \"gigabitEthernet 1/0/7\" contains:\n\nHere on the 2 sides, IFDESCR, SYSMAC and SYSNAME data seems correct so I think we have all necessary data to link ports together.\n\nReproduction steps:\n1. Import manually provided xml: SG2218P-2.0.xml and SG3428XF-1.20.xml\n2. Check ports table of the imported devices\n3. See \"gigabitEthernet 1/0/18\" port on \"SWITCH-008 PoE\" first asset has no connection\n4. See \"gigabitEthernet 1/0/7\" port on \"SWITCH-011 Main SFP\" second asset has no connection\n\nAdditional context:\nAlso checked in GLPI 10.0.20, issue is the same.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 21286, "url": "https://github.com/glpi-project/glpi/issues/21286", "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-03T16:05:55Z", "updatedAt": "2025-11-26T13:46:57Z", "closedAt": null }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Default filters behavior on GLPI 11", "detail": "Contribution description:\nCurrently, GLPI 11 has a new feature called Dafault filters at Setup > Dropdowns > Common which set the default filter for every profile in the entity where the parameters were set.\n\nIf you have it enabled on the list of tickets, for example, it will sum up the entity's default filter and the user's default filter always using the boolean AND option – there's no way to change this behavior, unless the user deletes its own default filter (saved search).\n\nIt would be great if:\n1. I, as a user, may have the option to sum up or not those two filters (entity default filter + my own saved search)\n2. I, as a user, may have the option to change between AND or OR when using those two filters (entity default filter + my own saved search)\n3. I, as a user, have A CLEAR alert that both filters are set (entity default filter + my own saved search)\n4. I, as a user, could clean my default filter, when using the entity default filter – which is not possible at the moment.\n\nTo replicate these behaviors, you must have a saved search set as default and a default filter set on dropdowns.", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22063, "url": "https://github.com/glpi-project/glpi/issues/22063", "author": "arthurrschaefer", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "open", "stateReason": null, "createdAt": "2025-11-25T11:34:03Z", "updatedAt": "2025-11-25T12:34:40Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Dashboards memory leak", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nFollowup investigation after noticing the memory leak on the ticket search results caused by auto-refresh (#22031) revealed a similar issue with dashboards that refresh.\nAfter approximately 200 refreshes (3.3 hours if the interval is set to 1 minute), the central page memory usage grew from around 90MB to around 500MB. Memory usage did not drop significantly after stopping the auto-refresh.\n\nIn this case, the main culprit is likely the ECharts instances not being disposed of properly before the HTML is replaced. A memory profile showed over 1000 EChart objects in memory and over 22,000 detached divs (\".chart .ct-chart\", \".card g-chart\", \".grid-stack\", etc).\nOther issues noticed:\n- Several empty div elements are added to the body with every refresh and not removed/replaced. These seem related to card tooltips?", "priority": "high", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 22061, "url": "https://github.com/glpi-project/glpi/issues/22061", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "open", "stateReason": null, "createdAt": "2025-11-25T11:05:19Z", "updatedAt": "2025-11-25T11:05:19Z", "closedAt": null }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Check crypt key on glpi update", "detail": "Affected version:\n11.1.0\n\nIssue description:\nAdd a check on glpi crypt key on glpi update.\n\nOn #21614 we added warning message if key is invalid. This can also be check to block update process.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 21648, "url": "https://github.com/glpi-project/glpi/issues/21648", "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-27T10:13:41Z", "updatedAt": "2025-10-27T10:13:53Z", "closedAt": null } }, { "title": "AD users may only be half-restored in some cases", "detail": "Issue description:\nAn issue exists where if you restore the user in AD and they try to log in before a sync, the is_deleted_ldap flag clears in GLPI without the restore action taking place so it remains soft-deleted and GLPI will not restore it properly during the next sync.\n\n_Originally posted by Taylor Adler in", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "in_progress", "isComplete": false, "comments": [], "source": { "project": "glpi-project/glpi", "issueNumber": 21498, "url": "https://github.com/glpi-project/glpi/issues/21498", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "open", "stateReason": null, "createdAt": "2025-10-15T12:15:20Z", "updatedAt": "2025-10-15T12:15:52Z", "closedAt": null }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Out of range value for column 'changetemplates_id'", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen I try to edit some properties of a Change I get an unexpected error\n\nAffected page:\n/front/change.form.php?id=56\n\nReproduction steps:\n1. Create a Change\n2. Try to edit a value\n3. Submit", "priority": "medium", "type": "support", "createdByEmail": "remy.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Is there a specific field that needs to be set or changed for this to occur?\n\nOriginal response date: 2026-05-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4360019473, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24082#issuecomment-4360019473", "createdAt": "2026-05-01T15:21:35Z" } }, { "userEmail": "morgan.blair@peppermint.local", "text": "We also see this isssue afer upgrading from 11.0.4 to 11.0.7. If you add a change by using default form everything is ok. If you create (or use an existing) custom form to add a change you will see the problem. php-errors.log say :\n\nglpi.ERROR: * An error occured during the form Debug submission: MySQL query error: Out of range value for column 'changetemplates_id' at row 1 (1264) in SQL query \"UPDATE glpi_changes SET changetemplates_id = '-1', date_mod = '' WHERE id = '50'\".\n\nThis behavior does not impact GLPI 11.0.4 but it does impact 11.0.7 (french language)\n\nOriginal response date: 2026-05-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4360169458, "author": "xrcam", "anonymizedAuthorEmail": "morgan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24082#issuecomment-4360169458", "createdAt": "2026-05-01T15:51:27Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I still cannot recreate the issue with a change created from a form; I am probably still missing something in my GLPI installation that causes this to happen.\n\nOriginal response date: 2026-05-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4361072963, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24082#issuecomment-4361072963", "createdAt": "2026-05-01T18:58:33Z" } }, { "userEmail": "morgan.blair@peppermint.local", "text": "Here are the actual plugins in the test environment.\n\n[Image omitted]\n\nOriginal response date: 2026-05-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4361249803, "author": "xrcam", "anonymizedAuthorEmail": "morgan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24082#issuecomment-4361249803", "createdAt": "2026-05-01T19:38:35Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "i have the same problem . Any modyfication on changes i get such problem or simillar\n\n[Image omitted]\n\nOriginal response date: 2026-05-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4368802695, "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24082#issuecomment-4368802695", "createdAt": "2026-05-04T06:41:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24082, "url": "https://github.com/glpi-project/glpi/issues/24082", "author": "tizianosartori", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "assignees": [ { "sourceLogin": "MyvTsv", "anonymizedEmail": "jesse.blair@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-30T13:17:50Z", "updatedAt": "2026-06-23T13:04:50Z", "closedAt": "2026-06-23T13:04:45Z" }, "assignedTo": "jesse.blair@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "GLPI 11 doesn't sending email notifications", "detail": "Affected version:\n11\n\nIssue description:\nGLPI 11 doesn't sending email notifications.\nI chose TLS option, but for any reason It always trying using SSL protocol.\nI copy the same configuration that I'm using on GLPI 10.\nOn GLPI 10 it's working Fine.\nI think it's a bug.\n\nReproduction steps:\nTry to configure smtp email\nIn my case I'm using gmail server with app password", "priority": "medium", "type": "support", "createdByEmail": "cameron.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "What was you configuration in GLPI 10.0 and what is your configuration in GLPI 11.0?\n\nWhen using TLS, the connection is made with the smtps:// scheme, and that is expected.\n\nIf you use SMTP+TLS, you have to use the port 587.\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460265668, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21676#issuecomment-3460265668", "createdAt": "2025-10-29T08:01:09Z" } }, { "userEmail": "kai.blair@peppermint.local", "text": "Same problem here. Configuration in GLPI10.0 using SMTP+TLS, port 587, it's working fine. Same configuration in GLPI 11.0 doesn't work (i'm using smtp.office365.com for both)\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460916639, "author": "squale323", "anonymizedAuthorEmail": "kai.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21676#issuecomment-3460916639", "createdAt": "2025-10-29T10:57:00Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "What was you configuration in GLPI 10.0 and what is your configuration in GLPI 11.0?\n\nWhen using TLS, the connection is made with the smtps:// scheme, and that is expected.\n\nIf you use SMTP+TLS, you have to use the port 587.\n\nHey bro, have a nice day.\nI´m using SMTP + TLS but I don´t know what the reason, but GLPI11 continues trying using SSL protocol.\nI´m sure that´s a bug.\nSame configuration is working fine in GLPI10\n\nSee the images attached.\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461039499, "author": "silvasocrates", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21676#issuecomment-3461039499", "createdAt": "2025-10-29T11:29:24Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "My bad, I misread the documentation. Could you check using the port 465 instead of 587?\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461058626, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21676#issuecomment-3461058626", "createdAt": "2025-10-29T11:34:21Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "My bad, I misread the codumentation. Could you chec using the port 465 instead of 587?\n\nhey again bro.\nI alredy tried this one.\nIt´s didn´t work too.\nGmail doesn´t support conection on port 465 anymore.\nAs I said the same configuration works fine in GLPI10\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461112748, "author": "silvasocrates", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21676#issuecomment-3461112748", "createdAt": "2025-10-29T11:48:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21676, "url": "https://github.com/glpi-project/glpi/issues/21676", "author": "silvasocrates", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-28T21:51:22Z", "updatedAt": "2026-02-12T00:39:06Z", "closedAt": "2025-10-30T05:40:21Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "upgrade from 10.0.20 failed", "detail": "Affected version:\n10.0.20 -> 11.0.2\n\nIssue description:\nHello\nI'm trying to upgrate my current 10.0.20 glpi version to 11.0.2\n\nI had some issues in log file :\n\nLe schéma de base de données n'est pas conforme à celui de la version installée de GLPI (10.0.18). Exécutez la commande \"php bin/console database:check_schema_integrity\" pour voir les différences.\n\nSo I stopped the auto installing and auto updating functions in env file, and tyied to do it manually\n\nIn update web page, when I'm trying to update from 10.0.20 to 11.0.2 i immediatly have this issue :\n\nMise à jour de la base de données...\nMise à jour vers 11.0.0…\n Une erreur s’est produite lors de la mise à jour. L’erreur est : MySQL query error: Duplicate entry '1-CartridgeItem-19-2' for key 'unicity' (1062) in SQL query \"INSERT INTO glpi_groups_items (SELECT NULL AS id, groups_id_tech AS groups_id, 'CartridgeItem' AS itemtype, id AS items_id, 2 AS type FROM glpi_cartridgeitems WHERE groups_id_tech > '0')\".\n\nIf I type \"php bin/console database:check_schema_integrity\" in my container I get a long error message attached in the log part\n\nI didn't changer anything in the database manually\n\nThank you for your help", "priority": "medium", "type": "support", "createdByEmail": "logan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "> Mise à jour de la base de données...\n> Mise à jour vers 11.0.0…\n> Une erreur s’est produite lors de la mise à jour. L’erreur est : MySQL query error: Duplicate entry '1-CartridgeItem-19-2' for key 'unicity' (1062) in SQL query \"INSERT INTO glpi_groups_items (SELECT NULL AS id, groups_id_tech AS groups_id, 'CartridgeItem' AS itemtype, id AS items_id, 2 AS type FROM glpi_cartridgeitems WHERE groups_id_tech > '0')\".\n\nMake sure you drop all tables, and restore a full v10 backup, before trying to update. Your current database is in a state between v10 and v11.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491008115, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21806#issuecomment-3491008115", "createdAt": "2025-11-05T12:41:43Z" } }, { "userEmail": "logan.bennett@peppermint.local", "text": "Thank you for your reply.\nI restored a database from 2–3 days ago. At that time, I hadn’t started any migration to GLPI 11 yet.\nHowever, this database already shows as version 11.0.2 instead of 10.x.x, and I don’t understand why.\nIs there any way to downgrade my database?\n\nLa version de la base de données semble correcte (11.0.2) - Parfait !\nMise à jour de la base de données...\nMise à jour vers 11.0.0…\nUne erreur s’est produite lors de la mise à jour\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3495831263, "author": "Cyril6789", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21806#issuecomment-3495831263", "createdAt": "2025-11-06T08:28:29Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I think 11.0.2 is the version of your MariaDB server.\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3495914975, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21806#issuecomment-3495914975", "createdAt": "2025-11-06T08:45:57Z" } }, { "userEmail": "logan.bennett@peppermint.local", "text": "ok, but even with an old version of my database, i cannot upgrade it. I immediately have error :\n\nUne erreur s’est produite lors de la mise à jour. L’erreur est : MySQL query error: Duplicate entry '1-CartridgeItem-19-2' for key 'unicity' (1062) in SQL query \"INSERT INTO glpi_groups_items (SELECT NULL AS id, groups_id_tech AS groups_id, 'CartridgeItem' AS itemtype, id AS items_id, 2 AS type FROM glpi_cartridgeitems WHERE groups_id_tech > '0')\".\n\nAnd I bet this is the first error before the next one... I'll have several error\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3495922314, "author": "Cyril6789", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21806#issuecomment-3495922314", "createdAt": "2025-11-06T08:47:36Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I will investigate on this. Maybe you have duplicated relations between cartridges and groups, I have to check if there is something to fix here.\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3495927375, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21806#issuecomment-3495927375", "createdAt": "2025-11-06T08:48:59Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21806, "url": "https://github.com/glpi-project/glpi/issues/21806", "author": "Cyril6789", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-05T11:50:56Z", "updatedAt": "2026-02-21T00:37:18Z", "closedAt": "2025-11-12T09:29:03Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Certificate management throws an error", "detail": "Affected version:\n11.0.2\n\nIssue description:\nAfter installing GLPI 11, our certificate management no longer works. When opening the page (front/certificate.php), I get the following error:\n\nAn unexpected error occurred\nReturn to previous page\nAn exception has been thrown during the rendering of a template (\"An error occurred\") in \"pages/generic_list.html.twig\" at line 37.\nIn ./templates/pages/generic_list.html.twig(37)\n#0 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#1 ./vendor/twig/twig/src/Template.php(373): Twig\\Template->display()\n#2 ./vendor/twig/twig/src/TemplateWrapper.php(51): Twig\\Template->render()\n#3 ./src/Glpi/Application/View/TemplateRenderer.php(170): Twig\\TemplateWrapper->render()\n#4 ./src/Glpi/Controller/AbstractController.php(68): Glpi\\Application\\View\\TemplateRenderer->render()\n#5 ./src/Glpi/Controller/GenericListController.php(51): Glpi\\Controller\\AbstractController->render()\n#6 ./vendor/symfony/http-kernel/HttpKernel.php(181): Glpi\\Controller\\GenericListController->invoke()\n#7 ./vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n#8 ./vendor/symfony/http-kernel/Kernel.php(197): Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n#9 ./public/index.php(70): Symfony\\Component\\HttpKernel\\Kernel->handle()\n#10 {main}\n\nPrevious: An error occurred\nIn ./vendor/thecodingmachine/safe/generated/Exceptions/DatetimeException.php(9)\n#0 ./vendor/thecodingmachine/safe/generated/8.3/datetime.php(1215): Safe\\Exceptions\\DatetimeException::createFromPhpError()\n#1 ./src/Glpi/Search/Provider/SQLProvider.php(6386): Safe\\strtotime()\n#2 ./src/Glpi/Search/Provider/SQLProvider.php(5219): Glpi\\Search\\Provider\\SQLProvider::giveItem()\n#3 ./src/Glpi/Search/SearchEngine.php(655): Glpi\\Search\\Provider\\SQLProvider::constructData()\n#4 ./src/Glpi/Search/SearchEngine.php(670): Glpi\\Search\\SearchEngine::getData()\n#5 ./src/Glpi/Search/SearchEngine.php(627): Glpi\\Search\\SearchEngine::showOutput()\n#6 [internal function]: Glpi\\Search\\SearchEngine::show()\n#7 ./src/Glpi/Application/View/Extension/PhpExtension.php(93): call_user_func_array()\n#8 /var/lib/glpi/_cache/11.0.2-52505ef9-production/templates/fe/fe46d70ce53b72576e15cbf75684b04a.php(55): Glpi\\Application\\View\\Extension\\PhpExtension->call()\n#9 ./vendor/twig/twig/src/Template.php(402): TwigTemplate_bc928cfd99306e9547d49a1826a7b368->doDisplay()\n#10 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#11 ./vendor/twig/twig/src/Template.php(373): Twig\\Template->display()\n#12 ./vendor/twig/twig/src/TemplateWrapper.php(51): Twig\\Template->render()\n#13 ./src/Glpi/Application/View/TemplateRenderer.php(170): Twig\\TemplateWrapper->render()\n#14 ./src/Glpi/Controller/AbstractController.php(68): Glpi\\Application\\View\\TemplateRenderer->render()\n#15 ./src/Glpi/Controller/GenericListController.php(51): Glpi\\Controller\\AbstractController->render()\n#16 ./vendor/symfony/http-kernel/HttpKernel.php(181): Glpi\\Controller\\GenericListController->invoke()\n#17 ./vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n#18 ./vendor/symfony/http-kernel/Kernel.php(197): Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n#19 ./public/index.php(70): Symfony\\Component\\HttpKernel\\Kernel->handle()\n#20 {main}\nTop of the page\n\nAffected page:\nfront/certificate.php\n\nEnvironment details:\nGLPI: 11.0.2 ( => /var/www/helpdesk)\nInstallation mode: TARBALL\nCurrent language: nl_NL\nSource Integrity: 7 files changed\n A: inc/autoload.function.php\n A: inc/based_config.php\n A: inc/config.php\n A: inc/db.function.php\n A: inc/define.php\n A: inc/downstream.php\n A: inc/index.php\n\nOperating system: Linux ubuntu2 6.8.0-87-generic #​88-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 11 09:28:41 UTC 2025 x86_64\n\nPHP: 8.3.6 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv,\nintl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer,\nxmlreader, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"8M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"2M\"\n\nWeb server: Apache/2.4.58 (Ubuntu) (Apache/2.4.58 (Ubuntu) Server at helpdesk.sint-gillis-waas.be Port 443)\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: (Ubuntu)\n\nServer Version: 8.0.43-0ubuntu0.24.04.2\n\nServer SQL Mode: STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@localhost/glpi\n\nHost info: Localhost via UNIX socket\n\nRequirements:\nPHP version (8.3.6) is supported.PHP version (8.3.6) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "morgan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "Hello,\n\ngot the same bug, the webpage loads only if the glpi_certificates table is truncated.\n\nI had to comment the if statement bloc in \"src/Glpi/Search/Provider/SQLProvider.php\" (lines 6385 to 6393) to bypass the issue.\nBecause of the call of strtotime (lines 6386)\n\nExample of one entry of my glpi_certificates table which causes the bug.\n\n| id | name | serial | otherserial | entities_id | is_recursive | comment | is_deleted | is_template | template_name | certificatetypes_id | dns_name | dns_suffix | users_id_tech | locations_id | manufacturers_id | contact | contact_num | users_id | is_autosign | date_expiration | states_id | command | certificate_request | certificate_item | date_creation | date_mod |\n| 294 | host.my.domain.com | | | 0 | 0 | | 0 | 0 | NULL | 1 | host | my.domain.com | 0 | 0 | 564 | | | 0 | 0 | 2026-01-22 | 13 | | | | 2023-07-06 13:28:14 | 2025-06-26 08:40:12 |\n\nDebian Trixie\nphp8.4-fpm\nGLPI 11.0.2\n\nBest regards,\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3542148638, "author": "CyrilVanErsche", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21916#issuecomment-3542148638", "createdAt": "2025-11-17T14:31:22Z" } }, { "userEmail": "parker.blair@peppermint.local", "text": "Hello,\n\nWe have the same issue. We worked around it by removing the expiration date from the certificate displayed colum (Setup → General → Search result display => click on \"certificate\" and change expiration date by another column \"ID\" for exmaple). At a minimum, you need to keep some information, for example the ID.\n\nphp8.4\nGLPI 11.0.2\n\nBest regards\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3542293680, "author": "TiboulVinci", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21916#issuecomment-3542293680", "createdAt": "2025-11-17T14:55:48Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Well, the following patch should solve the issue:\n\nBut the problem is it seems $_SESSION['glpi_currenttime'] has an invalid date; which should not happen. It may cause issues in other parts of the code.\n\nPlease try without any plugins , and on a recent GLPI v11 nightly build.\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3551645266, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21916#issuecomment-3551645266", "createdAt": "2025-11-19T09:18:01Z" } }, { "userEmail": "parker.blair@peppermint.local", "text": "If I change the expiry date to today's date or future in a certificate, I get this error :\n\nAn error occurred\nIn ./vendor/thecodingmachine/safe/generated/Exceptions/DatetimeException.php(9)\n#0 ./vendor/thecodingmachine/safe/generated/8.4/datetime.php(1228): Safe\\Exceptions\\DatetimeException::createFromPhpError()\n#1 ./src/Certificate.php(549): Safe\\strtotime()\n#2 ./src/CommonGLPI.php(683): Certificate->showForm()\n#3 ./ajax/common.tabs.php(108): CommonGLPI::displayStandardTab()\n#4 ./src/Glpi/Controller/LegacyFileLoadController.php(64): require('...')\n#5 ./vendor/symfony/http-kernel/HttpKernel.php(181): Glpi\\Controller\\LegacyFileLoadController->invoke()\n#6 ./vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n#7 ./vendor/symfony/http-kernel/Kernel.php(197): Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n#8 ./public/index.php(70): Symfony\\Component\\HttpKernel\\Kernel->handle()\n#9 {main}\n\nOriginal response date: 2025-11-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3575850188, "author": "TiboulVinci", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21916#issuecomment-3575850188", "createdAt": "2025-11-25T14:11:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "If I change the expiry date to today's date or future in a certificate, I get this error :\n\nAn error occurred In ./vendor/thecodingmachine/safe/generated/Exceptions/DatetimeException.php(9) #0 ./vendor/thecodingmachine/safe/generated/8.4/datetime.php(1228): Safe\\Exceptions\\DatetimeException::createFromPhpError() #1 ./src/Certificate.php(549): Safe\\strtotime() #2 ./src/CommonGLPI.php(683): Certificate->showForm() #3 ./ajax/common.tabs.php(108): CommonGLPI::displayStandardTab() #4 ./src/Glpi/Controller/LegacyFileLoadController.php(64): require('...') #5 ./vendor/symfony/http-kernel/HttpKernel.php(181): Glpi\\Controller\\LegacyFileLoadController->invoke() #6 ./vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw() #7 ./vendor/symfony/http-kernel/Kernel.php(197): Symfony\\Component\\HttpKernel\\HttpKernel->handle() #8 ./public/index.php(70): Symfony\\Component\\HttpKernel\\Kernel->handle() #9 {main}\n\nThis seems another isssue. Please provide the full lisible stacktrace.\n\nOriginal response date: 2025-11-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3575887023, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21916#issuecomment-3575887023", "createdAt": "2025-11-25T14:19:37Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21916, "url": "https://github.com/glpi-project/glpi/issues/21916", "author": "pieter-liekens", "anonymizedAuthorEmail": "morgan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-13T09:18:45Z", "updatedAt": "2026-05-24T01:02:57Z", "closedAt": "2026-02-12T11:23:14Z" } }, { "title": "HTML entities (') displayed raw in ticket titles instead of apostrophes", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nAfter migrating from GLPI 10.0.5 to GLPI 11.0.7, ticket titles containing\napostrophes are displayed as raw HTML entities (') instead of the\nactual character (').\n\nThis issue affects both migrated tickets AND newly created tickets, confirming\nit is not a data migration problem but a bug in GLPI 11.0.7 itself.\n\nExpected: l'accee\nActual: l'accee\n\n[Image omitted]\n\nAffected page:\n/front/ticket.form.php\n\nReproduction steps:\n1. Open GLPI 11.0.7\n2. Create a new ticket with an apostrophe in the title (e.g. \"l'accee\")\n3. Save the ticket\n4. Observe the title displayed as \"l'accee\" in the ticket view and title bar\n\nAdditional context:\n- Migrated from GLPI 10.0.5 to 11.0.7\n- Issue persists after clearing cache (php bin/console cache:clear)\n- LDAP authentication in use (Active Directory)\n- MariaDB 10.6.23 on Ubuntu 22.04", "priority": "medium", "type": "support", "createdByEmail": "jordan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue using the provided example title.\n\nOriginal response date: 2026-05-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4468636026, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24233#issuecomment-4468636026", "createdAt": "2026-05-17T00:27:59Z" } }, { "userEmail": "robin.blair@peppermint.local", "text": "Same problem reproduced after upgrade to 11.0.7.\nIndeed, it depends on the profile from which the ticket is opened. With simplified interface, the problem appears, and with standard interface, it is ok.\n\nOriginal response date: 2026-05-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4487708254, "author": "nhulot-a11y", "anonymizedAuthorEmail": "robin.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24233#issuecomment-4487708254", "createdAt": "2026-05-19T12:27:58Z" } }, { "userEmail": "robin.blair@peppermint.local", "text": "I cannot recreate the issue using the provided example title.\n\nHello Taylor Adler , have you been able to recreate the issue now, using simplified interface ?\n\nOriginal response date: 2026-05-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4554822036, "author": "nhulot-a11y", "anonymizedAuthorEmail": "robin.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24233#issuecomment-4554822036", "createdAt": "2026-05-27T13:13:55Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "No, I still cannot. I tested creating a ticket from a self-service user using the default Report an issue form and it displayed quotes properly in the created ticket.\n\nOriginal response date: 2026-05-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4556745292, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24233#issuecomment-4556745292", "createdAt": "2026-05-27T17:00:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24233, "url": "https://github.com/glpi-project/glpi/issues/24233", "author": "yassinedamir", "anonymizedAuthorEmail": "jordan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-15T14:50:55Z", "updatedAt": "2026-06-26T05:03:26Z", "closedAt": "2026-06-26T05:03:26Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI 10.0.20 - cannot create ticket with simplified interface", "detail": "Affected version:\n10.0.20\n\nIssue description:\nSince we upgraded to 10.0.20, our users with a profile with simplified mode cannot create a ticket (normal mode is OK).\nIf we remove the mandatory \"requestor\" field, we have this :\n[Image omitted]\nOtherwise :\n[Image omitted]\n\nWe have already tested without plugins and with a new template.\n\nThank-you !\n\nAffected page:\n\nReproduction steps:\n1. connect with user and profile with simplified mode\n2. create a ticket", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.blair@peppermint.local", "text": "I have the same issue\n\nOriginal response date: 2025-09-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3328072346, "author": "slytara", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20973#issuecomment-3328072346", "createdAt": "2025-09-24T12:01:47Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCan you test #21110?\n\nOriginal response date: 2025-09-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3328628220, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20973#issuecomment-3328628220", "createdAt": "2025-09-24T13:56:53Z" } }, { "userEmail": "skyler.blair@peppermint.local", "text": "Fix for me. Perfect. Thank a lot\n\nOriginal response date: 2025-09-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3332359771, "author": "slytara", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20973#issuecomment-3332359771", "createdAt": "2025-09-25T06:24:14Z" } }, { "userEmail": "dakota.blair@peppermint.local", "text": "ok thanks but Skyler Adler Skyler Blair when i replace the two files (TicketTest.php & Ticket.php) the problem is still present\nhave you make another change for this functions ?\ni also try to replace all folder by latest version on github but i've error message with dependencies\nthanks\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3338186295, "author": "efpbe", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20973#issuecomment-3338186295", "createdAt": "2025-09-26T11:14:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20973, "url": "https://github.com/glpi-project/glpi/issues/20973", "author": "efpbe", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-11T08:47:15Z", "updatedAt": "2026-03-12T00:36:01Z", "closedAt": "2025-12-01T08:34:05Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI 11 - error migrate generic objects (\"General\" item)", "detail": "Affected version:\n11.0.0\n\nIssue description:\nI used the Generic Objects plugin VERY heavily. I installed version 3 of the plugin and ran the migration but then got this error:\n\nThe migration failed.\n🛈 The object types families have not been imported as they are not handled by GLPI.\n🛈 The display preferences and saved searches related to a genericobject object type must be recreated manually.\nx Unable to copy General \"\".\nx Migration was aborted due to errors, all changes have been reverted.\n\nReproduction steps:\n1. login to terminal as www-data\n2. run command: php bin/console migration:genericobject_plugin_to_core\n3. Error shows after making it through all items and says it reverted everything back.", "priority": "medium", "type": "bug", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nIt seems that you have a \"General\" item that has no name.\nIs \"General\" corresponding to a generic object main item or to a generic object dropdown ?\n\nCould you check GLPI logs to see if there is something related to this error ?\n\nAlso, can you try to execute the migration with no active plugins ?\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3370715762, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21289#issuecomment-3370715762", "createdAt": "2025-10-06T09:33:48Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "I ran it again and this is what I found:\n\nSeems like the access to the \"Y\" subfolder was an issue. So I checked and the file in question was indeed set to root as the owner. So I removed the \"Y\" folder and tried again. Now it says a new folder \"J\".\n\nSo I zipped the cache and removed everything, disabled all plugins, and tried AGAIN! This was the result:\n\nNo other errors or logs.\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3372182651, "author": "jtfeatures", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21289#issuecomment-3372182651", "createdAt": "2025-10-06T15:05:04Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "Hi,\n\nIt seems that you have a \"General\" item that has no name. Is \"General\" corresponding to a generic object main item or to a generic object dropdown ?\n\nHow would I check this? I see all the objects in the database as different tables but I do not see one called \"General\".\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3372192150, "author": "jtfeatures", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21289#issuecomment-3372192150", "createdAt": "2025-10-06T15:06:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I ran it again and this is what I found:\n\nglpi.WARNING: * Failed to save key \"{key}\" of type array: rename(./files/_cache/11.0.0-f682f73d-production/core/iN-W9HE3,./files/_cache/11.0.0-f682f73d-production/core/T/Y/CvuKDXnNqtX1-1O0jcYQ): Permission denied\n\nThis is a filesystem permission issues, not related to reported issue. Make sure you run console scripts with same user your web server uses.\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3375147556, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21289#issuecomment-3375147556", "createdAt": "2025-10-07T04:26:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21289, "url": "https://github.com/glpi-project/glpi/issues/21289", "author": "jtfeatures", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-03T18:04:59Z", "updatedAt": "2026-03-15T00:45:03Z", "closedAt": "2025-12-04T07:04:10Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Entity transfer MySQL query error: Duplicate entry", "detail": "Affected version:\n11.0.0.BETA6\n\nIssue description:\nHello,\n\nI'm encountering an error when trying to transfer some computers from the root entity to a sub-entity.\n\nThe error occurs when I perform the transfer with all items retained so that the data goes to the sub-entity.\n\nI'm using version 11.0.0beta6", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This issue already exists on 10.0 versions\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3337091659, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20256#issuecomment-3337091659", "createdAt": "2025-09-26T07:13:33Z" } }, { "userEmail": "remy.blair@peppermint.local", "text": "I have a similar issue with tickets. Transferring between entities, similar to computers, also doesn't work. Taylor Adler, can you test it? Thanks\n\nOriginal response date: 2025-10-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3422393778, "author": "rjmontenegro", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20256#issuecomment-3422393778", "createdAt": "2025-10-20T14:45:42Z" } }, { "userEmail": "kendall.blair@peppermint.local", "text": "I have the same error when transferring a computer from a parent entity to a child entity. As a temporary workaround, I unchecked the “Keep software” option during the transfer so that it would work.\n\n[Image omitted]\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3479124297, "author": "igorvisi", "anonymizedAuthorEmail": "kendall.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20256#issuecomment-3479124297", "createdAt": "2025-11-03T06:43:54Z" } }, { "userEmail": "micah.blair@peppermint.local", "text": "Same error\n\nOriginal response date: 2025-11-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3515990330, "author": "teopost", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20256#issuecomment-3515990330", "createdAt": "2025-11-11T10:03:45Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20256, "url": "https://github.com/glpi-project/glpi/issues/20256", "author": "FelipeBasilio1991", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [ { "sourceLogin": "Lainow", "anonymizedEmail": "jesse.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-07-09T11:29:00Z", "updatedAt": "2026-01-26T07:11:19Z", "closedAt": "2026-01-26T07:11:18Z" }, "assignedTo": "jesse.blair@peppermint.local" }, { "title": "Fail to get computer page", "detail": "Affected version:\n11.0.4\n\nIssue description:\nAfter upgrading to GLPI 11.0.4, we can't open certain computer's pages with error :\n\nThis error occur with \"super-admin\" profile and not on all computers.\nWe have other custom profile without this bug (this profile has not rights on Tickets)\n\nAccording to the stack trace, I tried to execute SQL request in database with the same error. After little modification (table specification in WHERE clause), there is no more bug :\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "After little modification (table specification in WHERE clause), there is no more bug :\n\nCould you open a PR with the change (or at least share it)? I cannot reproduce on my side, so I'm not sure how to fix.\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744722974, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22635#issuecomment-3744722974", "createdAt": "2026-01-13T14:41:39Z" } }, { "userEmail": "robin.bennett@peppermint.local", "text": "Could you open a PR with the change (or at least share it)? I cannot reproduce on my side, so I'm not sure how to fix.\n\nMy change was made in my MySQL client, not in GLPI PHP files.\n\nAccording to GLPI debug mode and logs, I tried to execute this command directly in DB :\n\nCommand failed with following error :\n\n[Image omitted]\n\nWhen I specified table (to \"itemtype\" and \"items_id\"), no problem :\n\nI'm not dev so I didn't found where put this modification in PHP.\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744862166, "author": "infime-it", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22635#issuecomment-3744862166", "createdAt": "2026-01-13T15:07:28Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Well, I need a way to reproduce. On which tab does problem appears? What are the differences with ones that do not cause the issues?\n\nDid you try without plugins?\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744926373, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22635#issuecomment-3744926373", "createdAt": "2026-01-13T15:19:22Z" } }, { "userEmail": "robin.bennett@peppermint.local", "text": "Yeah but I didn't found any way to reproduce.\n\nIn the GUI, the difference is :\n\n- With a profile without rights on tickets, problems, ... : no problems\n- With a profile with rights on tickets, problems, ... : problem\n\nIn DB, a computer with this issue is present in most of \"glpi_items_deviceXXX\" tables and computer without this issue not.\n\nI tried without plugins but same issue.\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3745318311, "author": "infime-it", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22635#issuecomment-3745318311", "createdAt": "2026-01-13T16:38:36Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22635, "url": "https://github.com/glpi-project/glpi/issues/22635", "author": "infime-it", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-12T15:59:01Z", "updatedAt": "2026-04-25T00:46:22Z", "closedAt": "2026-01-14T11:05:44Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Bug: Server - Data Import, Display, and Dashboard Column Issues", "detail": "Affected version:\n11.0\n\nIssue description:\nData that is correctly collected by the GLPI Agent (and is present in the local inventory XML file) is not being imported, displayed correctly, or made available in the GLPI server UI.\n\nProcessor Speed (Dashboard Display)\n\nProblem: The processor speed is written completely wrong in the main dashboard (e.g., 40000mhz, 9000mhz).\n\nObservation: The correct speed is registered and visible if you click on the computer's name and check the frequency on the \"Processor\" component tab. The issue is only with the value shown on the computer dashboard.\n\nBluetooth Adapter (Dashboard Display)\n\nProblem: The Bluetooth adapter is correctly inventoried and shows up in the \"Network Ports\" tab when viewing an asset.\n\nObservation: It is impossible to show this Bluetooth interface on the main computer dashboard (e.g., in the \"Network Interface\" columns).\n\nMissing Dashboard Columns\n\nProblem: Several key data points are correctly inventoried and visible within an asset's component/detail tabs, but they cannot be added as columns to the main computer asset list/dashboard.\n\nMissing Columns Include:\n\nBattery Real Capacity (Health)\n\nBattery Original Capacity\n\nGPU VRAM\n\nStorage Interface (e.g., \"NVMe\")\n\nCapacity of particular storage drives (only the incorrect total from the Agent bug is available)\n\nPorts and Slots (Data Import/Display)\n\nProblem: Computer ports (USB, HDMI, etc.) and internal slots (e.g., M.2 slots) are all available in the local inventory XML.\n\nObservation: This information is not populated in the asset's \"Ports\" tab, nor can it be listed on the main dashboard.\n\nUSB Devices (Data Import)\n\nProblem: Connected USB devices (mouse, keyboard, speaker, etc.) are present in the local inventory XML but do not appear in the asset's \"Peripherals\" tab.\n\nExpected Behaviour\nThe GLPI Server should correctly import and display all data provided by the agent.\n\nProcessor Speed: The dashboard column should show the same, correct speed that is listed in the asset's \"Processor\" component tab.\n\nBluetooth Adapter: The Bluetooth interface (visible in \"Network Ports\") should be an available option to display as a column on the main computer dashboard.\n\nMissing Dashboard Columns: The following items should be available to add as columns to the main computer asset list:\n\nBattery Real Capacity (Health)\n\nBattery Original Capacity\n\nGPU VRAM\n\nStorage Interface (e.g., \"NVMe\")\n\nCapacity of particular storage drives\n\nPorts and Slots: All ports (USB, HDMI, etc.) and internal slots (M.2) listed in the XML should be imported and visible in the asset's \"Ports\" tab.\n\nUSB Devices: All USB peripherals (mouse, keyboard, etc.) listed in the XML should be imported and visible in the asset's \"Peripherals\" tab.\n\nAffected page:\n\nReproduction steps:\nTo Reproduce\nRun an agent inventory on a machine that correctly generates an XML file containing the data points listed above (e.g., Bluetooth, USB peripherals, ports, M.2 slots, correct processor speed).\n\nForce the agent to send the inventory to the GLPI server.\n\nCheck the asset's page (Peripherals tab, Ports tab, component details) and the main computer dashboard (column options) in GLPI.\n\nNote that the data is missing from the UI, displayed incorrectly on the dashboard, or not available as a dashboard column.\n\nAdditional context:\nI wrote the bug report myself and organized the report with the help of AI.\n\nI'm willing to help in anyway and get any required information to help the project.", "priority": "medium", "type": "support", "createdByEmail": "cameron.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "noel.bennett@peppermint.local", "text": "Hi! Have you created custom asset called \"Server\" for that?\n\nYou maybe need to enter a proper itemtype at agent.cfg file.\n\nitemtype = Glpi\\CustomAsset\\SerweryAsset - in my case.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432281819, "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21602#issuecomment-3432281819", "createdAt": "2025-10-22T13:07:03Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "Hi! Have you created custom asset called \"Server\" for that?\n\nYou maybe need to enter a proper itemtype at agent.cfg file.\n\nitemtype = Glpi\\CustomAsset\\SerweryAsset - in my case.\n\nSorry, I wrote server in the title of the issue in reference to the glpi server itself.\n\nThe problem is not with a server asset but with all assets.\n\nI'm separating the bugs I found in glpi from the bugs caused by the glpi agent, which I made a separate issue for in it's own repository.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432309731, "author": "Omareladawy", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21602#issuecomment-3432309731", "createdAt": "2025-10-22T13:13:28Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "> Hi! Have you created custom asset called \"Server\" for that?\n> You maybe need to enter a proper itemtype at agent.cfg file.\n> itemtype = Glpi\\CustomAsset\\SerweryAsset - in my case.\n\nSorry, I wrote server in the title of the issue in reference to the glpi server itself.\n\nThe problem is not with a server asset but with all assets.\n\nI'm separating the bugs I found in glpi from the bugs caused by the glpi agent, which I made a separate issue for in it's own repository.\n\nOh, I see!\n\nP.S: You can always set debug level to a least 1 and configure log file to analyze agent work.\nFor example logfile = /var/log/glpi-agent.log\n\n[Image omitted]\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432337480, "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21602#issuecomment-3432337480", "createdAt": "2025-10-22T13:20:02Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide example inventory file\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432408351, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21602#issuecomment-3432408351", "createdAt": "2025-10-22T13:36:39Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21602, "url": "https://github.com/glpi-project/glpi/issues/21602", "author": "Omareladawy", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-22T12:59:00Z", "updatedAt": "2026-02-26T00:37:13Z", "closedAt": "2025-11-17T07:07:11Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Is it planned to list generic assets in tickets in the final GLPI 11?", "detail": "Contribution description:\nGood evening, everyone!\n\nI just want to raise an issue here related to assets: as in version 10, I noticed that in version 11 there is also only the option to link native system assets, except for generic assets.\n\nNow that generic assets are being entered as native, is there any plan to include the feature of linking them in calls as well?\n\nWhen I say link, I mean like when you associate a computer with a ticket, for example, and then you can also associate that same computer through the form, as well as phones, printers, etc., everything except assets that are created by generic assets.\n\nVersion in question: GLPI 11 RC5\n\nThank you for your attention!\n\nTranslated with DeepL.com (free version)", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "You can add the custom assets as being allowed to be linked to tickets/changes/problems per-profile like other assets, but unlike most native assets they are not allowed to be linked by default. You can do this from the Profiles tab of the custom asset definition form or from individual profile forms.\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3316472357, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21085#issuecomment-3316472357", "createdAt": "2025-09-22T01:35:51Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "[Image omitted]\n\nTaylor Adler True, but I noticed something that could be seen as an improvement: even with that button marked “all items” within the profile > assistance, when you create a new item, it does not automatically consider that new item, so you end up having to go there and activate the new object in the profile > assistance to be able to associate it. This ends up going unnoticed because it is a very subtle permission.\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3316554684, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21085#issuecomment-3316554684", "createdAt": "2025-09-22T02:26:40Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The \"All\" button works the same for all dropdowns that accept multiple values. It adds all current options to the selection rather than representing all current and future options.\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3316558838, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21085#issuecomment-3316558838", "createdAt": "2025-09-22T02:29:27Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Ok Taylor Adler You can test in GLPI 11 rc5 the association of assets in the ticket destination via the form?\n\nI tried to open a ticket here in the native way and the asset associates normally, but through the form, both a computer and a generic asset, for example, do not associate. I also noticed that when you create the ‘specific asset’ association type, you choose one and below it creates an empty field.\n\nPath to replicate: within the form > destinations > Associated assets\n\nExpected behavior: open call with asset related to the issue or specifically as marked in the form properties.\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3316565213, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21085#issuecomment-3316565213", "createdAt": "2025-09-22T02:33:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21085, "url": "https://github.com/glpi-project/glpi/issues/21085", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" }, { "sourceLogin": "ccailly", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "beta / rc", "question" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-22T01:30:10Z", "updatedAt": "2026-01-22T00:34:16Z", "closedAt": "2025-10-13T14:24:17Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Error after migration to glpi11", "detail": "Affected version:\n11 RC2\n\nIssue description:\nhello,\n\ni have this error since multiple beta when I try to migrate from glpi 10 to 11.\nany idea ?\n\nthanks\n\nFatal error: Uncaught Safe\\Exceptions\\InfoException: An error occurred in /var/www/html/vendor/thecodingmachine/safe/generated/Exceptions/InfoException.php:9 Stack trace: #0 /var/www/html/vendor/thecodingmachine/safe/generated/8.3/info.php(430): Safe\\Exceptions\\InfoException::createFromPhpError() #1 /var/www/html/src/Glpi/Application/SystemConfigurator.php(273): Safe\\ini_set('session.cookie_...', '1') #2 /var/www/html/src/Glpi/Application/SystemConfigurator.php(60): Glpi\\Application\\SystemConfigurator->setSessionConfiguration() #3 /var/www/html/src/Glpi/Kernel/Kernel.php(69): Glpi\\Application\\SystemConfigurator->construct('/var/www/html', NULL) #4 /var/www/html/public/index.php(66): Glpi\\Kernel\\Kernel->construct() #5 {main} thrown in /var/www/html/vendor/thecodingmachine/safe/generated/Exceptions/InfoException.php on line 9", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "No feedback, closing\n\nOriginal response date: 2025-09-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3295976045, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20632#issuecomment-3295976045", "createdAt": "2025-09-16T06:54:19Z" } }, { "userEmail": "riley.bennett@peppermint.local", "text": "Hello, I'm having the same issue.\n\nThis is happening after upgrading to GLPI 11.\n\nAlready tried updating DB via console but it did not fix. I have no plugins on the plugins directory and I use a downstream.php file, but removing it does not fix the problem. Also, SELinux is not enforcing.\n\nI use nginx as web server.\n\nOriginal response date: 2025-10-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3356359670, "author": "redddcyclone", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20632#issuecomment-3356359670", "createdAt": "2025-10-01T13:33:20Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello, I'm having the same issue.\n\nThis is happening after upgrading to GLPI 11.\n\nAlready tried updating DB via console but it did not fix. I have no plugins on the plugins directory and I use a downstream.php file, but removing it does not fix the problem. Also, SELinux is not enforcing.\n\nI use nginx as web server.\n\nCould you try with this patch ?\n\nIt will probably push some warnings in the log, we need them to be able to investigate.\n\nOriginal response date: 2025-10-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3356398945, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20632#issuecomment-3356398945", "createdAt": "2025-10-01T13:42:47Z" } }, { "userEmail": "riley.bennett@peppermint.local", "text": "Hi Skyler Adler\n\nYes, the patch did fix the problem. I did not get any warnings on the logs though. Must I check a specific log file?\n\nOriginal response date: 2025-10-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3356430667, "author": "redddcyclone", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20632#issuecomment-3356430667", "createdAt": "2025-10-01T13:46:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20632, "url": "https://github.com/glpi-project/glpi/issues/20632", "author": "damien51", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-08-12T09:42:03Z", "updatedAt": "2026-02-22T00:40:15Z", "closedAt": "2025-10-02T05:22:49Z" } }, { "title": "ITIL Category internal codes are displayed to requesters in self-service forms", "detail": "Affected version:\n11.4\n\nIssue description:\nIssue Report: Display of ITIL Category Codes in Self-Service Forms\n\n1. Description\nWe would like to report an issue related to the display of ITIL categories within self-service forms. Currently, in forms where a question is configured using the GLPI object ITIL Category (dropdown list), the internal ITIL category code is being exposed to the requester alongside the category name.\n\nScope of the issue:\n\n Location: All forms using the ITIL Category object (e.g., “Suporte Técnico”).\n User Profile: Occurs when accessed via the Requester (Self-service) profile.\n\n2. Behavior Comparison\n\n Expected Behavior\n Actual Behavior\n\n The requester should only see the category name. Internal or technical codes should remain hidden in the self-service interface to ensure a clean user experience.\n The internal ITIL category code is displayed together with the category name. This exposes internal classification logic to end users.\n\n3. Business Impact\nBeyond the immediate usability issue for requesters, this behavior significantly impacts our established business rules strategy and governance.\n\nImpact on Business Rules & Automation:\nIn previous GLPI versions and other installations we manage, we have successfully utilized the internal code logic without exposing it to the user. Our standard configuration pattern relies on the following criterion:\n\n Criterion: \"Code representing the ticket category\" > Operator: \"contains\"\n\nThis approach has been consistently used to:\n\n Apply business rules reliably.\n Automate ticket assignments.\n Control workflows and governance.\n\nConclusion:\nWith the current behavior, the visibility of internal codes in the self-service interface breaks a long-established configuration pattern. This creates both usability concerns (confusing the end-user with codes) and governance issues (exposing backend logic that was previously hidden).\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "[Image omitted]\n\nI tested it here on 11.0.4 as well, and it is indeed happening. I believe it is a bug, since this does not happen in version 10. I also use code-based rules, and since the code can be quite extensive, this will cause a visual impact and is also irrelevant information for the requester.\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3715751540, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22582#issuecomment-3715751540", "createdAt": "2026-01-06T18:08:26Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "[Image omitted]\nI tested it here on 11.0.4 as well, and it is indeed happening. I believe it is a bug, since this does not happen in version 10. I also use code-based rules, and since the code can be quite extensive, this will cause a visual impact and is also irrelevant information for the requester.\n\nThis is not a problem specific to the simplified view. I believe it is a problem with the form itself, as it also appears if you click on the question while in the form administration or when accessing it through a profile with a standard interface via the assistance tab > service catalog.\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3715791406, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22582#issuecomment-3715791406", "createdAt": "2026-01-06T18:19:52Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Not a bug. #14245 made the code and/or alias of any items visible in dropdowns including groups, entities, categories, etc.\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3716133168, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22582#issuecomment-3716133168", "createdAt": "2026-01-06T20:06:53Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "Taylor Adler Thank you for the clarification regarding PR #14245.\n\nWhile I understand the rationale and the benefit for technical profiles (Technicians/Admins) to distinguish items, forcing this display for Self-Service/Requester profiles creates a significant UX and business impact.\n\nIn many business scenarios, internal codes are strictly for backend logic and automation, and exposing them to end-users causes confusion and \"dirty\" interfaces.\n\nSuggestion: It would be extremely valuable to have a configuration option (global or per profile) to toggle the display of these codes in dropdowns. This way, we could keep the technical precision for admins without impacting the clean experience required for self-service users.\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3716189599, "author": "Robyell", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22582#issuecomment-3716189599", "createdAt": "2026-01-06T20:24:07Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22582, "url": "https://github.com/glpi-project/glpi/issues/22582", "author": "Robyell", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-06T17:33:36Z", "updatedAt": "2026-06-14T01:11:21Z", "closedAt": "2026-03-05T14:24:25Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Lost authentification SSO with Apache", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen I am logged in via SSO, an authentication request is prompted when I want to create a new ticket.\nWith previous versions, no problem.\n\nReproduction steps:\n1. Connect in SSO (Direct connect in GLPI)\n2. New ticket\n3. Popup authentification", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "noel.blair@peppermint.local", "text": "Hello,\n\nI can confirm SSO/Kerberos issues with GLPI 11.0.5 as well.\n\nWe are using Apache with libapache2-mod-auth-gssapi in an on-premises Active Directory environment, combined with HTTPS, following the configuration described here:\n\nEnvironment\nOS: Debian 13\nGLPI: 11.0.4 works, 11.0.5 breaks SSO\nInstallation: manual archive (no Docker, no Composer), located in /var/www/glpi\nPHP: 8.4.11 (Debian build)\nApache: 2.4.65 (Debian build)\n\nProblem\nUp to GLPI 11.0.4 SSO worked without issues. After upgrading to 11.0.5, SSO is no longer working correctly (no other system changes).\n\nWe also observe the same behavior as described in issue #23029 (user not logged in correctly / similar symptoms).\n\nWhat we verified\nApache/GSSAPI authentication itself seems to work and the authenticated principal is passed to PHP:\n\nAUTH_TYPE=Negotiate\nREMOTE_USER=[email redacted]\nPHP_AUTH_USER=[email redacted]\nGSS_NAME=[email redacted]\n\nSo the GSSAPI context is established and PHP receives the expected values, but GLPI 11.0.5 still does not complete the login correctly.\n\nQuestion\nWhich log files / debug output would be most useful for you to diagnose this?\nWe can provide Apache logs (access/error with auth_gssapi:debug) and GLPI logs (from files/_log/), but please let us know what you need and what to look for.\n\nThank you.\n\nOriginal response date: 2026-02-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3925436064, "author": "mikeheisenberg70", "anonymizedAuthorEmail": "noel.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23041#issuecomment-3925436064", "createdAt": "2026-02-19T08:15:23Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "The problem is still there in the version 11.0.6\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024573757, "author": "emptipat", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23041#issuecomment-4024573757", "createdAt": "2026-03-09T15:25:07Z" } }, { "userEmail": "rowan.blair@peppermint.local", "text": "Same for me, still here in 11.0.6\n\nOriginal response date: 2026-03-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4053212670, "author": "Niko-F", "anonymizedAuthorEmail": "rowan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23041#issuecomment-4053212670", "createdAt": "2026-03-13T07:04:36Z" } }, { "userEmail": "noel.blair@peppermint.local", "text": "Confirmed on 10.0.6 as well. It would be helpful if a developer could comment on this.\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4073806941, "author": "mikeheisenberg70", "anonymizedAuthorEmail": "noel.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23041#issuecomment-4073806941", "createdAt": "2026-03-17T10:12:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23041, "url": "https://github.com/glpi-project/glpi/issues/23041", "author": "emptipat", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-06T16:23:29Z", "updatedAt": "2026-05-02T06:01:35Z", "closedAt": "2026-04-29T19:13:03Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "infocom automatic job not running - Caught Error: Call to a member function getFromDB() on false", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHi,\n\nevery time the infocom job (that sends the email) tries to run, it fails with an error. And I receive an email telling me that a job couldn't be executed and that I need to check it.\n\nEnvironment details:\nRunning on a Synology NAS with latest DSM in Web Station.\n\nOperating system: Linux ds1823 4.4.302+ #​86009 SMP Wed Nov 26 18:19:20 CST 2025 x86_64\n\nPHP: 8.4.14 fpm-fcgi\n\nPHP extensions: Core, date, libxml, pcre, ctype, dom, fileinfo, filter, hash, json, mbstring, pcntl, SPL, session, PDO, random,\nreadline, Reflection, standard, SimpleXML, tokenizer, xml, xmlreader, xmlwriter, mysqlnd, cgi-fcgi, apcu, bcmath, bz2, calendar,\ncurl, dba, exif, ftp, gd, gettext, gmp, iconv, intl, mysqli, openssl, pdo_dblib, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, zlib,\nposix, shmop, soap, sockets, sodium, sysvmsg, sysvsem, sysvshm, zip, Phar, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"240\" max_input_vars=\"1000\" memory_limit=\"256M\" post_max_size=\"80M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"80M\"\n\nWeb server: Apache/2.4.63 (Unix) ()\n\nUser agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0\nSafari/537.36\n\nDatabase:\n\nServer Software: Source distribution\n\nServer Version: 10.11.11-MariaDB\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi_user@127.0.0.1:3307/glpi\n\nHost info: 127.0.0.1 via TCP/IP\n\nRequirements:\nPHP version (8.4.14) is supported.PHP version (8.4.14) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (10.11.11) is supported.Database engine version (10.11.11) is\nsupported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /volume1/web/glpi/files/_cache has been validated. Write access to\n/volume1/web/glpi/files/_cron has been validated. Write access to /volume1/web/glpi/files has been validated. Write access to\n/volume1/web/glpi/files/_graphs has been validated. Write access to /volume1/web/glpi/files/_lock has been validated. Write\naccess to /volume1/web/glpi/files/_pictures has been validated. Write access to /volume1/web/glpi/files/_plugins has been\nvalidated. Write access to /volume1/web/glpi/files/_rss has been validated. Write access to /volume1/web/glpi/files/_sessions\nhas been validated. Write access to /volume1/web/glpi/files/_tmp has been validated. Write access to\n/volume1/web/glpi/files/_uploads has been validated.Write access to /volume1/web/glpi/files/_cache has been validated.\nWrite access to /volume1/web/glpi/files/_cron has been validated.\nWrite access to /volume1/web/glpi/files has been validated.\nWrite access to /volume1/web/glpi/files/_graphs has been validated.\nWrite access to /volume1/web/glpi/files/_lock has been validated.\nWrite access to /volume1/web/glpi/files/_pictures has been validated.\nWrite access to /volume1/web/glpi/files/_plugins has been validated.\nWrite access to /volume1/web/glpi/files/_rss has been validated.\nWrite access to /volume1/web/glpi/files/_sessions has been validated.\nWrite access to /volume1/web/glpi/files/_tmp has been validated.\nWrite access to /volume1/web/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is not presentldap extension is not present\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed:\nctype, iconv, sodium.\nWrite access to /volume1/web/glpi/marketplace has been validated.Write access to\n/volume1/web/glpi/marketplace has been validated.\nTimezones seems not loaded, see\n seems not loaded, see\n\nAdditional context:\nI'm not 100% sure, but it seems that it appeared after the update of php 8.3 to 8.4.\n\nAny idea how to debug would be highly appreciated!\n\nThanks,\nViktor", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try if you reproduce without plugins.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798185072, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22821#issuecomment-3798185072", "createdAt": "2026-01-26T07:14:42Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "I have no plugins installed\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798478536, "author": "viktor-sc", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22821#issuecomment-3798478536", "createdAt": "2026-01-26T08:48:01Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Problem seems to be there is an unknown itemtype stored somewhere in your database; hard to be more precise.\n\n#22827 should fix your issue; but there are chances the problem appears elsewhere.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798745234, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22821#issuecomment-3798745234", "createdAt": "2026-01-26T09:57:24Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "Ok, strange.\nSELECT DISTINCT itemtype FROM glpi_infocoms\nretrieves this list:\n\nCartridge\nComputer\nConsumable\nEnclosure\nGlpi\\CustomAsset\\facilityequipmentAsset\nGlpi\\CustomAsset\\furnitureAsset\nGlpi\\CustomAsset\\vehicleAsset\nItem_DeviceBattery\nItem_DeviceControl\nItem_DeviceGeneric\nItem_DeviceHardDrive\nItem_DeviceMemory\nItem_DeviceNetworkCard\nItem_DevicePowerSupply\nItem_DeviceSensor\nItem_DeviceSimcard\nMonitor\nNetworkEquipment\nPDU\nPeripheral\nPhone\nPrinter\nRack\nSoftwareLicense\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3799127083, "author": "viktor-sc", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22821#issuecomment-3799127083", "createdAt": "2026-01-26T11:35:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22821, "url": "https://github.com/glpi-project/glpi/issues/22821", "author": "viktor-sc", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-25T20:58:19Z", "updatedAt": "2026-05-14T00:59:52Z", "closedAt": "2026-02-02T08:14:18Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Printer page counter history lost after upgrade from 10.0.20 to 11.0.2", "detail": "Affected version:\n11.0.2\n\nIssue description:\nAfter upgrading GLPI from 10.0.20 to 11.0.2, the printer page counter history was lost.\nBefore the upgrade, the graphs in the “Page counters” section correctly displayed the historical page counter data collected by the inventory plugin.\n\nNow, after the upgrade, the graph starts from zero after the next inventory, as if all previous data was removed or not linked to the printers anymore.\n\nExpected behavior:\nThe printer page counters (total, prints, copies, scan, etc.) and their history should remain visible after the upgrade.\n\nActual behavior:\nOld history is missing — the graph starts again from the first inventory after the update.\n\nEnvironment:\n\nGLPI version: 11.0.2\nPrevious version: 10.0.20\nPlugin: GLPI Inventory\nInstallation type: Docker", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "kendall.blair@peppermint.local", "text": "I also have the same problem with Printer page counter history after updating from 10.0.20 to 11.0.2.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3510101683, "author": "WAV-mst", "anonymizedAuthorEmail": "kendall.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21822#issuecomment-3510101683", "createdAt": "2025-11-10T08:21:56Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "If issue is related to existing data, please provide a dump of printer logs table that can be used to reproduce.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3510142311, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21822#issuecomment-3510142311", "createdAt": "2025-11-10T08:30:55Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "printerlogs_6_.sql\nprinterlogs_6.sql\nprinter_6.sql\n\nI have temporarily rolled back to GLPI 10.0.20, where these tables are working as expected. The attached files were exported from this version and include\n\nprinter_6.sql — printer information from the glpi_printers table\nprinterlogs_6.sql — related counter history from the glpi_printerlogs table (filtered by printers_id = 6)\nprinterlogs_6_.sql — initial attempt using items_id (for reference only)\n\nPlease let me know if you need any additional tables to help reproduce the issue.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3510335864, "author": "virt1122", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21822#issuecomment-3510335864", "createdAt": "2025-11-10T09:08:42Z" } }, { "userEmail": "kendall.blair@peppermint.local", "text": "Sorry for my poor English, here are my printerlog from Glpi 11.0.2\n\nglpi_printerlogs.sql\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3510802513, "author": "WAV-mst", "anonymizedAuthorEmail": "kendall.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21822#issuecomment-3510802513", "createdAt": "2025-11-10T10:47:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21822, "url": "https://github.com/glpi-project/glpi/issues/21822", "author": "virt1122", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-05T18:26:54Z", "updatedAt": "2026-03-02T00:38:43Z", "closedAt": "2025-11-12T09:29:21Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "to [11.0.6] Issue with images in knowledge bases", "detail": "Affected version:\n11.0.2\n\nIssue description:\nI can't see any image in my knownloedge bases since i have update GLPI to 11.0.2.\n\nI was in 10.0.20 and made the update today.\n\nThis is an illustration of my issues :\n\n[Image omitted]\n\nDiagnostic information:\nthis is the PHP log errors (while i display knowbase page where images are broken) :\n\n./ajax/marketplace.php:63 Glpi\\Marketplace\\Controller->installPlugin()\n...Glpi/Controller/LegacyFileLoadController.php:64 require()\n./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\n[2025-11-27 13:17:21] glpi.CRITICAL: * Uncaught PHP Exception RuntimeException: \"GenericObject plugin cannot be migrated. Please update it to the latest version.\" at container.class.php line 171\nBacktrace :\n./marketplace/fields/inc/container.class.php:171\n./marketplace/fields/hook.php:81 PluginFieldsContainer::installBaseData()\n./src/Plugin.php:1200 plugin_fields_install()\n: Plugin->install()\n./src/Glpi/Marketplace/Controller.php:670 call_user_func()\n./src/Glpi/Marketplace/Controller.php:560 Glpi\\Marketplace\\Controller->setPluginState()\n./ajax/marketplace.php:63 Glpi\\Marketplace\\Controller->installPlugin()\n...Glpi/Controller/LegacyFileLoadController.php:64 require()\n./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\n[2025-11-27 13:26:51] glpi.CRITICAL: * Error thrown while running command \"{command}\". Message: \"{message}\"\nBacktrace :\n./vendor/symfony/console/Application.php:737\n./vendor/symfony/console/Application.php:266 Symfony\\Component\\Console\\Application->find()\n./vendor/symfony/console/Application.php:175 Symfony\\Component\\Console\\Application->doRun()\n./bin/console:144 Symfony\\Component\\Console\\Application->run()\n\n[2025-11-27 13:27:06] glpi.WARNING: * Test logger\n[2025-11-27 13:27:27] glpi.WARNING: * Test logger\n[2025-11-27 13:27:40] glpi.CRITICAL: * Error thrown while running command \"{command}\". Message: \"{message}\"\nBacktrace :\n./vendor/symfony/console/Application.php:737\n./vendor/symfony/console/Application.php:266 Symfony\\Component\\Console\\Application->find()\n./vendor/symfony/console/Application.php:175 Symfony\\Component\\Console\\Application->doRun()\n./bin/console:144 Symfony\\Component\\Console\\Application->run()\n\n[2025-11-27 13:40:27] glpi.WARNING: * Test logger\n[2025-11-27 13:40:58] glpi.WARNING: * Test logger", "priority": "medium", "type": "support", "createdByEmail": "jordan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "Sames problem on our side\n\nOriginal response date: 2025-11-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3581891057, "author": "AHTW4051", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22060#issuecomment-3581891057", "createdAt": "2025-11-26T15:34:46Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide logs.\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584356141, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22060#issuecomment-3584356141", "createdAt": "2025-11-27T06:14:48Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "And also make sur to try without plugins.\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584356802, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22060#issuecomment-3584356802", "createdAt": "2025-11-27T06:15:09Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "Hello,\n\nI have tried without any plugins, and I can't see any pictures.\n\nWhat kind of log do you want? And where can I find them?\n\nThank you.\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584588807, "author": "PTG85", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22060#issuecomment-3584588807", "createdAt": "2025-11-27T07:57:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22060, "url": "https://github.com/glpi-project/glpi/issues/22060", "author": "PTG85", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-25T10:40:06Z", "updatedAt": "2026-04-30T07:29:56Z", "closedAt": "2026-04-30T07:29:26Z" } }, { "title": "An unexpected error occurred", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHi,\n\nwhen i am trying to click on the recurrent ticket i get the following error\n\nAn exception has been thrown during the rendering of a template (\"Toolbox::getFgColor(): Argument #1 ($color) must be of type string, null given\") in \"components/user/picture.html.twig\" at line 53.\nIn ./templates/components/user/picture.html.twig(53)\n#0 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#1 ./vendor/twig/twig/src/Template.php(373): Twig\\Template->display()\n#2 ./vendor/twig/twig/src/TemplateWrapper.php(51): Twig\\Template->render()\n#3 ./vendor/twig/twig/src/Extension/CoreExtension.php(1520): Twig\\TemplateWrapper->render()\n#4 ./files/_cache/11.0.1-3a9929cf-production/templates/ef/ef906063bc7e00dd8c0b1661469818d3.php(64): Twig\\Extension\\CoreExtension::include()\n#5 ./vendor/twig/twig/src/Template.php(402): TwigTemplate_76992431e575f411cedfadbc775cbfe9->doDisplay()\n#6 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#7 ./vendor/twig/twig/src/Template.php(373): Twig\\Template->display()\n#8 ./vendor/twig/twig/src/TemplateWrapper.php(51): Twig\\Template->render()\n#9 ./vendor/twig/twig/src/Extension/CoreExtension.php(1520): Twig\\TemplateWrapper->render()\n#10 ./files/_cache/11.0.1-3a9929cf-production/templates/61/610289fa74ff4158b4471d3884938bf4.php(59): Twig\\Extension\\CoreExtension::include()\n#11 ./vendor/twig/twig/src/Template.php(402): TwigTemplate_e6eae5a1951355f18a9639de9d53ce2d->doDisplay()\n#12 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#13 ./vendor/twig/twig/src/Template.php(373): Twig\\Template->display()\n#14 ./vendor/twig/twig/src/TemplateWrapper.php(51): Twig\\Template->render()\n#15 ./vendor/twig/twig/src/Extension/CoreExtension.php(1520): Twig\\TemplateWrapper->render()\n#16 ./files/_cache/11.0.1-3a9929cf-production/templates/83/8363fa5137a91d793a83b1b667a73bc1.php(144): Twig\\Extension\\CoreExtension::include()\n#17 ./vendor/twig/twig/src/Template.php(402): TwigTemplate_2a32b25da73e55bf5886a63c6ece41c0->doDisplay()\n#18 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#19 ./vendor/twig/twig/src/TemplateWrapper.php(61): Twig\\Template->display()\n#20 ./src/Glpi/Application/View/TemplateRenderer.php(188): Twig\\TemplateWrapper->display()\n#21 ./src/Ticket.php(3765): Glpi\\Application\\View\\TemplateRenderer->display()\n#22 ./src/CommonGLPI.php(683): Ticket->showForm()\n#23 ./ajax/common.tabs.php(108): CommonGLPI::displayStandardTab()\n#24 ./src/Glpi/Controller/LegacyFileLoadController.php(64): require('...')\n#25 ./vendor/symfony/http-kernel/HttpKernel.php(181): Glpi\\Controller\\LegacyFileLoadController->invoke()\n#26 ./vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n#27 ./vendor/symfony/http-kernel/Kernel.php(197): Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n#28 ./public/index.php(70): Symfony\\Component\\HttpKernel\\Kernel->handle()\n#29 {main}\n\nPrevious: Toolbox::getFgColor(): Argument #1 ($color) must be of type string, null given\nIn ./src/Toolbox.php(3116)\n#0 [internal function]: Toolbox::getFgColor()\n#1 ./src/Glpi/Application/View/Extension/PhpExtension.php(93): call_user_func_array()\n#2 ./files/_cache/11.0.1-3a9929cf-production/templates/1e/1e9e6dad64d0e6efa9687717a4b67915.php(92): Glpi\\Application\\View\\Extension\\PhpExtension->call()\n#3 ./vendor/twig/twig/src/Template.php(402): TwigTemplate_e959ee081c032298cb5d21339668255a->doDisplay()\n#4 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#5 ./vendor/twig/twig/src/Template.php(373): Twig\\Template->display()\n#6 ./vendor/twig/twig/src/TemplateWrapper.php(51): Twig\\Template->render()\n#7 ./vendor/twig/twig/src/Extension/CoreExtension.php(1520): Twig\\TemplateWrapper->render()\n#8 ./files/_cache/11.0.1-3a9929cf-production/templates/ef/ef906063bc7e00dd8c0b1661469818d3.php(64): Twig\\Extension\\CoreExtension::include()\n#9 ./vendor/twig/twig/src/Template.php(402): TwigTemplate_76992431e575f411cedfadbc775cbfe9->doDisplay()\n#10 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#11 ./vendor/twig/twig/src/Template.php(373): Twig\\Template->display()\n#12 ./vendor/twig/twig/src/TemplateWrapper.php(51): Twig\\Template->render()\n#13 ./vendor/twig/twig/src/Extension/CoreExtension.php(1520): Twig\\TemplateWrapper->render()\n#14 ./files/_cache/11.0.1-3a9929cf-production/templates/61/610289fa74ff4158b4471d3884938bf4.php(59): Twig\\Extension\\CoreExtension::include()\n#15 ./vendor/twig/twig/src/Template.php(402): TwigTemplate_e6eae5a1951355f18a9639de9d53ce2d->doDisplay()\n#16 ./vendor/twig/twig/src/Template.php(358): Twig\\Template->yield()\n#17 ./vendor/twig/twig/src/Template.php(373): Twig\\Template->display()\n#18 ./vendor/twig/twig/src/TemplateWrapper.php(51): Twig\\Template->render()\n#19 ./vendor/twig/twig/src/Extension/CoreExtension.php(1520): Twig\\TemplateWrapper->render()\n#20 ./files/_cache/11.0.1-3a9929cf-production/templates/83/8363fa5137a91d793a83b1b667a73bc1.php(144): Twig\\Extension\\CoreExtension::include()\n#21 ./vendor/twig/twig/s\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "bailey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello, could you please elaborate the scenario to reproduce the error ? Maybe some URLs or screenshots can help. Thank you.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3430922871, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21592#issuecomment-3430922871", "createdAt": "2025-10-22T07:58:35Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "Hi Jordan Blair ,\n\ni have 9 recurrent tickets configured. out of which 1 recurrent ticket is causing this issue. when the ticket is created and the assigned technician trying to open the ticket, he gets this error.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nuntill Glpi version 10.0.18 i did not have this issue.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3431102365, "author": "roshanroche", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21592#issuecomment-3431102365", "createdAt": "2025-10-22T08:36:25Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "An exception has been thrown during the rendering of a template (\"Toolbox::getFgColor(): Argument #1 ($color) must be of type string, null given\") in \"components/user/picture.html.twig\" at line 53.\n\nSounds very strange because used value comes from User::getUserInitialsBgColor() which can not return null. Are you sure your files has not been modified? Also try without plugins.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3431106763, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21592#issuecomment-3431106763", "createdAt": "2025-10-22T08:37:18Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "Hi Skyler Adler ,\n\nnothing has been modified, just upgrade from glpi 10.0.18 to glpi 11.0.11, interestingly the same technician has another recurrent ticket and it works absolutely fine with that ticket.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3431140401, "author": "roshanroche", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21592#issuecomment-3431140401", "createdAt": "2025-10-22T08:45:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21592, "url": "https://github.com/glpi-project/glpi/issues/21592", "author": "roshanroche", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-10-22T07:16:53Z", "updatedAt": "2026-02-22T00:40:21Z", "closedAt": "2025-11-13T09:14:28Z" } }, { "title": "When opening a ticket via the endpoint, I am unable to associate the requester with the New GLPI 11 API.", "detail": "Affected version:\nGLPI 11 Rc5\n\nIssue description:\nGuys, when studying the new API, from what I understand, when you open a ticket, you now need to associate the actors (such as the requester) using the “team” block in the body of the request. So,\n\nexample of a request that works:\n\n{\n “name”: “test,”\n “content”: “test,”\n “entity”: 3,\n “request_type”: 8\n}\n\nIn this example, I can open a ticket with a title, description, origin, and specific entity.\n\nBut when I try to associate a test actor to try to associate a requester in the ticket, even though the ticket is open, it does not associate. I tried to copy a complete team from an open example ticket, but without success. I also tried using the user ID, saying that he is the requester, but also without success.\n\nI tried\n\n“team”: [\n {\n “role”: “requester”,\n “name”: “lucas.levi”,\n “realname”: “LLConsultorias”,\n “firstname”: “Lucas,”\n “display_name”: “Lucas LLConsultorias,”\n “href”: “/front/user.form.php?id=156”\n }]\n\nDoes anyone know if this is an error in the API? It is not considering the team in the request even though the call is open. If the way to associate the call actor is by ID, can you tell me the correct way?\n\nBefore you ask, I looked at the documentation, but this part is not clear there. In the old API, you associated the actors by user ID.\n\nPS: I didn't find any related errors in the log.\n\nThank you in advance for your attention.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Nested properties representing linked items are all readonly except for cases where it is a single item where you are allowed to specify the ID.\n\nExample, Tickets have:\n\nYou can specify it as the following to change the entity:\n\nYou cannot currently change team members this way or other types of linked items because the way the new API handles create and update operations currently only updates the main item. Team members are each separate items with no reference to them set directly on the ticket.\n\nIf you need to set a requester besides the user authenticated to the API, you will currently need a second API call to the \"/Assistance/Ticket/{ticket_id}/TeamMember\" endpoint to add a user to the \"team\".\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3340027705, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21159#issuecomment-3340027705", "createdAt": "2025-09-26T18:47:22Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "[Image omitted]\n\nTaylor Adler I understand, but in the example ticket endpoint in the body there is an example including the “team.” If this is not possible directly when opening the ticket, then it ends up creating a misunderstanding, but okay, thanks for the feedback.\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3340115114, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21159#issuecomment-3340115114", "createdAt": "2025-09-26T19:08:06Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I wanted to avoid having at least 2 schemas for every type of item which change depending on if you are fetching or creating/updating them. It is something that needs improved in documentation at least though.\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3340442072, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21159#issuecomment-3340442072", "createdAt": "2025-09-26T20:32:45Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Yes!\n\nI'm looking for the part that responds to the solution of the call and/or satisfaction, but from the little I've seen of this new API, it seems to be incomplete. Can you confirm this?\n\nThere is more documentation for testing, but I can't find keywords such as approve solution, satisfaction, and closure in the documentation.\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3340476044, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21159#issuecomment-3340476044", "createdAt": "2025-09-26T20:45:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21159, "url": "https://github.com/glpi-project/glpi/issues/21159", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "api", "beta / rc", "need user doc" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-26T01:14:13Z", "updatedAt": "2026-01-31T00:35:52Z", "closedAt": "2025-10-22T01:47:41Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Windows IIS - UI broken after upgrade to v11.0.7 from 11.0.6", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nAfter upgrading from v11.06 to 11.07, the interface is now broken, see attached screenshot. The upgrade process used has been same as used on multiple versions since v11 introduction\n\n[Image omitted]\n\nAffected page:\nfront/central.php\n\nReproduction steps:\n[Image omitted]\nPerform upgrade of self hosted GLPI instance from 11.0.6 to 11.0.7. The setup succeeds including DB update (tried web UI DB update and php bin/console db:update commandline approaches).\n\nEnvironment details:\nThis installation is running on windows/IIS:", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "morgan.bennett@peppermint.local", "text": "Additional: When activating Debug Mode, the UI returns to normal as per attached screenshot.\n\n[Image omitted]\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4349355989, "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24070#issuecomment-4349355989", "createdAt": "2026-04-30T02:50:31Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This sounds like a cache related issue. Make sure you clean GLPI and browser caches.\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4350010450, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24070#issuecomment-4350010450", "createdAt": "2026-04-30T05:51:07Z" } }, { "userEmail": "reese.blair@peppermint.local", "text": "I have the same problem and clean the cache don't resolve it\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4350287362, "author": "RegiloDeLaVega", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24070#issuecomment-4350287362", "createdAt": "2026-04-30T06:51:42Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "And it also does not explain why activating debug mode seems to resurrect the issue.\n\nNote also that when in 'failed' state, the UI is defaulting to dashboard edit mode as well\n\n--Andrew\n\nFrom: RegiloDeLaVega *@*.*>\nSent: Thursday, 30 April 2026 2:52 PM\nTo: glpi-project/glpi *@*.*>\nCc: Curtis, Andrew *@*.*>; Author *@*.*>\nSubject: Re: [glpi-project/glpi] Upgrade to v11.0.7 from 11.0.6 breaks interface (Issue #24070)\n\n[]RegiloDeLaVega left a comment (glpi-project/glpi#24070)\n\nI have the same problem and clean the cache don't resolve it\n\n-\nReply to this email directly, view it on GitHub, or unsubscribe.\nTriage notifications on the go with GitHub Mobile for iOS or Android.\nYou are receiving this because you authored the thread.Message ID: *@*.@*.*>>\n\nThis message and any attached files may contain information that is confidential and/or subject of legal privilege intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein. If you have received this message in error please notify the sender immediately and delete the message.\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4350308277, "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24070#issuecomment-4350308277", "createdAt": "2026-04-30T06:55:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24070, "url": "https://github.com/glpi-project/glpi/issues/24070", "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-30T02:43:50Z", "updatedAt": "2026-05-04T07:43:00Z", "closedAt": "2026-05-04T07:43:00Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Virtualization on Computer issue - still exist problem", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nThe issue persists after upgrading to version 11.0.5.\n\n[Image omitted]\n\nIn previous versions, the last column (\"Machine\") correctly displayed the inventoried computer name (e.g., Comp-000).\n\nCurrently, while the first column correctly shows the name from the virtualization system (e.g., the Proxmox VM name Windows-10), the linked computer field fails to show the associated asset name (Comp-000) .\nColumn \"Machine\" just duplicate column \"Virtualization model\"\n\n It was working correctly in version 11.0.1-3.\n\nI can still see the linked asset information after clicking on the VM, but this is an unnecessary extra step that wasn't required before. The linked name should be visible directly in the main list, as it was in previous versions.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "If you upgraded by overwriting files (not recommended), double check new files all have been uploaded.\nMake sure to clean cache also.\n\nPlease give original ticket reference.\n\nOriginal response date: 2026-02-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3892467936, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23102#issuecomment-3892467936", "createdAt": "2026-02-12T17:52:09Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "I am deleting all GLPI files and directories, excluding the glpi/marketplace and glpi/plugins folders, as well as the glpi/inc/downstream.php file (which defines the custom paths for config, files, and logs). Everything else is being wiped and replaced with a clean installation files.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3895367782, "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23102#issuecomment-3895367782", "createdAt": "2026-02-13T07:32:18Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "OK, got it.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3895466738, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23102#issuecomment-3895466738", "createdAt": "2026-02-13T07:57:24Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "See #23105\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3895519188, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23102#issuecomment-3895519188", "createdAt": "2026-02-13T08:12:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23102, "url": "https://github.com/glpi-project/glpi/issues/23102", "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-12T16:22:42Z", "updatedAt": "2026-05-25T01:03:58Z", "closedAt": "2026-02-13T13:20:40Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "MySQL Error when trying to update to 11.0.4", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen we try to update our GLPI from v11.0.2 to 11.0.4, we get this error.\n[Image omitted]\n\nAny idea?", "priority": "medium", "type": "maintenance", "createdByEmail": "bailey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Seems like you run update twice. If an update fails, you have to drop the database, restore the backup of the previous version, and try upgrade again.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612242603, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22235#issuecomment-3612242603", "createdAt": "2025-12-04T13:22:10Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "i have the same error : MySQL query error: Duplicate entry 'Printer-1225-2025-10-19' for key 'unicity' (1062) in SQL query \"UPDATE glpi_printerlogs SET itemtype = 'Printer' WHERE itemtype = ''\".\nIam sure that i run update once - my glpi is on VM and i got snapshoot before i start upgrade. So i can restore my job before i start.\nI restore my machine twice and i get the same error twice . looks like bug\n\nReturned to 11.0.2 version\nRun conole database check and check integrity and its ok for version 11.0.2 .\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3614743671, "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22235#issuecomment-3614743671", "createdAt": "2025-12-04T23:38:00Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Dakota Bennett could you please give the output of the following query:\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3615468308, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22235#issuecomment-3615468308", "createdAt": "2025-12-05T06:17:10Z" } }, { "userEmail": "taylor.blair@peppermint.local", "text": "I seem to have the same problem.\n\nUsing docker with glpi/glpi:11.0.2 image, tried to update to 11.0.3 and 11.0.4.\n\nError:\n\n|id|itemtype|items_id|total_pages|bw_pages|color_pages|rv_pages|prints|bw_prints|color_prints|copies|bw_copies|color_copies|scanned|date|date_creation|date_mod|faxed|\n|--|--------|--------|-----------|--------|-----------|--------|------|---------|------------|------|---------|------------|-------|----|-------------|--------|-----|\n|3458||109|8102|0|4683|240|0|0|0|0|0|0|0|2025-10-19|2025-10-19 00:23:11.000|2025-10-19 00:23:11.000|0|\n|3497|Printer|109|8102|0|4683|240|0|0|0|0|0|0|0|2025-10-19|2025-10-19 20:51:48.000|2025-10-19 20:51:48.000|0|\n\nHaven't done anything fancy with the install, plugin list below.\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3616166455, "author": "lameslime", "anonymizedAuthorEmail": "taylor.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22235#issuecomment-3616166455", "createdAt": "2025-12-05T10:07:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22235, "url": "https://github.com/glpi-project/glpi/issues/22235", "author": "meijin4", "anonymizedAuthorEmail": "bailey.adler@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "inventory" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-04T13:11:48Z", "updatedAt": "2026-05-07T00:55:09Z", "closedAt": "2026-01-26T12:50:25Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI 11.0.1 ticket : The Reply button no longer appears when it is resolved or the approval request no longer appears", "detail": "Affected version:\nglpi 11.0.1\n\nIssue description:\nWhen a technician provides the solution on a ticket, the status changes to “Resolved,” but it seems that the Reply button disappears. In version 10, this button used to be available even when the ticket was marked as resolved, allowing the user to respond if the issue wasn’t actually fixed — for example:\n\nThe user had 3 days to reply to this ticket (in standard or simplified profile). If the user responded, the status was no longer in resolved mode.\n\n[Image omitted]\n\nReproduction steps:\n1 . Create ticket\n2 . solve ticket\n3 . The Reply button no longer appears when the ticket is resolved.", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello, did the requester accept the solution provided ? I reproduced the steps you gave, and the Reply button disappeared on my side once the requester approves the given solution by the tech.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400610013, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21461#issuecomment-3400610013", "createdAt": "2025-10-14T08:11:02Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "maybe this probleme mode simplified ? Case KO\n[Image omitted]\n\nmode standard user\n[Image omitted]\ncase OK\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400708709, "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21461#issuecomment-3400708709", "createdAt": "2025-10-14T08:31:31Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "It seems to me that in version 10, we could reply without having to check this box in order to respond.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400782041, "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21461#issuecomment-3400782041", "createdAt": "2025-10-14T08:51:53Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "I just compared the behaviour in 10.0.20, in the ticket interface itself, and it seems to be the same on 11.0.1. Haven't checked on the list view, let me do the comparison again.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400827957, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21461#issuecomment-3400827957", "createdAt": "2025-10-14T09:03:59Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21461, "url": "https://github.com/glpi-project/glpi/issues/21461", "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-14T06:49:06Z", "updatedAt": "2026-04-16T00:51:32Z", "closedAt": "2026-01-05T09:58:30Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Incorrect encoding for Cyrillic", "detail": "Affected version:\n11.0.2\n\nIssue description:\nGood afternoon. When collecting data from a PC using the GLPI agent, Cyrillic characters are displayed incorrectly. I've attached a screenshot.\nI'm also having trouble with clickable elements in tables. For example, I can't even access the settings for an existing location (I can't click them).\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Accessing locations will be fixed in next version, this issues already has been reported several times.\n\nFor encoding issue, please provide an inventory file.\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584410684, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22083#issuecomment-3584410684", "createdAt": "2025-11-27T06:41:12Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "В случае проблем с кодировкой предоставьте файл инвентаризации.\n\nWhich file exactly needs to be identified, please tell me?\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584446441, "author": "tattami", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22083#issuecomment-3584446441", "createdAt": "2025-11-27T06:58:34Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "We need the data agent send to server; see agent documentation to export it.\n\nIt's also possible to get it from the GLPI UI, but it may already been corrupted; so agent raw data is better.\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584540508, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22083#issuecomment-3584540508", "createdAt": "2025-11-27T07:39:41Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "It's also possible to get it from the GLPI UI, but it may already been corrupted; so agent raw data is better.\n\nglpi-agent.log\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584620673, "author": "tattami", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22083#issuecomment-3584620673", "createdAt": "2025-11-27T08:06:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22083, "url": "https://github.com/glpi-project/glpi/issues/22083", "author": "tattami", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-27T06:18:17Z", "updatedAt": "2026-03-19T00:41:02Z", "closedAt": "2025-12-08T12:41:56Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Can't select the TTO or TTR", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen we create/modify a ticket, the TTR/TTO or internal ttr/tto can not be select or input.\n\n[Image omitted]\n\nAffected page:\nfront/ticket\n\nReproduction steps:\n1. click the assistance of the left menu\n2. click the \"Create ticket\" or \"Tickets\"-\"Add\" button on the top\n3. on the left side, all the box of the service levels", "priority": "medium", "type": "support", "createdByEmail": "bailey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.blair@peppermint.local", "text": "Same problem on my test base after update GLPI 11.0.2\n\n[Image omitted]\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3497919576, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21833#issuecomment-3497919576", "createdAt": "2025-11-06T15:44:20Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate this issue. Was it working correctly in an earlier version of GLPI 11?\n\nDo you have any errors in the browser console (F12 key > Console tab) when viewing the ticket?\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3499995029, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21833#issuecomment-3499995029", "createdAt": "2025-11-07T00:47:51Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "I cannot recreate this issue. Was it working correctly in an earlier version of GLPI 11?\n\nDo you have any errors in the browser console (F12 key > Console tab) when viewing the ticket?\n\nIn GLPI10, on problem on this, but in GLPI 11 and GLPI 11.0.2, we have same issue.\n\nBelow is the screenshot of the browser console.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3500045857, "author": "DWXXX", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21833#issuecomment-3500045857", "createdAt": "2025-11-07T01:14:00Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "> I cannot recreate this issue. Was it working correctly in an earlier version of GLPI 11?\n> Do you have any errors in the browser console (F12 key > Console tab) when viewing the ticket?\n\nIn GLPI10, on problem on this, but in GLPI 11 and GLPI 11.0.2, we have same issue.\n\nBelow is the screenshot of the browser console.\n[Image omitted] [Image omitted] [Image omitted]\n\nAbove message is from edge, below is from Firefox.\n\nMouseEvent.mozInputSource is deprecated,please use PointerEvent.pointerType。\n\n[Image omitted]\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3500065069, "author": "DWXXX", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21833#issuecomment-3500065069", "createdAt": "2025-11-07T01:23:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21833, "url": "https://github.com/glpi-project/glpi/issues/21833", "author": "DWXXX", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-06T11:35:22Z", "updatedAt": "2026-03-07T00:36:59Z", "closedAt": "2025-11-26T15:13:27Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "form problem", "detail": "Affected version:\n11.0.0\n\nIssue description:\nSo, I'm not sure if this is normal, if it's designed this way, or if it's a bug. In version 10.0.0, when creating a form, we could offer the user several choices, and depending on their selection, some questions would appear or disappear based on filters we had configured. However, some of these hidden questions were marked as required, which didn't prevent the form from being submitted (in version 10.0.0). But in version 11.0.0, these hidden (and supposedly irrelevant) required questions, when they do appear, block the form submission because the system considers that not all required questions have been answered, which is frustrating when the form is otherwise complete. We are forced to mark these questions as required because sometimes users forget to answer them. We've noticed that this doesn't cause a problem if the section is at the top of the form, but if the user selects a section further down, it causes a problem. The only solution we've found is to split our forms, for example, into three separate forms.\n\nReproduction steps:\n1. Create a form\n2. Create more than 2 sections\n3. Add display filters; for example, if a certain checkbox is selected, display a specific question (required), and vice versa for other questions\n4. Fill out the form from the user's perspective, trying to trigger the display of the lower sections\n\nEnvironment details:\nOperating system: Linux SRV-GLP-04 6.12.48+deb13-amd64 #​1 SMP PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20) x86_64\n\nPHP: 8.4.11 fpm-fcgi\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\ncgi-fcgi, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv,\nintl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer,\nxmlreader, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"8M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"2M\"\n\nWeb server: Apache/2.4.65 (Debian) (Apache/2.4.65 (Debian) Server at 10.1.4.17 Port 80)\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0\n\nDatabase:\n\nServer Software: -- Please help get to 10k stars at\n\nServer Version: 11.8.3-MariaDB-0+deb13u1 from Debian\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION", "priority": "medium", "type": "bug", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "[Image omitted]\n\nOriginal response date: 2025-10-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3366401643, "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21287#issuecomment-3366401643", "createdAt": "2025-10-03T16:41:58Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "For example: Request type: software or hardware\nIf software: display this section with its required questions\nIf hardware: display this section with its required questions (this specific section order must be maintained)\nIf the user selects \"hardware\" and fills out the form: error (as indicated in the previous message)\nSame applies for software\nHardware and software are two separate sections\n\nOriginal response date: 2025-10-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3366418027, "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21287#issuecomment-3366418027", "createdAt": "2025-10-03T16:46:11Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hidden mandatory question should be ignored, I've tried a simple form and it seems OK:\n\n[Image omitted]\n\nWhen I open the form, my mandatory question is not shown:\n[Image omitted]\n\nI can submit the form without issues:\n[Image omitted]\n\nDo you have a specific form you could export so I can try it on my side?\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3371961636, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21287#issuecomment-3371961636", "createdAt": "2025-10-06T14:25:03Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Yes, but as stated earlier, the best way to create the problem is to create multiple sections containing mandatory questions. The first section asks which section to display: in my case, application or hardware (I should point out that this choice proposed in the first section calls the other sections, not displayed by default). These sections, which will be called, as you will have understood, are hidden. If I choose \"hardware\" (which, when creating the form, is under \"software\"), the rest of the hardware-specific form will be revealed. It is only when submitting the form that it crashes. I hope I am clear\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3372131368, "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21287#issuecomment-3372131368", "createdAt": "2025-10-06T14:55:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21287, "url": "https://github.com/glpi-project/glpi/issues/21287", "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "bug", "forms", "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-03T16:39:13Z", "updatedAt": "2026-01-22T00:34:23Z", "closedAt": "2025-10-13T13:04:37Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "It's possible to add & update an Operating System to a Computer with all fields empty", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello,\nIt's possible to add/update an empty form on \"Operating Systems\" tab of an asset:\n\nIt even updates the tab with the operating system count.\n\nIf all fields are empty, the Operating System should be unlinked/deleted from asset.\n\nAffected page:\n\nReproduction steps:\n1. Go to Assets > Computer tab.\n2. Create or select an existing Computer.\n3. Go to Operating Systems tab.\n4. Fill no fields and click on [Add].\n5. The same behavior happens when updating with empty fields.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "While I may agree form no OS should be added when no field is set; there is no \"unlink\" notion between OS and computers - and I really do not see valable reason to add that.\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3817663167, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22897#issuecomment-3817663167", "createdAt": "2026-01-29T13:21:13Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Yes, not sure how to express it, but I'm sure it's not a link, but there's some kind of association between an OS and an asset, as it increases the counter on tab.\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3817710457, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22897#issuecomment-3817710457", "createdAt": "2026-01-29T13:30:40Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "While I may agree form no OS should be added when no field is set; there is no \"unlink\" notion between OS and computers - and I really do not see valable reason to add that.\n\nThere is partial support for multiple operating systems though, at least from the API. I wonder if it should have the implementation finished or enforce only 1 Item_OperatingSystem per asset.\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3817715548, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22897#issuecomment-3817715548", "createdAt": "2026-01-29T13:31:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do think that implementation should not enforce only 1 Item_OperatingSystem per asset. Some appliances (e.g. Aruba Mobility controllers) have two OS partitions, that may contain a different OS version, but SNMP inventory tools maybe gather this information and fill those information on Operating Systems tab of the asset. There's other appliances that contains similar behavior, like SIEMENS industrial routers, Cisco Catalyst supervisors, Juniper MX/QFX with dual Routing Engines, and Endian UTM firewalls often have firmware dual partitions: one active and one backup or factory/default vs customized for recovery.\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3818297616, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22897#issuecomment-3818297616", "createdAt": "2026-01-29T15:08:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22897, "url": "https://github.com/glpi-project/glpi/issues/22897", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-29T13:02:00Z", "updatedAt": "2026-06-04T12:28:31Z", "closedAt": "2026-06-04T12:16:43Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Forms are unable to create tickets after upgrading to GLPI 11.0.6", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAfter upgrading GLPI to version 11.0.6, all forms stopped creating tickets. The issue affects every form submission, making it impossible to generate new tickets through the form interface.\n\nSteps to Reproduce:\n\nAccess any existing form\nFill in the required fields\nSubmit the form\n\nExpected Behavior:\nA new ticket should be created successfully after form submission.\n\nActual Behavior:\nThe request fails with a 500 Internal Server Error on the endpoint:\n\nPOST /Form/SubmitAnswers\n\nNo ticket is created.\n\nAdditional Information:\n\nError observed in browser console:\n\nPOST /Form/SubmitAnswers 500 (Internal Server Error)\nThe issue started immediately after upgrading to GLPI 11.0.6\nPreviously, forms were working correctly\nLikely related to backend processing (PHP error or plugin compatibility)\n\nAffected page:\n\nReproduction steps:\nSteps to Reproduce:\n\nLog in to GLPI\nNavigate to Forms (or Formcreator interface)\nOpen any available form\nFill in all required fields with valid data\nClick on Submit\n\nEnvironment details:\nGLPI version: 11.0.6\nWeb server: Apache\nPHP version: 8.3\nDatabase: MySQL/MariaDB", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Devon Blair,\n\nThere should be an error in your server logs, specifically in the php-errors.log file.\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4111642123, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23576#issuecomment-4111642123", "createdAt": "2026-03-23T15:46:35Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "yes:\n ./src/CronTask.php:887 PendingReasonCron::cronPendingreason_autobump_autosolve()\n ./front/cron.php:166 CronTask::launch()\n ./vendor/symfony/http-kernel/HttpKernel.php:101 Glpi\\Controller\\LegacyFileLoadController->{closure}()\n ...ymfony/http-foundation/StreamedResponse.php:106 Symfony\\Component\\HttpKernel\\HttpKernel::Symfony\\Component\\HttpKernel\\{closure}()\n ./vendor/symfony/http-foundation/Response.php:423 Symfony\\Component\\HttpFoundation\\StreamedResponse->sendContent()\n ./src/Glpi/Kernel/Kernel.php:295 Symfony\\Component\\HttpFoundation\\Response->send()\n ./public/index.php:73 Glpi\\Kernel\\Kernel->sendResponse()\n\n[2026-03-23 14:33:38] glpi.WARNING: * Test logger\n[2026-03-23 14:34:37] glpi.WARNING: * Test logger\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4111786292, "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23576#issuecomment-4111786292", "createdAt": "2026-03-23T16:07:29Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "I think the log in php-error-logs has nothing to do with the situation. I enabled debugging mode and it didn't show any errors on the screen either. The situation occurred after migrating from version 10.0.18 to 11.0.6. I performed the update and ran the command to migrate the forms to the core. After that, all existing forms stopped generating tickets.\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4112777278, "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23576#issuecomment-4112777278", "createdAt": "2026-03-23T18:22:23Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Can you clear the log file, press the submit form button then check the logs again?\n\nThe errors above seems unrelated, and the No route found for \"GET \": Method Not Allowed (Allow: POST) message doesn't make sense unless you are manually going to the /Form/SubmitAnswer page instead of clicking the submit button.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4117074582, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23576#issuecomment-4117074582", "createdAt": "2026-03-24T10:29:30Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23576, "url": "https://github.com/glpi-project/glpi/issues/23576", "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-23T13:31:40Z", "updatedAt": "2026-05-07T12:58:43Z", "closedAt": "2026-03-24T13:30:25Z" } }, { "title": "Misaligned description field in change template", "detail": "Affected version:\n11.0.2\n\nEnvironment:\nGLPI 11.0.2 - Theme: Vintage - Browser: Brave (Shields off) - OS: Debian 12 (server) - Windows 11 (client)\n\nIssue:\nIn Assistance > Changes > Change templates > [Template] > Predefined field, the Description input field is cut off and the Add button overlaps. Layout breaks in Vintage theme, also tried in Light Blue and Auror themes, same thing.\n\nExpected:\nField and button align cleanly without overlap.\n\nActual:\nDescription input is truncated and seems to be displayed vertically instead of horizontally.\n\nNotes:\n* Clearing cache or switching browsers doesn’t fix it.\n* Also happens on my colleagues computers.\n* Had the issue in 11.0.1, updated to 11.0.2 and still have the issue.\n\nAffected page:\n\nReproduction steps:\n1. Open any Change Template.\n2. Go to Predefined fields tab.\n3. Observe misalignment of Description field and Add button.\n\nEnvironment details:\n[Image omitted]\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Could you share a screenshot of the issue?\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3524469575, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21893#issuecomment-3524469575", "createdAt": "2025-11-13T00:17:30Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Original response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3527469262, "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21893#issuecomment-3527469262", "createdAt": "2025-11-13T11:56:32Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Taylor Adler I added an image of the issue\n\nOriginal response date: 2025-11-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3548565767, "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21893#issuecomment-3548565767", "createdAt": "2025-11-18T16:47:02Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "any updates on this? It's kind of annoying of having to write the text on a separate notepad then copy pasting it into the window :/\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3559666316, "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21893#issuecomment-3559666316", "createdAt": "2025-11-20T19:20:30Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21893, "url": "https://github.com/glpi-project/glpi/issues/21893", "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [ "good first issue", "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-12T10:07:52Z", "updatedAt": "2026-05-08T00:54:34Z", "closedAt": "2026-01-27T08:21:50Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 11 : Forms / Date and Time / No Time in calendar", "detail": "Affected version:\n11.02\n\nIssue description:\nHello. In a form, when you want a date and time, a calendar comes but without the time, it's not the same as GLPI 10.\n\nCalendar forms glpi 10 - GLPI 11.pdf\n\nReproduction steps:\nCreate a form in GLPI 11.02.\nMake a question with Date and Time., ask for Date and Time\nTest the Form, the calendar has no time to select. In Glpi 10 Time was in the calendar.", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Avery Blair,\n\nThis is something we did on purpose, the calendar \"widget\" has been replaced by the default date picker from your browser.\n\nWe thought it was similar enough, is this really an issue on your side?\nThe time can be added directly in the input after the date since it is just two numbers.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3520872582, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21852#issuecomment-3520872582", "createdAt": "2025-11-12T09:12:02Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Hello Avery Blair,\n\nThis is something we did on purpose, the calendar \"widget\" has been replaced by the default date picker from your browser.\n\nWe thought it was similar enough, is this really an issue on your side? The time can be added directly in the input after the date since it is just two numbers.\n\nIs there a technical reason not to use Flatpickr to match the look and feel of the other date/time fields in GLPI?\nThe native date/time input controls work very differently between browsers. Chrome has no picker while Firefox does but doesn't have the time inside the picker.\n\nUnless Flatpickr had some technical issues, and maybe even then, I think it should be used here as well to have a consistent user experience across the entire app, regardless of the browser.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521473273, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21852#issuecomment-3521473273", "createdAt": "2025-11-12T11:31:44Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Apparently the lack of a time picker in Firefox is a bug, but my comment is still relevant.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521476984, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21852#issuecomment-3521476984", "createdAt": "2025-11-12T11:32:53Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Chrome has no picker\n\nAre you sure? I tested on my side on it does seem to have one.\n\nI think it should be used here as well to have a consistent user\n\nIt was discussed with Taylor Adler at the time and we wanted to see if we could remove flatpicker everywhere so this was a step in this direction.\n\n(It was a while ago so opinions may have changed since then)\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521883464, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21852#issuecomment-3521883464", "createdAt": "2025-11-12T13:14:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21852, "url": "https://github.com/glpi-project/glpi/issues/21852", "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-07T09:18:58Z", "updatedAt": "2026-03-20T00:39:17Z", "closedAt": "2025-12-09T13:04:21Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "Unable to Select Status for \"If the asset status is\" and \"Status to apply\" under Agent Cleanup", "detail": "Affected version:\nGLPI 11.0.1\n\nIssue description:\nUnder Administration -> Inventory\n\nBoth Dropdowns unable to filter for existing statuses:\n[Image omitted]\n\nAffected page:\n/front/inventory.conf.php\n\nReproduction steps:\n1. Click on Administration\n2. Click on Inventory\n3. Select unter Agent Cleanup - Action -> Change the status\n4. Try to select a status under \"if the asset status is:\" or \"Status to apply:\"", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "noel.bennett@peppermint.local", "text": "Have you tried to add new status with \"+\" icon?\nI've tested it and after adding new status, it is still not appearing.\n\nIn my case it just automatically puts \"All\" once I'm selecting \"Change the status\"\n\n[Image omitted]\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432348390, "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21604#issuecomment-3432348390", "createdAt": "2025-10-22T13:22:53Z" } }, { "userEmail": "jamie.bennett@peppermint.local", "text": "I tried to create a new status using both \"+\" icons. The statuses were successfully created:\n[Image omitted]\nHowever, under \"Status to apply\", I'm unable to select them. All visibility settings are set to \"Yes\":\n[Image omitted]\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432401761, "author": "ghost", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21604#issuecomment-3432401761", "createdAt": "2025-10-22T13:35:48Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide logs, as requested.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432414565, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21604#issuecomment-3432414565", "createdAt": "2025-10-22T13:38:16Z" } }, { "userEmail": "jamie.bennett@peppermint.local", "text": "Skyler Adler Done. Added the relevant log.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432463543, "author": "ghost", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21604#issuecomment-3432463543", "createdAt": "2025-10-22T13:48:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21604, "url": "https://github.com/glpi-project/glpi/issues/21604", "author": "ghost", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-22T13:14:37Z", "updatedAt": "2026-02-02T00:39:41Z", "closedAt": "2025-10-24T08:48:08Z" } }, { "title": "Printer page counters are not showing anything", "detail": "Affected version:\n11.0.1\n\nIssue description:\nPrinter scanned with snmp is not showing \"Page counters\" properly even if there is some data. Attaching .csv exported from graph from GLPI\nprinter_counter.csv\n\n[Image omitted]\n\nAffected page:\n/front/printer.form.php\n\nEnvironment details:\nGLPI: 11.0.1 ( => /var/www/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: OK", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "noel.bennett@peppermint.local", "text": "We started using it only from GLPI 11.0.1 so don't know if it was working in previous versions\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3410092996, "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21519#issuecomment-3410092996", "createdAt": "2025-10-16T09:54:37Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I'll take an eye to reproduce; and I'll see if that was already existing in v10.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3410097952, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21519#issuecomment-3410097952", "createdAt": "2025-10-16T09:56:04Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "i have log for this :\n[Image omitted]\n\n[Image omitted]\n\nglpi.WARNING: * Warning: array_sum(): Addition is not supported on type array at PrinterLog.php line 286\n Backtrace :\n ./src/PrinterLog.php:286\n ./src/PrinterLog.php:82 PrinterLog->showMetrics()\n ./src/CommonGLPI.php:694 PrinterLog::displayTabContentForItem()\n ./ajax/common.tabs.php:108 CommonGLPI::displayStandardTab()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3410434411, "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21519#issuecomment-3410434411", "createdAt": "2025-10-16T11:31:51Z" } }, { "userEmail": "rowan.blair@peppermint.local", "text": "Isn't this exactly the same as #20530 ?\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3410882288, "author": "kmpm", "anonymizedAuthorEmail": "rowan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21519#issuecomment-3410882288", "createdAt": "2025-10-16T13:24:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21519, "url": "https://github.com/glpi-project/glpi/issues/21519", "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-16T09:53:29Z", "updatedAt": "2026-01-30T00:37:49Z", "closedAt": "2025-10-21T09:09:31Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Various errors when trying to use GLPI 11 RC5 webhooks", "detail": "Affected version:\nGLPI 11 RC5\n\nIssue description:\nGood afternoon everyone, I ran some tests sending call data to an n8n webhook post to see what data would come through, but errors occurred in both attempts. In the first attempt, I tried the new call event, and in the second, the new follow-up , and in both cases, I got this error message:\n\n[Image omitted]\n\nSome errors appeared in the logs (I'll leave them below).\n\nWhen I returned to the created webhook, it also displayed an error screen.\n\n[Image omitted]\n\nIn the last test, I saw that there is a button to test the result of the event from a call, which also gave an error in the logs (I will leave it below).\n\n[Image omitted]\n\nI also noticed that the event was not created in the webhook queue and the webhook cron is running normally every minute.\n\nAffected page:\n/front/webhook.form.php?\n\nReproduction steps:\n1. Use GLPI 11 rc5\n2. Activate a webhook with some type of event (new follow-up, new call, etc.)\n3. Define the Post URL that will receive the call data\n4. The expected result would be for the webhook to be sent with the ticket data", "priority": "medium", "type": "bug", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Hello, the warnings and critical Uncaught PHP Exception TypeError: \"Illegal offset type\" will be fixed in #21181\n\nI couldn't reproduce the issue with critical ($api_data) must be of type array, null given (your first error in the output)\n\nDo you have more information on how to reproduce it ?\n\nI've tried creating a webhook on new ITILFollowup and I don't get that error.\nDid you created a custom payload ?\n\nOriginal response date: 2025-09-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3346118066, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21168#issuecomment-3346118066", "createdAt": "2025-09-29T10:11:19Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Taylor Adler Hello, no, I used the default load that it creates. I tried both new tracking and left ‘new event’ and also new call and new solution in version 11 RC5.\n\nI want to emphasize that in this case, the environment I am using was GLPI version 10, which I updated to the new version 11. I don't know if this is relevant.\n\nOriginal response date: 2025-09-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3347139788, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21168#issuecomment-3347139788", "createdAt": "2025-09-29T14:00:27Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "New test on 09/29\n\nI created a notification for a new follow-up\n\n[Image omitted]\n\nError within the call when I added the tracking:\n[Image omitted]\n\nErrors that appear in the log regarding this event:\n\n_\nglpi.WARNING: * Warning: Undefined array key \"parent\" at Webhook.php line 922\n Backtrace :\n ./src/Webhook.php:922\n ./src/Webhook.php:941 Webhook::getAPISchemaBySupportedItemtype()\n ./ajax/webhook.php:173 Webhook::getMonacoSuggestions()\n ...Glpi/Controller/LegacyFileLoadController.php:63 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n_\nglpi.WARNING: * Warning: Undefined array key \"parent\" at Webhook.php line 922\n Backtrace :\n ./src/Webhook.php:922\n ./src/Webhook.php:941 Webhook::getAPISchemaBySupportedItemtype()\n ./ajax/webhook.php:173 Webhook::getMonacoSuggestions()\n ...Glpi/Controller/LegacyFileLoadController.php:63 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\n_\n\nglpi.WARNING: * Warning: Undefined array key \"\" at Webhook.php line 922\n Backtrace :\n ./src/Webhook.php:922\n ./src/Webhook.php:941 Webhook::getAPISchemaBySupportedItemtype()\n ./ajax/webhook.php:173 Webhook::getMonacoSuggestions()\n ...Glpi/Controller/LegacyFileLoadController.php:63 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n_\nglpi.WARNING: * Warning: Undefined array key \"\" at Webhook.php line 922\n Backtrace :\n ./src/Webhook.php:922\n ./src/Webhook.php:941 Webhook::getAPISchemaBySupportedItemtype()\n ./ajax/webhook.php:173 Webhook::getMonacoSuggestions()\n ...Glpi/Controller/LegacyFileLoadController.ph\n\n[Content truncated.]\n\nOriginal response date: 2025-09-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3347240489, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21168#issuecomment-3347240489", "createdAt": "2025-09-29T14:16:59Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "After the error occurs when returning to the webhook event I created, I can no longer navigate through the tabs; this message appears on all of them.\n\n[Image omitted]\n\nOriginal response date: 2025-09-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3347248561, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21168#issuecomment-3347248561", "createdAt": "2025-09-29T14:18:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21168, "url": "https://github.com/glpi-project/glpi/issues/21168", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [ { "sourceLogin": "froozeify", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "beta / rc", "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-27T15:19:10Z", "updatedAt": "2026-01-22T00:35:05Z", "closedAt": "2025-10-13T05:53:15Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "GLPI 11.0.x migration from genericobject to core - php RAM usage - memory limit", "detail": "Issue description:\nFor my migration, with memory limit 20GB migration crash with memory error - standard 2G.\n\nphp -d memory_limit=20G bin/console migration:genericobject_plugin_to_core\n\nI'll test it with a higher value once I get more RAM, but it looks like there's no optimization here.", "priority": "high", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "What a great, efficient and helpful description.\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4313414071, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24007#issuecomment-4313414071", "createdAt": "2026-04-24T13:05:32Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Could you give some details about your generic object plugin usage like the number of custom objects and the number of fields they have?\n\nPlease also include the information requested by the bug report template. Even if there isn't an error being raised here, some of the things asked like \"Your GLPI setup information\" specifically are still relevant.\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4313452167, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24007#issuecomment-4313452167", "createdAt": "2026-04-24T13:11:56Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Taylor Adler\n\ncustom object: 14\nItems in asset: 15 000,300,300,2 500,100,6 000,35 000,300,35 000,600,1 100,3 000,50,100\n(The problem is that this data is no longer show in GLPI since the migration to GLPI 11.0.4 — it is from host predates the migration.)\nOther:\nGLPI Log table - about 56GB\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4313752022, "author": "Wolvverine", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24007#issuecomment-4313752022", "createdAt": "2026-04-24T13:59:54Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Requested information are still missing.\n\nSee\n\nOriginal response date: 2026-04-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4324894160, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24007#issuecomment-4324894160", "createdAt": "2026-04-27T07:01:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24007, "url": "https://github.com/glpi-project/glpi/issues/24007", "author": "Wolvverine", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback", "performance" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-24T13:01:48Z", "updatedAt": "2026-05-05T12:50:34Z", "closedAt": "2026-05-05T12:50:34Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Public Forms do not work with Webhook function (Error)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.5\n\nIssue description:\nWe have one webhook role what change one information in historic of new tickets after open. When i create one ticket with one public form and my user is autenticated, the ticket work, the webhook rule work and is all rigth, but, when i create one ticket no autenticated with my user, the ticker is created but show one error menssage say \"the Webhook do not read\", show de ID ticket for user and the script in this case not work.\n\nUser Autenticated with sucess in Webhook rulers\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nUser not autenticated with webhook error\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. Create any webhook and any rule for new ticket actions\n2. Open one public form no autenticated user with the public URL for this form.\n3. open de ticket\n4. refresh the page\n\nEnvironment details:\nGLPI 11.0.5", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with latest stable release.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4140697765, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23647#issuecomment-4140697765", "createdAt": "2026-03-27T07:24:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Harper Bennett,\n\nI've tried with a simple public form and a simple webkook and it works fine on my side:\n\nWebhook config:\n[Image omitted]\n\nSubmitting a simple public form:\n[Image omitted]\n\nData is collected without issue by the webhook target:\n[Image omitted]\n\nThere must be something related to your webhook itself, maybe it is not configured correctly.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4141101326, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23647#issuecomment-4141101326", "createdAt": "2026-03-27T08:53:03Z" } }, { "userEmail": "harper.bennett@peppermint.local", "text": "Adrien, good morning, how are you?\n\nFirst of all, thank you for your attention and reply.\n\nWhen you registered the ticket via the public catalog, as soon as you clicked \"Submit\" and received the message that the ticket was successfully created, did you refresh the page and there was no error message indicating that the webhook wasn't working? And did the ticket that was successfully opened through the public catalog receive the changes that your webhook is supposed to process normally?\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4142622584, "author": "wesleipedroza", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23647#issuecomment-4142622584", "createdAt": "2026-03-27T13:35:34Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "When you registered the ticket via the public catalog, as soon as you clicked \"Submit\" and received the message that the ticket was successfully created, did you refresh the page and there was no error message indicating that the webhook wasn't working?\n\nYes, there was no errors.\n\nAnd did the ticket that was successfully opened through the public catalog receive the changes that your webhook is supposed to process normally?\n\nIt was successfully opened, I am not sure what you mean that \"receive the changes that your webhook is supposed to process normally\". Are you using GLPI's API to modify the ticket itself with a webhook? I am not sure this is officially recommended, this kind of modification are usually handled by the ticket's rules instead.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4143188352, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23647#issuecomment-4143188352", "createdAt": "2026-03-27T14:53:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23647, "url": "https://github.com/glpi-project/glpi/issues/23647", "author": "wesleipedroza", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-26T14:51:21Z", "updatedAt": "2026-07-11T00:41:55Z", "closedAt": "2026-04-01T16:06:39Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI 11.0.1 Bug when editing a knowledge base entry", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHello,\n\nI'm experiencing a problem using edit mode on a knowledge base entry in GLPI.\n\nWhen I fill out a entry enough for the vertical scroll bar to appear, then return to edit mode, abnormal behavior occurs the first time I enter edit mode. If I position the cursor at the bottom of the entry (or lower than the initial page height) to add text, the page automatically moves back to the middle, making editing difficult.\n\nThis automatic scrolling only occurs once, when I start editing the entry.\n\nThank you in advance for your help.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm. Focusing on the TinyMCE field causes it to center the view on it/the label.\n\nIssue is with the TinyMCE library, not GLPI.\n\nRef:\n\nCaused by a workaround they added:\n\nBehavior seems to match their workaround given I can only reproduce the issue in Chrome and not Firefox.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3407942956, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21506#issuecomment-3407942956", "createdAt": "2025-10-15T19:23:31Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Yes, that's right. I tried it here, and when I enter edit mode, scroll to the bottom, and click inside the knowledge base, it moves up to the middle of the screen on its own. This happens the first time you access the base, enter edit mode, scroll to the bottom, and click with the mouse inside the base.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3407963753, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21506#issuecomment-3407963753", "createdAt": "2025-10-15T19:31:08Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "Thank you for your feedback.\n\nI have a quick question, perhaps off-topic.\n\nAre there any plans to upgrade the editing mode to allow multiple people to edit a document simultaneously, with real-time updates?\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409530520, "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21506#issuecomment-3409530520", "createdAt": "2025-10-16T07:21:16Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "I also add that the Tab key does not work correctly in the editor.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3410781958, "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21506#issuecomment-3410781958", "createdAt": "2025-10-16T12:59:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21506, "url": "https://github.com/glpi-project/glpi/issues/21506", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "javascript", "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-15T19:09:21Z", "updatedAt": "2026-06-20T01:05:48Z", "closedAt": "2026-03-11T08:50:49Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Upon changing category of the ticket - getting error in php-error.log", "detail": "Affected version:\n11.0.4\n\nIssue description:\nI have checked the db - havent found any issues via ITIcategories table.\nI have only 1 entity root, its id is 0 and correctly specified in the ITILcategories table.\n\nWhile at the same time - no issues with functionality and no problems of using or saving/updating ticket.\nJust the error that is always logged in the logs whenever changing the category on the ticket.\n\nAny advices?\n\nAffected page:\n\nReproduction steps:\n1 Create ticket\n2 Assign a category to ticket / change category on ticket\n3 Check php-error.log", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce, please try without plugins (no idea if you use any since you do not provide requested system information).\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3668866005, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22420#issuecomment-3668866005", "createdAt": "2025-12-18T07:53:30Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "I do not reproduce, please try without plugins (no idea if you use any since you do not provide requested system information).\n\nOh sorry, here is the system info, also i have tried deleting the plugins, but did not see differences\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3668887451, "author": "KirillLd", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22420#issuecomment-3668887451", "createdAt": "2025-12-18T07:57:31Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Since I do not reproduce, I have no idea what's wrong. It may be related to a conf on your side, or a database contents, or...\nWe need a way to reproduce on a fresh instance.\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3668972226, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22420#issuecomment-3668972226", "createdAt": "2025-12-18T08:16:55Z" } }, { "userEmail": "taylor.blair@peppermint.local", "text": "### What happens / errors observed\n\nWhen updating a ticket (e.g. changing the category), two errors are logged:\n\n1. PHP warning:\nUndefined array key \"entities_id\" at CommonITILObject.php line 8361\n\n2. MySQL error (Fields plugin container values):\nMySQL query error: Duplicate entry 'Ticket-0-5' for key 'itemtype_item_container' (1062)\nSQL: INSERT INTO glpi_plugin_fields_ticketnchamadodofornecedors\n (plugin_fields_containers_id, items_id, nchamadodofornecedorfield, entities_id)\n VALUES ('5', '0', '', '50')\n\nBacktrace shows this happens during update:\nfront/ticket.form.php(90) -> CommonDBTM->update()\n-> PluginFieldsContainer::preItemUpdate() / updateFieldsValues() / add()\n\n---\n\n### Why it happens (explanation)\n\nDuring the update flow in front/ticket.form.php (around line 90), GLPI does:\n\n$_POST = $track->enforceReadonlyFields($_POST);\n$track->update($_POST);\n\nenforceReadonlyFields() can remove fields from the submitted input, and in this case it may remove entities_id.\nRight after that, update() is called without entities_id.\n\nInside the update pipeline, prepareInputForUpdate() calls:\n$input = $this->handleTemplateFields($input);\n\nTemplate handling (and related predefined fields logic) expects entities_id to be present in the options/input.\nIf it is missing, GLPI logs the warning \"Undefined array key entities_id\".\n\nAdditionally, because entities_id is missing/incorrect at some point, plugins (like Fields) may compute or use\nwrong context/options and end up attempting to insert container values with an unexpected items_id (seen as 0)\nand the same (itemtype, item, container) combination, triggering the unique key:\nitemtype_item_container => Duplicate entry 'Ticket-0-5'.\n\nSo: the root problem is that entities_id is not reliably present in the POST input during update, and that breaks\ndownstream logic (templates + plugin hooks), causing noisy warnings and potentially incorrect plugin inserts.\n\n---\n\n### Workaround / proposed fix\n\nEnsure entities_id is always present BEFORE calling enforceReadonlyFields() and update().\n\nPatch example in front/ticket.form.php:\n\n} elseif (isset($_POST['update'])) {\n if (!$track::canUpdate()) {\n throw new AccessDeniedHttpException();\n }\n\n // Ensure entities_id is present before readonly enforcement / template handling\n if (!isset($_POST['entities_id']) && isset($track->fields['entities_id'])) {\n $_POST['entities_id'] = $track->fields['entities_id'];\n }\n\n $_POST = $track->enforceReadonlyFields($_POST);\n $track->\n\n[Content truncated.]\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3772525108, "author": "ojeaaan", "anonymizedAuthorEmail": "taylor.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22420#issuecomment-3772525108", "createdAt": "2026-01-20T11:58:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22420, "url": "https://github.com/glpi-project/glpi/issues/22420", "author": "KirillLd", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-18T07:51:08Z", "updatedAt": "2026-05-02T00:52:59Z", "closedAt": "2026-01-21T06:38:25Z" } }, { "title": "GLPI 11 : Trash button not working on ticket", "detail": "Affected version:\n11.0.0\n\nIssue description:\nHello,\n\nNothing happens when you check the box to view the trash in tickets.\n\nReproduction steps:\ntry to check trash on ticket page", "priority": "medium", "type": "support", "createdByEmail": "quinn.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI cannot reproduce.\n\nCould you check if you have a javascript issue in your browser console ? Is there any GLPI log related to this ?\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3380089445, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21309#issuecomment-3380089445", "createdAt": "2025-10-08T07:19:55Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "At page load:\n\nOn click:\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3380128393, "author": "tguichard25", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21309#issuecomment-3380128393", "createdAt": "2025-10-08T07:32:49Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce nor have any JS error on my side. Could you please tests without any plugins to be sure this is not one of them that cause the issue?\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3380135939, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21309#issuecomment-3380135939", "createdAt": "2025-10-08T07:35:28Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "same result with all plugins disabled.\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3380143772, "author": "tguichard25", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21309#issuecomment-3380143772", "createdAt": "2025-10-08T07:38:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21309, "url": "https://github.com/glpi-project/glpi/issues/21309", "author": "tguichard25", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-06T14:57:05Z", "updatedAt": "2026-03-01T00:44:13Z", "closedAt": "2025-11-20T11:11:46Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Will tickets opened by other users be released by default to requesters? GLPI 11 rc5", "detail": "Contribution description:\nGood afternoon, everyone. I have a question here that I don't know if it's a bug or a feature that hasn't been developed properly:\n\nI noticed that in the new version of the form, this feature has been activated, opening a ticket for myself or another user.\n\n[Image omitted]\n\nWell, I noticed that it is also active in the applicant view (self-service). I checked the profile permissions and the global and/or entity settings, and apparently there is no way to disable this button (in my opinion, it should be optional).\n\nIt allows you to open a ticket for another user, and the ticket remains visible after it is opened for the user who opened it, even on behalf of another user.\n\n[Image omitted]\n\nIf it is something that cannot be disabled, it will have an impact in some scenarios because, although it is a discreet button, there are several types of operations in GLPI, such as companies where the ticket is opened by an external customer, etc. In my opinion, this should be an optional checkbox on the form (which makes more sense).\n\nI also looked in the form settings to see if there was anything I could disable, but I couldn't find anything. I noticed that when creating a new form, it automatically creates this open button called by myself or someone else.\n\nVersion : GLPI 11 Rc5", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello, this feature is not entirely related to forms (it already existed in GLPI 10 but was hidden when you used formcreator).\n\nThis is what we call \"delegation\" and it is only active if you are the delegatee of a group:\n\n[Image omitted]\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3319136419, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21081#issuecomment-3319136419", "createdAt": "2025-09-22T13:44:33Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Hey Skyler Adler , I tested it here and it's true that if the person is in a group, it unlocks that box. But in my opinion, this should be disregarded, just like in version 10. It could be left as an optional question, and if the person wants to open a ticket for someone else, they can unlock it.\n\nIn any case, those who use this feature are usually technicians in forms, apart from opening tickets by the user. If we base it on version 10, the scenario would be a question within the GLPI object type form > users.\n\nMy suggestion is to keep it as it is in version 10. Thank you for your attention.\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3319368171, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21081#issuecomment-3319368171", "createdAt": "2025-09-22T14:24:42Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I want to clarify, this is not just about being in a group, this is about being a \"delegatee\" in a group.\nAs far as I known, this is the only use case of being a \"delegatee\" in a group, so if you do not want the feature I think you should remove all your delegatees as they don't serve another purpose anyway.\n\nI understand that if you used formcreator before it might seem normal to remove this feature to be coherent but we also have many users that never used formcreator and expect the opposite and would complain if it is missing.\n\nI think there are no others alternative that to review your groups and remove the delegatees.\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3319441545, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21081#issuecomment-3319441545", "createdAt": "2025-09-22T14:35:04Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Skyler Adler I understand, thank you for your response. Actually, it was good to clarify this function for me, because I didn't understand the explanation anywhere else or on any forum. Now I understand that delegating means opening a ticket for another user, correct? And not including them doesn't affect the profile/service part, right?\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3319461201, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21081#issuecomment-3319461201", "createdAt": "2025-09-22T14:38:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21081, "url": "https://github.com/glpi-project/glpi/issues/21081", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" }, { "sourceLogin": "ccailly", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "beta / rc", "forms", "question" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-20T18:33:38Z", "updatedAt": "2026-02-23T00:40:01Z", "closedAt": "2025-09-23T05:33:19Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Kanban Global not charging", "detail": "Affected version:\n11.0.1 - Docker Container\n\nIssue description:\nHello,\nUsing the GLPI user in the internal database, I can add project statuses to the global Kanban. Refresh the page. Everything works. With other LDAP Super-Admin users in the same entity, access to projects works. The global Kanban works, but as soon as you add a status to the page, it's impossible to return to the page. It loads in a loop.\n\nEnvironment details:\nDocker Image 11.0.1 officiel\n\nAdditional context:\nIn the browser in console mode, I have this warning:\n[Vue warn]: Unhandled error during execution of setup function\n at \n at \n at \nPromise.then\n(anonymous) @ project.form.php?showglobalkanban=1:4499\n\nAnd this, in error :\nUncaught (in promise) TypeError: Cannot read properties of undefined (reading 'length')\n at Object. (Kanban.vue:468:76)\n(anonymous) @ Kanban.vue:468\nXMLHttpRequest.send\neval @ VM1708:380\nobj. @ VM1708:181\nloadColumn @ Kanban.vue:444\n(anonymous) @ Kanban.vue:370\nXMLHttpRequest.send\neval @ VM1708:380\nobj. @ VM1708:181\nloadState @ Kanban.vue:345\n(anonymous) @ Kanban.vue:1286\nsetup @ Kanban.vue:1286\nPromise.then\n(anonymous) @ project.form.php?showglobalkanban=1:4499", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Can you test #21572?\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3426180663, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21568#issuecomment-3426180663", "createdAt": "2025-10-21T11:44:03Z" } }, { "userEmail": "harper.bennett@peppermint.local", "text": "How can i try locallly in docker container ?\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3426261739, "author": "Pixels-IT", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21568#issuecomment-3426261739", "createdAt": "2025-10-21T12:05:33Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Actually, it probably isn't so easy since it is in a file that needs built and those dependencies aren't included with release versions.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3426311345, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21568#issuecomment-3426311345", "createdAt": "2025-10-21T12:18:47Z" } }, { "userEmail": "harper.bennett@peppermint.local", "text": "Okay, so I wait? :)\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3426324745, "author": "Pixels-IT", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21568#issuecomment-3426324745", "createdAt": "2025-10-21T12:22:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21568, "url": "https://github.com/glpi-project/glpi/issues/21568", "author": "Pixels-IT", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-21T10:03:16Z", "updatedAt": "2026-01-31T00:35:46Z", "closedAt": "2025-10-22T08:19:35Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "API Broken after upgrading to 11.0.7 - \"An error occurred\" at SessionException.php", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nOne of our service provider is using GLPI API to sync their software with our GLPI Instance, they cannot use the API anymore\n\nReproduction steps:\nHere is what they do on their side:\n\nSession Initialization\n\nGET /initSession\n\nParams: app_token, user_token\n\nReturns: A session_token to be used in all subsequent calls.\n\nTicket Search\n\nGET /search/Ticket\n\nParams: Filter criteria by update date (between two dates), pagination (range)\n\nReturns: A list of tickets with their total count.\n\nRetrieve a Ticket\n\nGET /Ticket/{id}\n\nReturns: Title, creation date, closure date, status, description, priority.\n\nRetrieve Ticket Comments\n\nGET /Ticket/{id}/ITILFollowup\n\nReturns: List of ticket follow-ups: ID, date, author, content.\n\nAdd a Comment\n\nPOST /ITILFollowup\n\nRequest Body:\n\nitemtype: \"Ticket\"\nitems_id: GLPI ticket ID\nusers_id: 281 (Bot user)\ncontent: Comment text (format: \"date : author (type) message\")\nis_private: 0 (public comment)\n\nUpdate Ticket Status\n\nPUT /Ticket/{id}\n\nRequest Body:\n\nstatus: Numeric value of the new status\n\nRetrieve a User\n\nGET /User/{id}\n\nReturns: ID, first name, last name.\n\nUse case: Identify the author of a ticket or comment.", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "cameron.blair@peppermint.local", "text": "I have the same issue\n\nOriginal response date: 2026-05-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4464462254, "author": "j-guevara-m", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24211#issuecomment-4464462254", "createdAt": "2026-05-15T23:19:20Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Please post your GLPI Setup Information. The original report shows a massive number of alterations to the GLPI code files which makes it difficult to troubleshoot and be sure this is indeed a bug and not an issue with custom changes.\n\nOriginal response date: 2026-05-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4464983514, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24211#issuecomment-4464983514", "createdAt": "2026-05-16T01:26:40Z" } }, { "userEmail": "jamie.bennett@peppermint.local", "text": "We did not changed a single line of code in GLPI. We are using the file from the 11.0.7 zip file.\n\nOriginal response date: 2026-05-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4465931436, "author": "SteadEXE", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24211#issuecomment-4465931436", "createdAt": "2026-05-16T06:04:51Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Maybe not, but something caused GLPI to think a bunch of files were missing.\n\nOriginal response date: 2026-05-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4466482872, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24211#issuecomment-4466482872", "createdAt": "2026-05-16T09:38:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24211, "url": "https://github.com/glpi-project/glpi/issues/24211", "author": "SteadEXE", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-13T08:30:53Z", "updatedAt": "2026-06-30T11:59:14Z", "closedAt": "2026-06-30T11:59:14Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Log from which position a user is removed", "detail": "Contribution description:\nWhen adding a requester, observer and technician assignments in a ticket, the position the user is assigned to is logged. But when removing a user from a position the position is not logged.\nCombined with the fact that users are added first the log the appears to be in the wrong order.\nI would like adding the position the user is removed from to the log", "priority": "low", "type": "feature", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "When opening an issue; please use template and fill all requested information; thank you.\n\nOriginal response date: 2025-09-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3305859890, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21059#issuecomment-3305859890", "createdAt": "2025-09-18T07:38:00Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Skyler Adler I used the template for contribution request ? As I would not consider it a bug more of an improvement I'm willing to contribute if the glpi team is interested / considers it useful. Was this the wrong approach?\n\nOriginal response date: 2025-09-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3305889992, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21059#issuecomment-3305889992", "createdAt": "2025-09-18T07:42:15Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Oh... I did not understand this was a feature proposal you plan to work on. Sorry, I reopen.\n\nI can't say if that change is or not interesting, I'll let someone else take a look.\n\nOriginal response date: 2025-09-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3305929324, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21059#issuecomment-3305929324", "createdAt": "2025-09-18T07:50:08Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I would like adding the position the user is removed from to the log\n\nPlease yes, you can submit a PR for that.\n\nOriginal response date: 2025-09-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3306338580, "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21059#issuecomment-3306338580", "createdAt": "2025-09-18T08:52:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21059, "url": "https://github.com/glpi-project/glpi/issues/21059", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "tograss", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "enhancement" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-18T07:33:48Z", "updatedAt": "2026-03-07T00:37:01Z", "closedAt": "2025-11-26T10:36:38Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Slowness after updating GLPI 10.0.20 to GLPI 11.0.1", "detail": "Affected version:\n11.0.1\n\nIssue description:\nAfter updating a GLPI 10.0.20 instance to GLPI 11.0.1 (around 90,000 tickets), we are experiencing significant slowness when searching for tickets.\nEach search can take several seconds or more, whereas the same environment running GLPI 10.0.20 + MySQL 5.7.44 had no slowdown.\n\nEnvironment\n\n- GLPI: 11.0.1\n- Database: MySQL 9.4 (migrated from MySQL 5.7.44)\n- System: Debian 12\n- Data volume: ~90,000 tickets\n\nObservations\n\nThe issue seems directly related to the MySQL upgrade, because :\n- GLPI 10.0.20 with MySQL 5.7 works normally.\n- As soon as we switch to a more recent version of MySQL (8 or 9), searches become noticeably slower.\n- The same phenomenon has already been observed on other environments after migrating from 5.7 to 8.x+.\n\nChecks performed\n- Execution of the command:\nphp bin/console db:check_schema_integrity\nNo issues detected.\n\n- Analysis and optimization of MySQL statistics (ANALYZE TABLE) without significant improvement.\n- No specific plugin affecting performance.\n\nQuestion\n\nIs this behavior known with MySQL 8+ / 9 ?\nAre there any recommended adjustments (indexes, SQL parameters, GLPI configuration) to restore the performance previously observed under MySQL 5.7 ?", "priority": "high", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I don't know about any specific MySQL issues. I personally use MariaDB.\n\nIf you could enable debug mode (from the top-right dropdown menu while connected as a Super-Admin), you should have some more performance metrics in the debug toolbar which could help identify the cause.\n\n[Image omitted]\nDebug toolbar buttons from left to right (only the first 4 are relevant):\n1. Server performance - This will tell you the page load time and memory usage from the server's point of view\n2. SQL requests - Every SQL request made on the current page\n3. HTTP Requests - The initial page load and all AJAX requests made for the current page. On the right side of this panel, you can see the server performance, SQL requests and profiler data (execution times of specific sections of code) specific to that request.\n4. Client Performance - This shows a bunch of client-side metrics like how long it takes to render the page and memory usage\n\nOriginal response date: 2025-10-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3418886345, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21542#issuecomment-3418886345", "createdAt": "2025-10-18T22:30:53Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Search all tickets and number of lines per page = 1000 :\n\n- GLPI 10.0.20 MySQL 5.7.44 :\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n- GLPI 11.0.1 MySQL 9.4\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-10-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3419050423, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21542#issuecomment-3419050423", "createdAt": "2025-10-18T23:10:14Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "I ran two MySQL query analyses using the same search criteria.\n\nGLPI 11.0.1 - MySQL 9.4 query :\n\nGLPI 11.0.1 - MySQL 9.4 analysis :\n\nGLPI 10.0.20 - MySQL 5.7.44 query :\n\nGLPI 10.0.20 - MySQL 5.7.44 analysis :\n\nOriginal response date: 2025-10-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3419539778, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21542#issuecomment-3419539778", "createdAt": "2025-10-19T09:57:16Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Hello, while we're on the subject, can you confirm whether your operations are also experiencing slowdowns in service as a whole? When entering a call, when clicking on reply/task, etc. If you want to take a look, I have an open issue with this subject, and all feedback is welcome: #21115\n\nOriginal response date: 2025-10-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3420070774, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21542#issuecomment-3420070774", "createdAt": "2025-10-19T23:56:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21542, "url": "https://github.com/glpi-project/glpi/issues/21542", "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [ "performance", "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-18T22:21:51Z", "updatedAt": "2026-02-04T00:36:07Z", "closedAt": "2025-10-26T14:58:34Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Bug/Evolution", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nIn legacy formcreator, I could add itemtypes to be available in itemtypes : Cluster, Datacenter,\n Datacenter::class => Datacenter::getTypeName($plural),\n Cluster::class => Cluster::getTypeName($plural),\n\nI tried to do the same thing in form, updating src/glpi/form/questiontype/questiontypeitem.php\n\n[Image omitted]\n\nRack, datacenter, Cluster are not visible in itemtypes dropdown of forms\n\nBut, when adding these values in $CFG_GLPI['management'] (src/autoload/cfg_GLPI.php -> I can see these items in dropdown.\n\nHow about the custom plugin whose object have to be seen in forms ?", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Casey Blair, you should be able to add values into $CFG_GLPI['asset_types'] / $CFG_GLPI['asset_types'] / $CFG_GLPI['management_types'] / $CFG_GLPI['tools_types'] / $CFG_GLPI['admin_types'] directly in your plugin code.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4117660001, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23372#issuecomment-4117660001", "createdAt": "2026-03-24T12:03:18Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Hello\nIn fact, plugin formcreator had been set in core of GLPI.\nAnd the lines you see ar lines from core itself -> I tried to update lines in core/form to to the same thing it was done in formcreator plugin : Adding Cluster, for instance to be used in the new core form of GLPI.\nthanks\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4120415940, "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23372#issuecomment-4120415940", "createdAt": "2026-03-24T18:16:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "You should not modify code from GLPI's core, it is better to write a plugin instead.\n\nIn your plugin's init function, you can add:\n\nThen it show up as expected:\n\n[Image omitted]\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4124758322, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23372#issuecomment-4124758322", "createdAt": "2026-03-25T08:42:33Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "I understand your point : no problem\nnevertheless,\nI have no plugin for that : in V10, I used formcreator and in formcreator plugin I used to propose Skyler Adler to add assets (like appliance, cluster and so on ) for those assets may be used in formcreator plugin.\n\nas formcreator plugin had been migrated into core : it will be good to add cluster, DCroom and so on in order those assets to be used in form...\n\nWhat i don't understand :\nwhy by updating $cfg_glpi (and adding asset in asset_types in config) this update doesn't impact form : we don't see the added assets.\nBut updating the form core by adding manually assets : then assets are seen in forms...\n\nthanks\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4125067186, "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23372#issuecomment-4125067186", "createdAt": "2026-03-25T09:34:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23372, "url": "https://github.com/glpi-project/glpi/issues/23372", "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-05T13:13:43Z", "updatedAt": "2026-07-10T00:48:27Z", "closedAt": "2026-03-31T15:01:02Z" } }, { "title": "[11.0.4] SQL Syntax Error in Budget Items tab (glpi_consumables.0 AS is_deleted)", "detail": "Affected version:\n11.0.4\n\nIssue description:\n[Image omitted]\n\nAfter upgrading from GLPI 10.0.x to GLPI 11.0.4, accessing the \"Items\" tab within a Budget causes an \"Unexpected Error\" (red banner).\n\nThe logs indicate a SQL syntax error generated by the query builder regarding the glpi_consumables table. It seems the system is incorrectly appending the table name to a constant value (glpi_consumables.0) in the SELECT clause.\n\nReproduction steps:\n1. Go to Management > Budgets.\n2. Open any existing Budget (that potentially has linked items or consumables).\n3. Click on the Items tab (left menu).\n4. The error \"An expected error occurred\" appears immediately.\n\nDiagnostic information:\nThe php-errors.log shows the following Critical Exception:\n\nshell\n[2026-01-17 01:08:24] glpi.CRITICAL: * Uncaught PHP Exception RuntimeException: \"MySQL query error: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '.0 AS is_deleted, glpi_consumables.NULL AS serial, glpi_consumables.N...' at line 1 (1064) in SQL query \"SELECT * FROM ((SELECT 'Consumable' AS _itemtype, glpi_consumables.id, glpi_consumables.entities_id, glpi_consumables.0 AS is_deleted, ...\n\nAffected page:\nhttps/glpimodel/front/budget.form.php?id=6\n\nReproduction steps:\n1. Go to Management > Budgets.\n2. Open any existing Budget (that potentially has linked items or consumables).\n3. Click on the Items tab (left menu).\n4. The error \"An expected error occurred\" appears immediately.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce. First, try without any plugins. If you still reproduce, please provide full log stack trace when the issue happens.\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3766870605, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22727#issuecomment-3766870605", "createdAt": "2026-01-19T07:30:58Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "I have captured the full stack trace with *Debug Mode enabled and all plugins disabled*.\n\nThe error is indeed a SQL Syntax error generated within src/Budget.php.\nSpecifically, inside the query builder, the system is prepending the table name glpi_consumables to the constant value 0, resulting in the invalid syntax glpi_consumables.0.\n\nStack Trace:\n\ntext\nMySQL query error: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '.0 AS is_deleted, glpi_consumables.NULL AS serial, glpi_consumables.N...' at line 1 (1064) in SQL query \"SELECT * FROM ((SELECT 'Consumable' AS _itemtype, glpi_consumables.id, glpi_consumables.entities_id, glpi_consumables.0 AS is_deleted, ...\n\nIn ./src/DBmysql.php(392)\n#0 ./src/DBmysqlIterator.php(125): DBmysql->doQuery()\n#1 ./src/DBmysql.php(1061): DBmysqlIterator->execute()\n#2 ./src/Budget.php(463): DBmysql->request()\n#3 ./src/Budget.php(120): Budget->showItems()\n#4 ./src/CommonGLPI.php(694): Budget::displayTabContentForItem()\n#5 ./ajax/common.tabs.php(108): CommonGLPI::displayStandardTab()\n#6 ./src/Glpi/Controller/LegacyFileLoadController.php(64): require('...')\n#7 ./vendor/symfony/http-kernel/HttpKernel.php(181): Glpi\\Controller\\LegacyFileLoadController->invoke()\n#8 ./vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n#9 ./vendor/symfony/http-kernel/HttpKernel.php(197): Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n#10 ./public/index.php(70): Symfony\\Component\\HttpKernel\\Kernel->handle()\n\nLog:\nMySQL query error: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '.0 AS is_deleted, glpi_consumables.NULL AS serial, glpi_consumables.N...' at line 1 (1064) in SQL query \"SELECT * FROM ((SELECT 'Consumable' AS _itemtype, glpi_consumables.id, glpi_consumables.entities_id, glpi_consumables.0 AS is_deleted, glpi_consumables.NULL AS serial, glpi_consumables.NULL AS otherserial, NULL AS devices_id, glpi_infocoms.value FROM glpi_infocoms INNER JOIN glpi_consumables ON (glpi_consumables.id = glpi_infocoms.items_id) WHERE glpi_infocoms.itemtype = 'Consumable' AND glpi_infocoms.budgets_id = '6' AND (true) ORDER BY glpi_consumables.entities_id) UNION ALL (SELECT 'Contract' AS _itemtype, glpi_contracts.id, glpi_contracts.entities_id, glpi_contracts.is_deleted, NULL AS serial, NULL AS otherserial, NULL AS de\n\n[Content truncated.]\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3767784995, "author": "wctrjunior", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22727#issuecomment-3767784995", "createdAt": "2026-01-19T11:10:58Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I still do not reproduce. Maybe there are some data/relation/configuration missing on my instance.\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3768297478, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22727#issuecomment-3768297478", "createdAt": "2026-01-19T13:18:12Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "I still do not reproduce. Maybe there are some data/relation/configuration missing on my instance.\n\nI believe the key factor here is the upgrade process versus a fresh install. My instance was upgraded from 10.0.x to 11.0.x. The data causing the crash (Budget linked to a Consumable) was created in version 10.\n\nIf you create a fresh install of GLPI 11 and add a consumable, the issue might not appear because the database structure/relations are native to v11.\n\nTo reproduce accurately, please try:\n\nInstall GLPI 10.0.19.\n\nCreate a Budget.\n\nCreate a Consumable.\n\nGo to Management > Budgets > (Select Budget) > Main tab: Add the Consumable to the budget (generating an entry in glpi_infocoms).\n\nUpgrade this instance to GLPI 11.0.4.\n\nGo to Management > Budgets > (Select Budget) > Items tab.\n\nTechnical Insight: The error glpi_consumables.0 suggests that glpi_consumables table does not have an is_deleted column, so the code tries to inject a static 0 value. However, the Query Builder erroneously prefixes this static value with the table name (resulting in syntax error), likely because it's iterating over a union of tables where other tables (like glpi_contracts) DO have the is_deleted column.\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3774668808, "author": "wctrjunior", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22727#issuecomment-3774668808", "createdAt": "2026-01-20T19:53:24Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22727, "url": "https://github.com/glpi-project/glpi/issues/22727", "author": "wctrjunior", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-19T01:20:48Z", "updatedAt": "2026-07-05T00:53:39Z", "closedAt": "2026-03-26T20:59:29Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Custom field \"date\" decreases each time an asset is saved", "detail": "Affected version:\n11.x\n\nIssue description:\nThe date in the custom field decreases each time an asset is recorded (or each time an object is modified without necessarily changing the date).\n\nReproduction steps:\n1. Create a custom asset\n2. Add a custom date field\n3. Create an object in this asset and put a date\n4. Save and look at the date decrementing (save multiple time and see the date decrementing multiple time)\n\nEnvironment details:\nGLPI: 11.0.1 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: fr_FR\nOperating system: Linux 51e8d181c965 6.12.0-55.37.1.el10_0.x86_64 #​1 SMP PREEMPT_DYNAMIC Fri Oct 3 16:07:46 UTC 2025 x86_64\n\nPHP: 8.4.13 fpm-fcgi\n\nPHP extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, ctype, curl, dom, fileinfo, filter, hash, iconv, json,\nmbstring, SPL, session, PDO, pdo_sqlite, bz2, posix, random, readline, Reflection, standard, SimpleXML, tokenizer, xml,\nxmlreader, xmlwriter, mysqlnd, cgi-fcgi, mysqli, pdo_mysql, gd, intl, exif, zip, Phar, ldap, bcmath, sodium, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"300\" max_input_vars=\"5000\" memory_limit=\"512M\" post_max_size=\"60M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"50M\"\n\nWeb server: Apache/2.4.65 (Unix) ()\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 12.0.2-MariaDB-ubu2404\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpidb_user@mariadb/glpi\n\nHost info: mariadb via TCP/IP\n\nRequirements:\nPHP version (8.4.13) is supported.PHP version (8.4.13) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (12.0.2) is supported.Database engine version (12.0.2) is supported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/pod/glpi/files/_cache has been validated. Write access to\n/var/pod/glpi/files/_cron has been validated. Write access to /var/pod/glpi/files has been validated. Write access to\n/var/pod/glpi/files/_graphs has been validated. Write access to /var/pod/glpi/files/_lock has been validated. Write access to\n/var/pod/glpi/files/_pictures has been validated. Write access to /var/pod/glpi/files/_plugins has been validated. Write access\nto /var/pod/glpi/files/_rss has been validated. Write access to /var/pod/glpi/files/_sessions has been validated. Write access\nto /var/pod/glpi/files/_tmp has been validated. Write access to /var/pod/glpi/files/_uploads has been validated.Write access\nto /var/pod/glpi/files/_cache has been validated.\nWrite access to /var/pod/glpi/files/_cron has been validated.\nWrite access to /var/pod/glpi/files has been validated.\nWrite access to /var/pod/glpi/files/_graphs has been validated.\nWrite access to /var/pod/glpi/files/_lock has been validated.\nWrite access to /var/pod/glpi/files/_pictures has been validated.\nWrite access to /var/pod/glpi/files/_plugins has been validated.\nWrite access to /var/pod/glpi/files/_rss has been validated.\nWrite access to /var/pod/glpi/files/_sessions has been validated.\nWrite access to /var/pod/glpi/files/_tmp has been validated.\nWrite access to /var/pod/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed:\nctype, iconv, sodium.\nWrite access to /var/pod/glpi/files/plugins has been validated.Write access to\n/var/pod/glpi/files/plugins has been validated.\nTimezones seems loaded in database.Timezones seems loaded in database.\n\nGLPI_ROOT: \"/var/www/html/glpi\"\nGLPI_VERSION: \"11.0.1\"\nGLPI_SCHEMA_VERSION: \"11.0.1@ea2dbba0e1edbf5128d73bdb23c2c9b9f68468ba\"\nGLPI_FILES_VERSION: \"11.0.1-3a9929cf\"\nGLPI_MIN_PHP: \"8.2\"\nGLPI_MAX_PHP: \"8.5\"\nGLPI_YEAR: \"2025\"\nGLPI_I18N_DIR: \"/var/www/html/glpi/locales\"\nGLPI_CONFIG_DIR: \"/var/pod/glpi/config\"\nGLPI_VAR_DIR: \"/va\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "kendall.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce on current 11.0/bugfixes. Try without plugins, and clear your cache.\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3472945911, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21724#issuecomment-3472945911", "createdAt": "2025-10-31T12:44:39Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "Hello,\nI tried to disable all the plugins and clear the cache under _cache/ but the problem still occurs.\nI also tried with Chrome, Edge, Firefox.\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3473352443, "author": "Cyanur", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21724#issuecomment-3473352443", "createdAt": "2025-10-31T14:30:54Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I guess there could be something odd with the date conversion being done but it escapes me at the moment. Since the custom fields are all stored in a JSON column, we cannot use the automatic timezone conversions of TIMESTAMP columns so we convert values to UTC to store them and then convert them to the user's timezone when loading them from the database. A difference could be the cause of the value decreasing by a single day each time.\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3474882499, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21724#issuecomment-3474882499", "createdAt": "2025-10-31T20:58:32Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "Hi,\nIf it can help on the investigations, here is what we did :\n\n- We went to a new GLPI server for preprod environnement, to try out every new features before pushing it to production\n=> Many changes has been done between both server, Ubuntu 2404 and RAW service installation to Rocky 10 and dockerized lamp stack\n- Prod GLPI is 10.0.20, mariadb have no timezone loaded on this server\n- We exported the database to the new preprod server where we installed another 10.0.20, mariadb lastest version with timezones\n- Preprod GLPI has been upgraded to 11.0\n- We created some assets and the custom fields we need=> The problem was already here\n- We upgraded to 11.01, => still here\n\nI was thinking about something to do with CET to UTC conversion when we POST on the browser, but I don't know...\n\nAlso I didn't tried to upgrade to 11.0.2 for now.\n\nRegards !\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491941094, "author": "Cyanur", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21724#issuecomment-3491941094", "createdAt": "2025-11-05T15:36:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21724, "url": "https://github.com/glpi-project/glpi/issues/21724", "author": "Cyanur", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-31T11:08:40Z", "updatedAt": "2026-06-20T01:05:36Z", "closedAt": "2026-03-11T14:15:13Z" } }, { "title": "[BUG 11.0.6] Error creating a ticket including an image in the description", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello glpi team,\n\nWhen we create a new ticket, including an image in the description then changing the category, give an \"Une erreur est survenue\" during the \"refresh\" of the ticket.\n\nI get php errors.\n\nThanks.\n\nYannick", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This looks like a permission issues. Double check permissions on your whole /var/glpi/files/ directory.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4003735510, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23366#issuecomment-4003735510", "createdAt": "2026-03-05T09:39:42Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "Permissions seem to be ok :\n\n:/var/glpi/files$ ls -rtl\ntotal 348\ndrwxr-xr-x. 4 www-data www-data 26 Nov 9 2022 PPT\ndrwxr-xr-x. 3 www-data www-data 16 Nov 9 2022 RTF\ndrwxr-xr-x. 2 www-data www-data 24 Nov 9 2022 _locales\ndrwxr-xr-x. 3 www-data www-data 16 Nov 9 2022 ODS\ndrwxr-xr-x. 3 www-data www-data 16 Nov 9 2022 BMP\ndrwxr-xr-x. 258 www-data www-data 8192 Jun 22 2023 PNG\ndrwxr-xr-x. 6 www-data www-data 46 Jan 10 2024 HTML\ndrwxr-xr-x. 4 www-data www-data 26 Mar 13 2024 GIF\ndrwxr-xr-x. 32 www-data www-data 4096 Apr 23 2024 DOC\ndrwxr-xr-x. 14 www-data www-data 126 Jul 9 2024 LOG\ndrwxr-xr-x. 28 www-data www-data 4096 Oct 10 2024 XLS\ndrwxr-xr-x. 22 www-data www-data 4096 May 28 2025 ZIP\ndrwxr-xr-x. 257 www-data www-data 8192 Jun 2 2025 PDF\ndrwxr-xr-x. 11 www-data www-data 96 Jul 31 2025 PPTX\ndrwxr-xr-x. 223 www-data www-data 4096 Sep 18 14:00 MSG\ndrwxr-xr-x. 155 www-data www-data 4096 Sep 23 13:04 DOCX\ndrwxr-xr-x. 169 www-data www-data 4096 Nov 20 15:20 XLSX\ndrwxr-xr-x. 142 www-data www-data 4096 Nov 27 06:38 JPG\ndrwxr-xr-x. 94 www-data www-data 4096 Dec 1 08:16 TXT\ndrwxr-xr-x. 73 www-data www-data 4096 Dec 2 13:32 XML\ndrwxr-xr-x. 65 www-data www-data 4096 Dec 3 16:32 CSV\ndrwxr-xr-x. 2 www-data www-data 4096 Dec 11 06:35 _log\ndrwxr-xr-x. 4 www-data www-data 151552 Dec 11 07:02 _inventories\ndrwxr-xr-x. 2 www-data www-data 4096 Dec 11 08:01 _dumps\ndrwxr-xr-x. 2 www-data www-data 6 Dec 11 08:09 _themes\ndrwxr-xr-x. 5 www-data www-data 36 Dec 12 10:23 JSON\ndrwxr-xr-x. 68 www-data www-data 4096 Mar 5 08:53 JPEG\ndrwxr-xr-x. 22 www-data www-data 4096 Mar 5 10:19 _pictures\ndrwxr-xr-x. 2 www-data www-data 24 Mar 5 10:19 _lock\ndrwxr-xr-x. 2 www-data www-data 6 Mar 5 10:19 _graphs\ndrwxr-xr-x. 2 www-data www-data 24 Mar 5 10:19 _cron\ndrwxr-xr-x. 37 www-data www-data 4096 Mar 5 10:19 _cache\ndrwxr-xr-x. 2 www-data www-data 24 Mar 5 10:19 _uploads\ndrwxr-xr-x. 2 www-data www-data 156 Mar 5 10:19 _rss\ndrwxr-xr-x. 5 www-data www-data 77 Mar 5 10:19 _plugins\ndrwxr-xr-x. 2 www-data www-data 28672 Mar 5 10:19 _sessions\ndrwxr-xr-x. 2 www-data www-data 4096 Mar 5 10:20 _tmp\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4003997420, "author": "YannickBarone", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23366#issuecomment-4003997420", "createdAt": "2026-03-05T10:22:24Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "All possible sub direcotries and files may not have the same ACLs. Run chmod/chown te be sure.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4004132811, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23366#issuecomment-4004132811", "createdAt": "2026-03-05T10:42:54Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "chmod/chown done, I still get the same error.\n\nWe didn't had this error wth the 11.0.4 version.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4004153588, "author": "YannickBarone", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23366#issuecomment-4004153588", "createdAt": "2026-03-05T10:46:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23366, "url": "https://github.com/glpi-project/glpi/issues/23366", "author": "YannickBarone", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-05T09:33:01Z", "updatedAt": "2026-06-15T01:13:42Z", "closedAt": "2026-03-06T13:24:56Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Issue while posting a ticket on 11.0.5", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello,\n\nThe issue is when i try to post a ticket, here's the error I get:\n\nI was on 11.0.2 before and I updated to 11.0.5 and now i get this issue.\nI rebooted the server, I recopied over the files on glpi on my server in case something was broken / missing.\n\nStilll having this issue.\n\nReproduction steps:\n1. Click to create a new ticket\n2. Enter the required fields\n3. Click the button to create the ticket\n4. It fails here\n\nEnvironment details:\nGLPI: 11.0.5 ( => /var/www/glpi/glpi)\nInstallation mode: TARBALL\nCurrent language: fr_CA\nSource Integrity: OK\n\nOperating system: Linux s-glpi2.ourdomain.ca 6.8.0-90-generic #​91-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 18 14:14:30 UTC 2025 x86_64\n\nPHP: 8.3.6 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv,\nimap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm,\ntokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"8M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"2M\"\n\nWeb server: Apache ()\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0\n\nDatabase:\n\nServer Software: (Ubuntu)\n\nServer Version: 8.0.44-0ubuntu0.24.04.2\n\nServer SQL Mode: STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@127.0.0.1/glpi\n\nHost info: 127.0.0.1 via TCP/IP\n\nRequirements:\nPHP version (8.3.6) is supported.PHP version (8.3.6) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (8.0.44) is supported.Database engine version (8.0.44) is supported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/www/glpi/glpi/files/_cache has been validated. Write access to\n/var/www/glpi/glpi/files/_cron has been validated. Write access to /var/www/glpi/glpi/files has been validated. Write access to\n/var/www/glpi/glpi/files/_graphs has been validated. Write access to /var/www/glpi/glpi/files/_lock has been validated. Write\naccess to /var/www/glpi/glpi/files/_pictures has been validated. Write access to /var/www/glpi/glpi/files/_plugins has been\nvalidated. Write access to /var/www/glpi/glpi/files/_rss has been validated. Write access to /var/www/glpi/glpi/files/_sessions\nhas been validated. Write access to /var/www/glpi/glpi/files/_tmp has been validated. Write access to\n/var/www/glpi/glpi/files/_uploads has been validated.Write access to /var/www/glpi/glpi/files/_cache has been validated.\nWrite access to /var/www/glpi/glpi/files/_cron has been validated.\nWrite access to /var/www/glpi/glpi/files has been validated.\nWrite access to /var/www/glpi/glpi/files/_graphs has been validated.\nWrite access to /var/www/glpi/glpi/files/_lock has been validated.\nWrite access to /var/www/glpi/glpi/files/_pictures has been validated.\nWrite access to /var/www/glpi/glpi/files/_plugins has been validated.\nWrite access to /var/www/glpi/glpi/files/_rss has been validated.\nWrite access to /var/www/glpi/glpi/files/_sessions has been validated.\nWrite access to /var/www/glpi/glpi/files/_tmp has been validated.\nWrite access to /var/www/glpi/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed:\nctype, iconv, sodium.\nWrite access to /var/www/glpi/glpi/marketplace has been validated.Write access to\n/var/www/glpi/glpi/marketplace has been validated.\nTimezones seems loaded in database.Timezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "riley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "lane.blair@peppermint.local", "text": "Exactly the same problem after the update.\nI'm reverting to version 11.0.4\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3813499760, "author": "ozit", "anonymizedAuthorEmail": "lane.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22877#issuecomment-3813499760", "createdAt": "2026-01-28T19:43:38Z" } }, { "userEmail": "noel.blair@peppermint.local", "text": "I had the same issue, and after looking into it, I managed to resolve it. You need to remove the mandatory fields defined in your ticket templates.\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3816195723, "author": "AurelienFroment", "anonymizedAuthorEmail": "noel.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22877#issuecomment-3816195723", "createdAt": "2026-01-29T08:22:51Z" } }, { "userEmail": "lane.blair@peppermint.local", "text": "I have 44 ticket templates !\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3816654996, "author": "ozit", "anonymizedAuthorEmail": "lane.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22877#issuecomment-3816654996", "createdAt": "2026-01-29T10:03:32Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "I'd the same issue. It was due to mixing php version between 8.4 and 8.5, I solved it after fully setup to php 8.5\n\nOriginal response date: 2026-02-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3853642151, "author": "AHTW4051", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22877#issuecomment-3853642151", "createdAt": "2026-02-05T13:25:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22877, "url": "https://github.com/glpi-project/glpi/issues/22877", "author": "blackxthink", "anonymizedAuthorEmail": "riley.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-28T16:06:56Z", "updatedAt": "2026-05-22T01:01:47Z", "closedAt": "2026-02-10T06:31:58Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI 10 / GLPI 11 : Dates in management tab not saving", "detail": "Affected version:\n11.0.2\n\nIssue description:\nIn \"management\" tab of a computer, when we input an order date, a buy date, a delivery date, a use date, an inventory_date and save, the date isn't stored.\nBut the decommission date and use date are OK.\nSee video attached.\n\nReproduction steps:\n1. in a computer asset\n2. Enable management if not\n3. Select dates or type them\n4. Click Save", "priority": "medium", "type": "support", "createdByEmail": "reese.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This issue already has been reported\n\nOriginal response date: 2025-11-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3588653260, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22100#issuecomment-3588653260", "createdAt": "2025-11-28T10:03:35Z" } }, { "userEmail": "reese.bennett@peppermint.local", "text": "link to the previous issue ?\nThanks\n\nOriginal response date: 2025-11-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3588660462, "author": "apohutenumera", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22100#issuecomment-3588660462", "createdAt": "2025-11-28T10:05:26Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "See #21416.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3595319573, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22100#issuecomment-3595319573", "createdAt": "2025-12-01T08:47:59Z" } }, { "userEmail": "reese.bennett@peppermint.local", "text": "Skyler Adler thanks !\nBut it's not the same: the issue linked is about the decimal values and not the dates. so the fix merged doesn't solve this issue.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3595358022, "author": "apohutenumera", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22100#issuecomment-3595358022", "createdAt": "2025-12-01T08:58:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22100, "url": "https://github.com/glpi-project/glpi/issues/22100", "author": "apohutenumera", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-28T09:59:03Z", "updatedAt": "2026-04-17T00:48:46Z", "closedAt": "2025-12-25T12:39:33Z" } }, { "title": "v11.0.2 Financial and Administrative Information fields not displaying values for Custom Assets in Assets->Global view", "detail": "Affected version:\n11.0.2 - On-Prem\n\nIssue description:\nCreating a Custom Asset definition. (Setup->Asset Definitions), then adding \"Financial and administrative information\" field data to the Assets-> Global view for the custom asset, does not show \"Financial and administrative information\" field values for custom assets. Fieldname headers are displayed ok, simply no data shown. Core assets display this data ok.\nProfiles, capacities etc are all confirmed set for the custom assets\n\nAffected page:\n[instance]/front/allassets.php\n\nReproduction steps:\nConfirming \"Enable the financial and administrative information by default\" is set to yes in setup.\n1. Create a Custom Asset definition. (Setup->Asset Definitions)\n2. Ensure profiles set accordingly\n3. Ensure capacities include \"Financial and administrative information\"\n4. Create a new instance of your custom asset.\n5. Enter some \"Financial and administrative information\" field data (e,g Business Criticity) and save\n6. Now choose Assets->Global\n7. Custom asset displayed in the list, ok so far\n8. Select \"Select default items to show\" add the 'Business Criticity\" field to the global view.\n9. Note the column heading is displayed \"Financial and administrative information - Business Criticity\", however the value of the field for your custom asset is not displayed. All fields in the 'Financial and administrative information\" section of custom assets can be added to the Assets->Global view and have the headings displayed, but no values are shown in the view for these fields.\n10. Note other asset types (core) display the values for the \"Financial and administrative information\" fields with no issue.\n\nAlso confirmed issue present in a second v11.0.2 instance as corroboration.\n\nEnvironment details:\ndetailssummaryGLPI informationsummaTEST-11.0.2.txt\n\nAdditional context:\nThe display of Financial and Admin info across all assets, core and custom alike is key to our goals in using GLPI. Hope you can advise on way forward here.", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This has been fixed in latest release.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630622482, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22290#issuecomment-3630622482", "createdAt": "2025-12-09T06:48:15Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "I originally identified this issue in an upgraded instance 11.0.2->11.0.4 and elected to revert back to 11.0.2 where I reported this issue here. The issue was present in 11.0.4.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3634771318, "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22290#issuecomment-3634771318", "createdAt": "2025-12-09T23:56:16Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "I have just repeated an upgrade from 11.0.2->11.0.4. On the php bin/console db:update command, noticed this anomaly:\n\n[Image omitted]\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3635328099, "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22290#issuecomment-3635328099", "createdAt": "2025-12-10T04:28:33Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "I have repeated the reported issue (at v11.0.2) on the upgraded 11.0.4 and the issue persists\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3635344905, "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22290#issuecomment-3635344905", "createdAt": "2025-12-10T04:36:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22290, "url": "https://github.com/glpi-project/glpi/issues/22290", "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-09T04:05:27Z", "updatedAt": "2026-04-16T00:51:08Z", "closedAt": "2026-01-05T10:31:33Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Upgrade to GLPI 11 fails", "detail": "Issue description:\nHi All,\n\nI've been trying to get my GLPI 10 version to 11.0.2 but i've been running into error after error.\nFirst I struggled to resolve the issue where the webserver was supposedly configured wrongly even though the URL stuff should've been okay.\nAfter a while I finally managed to get into the upgrade windows, but now it fails time after on the DB Upgrade, so I tried to use the 11.0 files instead but then I get the error that my DB is already higher than the GLPI files, so it did something.\n\nWhen I try to go into the logs, I don't get any newer errors, but the last ones I have are these:\n\n[2025-11-14 10:35:24] glpi.ALERT: * Uncaught Error: syntax error, unexpected token \"readonly\", expecting \"abstract\" or \"final\" or \"class\"\n Backtrace :\n ...ner\\ControllerListener\\CheckCsrfListener.php:44\n .\\vendor\\composer\\ClassLoader.php:427 Composer\\Autoload\\{closure}()\n : Composer\\Autoload\\ClassLoader->loadClass()\n ...y\\config\\Resource\\ClassExistenceResource.php:76 class_exists()\n ...y\\dependency-injection\\ContainerBuilder.php:361 Symfony\\Component\\Config\\Resource\\ClassExistenceResource->isFresh()\n ...\\dependency-injection\\Loader\\FileLoader.php:293 Symfony\\Component\\DependencyInjection\\ContainerBuilder->getReflectionClass()\n ...\\dependency-injection\\Loader\\FileLoader.php:121 Symfony\\Component\\DependencyInjection\\Loader\\FileLoader->findClasses()\n ...oader\\Configurator\\PrototypeConfigurator.php:72 Symfony\\Component\\DependencyInjection\\Loader\\FileLoader->registerClasses()\n ...Configurator\\AbstractServiceConfigurator.php:69 Symfony\\Component\\DependencyInjection\\Loader\\Configurator\\PrototypeConfigurator->destruct()\n .\\dependency_injection\\services.php:62 Symfony\\Component\\DependencyInjection\\Loader\\Configurator\\AbstractServiceConfigurator->load()\n ...pendency-injection\\Loader\\PhpFileLoader.php:146 Symfony\\Component\\DependencyInjection\\Loader\\ProtectedPhpFileLoader::Symfony\\Component\\DependencyInjection\\Loader\\Configurator\\{closure}()\n ...ependency-injection\\Loader\\PhpFileLoader.php:64 Symfony\\Component\\DependencyInjection\\Loader\\PhpFileLoader->executeCallback()\n .\\vendor\\symfony\\config\\Loader\\FileLoader.php:167 Symfony\\Component\\DependencyInjection\\Loader\\PhpFileLoader->load()\n .\\vendor\\symfony\\config\\Loader\\FileLoader.php:98 Symfony\\Component\\Config\\Loader\\FileLoader->doImport()\n ...y\\dependency-injection\\Loader\\FileLoader.php:70 Symfony\\Component\\Config\\Loader\\FileLoader->import()\n ...oader\\Configurator\\ContainerConfigurator.php:64 Symfony\\Component\\DependencyInjection\\Loader\\FileLoader->import()\n .\\src\\Glpi\\Kernel\\Kernel.php:190 Symfony\\Component\\DependencyInjection\\Loader\\Configurator\\ContainerConfigurator->import()\n ...ramework-bundle\\Kernel\\MicroKernelTrait.php:190 Glpi\\Kernel\\Kernel->configureContainer()\n ...ependency-injection\\Loader\\ClosureLoader.php:36 Glpi\\Kernel\\Kernel->Symfony\\Bundle\\FrameworkBundle\\Kernel\\{closure}()\n ...r\\symfony\\config\\Loader\\DelegatingLoader.php:37 Symfony\\Component\\DependencyInjection\\Loader\\ClosureLoader->load()\n ...ramework-bundle\\Kernel\\MicroKernelTrait.php:198 Symfony\\Component\\Config\\Loader\\DelegatingLoader->load()\n .\\vendor\\symfony\\http-kernel\\Kernel.php:617 Glpi\\Kernel\\Kernel->registerContainerConfiguration()\n .\\src\\Glpi\\Kernel\\Kernel.php:183 Symfony\\Component\\HttpKernel\\Kernel->buildContainer()\n .\\vendor\\symfony\\http-kernel\\Kernel.php:506 Glpi\\Kernel\\Kernel->buildContainer()\n .\\vendor\\symfony\\http-kernel\\Kernel.php:772 Symfony\\Component\\HttpKernel\\Kernel->initializeContainer()\n .\\vendor\\symfony\\http-kernel\\Kernel.php:126 Symfony\\Component\\HttpKernel\\Kernel->preBoot()\n .\\src\\Glpi\\Kernel\\Kernel.php:143 Symfony\\Component\\HttpKernel\\Kernel->boot()\n .\\front\\cron.php:74 Glpi\\Kernel\\Kernel->boot()\n\n[2025-11-14 10:40:24] glpi.ALERT: * Uncaught Error: syntax error, unexpected token \"readonly\", expecting \"abstract\" or \"final\" or \"class\"\n Backtrace :\n ...ner\\ControllerListener\\CheckCsrfListener.php:44\n .\\vendor\\composer\\ClassLoader.php:427 Composer\\Autoload\\{closure}()\n : Composer\\Autoload\\ClassLoader->loadClass()\n ...y\\config\\Resource\\ClassExistenceResource.php:76 class_exists()\n ...y\\dependency-injection\\ContainerBuilder.php:361 Symfony\\Component\\Config\\Resource\\ClassExistenceResource->isFresh()\n ...\\dependency-injection\\Loader\\FileLoader.php:293 Symfony\\Component\\DependencyInjection\\ContainerBuilder->getReflectionClass()\n ...\\dependency-injection\\Loader\\FileLoader.php:121 Symfony\\Component\\DependencyInjection\\Loader\\FileLoader->findClasses()\n ...oader\\Configurator\\PrototypeConfigurator.php:72 Symfony\\Component\\DependencyInjection\\Loader\\FileLoader->registerClasses()\n ...Configurator\\AbstractServiceConfigurator.php:69 Symfony\\Component\\DependencyInjection\\Loader\\Configurator\\PrototypeConfigurator->destruct()\n .\\dependency_injection\\services.php:62 Symfony\\Component\\DependencyInjection\\Loader\\Configurator\\AbstractServiceConfigurator->load()\n ...pendency-injection\\Loader\\PhpFileLoader.php:146 Symfony\\Component\\DependencyInjection\\Loader\\ProtectedPhpFileLoader::Symfony\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "quinn.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Try removing all plugins directories\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3540351936, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21940#issuecomment-3540351936", "createdAt": "2025-11-17T07:36:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nYou cannot rollback to a previous version, so if your database has been upgraded to GLPI 11.0.2, you have to use the GLPI 11.0.2 source code.\n\nAs far as I see, in your logs, you first had issues with an incompatible PHP version, then you had some issues with your mail receiver and your LDAP connection, probably due to the fact that you did not copied the GLPI key file (config/glpicrypt.key) from the previous GLPI version.\n\nNow, we could not help as you do not really explain what is your issue with GLPI 11.0.2. What is not working exactly? Can you provide screenshots?\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558510776, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21940#issuecomment-3558510776", "createdAt": "2025-11-20T14:59:47Z" } }, { "userEmail": "lane.blair@peppermint.local", "text": "the documentation is wrong...... it says the php version can be 7.x~8.2\nthe PHP version MUST be 8.2 to fix the first error\n\nwithout this fix the DB will not upgrade\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584512561, "author": "we-sell-bags", "anonymizedAuthorEmail": "lane.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21940#issuecomment-3584512561", "createdAt": "2025-11-27T07:27:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Which documentation is wrong?\n\nInstall doc is OK:\n\n[Image omitted]\n\nAs well as Github's README:\n\n[Image omitted]\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584546716, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21940#issuecomment-3584546716", "createdAt": "2025-11-27T07:42:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21940, "url": "https://github.com/glpi-project/glpi/issues/21940", "author": "Lucitiana", "anonymizedAuthorEmail": "quinn.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-14T13:39:33Z", "updatedAt": "2026-03-14T00:36:38Z", "closedAt": "2025-12-03T16:34:34Z" } }, { "title": "Trying to link locations and status to an asset generates \"The results could not be loaded\" error", "detail": "Affected version:\nv11.0.1 and v11.0.2\n\nIssue description:\nAs per forum post here: and title of this report.\n\nTrying to load these relations in the dropdown from an asset generates this error. Debuging reveals the error bellow.\n\nI am using a DigitalOcean managed database server. By default, ONLY_FULL_GROUP_BY is enabled. Thankfully I can disable it and doing so fixes the issue, but other managed database engines may not allow this?\n\nAffected page:\n\nReproduction steps:\nOpen GLPI super admin screen\nNavigate to assets > computers (or any other asset)\nAdd a new asset\nSelect location or status dropdown\nError loaded below field\n\nEnvironment details:\nv11.0.1 or v11.0.2\nVM with 1 vcpu 2GB RAM\nUbuntu 24.04\nManaged MYSQL DB server (MySQL 8, no other info)", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "devon.blair@peppermint.local", "text": "To clarify, disabling ONLY_FULL_GROUP_BY on the MySQL server fixes the issue.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501729610, "author": "mo-wcma", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21855#issuecomment-3501729610", "createdAt": "2025-11-07T10:27:56Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "By default, this mode should be disabled from GLPI by following query:\n\nThis is already done like this in GLPI v10. Did you try removing all plugins?\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501770855, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21855#issuecomment-3501770855", "createdAt": "2025-11-07T10:35:31Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I wonder if this could fail based on SQL user permissions or something else. It is a query direct on the mysqli connection so we don't log errors for it and there is no error check afterwards.\n\nCan you try adding this after the SET SESSION sql_mode line in src/DBmysql.php?\n\nThen, try to link locations or statuses again and check the files/_log/php-errors.log file to see if the warning is logged.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3502099156, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21855#issuecomment-3502099156", "createdAt": "2025-11-07T11:46:34Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "By default, this mode should be disabled from GLPI by following query:\n\nThis is already done like this in GLPI v10. Did you try removing all plugins?\n\nI am running a vanilla install, so no plugins that I am aware of are installed.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3505086594, "author": "mo-wcma", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21855#issuecomment-3505086594", "createdAt": "2025-11-07T21:37:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21855, "url": "https://github.com/glpi-project/glpi/issues/21855", "author": "mo-wcma", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-07T10:27:19Z", "updatedAt": "2026-03-13T00:38:31Z", "closedAt": "2025-12-02T08:34:03Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Group Complete Name Display Error", "detail": "Affected version:\n11.0.1\n\nIssue description:\nCreating Multiple Groups ( Group 1 & Group 2 )& assigning it to one user.\nOutput: Two Groups were assigned, but display the same Complete Name( Group 1 & Group 1)\n\n[Image omitted]\n\nReproduction steps:\n1. Create Groups > Group 1 & Group 2\n2. Assign Group 1 to one User ( Reflects Group 1 )\n2. Assign Group 2 to the same User ( Reflects Group 1 )", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Where is the display error ocurring? Is this the search results for the users?\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3404142740, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21486#issuecomment-3404142740", "createdAt": "2025-10-15T01:00:21Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Yes, when viewing all users, then adding default items to show ( Groups ).\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3404156622, "author": "netsysspecialist-boop", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21486#issuecomment-3404156622", "createdAt": "2025-10-15T01:08:50Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the bug. The SQL query returns the correct results for the group column like \"All Users$#$1$$##$$Admins$#$2\", and the links in the displayed results actually go to the correct groups, but the names shown for each link are always the first group.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3407850002, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21486#issuecomment-3407850002", "createdAt": "2025-10-15T19:02:07Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Linked PR seems irrelevant. The reported issue was with the search results showing the first group's label for all of the user's groups even though the links were correct, not that the list in the User's Groups tab wasn't showing the completename.\n\nFurther, this issue has gotten worse since I originally tested. Now, only the first group shows at all and it isn't a link anymore.\n#21510 seems to be causing an early return so the remaining groups are not processed and the itemlink handling isn't either.\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461021376, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21486#issuecomment-3461021376", "createdAt": "2025-10-29T11:24:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21486, "url": "https://github.com/glpi-project/glpi/issues/21486", "author": "netsysspecialist-boop", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-15T00:57:39Z", "updatedAt": "2026-02-08T00:49:01Z", "closedAt": "2025-10-30T13:27:11Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI 11 - Issues displaying items in forms for regular users", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWe created the form so that the user can link a printer item in the call, as shown in the print:\n\n[Image omitted]\n\n[Image omitted]\n\nHowever, nothing is displayed to the user in the common profile:\n\n[Image omitted]\n\nWe checked the profile configuration, but we didn't find anything that could be preventing this selection:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "sage.blair@peppermint.local", "text": "I also have this issue, Users are not able to see their objects in forms when using Objects in forms\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3411425670, "author": "cjdrilling29", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21502#issuecomment-3411425670", "createdAt": "2025-10-16T15:19:50Z" } }, { "userEmail": "lane.blair@peppermint.local", "text": "The issue is in the simplified interface that restricts users from any access to assets, even from forms. I cloned the self-service profile, then changed it to the standard interface - the issue disappeared from that.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3425819690, "author": "drumofragnarock", "anonymizedAuthorEmail": "lane.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21502#issuecomment-3425819690", "createdAt": "2025-10-21T10:17:52Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "I believe the best user interface is a simplified one.\n\nIt's a good suggestion, but I think it's interesting that they work to fix the issue, since the simplified profile has release options.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3426194489, "author": "afpes", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21502#issuecomment-3426194489", "createdAt": "2025-10-21T11:47:38Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Are you trying to let the user see all available printers or just the one that he is assigned to?\n\nIt might be a bit dangerous to enable self service users to access all available assets, maybe we need to add a right for that? ping Skyler Adler\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432855465, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21502#issuecomment-3432855465", "createdAt": "2025-10-22T15:03:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21502, "url": "https://github.com/glpi-project/glpi/issues/21502", "author": "afpes", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-15T13:32:57Z", "updatedAt": "2026-02-06T00:37:07Z", "closedAt": "2025-10-28T08:02:39Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "\"Save\" button disappeared in \"Personalized CSS\" (\"Entity - Customized Interface\")", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHi,\n\nIn the Administration -> Entity -> Customized Interface, I activated a \"Personalized CSS\" but I can't go back to \"No\", i don't have the \"Save\" button anymore. (sorry, my glpi is in french so I don't know exactly the english menu name)\n\nWith developers tools in Google Chrome, I reduced the size (width) of many \"div\" but button didn't reappear.\n\nMaybe it exists a workaround for that, to reinitilaze CSS but I didn't see anything anywhere.\n\nBut for me it's a bug because I don't touch to the stucture of glpi css, it's just for a different logo.\nHere is my CSS personalization :\n.page .glpi-logo {\n background: url(\"../pics/logos/logo-100-white.png\") no-repeat;\n}\n\nCan you reproduce the bug ?\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. administration\n2. entity\n3. Interface customization\n4. CSS personalization\n5. Put my css code\n6. Save\n7. Try to change to \"No\" for CSS personalization : \"Save\" button not present\n\nAdditional context:\nNo", "priority": "medium", "type": "support", "createdByEmail": "riley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3403138431, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21484#issuecomment-3403138431", "createdAt": "2025-10-14T18:38:17Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "[Image omitted]\n\nFor me, it was normal, although the argument seems to be incorrect. This happened to me in version 10. You probably used a card that reflects on the buttons on all tabs, and it disappeared. To disable this, you'll only be able to do so through the database by leaving the UI customization column blank and leaving the custom UI option as no, but you have to do this in the entity you changed, through the database.\n\nI don't think it's a problem there, it's just that what you tried to change ended up bugging the buttons on the screen. I say this because it happened to me and it was only solved by disabling it directly through the database to disable the applied customization.\n\nTranslated with DeepL.com (free version)\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3403639399, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21484#issuecomment-3403639399", "createdAt": "2025-10-14T21:14:26Z" } }, { "userEmail": "riley.bennett@peppermint.local", "text": "OK thank you very much for your answer.\nI changed in database the value of \"enable_custom_css\" from 1 to 0:\n\n[Image omitted]\n\nAnd in GLPI Administration -> Entity, it's OK :\n\n[Image omitted]\n\nBUT, when I would change back to a customized CSS, button \"Save\" not appears again !\n\n[Image omitted]\n\nI reset the \"custom_css_code to \"blank\" ('') but again, button \"Save\" not appears.\n\n[Image omitted]\n\nI restart Apache2 and Mariadb services too. Nothings new.\nI dont know what to do at this step... maybe i just will backup my data, database as a new install and reinstall GLPI 11.0.1 ?\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3405544415, "author": "desrimaisd", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21484#issuecomment-3405544415", "createdAt": "2025-10-15T09:50:25Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "run php bin/console glpi:cache:clear in folder of glpi \"/glpi\" and try\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3406828939, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21484#issuecomment-3406828939", "createdAt": "2025-10-15T14:46:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21484, "url": "https://github.com/glpi-project/glpi/issues/21484", "author": "desrimaisd", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-14T15:44:56Z", "updatedAt": "2026-01-26T00:35:09Z", "closedAt": "2025-10-17T12:28:54Z" } }, { "title": "[11.0.5 GLPI Inventory] Incorrect integer value: 'NTFS' for column 'filesystems_id'", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello! When synchronizing the GLPI Inventory, no computer information is added or updated.\n\nAgent inventory file attached.\n\nINVENTORY FILE inv.json\n\nYou can check it out?\n\nEnvironment details:\nOperating system: Linux 01-sm-webserver 5.15.0-157-generic #​167-Ubuntu SMP Wed Sep 17 21:35:53 UTC 2025 x86_64\nPHP: 8.2.30 apache2handler\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, igbinary, imap, intl, ldap, exif, msgpack, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg,\nsysvsem, sysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, memcached, Zend OPcache\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"8M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"2M\"\nWeb server: Apache ()\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0\nYaBrowser/25.12.0.0 Safari/537.36\nDatabase:\nServer Software: (Ubuntu)\nServer Version: 8.0.45-0ubuntu0.22.04.1\nServer SQL Mode: STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION", "priority": "medium", "type": "maintenance", "createdByEmail": "finley.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "We need a way to reproduce on a fresh GLPI installation.\nMake sure you can reproduce on a test database; and provide us the invnetory file that cause the issue.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3876499906, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23065#issuecomment-3876499906", "createdAt": "2026-02-10T09:43:16Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi Finley Blair\n\nI tested your inv.json file in a fresh 11.0.5 test instance and it was imported without any error and I can see drives:\n\n[Image omitted]\n\nMariaDB extract:\n\n[Image omitted]\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3876571482, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23065#issuecomment-3876571482", "createdAt": "2026-02-10T09:56:22Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I did not pay attention inventory file was provided...\n\nBut I'm not surprised of the result. This kind of issue is often related to data that already exists; from an older inventory of any asset, or from a rule, a dictionary, a locked field, a plugin, ..., ..., ...\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3876699604, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23065#issuecomment-3876699604", "createdAt": "2026-02-10T10:19:24Z" } }, { "userEmail": "finley.blair@peppermint.local", "text": "Skyler Adler Elliot Bennett Thank you for such a prompt response!\n\nThe plugins have been disabled. What advice can you give? The database structure is correct, I did database:check_schema_integrity, and it returns \"OK\"\n\n Can I make a TRUNCATE of \"disks table\" data and so on (except for the computer table)? They will be updated anyway.\n\nWe have a certain database of computers, which has been maintained since the days of Fusion Inventory. The updates were timely and at the time of the transition to GLPI Inventory, everything was working correctly, probably before the transition to version 11 (I can't say for sure)\n\n\"from an older inventory of any asset, or from a rule, a dictionary, a locked field, a plugin, ..., ..., ...\" - Thanks, I went to check.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3876758162, "author": "sazanof", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23065#issuecomment-3876758162", "createdAt": "2026-02-10T10:30:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23065, "url": "https://github.com/glpi-project/glpi/issues/23065", "author": "sazanof", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "inventory" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-10T09:28:45Z", "updatedAt": "2026-06-08T07:55:46Z", "closedAt": "2026-06-08T07:55:46Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Attachments aren´t being included in email notifications", "detail": "Affected version:\n10.0.22\n\nIssue description:\nIn GLPI 10.0.22 (latest version), task attachments added by technicians are not being included in email notifications as intended.\n\nReproduction steps:\n1. Create an active notification (and template) of type Ticket > Task creation with defined recipients.\n2. Make sure mail notifications are enabled and properly configured.\n3. Create a ticket.\n4. Create a task within the ticket and add one attachment (e.g., .pdf, .csv, .zip, etc.).\n5. Go to Administration > Notification queue and check when the email is scheduled to be sent but most importantly, do not trigger the send manually.\n6. Once the email arrives in your inbox, verify that it does not include the attachment.\n\nAdditional context:\nIMPORTANT: When the notification is manually dispatched in the Notification queue then it works as expected.\n\nEnvironment details:\nNotifications \nWay of sending emails: SMTP (anonymous@127.0.0.1)", "priority": "medium", "type": "support", "createdByEmail": "devon.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "reese.blair@peppermint.local", "text": "I can confirm, we are experiencing the same problem in our instance.\n\nOriginal response date: 2025-12-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3653866737, "author": "tilkov", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22315#issuecomment-3653866737", "createdAt": "2025-12-15T07:03:35Z" } }, { "userEmail": "skyler.blair@peppermint.local", "text": "Hello. We are also affected by this bug.\n\nAfter doing some research, it seems to be due to this change:\n\nJordan Blair or Skyler Adler could you help us?\n\nOriginal response date: 2025-12-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3657736127, "author": "cosmedd", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22315#issuecomment-3657736127", "createdAt": "2025-12-15T21:45:03Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "I can confirm this too.\nNot just for Task Notification - but for all Ticket Notifications.\n\nAttachments are visible in GLPI web interface, but they are not included in email notifications.\n\nUsing GLPI 10.0.22.\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3685594991, "author": "oneill2john", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22315#issuecomment-3685594991", "createdAt": "2025-12-23T07:49:34Z" } }, { "userEmail": "parker.blair@peppermint.local", "text": "Same issue\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737128558, "author": "benoooo85", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22315#issuecomment-3737128558", "createdAt": "2026-01-12T06:55:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22315, "url": "https://github.com/glpi-project/glpi/issues/22315", "author": "rootjog", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-10T08:52:47Z", "updatedAt": "2026-02-17T08:47:28Z", "closedAt": "2026-02-05T08:31:37Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "DB Upgrade from 0.85.5 to 11.0.4 fails", "detail": "Affected version:\n0.85.5\n\nIssue description:\nWe're migrating an old install of 0.84.6 to 11.0.4 and just did the upgrade to 0.85.5.\n\nAfter that we tried to jump to 11.0.4 with php bin/console db:update:\n-> integrity of db scheme was ok\n\nThen we got:\nUpdate to 0.90 version completed.\nUpdate to 0.90.1 version completed.\nUpdate to 0.90.5 version completed.\nUpdate to 9.1 version completed.\nUpdate to 9.1.1 version completed.\nUpdate to 9.1.3 version completed.\nApi users tokens has been reset, if you use REST/XMLRPC api with personal token for authentication, please reset your user's token.\nBeim Updaten ist folgender Fehler aufgetreten: MySQL query error: Unknown column 'old_id' in 'INSERT INTO' (1054) in SQL query \"INSERT INTO glpi_logs (items_id, itemtype, itemtype_link, linked_action, user_name, date_mod, id_search_option, old_value,mys, new_value, new_id) VALUES ('1', 'DeviceFirmware', '0', '20', '', '2026-01-14 19:28:51', '0', '', NULL, '', NULL)\".\n\nThe table glpi_log is just fine as defined in - there is no old_id or new_id\n\nReproduction steps:\n1. create db\n2. import 0.85.5 mysql dump\n3. run php bin/console migration:myisam_to_innodb\n4. run php bin/console db:update", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould your provide the full error trace that can be found in the files/_log/php-errors.log file? It is necessary to be able to identify the exact step that failed.\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3753191636, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22669#issuecomment-3753191636", "createdAt": "2026-01-15T07:11:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "#22674 should fix this issue. Could you confirm?\n\nPatch for GLPI 11:\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3753258370, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22669#issuecomment-3753258370", "createdAt": "2026-01-15T07:36:07Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Juste a note: please make sure to first drop the entire broken database (that may be partially updated), and restore a clean dump of your original data.\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3753266419, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22669#issuecomment-3753266419", "createdAt": "2026-01-15T07:38:36Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "Skyler Adler the provided patch works - the db:update runs through (Skyler Adler with a newly imported dump)\n\nThanks for your help!\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3753861139, "author": "sr-it1", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22669#issuecomment-3753861139", "createdAt": "2026-01-15T09:57:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22669, "url": "https://github.com/glpi-project/glpi/issues/22669", "author": "sr-it1", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-14T19:51:20Z", "updatedAt": "2026-07-18T00:40:02Z", "closedAt": "2026-01-15T08:32:44Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Tickets opened via form changing entity without need in GLPI 11", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHey everyone, good afternoon!\n\nI came across a situation here regarding entity transfers in forms.\n\nThe thing is that in glpi 11, unlike 10, when you transfer the entity form, it also transfers the calls that have already been opened by it. I believe this must be a bug, as this should not happen.\n\nExample below:\n\nHere is a form created that is in the root entity, but in its target, I left it so that it would fall to the entity based on the user who filled it out, as is more common.\n\n[Image omitted]\n\nNow look at two tickets opened by this form. Note that each one is from a different entity. Imagine that a user in each entity accessed the same form and opened the ticket. So far, everything is normal:\n\n[Image omitted]\n\nNow, even after the tickets have been opened, regardless of whether they have been closed or not, etc., if I transfer the entity form, it will also transfer all tickets that have already been opened by that form to the same entity.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nThis does not happen in version 10. Although it is not common for someone to want to transfer an entity form after it has been created, this can happen if access needs to be restricted or something similar. The fact is that, apparently, as the new version of the forms now creates a link with all open calls, any change to the form entity will change the entity of all open calls. This cannot happen, since in the same form I can have several different conditions with calls being opened in other entities, since some define the target entity directly in the form or create questions for this.\n\nI believe it is a bug. A customer reported it, and then I tested it on two more GLPIs in version 11.0.4, and the behavior was the same.\n\nThank you for your attention!\n\nReproduction steps:\nOpen tickets from the same form with different target entities, transfer the entity form, and notice that all open tickets have changed to that same entity.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "Another detail: imagine that a user transfers the entity from the form and already has many open tickets in that form from different entities. They would change the entity of all tickets to that of the form. Imagine having to retransfer the ticket from each entity that changed incorrectly. It would be a big problem in reports, ticket access to technicians with entity profile limitations, indicators, etc.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3801838588, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22841#issuecomment-3801838588", "createdAt": "2026-01-26T21:27:14Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Micah Bennett,\n\nThis is configurable when executing the transfer:\n\n[Image omitted]\n\nIf you pick \"disconnect\", the tickets should not be moved into the new entity.\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4110768484, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22841#issuecomment-4110768484", "createdAt": "2026-03-23T13:51:25Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "OláMicah Bennett,\n\nIsso pode ser configurado ao executar a transferência:\n\n[Image omitted]\nSe você selecionar \"desconectar\", os tickets não devem ser movidos para a nova entidade.\n\nHello, thanks for the feedback. The problem is that I don’t think users will remember to click there. It would be better if the form remained separate from the generated tickets, as it was in GLPi 10. Because if a user transfers tickets without paying attention to this detail—say, transferring old tickets to entities they shouldn’t—it will affect metrics, ticket access, and so on.\n\nI suggest that, by default, the transfer should not affect tickets that have already been created, without the need to check this option, or else that this option should be checked by default when transferring.\n\nTranslated with DeepL.com (free version)\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4111397127, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22841#issuecomment-4111397127", "createdAt": "2026-03-23T15:13:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "If you want to change the default value of the \"complete\" transfert mode, you can do it here:\n\n[Image omitted]\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4116863218, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22841#issuecomment-4116863218", "createdAt": "2026-03-24T09:58:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22841, "url": "https://github.com/glpi-project/glpi/issues/22841", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-26T21:22:31Z", "updatedAt": "2026-07-04T00:48:39Z", "closedAt": "2026-03-25T07:49:02Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "No attachment in email notification", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello, e-mail notifications triggered by Event: \"Ticket Solved\" + Add Documents: \"Only documents related to the item that triggers the event\" will be sent without attachments.\n\nWe also have a similar notification for follow-ups, and in that case the attachments are sent correctly. This issue seems to affect solutions only.\n\nReproduction steps:\n1. Notification settings:\nNotification settings\n\n2. In the ticket, when we click “Add Solution” and attach one or more files:\nAdd new solution\n\n3. The solution is saved correctly and the attachment is visible in the ticket:\nSolution with attached file\n\n4. Ticket is set to \"Solved\" after adding solution:\nSolved\n\n5. The notification is generated and sent by GLPI via email, but no attachment is included:\nE-mail", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.blair@peppermint.local", "text": "I'm experiencing the exact same issue in version 11.0.4. Attached documents to the \"Ticket Resolve\" aren't sent in the email notification.\n\nOriginal response date: 2026-02-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3889667690, "author": "gromka", "anonymizedAuthorEmail": "taylor.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23071#issuecomment-3889667690", "createdAt": "2026-02-12T09:13:15Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please test #23099.\n\nOriginal response date: 2026-02-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3891151246, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23071#issuecomment-3891151246", "createdAt": "2026-02-12T14:04:44Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Hi,\nWe upgraded to GLPI version 10.0.24 in order to fix the issue with sending email attachments. However, the problem is still not resolved.\n\nSometimes the attachments are correctly included in the email, but sometimes they are missing. In those cases, we have to reopen the ticket and recreate the solution so that the attachment is properly sent by email.\n\nThis issue is really problematic for us because we send resolutions to users who do not have direct access to GLPI.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4023760126, "author": "xseth03", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23071#issuecomment-4023760126", "createdAt": "2026-03-09T13:22:20Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Hello Lane Bennett you mentioned 11.0.5 on the issue.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024537377, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23071#issuecomment-4024537377", "createdAt": "2026-03-09T15:20:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23071, "url": "https://github.com/glpi-project/glpi/issues/23071", "author": "dioig0", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-10T13:45:37Z", "updatedAt": "2026-06-20T01:05:45Z", "closedAt": "2026-03-11T08:56:07Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "PHP Error on Excel Export", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWe see PHP errors in the log (from an yet unknown user action) regarding to Excel export.\n\nReproduction steps:\nunknown", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "lane.bennett@peppermint.local", "text": "Maybe related to\nFormula Error: Unexpected operator '=' in /vendor/phpoffice/phpspreadsheet/src/PhpSpreadsheet/Cell/Cell.php:563 · Issue #4710 · PHPOffice/PhpSpreadsheet\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3957067599, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23231#issuecomment-3957067599", "createdAt": "2026-02-25T06:10:28Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "AI determines the following 2 solutions to solve the problem, maybe its a hint, i don't know.....\n\nSolution 1 (Recommended): Force the cell value to be written as TEXT\n\nProblem:\nPhpSpreadsheet automatically treats any value starting with = as a formula and tries to evaluate it, which causes the exception.\n\nFix:\nExplicitly set the cell data type to TYPE_STRING so the value is never interpreted as a formula.\n\nuse PhpOffice\\PhpSpreadsheet\\Cell\\DataType;\n\n$cell->setValueExplicit(\n $value,\n DataType::TYPE_STRING\n);\n\nResult:\n\nPrevents formula parsing\n\nWorks for all user-provided content\n\nSafest and most robust solution\n\nRecommended for:\nGLPI XLSX exports using\nPhpSpreadsheet\n\nSolution 2 (Alternative): Escape leading = characters\n\nProblem:\nValues starting with = are treated as formulas.\n\nFix:\nIf a string starts with =, prefix it with a single quote ', which forces Excel to treat it as text.\n\nif (is_string($value) && str_starts_with($value, '=')) {\n $value = \"'\" . $value;\n}\n\nResult:\n\nExcel displays the value as text\n\nFormula evaluation is skipped\n\nNote:\nThis is a valid workaround but slightly less clean than Solution 1, because it alters the displayed value format internally.\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3957074152, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23231#issuecomment-3957074152", "createdAt": "2026-02-25T06:12:40Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Can you provide a list of steps to reproduce this issue?\n\nHaving a field starting with \"=\" in the export does seem to be treated as a formula (by LibreOffice. I don't use MS Office), but I don't know how the PHP exception is being triggered for you.\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3961121686, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23231#issuecomment-3961121686", "createdAt": "2026-02-25T18:17:33Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "I tried to reproduce the error by exporting a Ticket list, but that was (technically) ok.\n\nNow i tried that with the solved+closed Tickets, and i get the error. These are 15590 Tickets.\n\nCould you provide a SQL to find the \"bad\" one(s) ?\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3964518315, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23231#issuecomment-3964518315", "createdAt": "2026-02-26T06:56:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23231, "url": "https://github.com/glpi-project/glpi/issues/23231", "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-25T06:08:47Z", "updatedAt": "2026-06-15T01:13:48Z", "closedAt": "2026-03-06T12:35:46Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Error accessing Projects module without “View all” permission", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen creating a custom profile without enabling the “View all” permission under the Projects tab, an error occurs when the user tries to access the Projects section from the main menu.\n\nIf the “View all” permission is checked, the module loads normally.\nThe issue only occurs when this permission is disabled.\n\nReproduction steps:\n1. Go to Setup → Profiles.\n2. Create or edit a profile and open the Projects permissions tab.=\n3. Uncheck the “View all” option.\n4. Assign this profile to a test user.\n5. Log in with that user and access the Projects menu.\n6. The system throws an error, and the page fails to load correctly.", "priority": "medium", "type": "support", "createdByEmail": "finley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Please post the exact error you are seeing and any entries from the GLPI logs (files/_log folder) around the time of the issue.\n\nOriginal response date: 2025-11-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3515896361, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21876#issuecomment-3515896361", "createdAt": "2025-11-11T09:39:59Z" } }, { "userEmail": "finley.bennett@peppermint.local", "text": "I cannot recreate the issue. Please post the exact error you are seeing and any entries from the GLPI logs (files/_log folder) around the time of the issue.\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3553925708, "author": "SRDEYV", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21876#issuecomment-3553925708", "createdAt": "2025-11-19T17:39:44Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I cannot reproduce. Please try without plugins.\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3556070588, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21876#issuecomment-3556070588", "createdAt": "2025-11-20T06:11:23Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I suspect an issue when $_SESSION['glpigroups'] is empty.\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3556237044, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21876#issuecomment-3556237044", "createdAt": "2025-11-20T06:59:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21876, "url": "https://github.com/glpi-project/glpi/issues/21876", "author": "SRDEYV", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-10T20:00:24Z", "updatedAt": "2026-05-15T00:57:10Z", "closedAt": "2026-02-03T10:33:35Z" } }, { "title": "When searching a Custom Asset I get a error", "detail": "Affected version:\n11.0.4\n\nIssue description:\nIn my Asset webpage, when I search for any filter in the search field I get an error.\nAn unexpected error occurred\nReturn to previous page\n\nReproduction steps:\nHave a Custom asset\nUse the search field\nWrite anything in the \"contains\" field for example\n\nEnvironment details:\nGLPI 11.0.4\nRunning on AWS EC2 instance, debian.", "priority": "medium", "type": "support", "createdByEmail": "elliot.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "There should be a PHP error in the GLPI logs (files/_log folder by default) which we would need.\n\nOriginal response date: 2026-01-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3720480321, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22588#issuecomment-3720480321", "createdAt": "2026-01-07T19:44:06Z" } }, { "userEmail": "riley.blair@peppermint.local", "text": "I see the same screen when accessing projects with a profile that has the \"see all\" project option disabled in the profile settings.\n\nThe error screen follows with DEBUG mode enabled.\n[Image omitted]\n\nIn the php_erros.log file, the following error is returned:\n[2026-01-15 21:43:43] glpi.CRITICAL: * Uncaught PHP Exception Twig\\Error\\RuntimeError: \"An exception has been thrown during the rendering of a template (\"Empty IN are not allowed\") in \"pages/generic_list.html.twig\" at line 37.\" at generic_list.html.twig line 37\n Backtrace :\n ./templates/pages/generic_list.html.twig:37\n ./vendor/twig/twig/src/Template.php:358 Twig\\Template->yield()\n ./vendor/twig/twig/src/Template.php:373 Twig\\Template->display()\n ./vendor/twig/twig/src/TemplateWrapper.php:51 Twig\\Template->render()\n .../Glpi/Application/View/TemplateRenderer.php:170 Twig\\TemplateWrapper->render()\n ./src/Glpi/Controller/AbstractController.php:68 Glpi\\Application\\View\\TemplateRenderer->render()\n ./src/Glpi/Controller/GenericListController.php:51 Glpi\\Controller\\AbstractController->render()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\GenericListController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n Previous: Empty IN are not allowed\n ./src/DBmysqlIterator.php:612\n ./src/DBmysqlIterator.php:578 DBmysqlIterator->analyseCriterion()\n ./src/DBmysqlIterator.php:566 DBmysqlIterator->analyseCrit()\n ./src/DBmysqlIterator.php:309 DBmysqlIterator->analyseCrit()\n ./src/Search.php:619 DBmysqlIterator->buildQuery()\n ./src/Glpi/Search/Provider/SQLProvider.php:4246 Search::addDefaultWhere()\n ./src/Glpi/Search/SearchEngine.php:662 Glpi\\Search\\Provider\\SQLProvider::constructSQL()\n ./src/Glpi/Search/SearchEngine.php:678 Glpi\\Search\\SearchEngine::getData()\n ./src/Glpi/Search/SearchEngine.php:635 Glpi\\Search\\SearchEngine::showOutput()\n : Glpi\\Search\\SearchEngine::show()\n ...Application/View/Extension/PhpExtension.php:105 call_user_func_array()\n ...ates/01/01699a601bc2513f78cd044355a7a569.php:55 Glpi\\Application\\View\\Extension\\PhpExtension->call()\n ./vendor/twig/twig/src/Template.php:402 TwigTemplate_e85adf5555ff44ed23544ca214e06a46->doDisplay()\n ./vendor/twig/twig/src/Template.php:358 Twig\\Template->yield()\n ./vendor/twig/twig/src/Template.php:373 Tw\n\n[Content truncated.]\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3757032253, "author": "jvergacas", "anonymizedAuthorEmail": "riley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22588#issuecomment-3757032253", "createdAt": "2026-01-15T21:47:10Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce.\n\nFirst, try without any plugin.\nThen, if you still reproduce - that's maybe because you have a field/field type that is displayed on your side that is not on mine.\n\nWe need a way to reproduce in order to work on a fix.\n\nOriginal response date: 2026-01-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3758517564, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22588#issuecomment-3758517564", "createdAt": "2026-01-16T07:17:15Z" } }, { "userEmail": "sage.bennett@peppermint.local", "text": "I am writing in this field because I am experiencing the same issue.\nI created two custom assets:\n\n[Image omitted]\n\n[Image omitted]\n\nMaintenant quand je vais sur mon onglet Parc -> Carte SIM et que je fait une recherche via le nom utilisateur (par exemple)\nla serveur plante et seul la réinitialisation des données de navigation permet de retrouver la page\nle lien pointe sur\n\nNow, when I go to onglet Parc -> Carte SIM and a search using the user name (for example), the server crashes, and only resetting the browsing data allows the page to be accessible again.\nThe link points to:\n\n[Image omitted]\n\nI noticed that if I remove the custom field column “Forfait”, the search works correctly.\n\n[Image omitted]\n\nI am also including the PHP error that occurs afterward\n\nglpi.CRITICAL: * Uncaught PHP Exception Twig\\Error\\RuntimeError: \"An exception has been thrown during the rendering of a template (\"MySQL query error: Unknown column 'glpi_assets_assets_96f688200abc7dc2a2376456bdba771d.name' in 'where clause' (1054) in SQL query \"SELECT DISTINCT glpi_assets_assets.id AS id, 'christopher' AS currentuser,\n glpi_assets_assets.entities_id, glpi_assets_assets.is_recursive, glpi_assets_assets.name AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_1, glpi_assets_assets.id AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_1_id, glpi_entities.completename AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_80, glpi_assets_assettypes.name AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_4, glpi_manufacturers.name AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_23, glpi_states.completename AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_31, glpi_users.name AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_70, glpi_users.realname AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_70_realname, glpi_users.id AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_70_id, glpi_users.firstname AS ITEM_Glpi\\CustomAsset\\CarteSimAsset_70_firstname, glpi_phones_custom_fields_61cc926924ef60eb7fe0e9914d862c1b.name AS ITEM\n\n[Content truncated.]\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3777015134, "author": "Toyama007", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22588#issuecomment-3777015134", "createdAt": "2026-01-21T09:18:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22588, "url": "https://github.com/glpi-project/glpi/issues/22588", "author": "GOAguiar99", "anonymizedAuthorEmail": "elliot.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-07T19:41:41Z", "updatedAt": "2026-05-02T00:52:50Z", "closedAt": "2026-01-21T13:02:55Z" } }, { "title": "Collector V10 - Issue in creating requestor if header contains From: first_name.last_name", "detail": "Affected version:\nGLPI 10.0.18 ( => /var/www/html/glpi) Installation mode: TARBALL Current language:fr_FR\n\nIssue description:\nThe user is unknown (GLPI must create them) - The Display Name is identical to the local part of the address (first_name.last_name ). This redundancy leads to a failure in the user creation routine.\n\nInterpretation issue with the 'From' field = first_name.last_name [[email redacted]](mailto:[email redacted]) in the GLPI collector, which seems to prevent the creation of a row in the glpi_tickets_users table as the requestor in the email field associated with the ticket.\n\nI created a Google account to simulate user = last_name.first_name and email=[email redacted], and the mail arrives with the header containing From = \"last_name.first_name\" .\n\nHypothesis 1: The display name is the same as the local part of the mailbox - RFC 5322 Standard - if From = \"first_name.last_name\" >> it's OK > requestor field = email; if From = first_name.last_name >> it's NOT OK (KO) > the ticket is created but without a requestor.\n\nWe do not integrate the requestors from collected emails as users; the emails will be recorded as the requestor (type = 1 in the Ticket users table).\n\nHypothesis 2: The problematic email uses the iso-8859-1 encoding for the subject, whereas the working email uses standard ASCII. If your GLPI is configured for UTF-8 and encounters an issue when decoding iso-8859-1 specifically on this mail, this could also generate the exception that causes the failure in the requestor attribution step.\n\nSubject Field = =?iso-8859-1?Q?RE:_Mise_=E0_jour_Rxx?= // RFC 2047 Standard (Encoding Non-ASCII Strings) - Uses iso-8859-1 encoding (Latin-1).\n\nEnvironment details:\nGLPI 10.0.18 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language:fr_FR", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please write in English (automatic translations are OK).\n\nHaving issues reported all in English helps ensure that searching for existing/already reported issues is easier.\nAlso, the community and development team is international so having a common language helps us too.\n\nVeuillez écrire en anglais (les traductions automatiques sont acceptables).\n\nLe fait que les problèmes signalés soient tous en anglais permet de faciliter la recherche de problèmes existants ou déjà signalés.\nDe plus, la communauté et l'équipe de développement étant internationales, le fait d'avoir une langue commune nous aide également.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3632794679, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22308#issuecomment-3632794679", "createdAt": "2025-12-09T15:14:36Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please:\n- write in english only\n- use the latests available release\n- try without any plugin.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3632798279, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22308#issuecomment-3632798279", "createdAt": "2025-12-09T15:15:16Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "Sorry, I just updated the title and bug description\n\nOriginal response date: 2025-12-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3646988266, "author": "wfort-GRADeS-CVL", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22308#issuecomment-3646988266", "createdAt": "2025-12-12T15:24:53Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "* use the latests available release\n\n* try without any plugin.\n\nThose are still required\n\nOriginal response date: 2025-12-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3653483735, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22308#issuecomment-3653483735", "createdAt": "2025-12-15T06:05:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22308, "url": "https://github.com/glpi-project/glpi/issues/22308", "author": "wfort-GRADeS-CVL", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-09T15:10:16Z", "updatedAt": "2026-04-16T00:51:41Z", "closedAt": "2026-01-05T09:56:26Z" } }, { "title": "missing buttons - \"Put in trashbin\" ans \"Save\"", "detail": "Affected version:\nGLPI 11.0.4\n\nIssue description:\nmissing buttons:\n\n\"Put in trashbin\" in \"Actions\"\nthis prevents deletions of Computers, in Assets\n\n\"Save\"\nagain, in any Computer Details, in Computers in Assets, \"Save\" button is missing, so I cannot edit any Information in Computers, Assets\n\nPlease note:\nas far as I noticed, _this only affects Computers, in Assets_ - I dont have itens in the majoroty of Assets Categories, so I can’t guarantee that all of those categories have the same issue.\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\ntry to delete a Computer from Assets", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The buttons to put in trashbin and save are at the bottom of the main form, not in the Actions menu. The actions menu is mainly the same as the massive actions menu which you can access by selecting items in the search results list and clicking the Actions button. Since the delete button is already on the form, it is removed from the list for single items.\n\nCan you confirm the buttons show at the bottom of the form?\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3697578240, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22502#issuecomment-3697578240", "createdAt": "2025-12-29T21:26:40Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "hello\nthanks for your quick answer.\n\nplease check the following two Pictures:\n\n- the first one shows the Buttons on Monitor Details (in \"Assets\", \"Monitors\",)\n- on the second, on Computer Details, the Buttons are missing (in \"Assets\", \"Computers\",)\n\n[Image omitted]\n\n[Image omitted]\n\nBest Regards,\nJose Luis\n\nOriginal response date: 2025-12-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3699664280, "author": "jluis144", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22502#issuecomment-3699664280", "createdAt": "2025-12-30T15:12:51Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Please test with plugins disabled.\n\nOriginal response date: 2025-12-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3699887482, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22502#issuecomment-3699887482", "createdAt": "2025-12-30T16:34:03Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "with Plugins disable, nothing changes - both buttons are still missing\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-12-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3699957281, "author": "jluis144", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22502#issuecomment-3699957281", "createdAt": "2025-12-30T17:02:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22502, "url": "https://github.com/glpi-project/glpi/issues/22502", "author": "jluis144", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-29T20:12:12Z", "updatedAt": "2026-04-11T00:42:34Z", "closedAt": "2025-12-31T15:59:52Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Wrong language selected for login panel", "detail": "Affected version:\n10.0.18\n\nIssue description:\nWhen trying to log in to a main panel i encountered weird issue. When i have more than 1 language in web browser, it selects by default english. I have to delete all other languages to make it select my actual language.\n\nIt appears despite having default language Polish on my web browser and system. I'm using Windows 11 and 10 OS.\n\nI also tested it from a CMD level by a curl command and it didn't have to select correct language to display - Polish. On a Linux Ubuntu and Windows it both displayed polish for a login panel - It is a good behavior.\n\nPlease let me know if it was fixed because i didn't find solutions in changelogs and glpi forum\n\nEnvironment details:\nv10.0.18 GLPI\nextra plugins: ActualTime, GroupCategory, taskList", "priority": "medium", "type": "support", "createdByEmail": "jordan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "GLPI 10.0.18 has been released on February. It is pretty hard to remember every fix done, so you should test on GLPI 10.0.22 by yourself to see if the problem persists.\n\nAlso, please indicate what is the request headers sent by your browser, it may help to investigate.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3636386283, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22321#issuecomment-3636386283", "createdAt": "2025-12-10T10:25:49Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "Maybe that will suit your need better :) This is a url for our GLPI\n\nOriginal response date: 2025-12-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3642371816, "author": "wojtek19022", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22321#issuecomment-3642371816", "createdAt": "2025-12-11T15:07:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Maybe that will suit your need better :) This is a url for our GLPI\n\nNot really. The result depends on the headers sent by your browser.\nFor instance, your GLPI's login page is correctly displayed in French on my machine, according to the sent headers (accept-language: fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7).\n\nOriginal response date: 2025-12-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3642403910, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22321#issuecomment-3642403910", "createdAt": "2025-12-11T15:15:19Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "Oh sorry my bad.\n\nOriginal response date: 2025-12-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3642538558, "author": "wojtek19022", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22321#issuecomment-3642538558", "createdAt": "2025-12-11T15:44:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22321, "url": "https://github.com/glpi-project/glpi/issues/22321", "author": "wojtek19022", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "froozeify", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-10T10:15:15Z", "updatedAt": "2026-03-28T00:40:17Z", "closedAt": "2025-12-17T13:12:15Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Some languages are not able to retrieve form translations", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nOriginally noted in\n\nSeems like an issue within ItemTranslation::getTranslation. When it is asked for a translation with a count of 1, it tries getting the \"other\" translation instead of \"one\" for Japanese. The logic may be technically correct since I don't think Japanese has plurals as it relies on context, but it seems incompatible with our locales and doesn't let 1 = singular. Even though the issue is noted from this PR, the same issue occurs if you use the form translation UI to add a Japanese translation where the UI presents fields for \"one\" translations but then tries getting \"other\" translations later.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "The plural forms described in the ja_JP.po file are Plural-Forms: nplurals=1; plural=0;. The same rule also applies to id_ID, ko_KR, ms_MY, th_TH, vi_VN, zh_CN, zh_HK, zh_TW. It is supposed to mean that any n value will correspond to the unique plural form of the translation.\n\nNote that even if it fixes the issue (I am not sure of that), tt will not be possible to use 0 = singular because many languages are using the Plural-Forms: nplurals=2; plural=(n != 1); rule, meaning that 0 will return the plural form of the string.\n\nOriginal response date: 2025-09-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3291841632, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21003#issuecomment-3291841632", "createdAt": "2025-09-15T12:08:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "From\n\nSome languages only require one single form. There is no distinction between the singular and plural form. An appropriate header entry would look like this:\nPlural-Forms: nplurals=1; plural=0;\nLanguages with this property include:\nAsian family\nJapanese, Vietnamese, Korean\nTai-Kadai family\nThai\n\nOriginal response date: 2025-09-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3291986246, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21003#issuecomment-3291986246", "createdAt": "2025-09-15T12:41:00Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I think our locale files are correct, but the logic used to determine the form to get from form translations seems wrong although I wasn't able to understand what it was doing from a quick glance. The use of eval seems suspicious. It seems safe to assume that if $count is 1, we want the translation stored in the \"one\" key regardless of how plurals work for the language.\n\nOriginal response date: 2025-09-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3291997429, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21003#issuecomment-3291997429", "createdAt": "2025-09-15T12:44:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I did not understood how the failing method should work (I did not take time to try ^^)\n\nIt seems safe to assume that if $count is 1, we want the translation stored in the \"one\" key regardless of how plurals work for the language.\n\nYes, sounds like this should work like that.\n\nOriginal response date: 2025-09-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3292216157, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21003#issuecomment-3292216157", "createdAt": "2025-09-15T13:38:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21003, "url": "https://github.com/glpi-project/glpi/issues/21003", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-15T11:55:54Z", "updatedAt": "2026-03-21T00:37:01Z", "closedAt": "2025-12-10T13:04:11Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Session::loadAllCoreLocales huge memory usage", "detail": "Issue description:\nThis method load all locales files and messages, costing 50MB of memory.\n\nThis is huge, especially since GLPI memory recommandation is 64MB.\n\nThe installation use 126MB on GLPI 11 (versus 35MB on GLPI 10) so we need to either fix it or increase the recommendation.", "priority": "high", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "My thoughts at the time were that we could eventually let the user specify the languages they want to use in GLPI and then only load those locales to pre-fill form translations. Most businesses will probably use 5 or less locales.\n\nOriginal response date: 2025-12-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3601604070, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22173#issuecomment-3601604070", "createdAt": "2025-12-02T11:37:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This seems to fix the issue:\n\nIt need some work to make it cleaner (and exclude the default language as it should probably never be deleted).\n\nOriginal response date: 2025-12-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3601618229, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22173#issuecomment-3601618229", "createdAt": "2025-12-02T11:42:02Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "let the user specify the languages they want to use\n\nNot sure about that idea. How an administrator can know which language a GLPI user would like to use? Having several locales available should not have a huge cost; since it should only be called on demand.\n\nThis is huge, especially since GLPI memory recommandation is 64MB.\n\nAnyway, it probably can also be increased; 64Mb is not that much nowadays.\n\nOriginal response date: 2025-12-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3601783127, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22173#issuecomment-3601783127", "createdAt": "2025-12-02T12:26:15Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Not sure about that idea. How an administrator can know which language a GLPI user would like to use? Having several locales available should not have a huge cost; since it should only be called on demand.\n\nIt is only affecting the pre-fill of translations for items like the default forms. Users could still choose their own language beyond those initial selections. The GLPI admin doing the install probably has or could get a good idea of the required languages based on the geographic areas their business operates in.\n\nOriginal response date: 2025-12-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3601880050, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22173#issuecomment-3601880050", "createdAt": "2025-12-02T12:51:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22173, "url": "https://github.com/glpi-project/glpi/issues/22173", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-02T11:31:32Z", "updatedAt": "2026-03-15T00:44:42Z", "closedAt": "2025-12-04T14:52:37Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "CAS users not autocreate", "detail": "Affected version:\n11.01\n\nIssue description:\nHello,\n\nI have installed the new version GLPI 11.01.\nI am encountering a problem with CAS authentication when a new user logs in.\nIf I do not manually create the user, an error occurs during login and their account is not created.\n\nThe option in Authentication → Authentication Configuration → Automatically add users : YES\n\nBest regards,", "priority": "medium", "type": "support", "createdByEmail": "hayden.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "remy.blair@peppermint.local", "text": "Hello. We are using ApereoCAS and OpenLDAP. Authentication of new users, based on ldap, with noCAS=1 is ok. Import of LDAP users with users manager page is ok. But same bug, can't login with CAS for new users :\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605588230, "author": "FranckAudebrand", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21778#issuecomment-3605588230", "createdAt": "2025-12-03T08:12:39Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "#22185 should solve this issue. Could you confirm ?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605640797, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21778#issuecomment-3605640797", "createdAt": "2025-12-03T08:29:04Z" } }, { "userEmail": "remy.blair@peppermint.local", "text": "This work :\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605706034, "author": "FranckAudebrand", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21778#issuecomment-3605706034", "createdAt": "2025-12-03T08:46:25Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Remy Blair could you please just test the proposed solution?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605844033, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21778#issuecomment-3605844033", "createdAt": "2025-12-03T09:17:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21778, "url": "https://github.com/glpi-project/glpi/issues/21778", "author": "nicoGri34", "anonymizedAuthorEmail": "hayden.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-04T12:27:52Z", "updatedAt": "2026-03-14T00:37:17Z", "closedAt": "2025-12-03T10:01:40Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "The result count disappears if you ask to display more than this number", "detail": "Affected version:\n11.0.2\n\nIssue description:\nI have 47 results here. If I ask to display 40 per page, I get this display:\n\n[Image omitted]\n\nBut if I ask for more than 47 per page, the number of results disappears:\n\n[Image omitted]\n\nThank you. Pierre", "priority": "medium", "type": "support", "createdByEmail": "micah.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Where do you have this bug? Main lists (like Computer or Ticket) seems to work as expected.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3570748011, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22046#issuecomment-3570748011", "createdAt": "2025-11-24T13:15:44Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I do not see a bug here. The pagination controls disappear when there is only one page to show.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3571541249, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22046#issuecomment-3571541249", "createdAt": "2025-11-24T16:01:18Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "As far as I understand, Micah Adler complains about number of results (47 in his screenshot are missing).\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3572110131, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22046#issuecomment-3572110131", "createdAt": "2025-11-24T18:15:25Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "In the \"short_display\" version the item count is part of the pagination controls. In other cases it is separate. I cannot tell where this issue is being seen from the screenshot though.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3572131273, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22046#issuecomment-3572131273", "createdAt": "2025-11-24T18:20:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22046, "url": "https://github.com/glpi-project/glpi/issues/22046", "author": "PierreTeclib", "anonymizedAuthorEmail": "micah.adler@peppermint.local", "assignees": [ { "sourceLogin": "RomainLvr", "anonymizedEmail": "sage.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-24T11:47:23Z", "updatedAt": "2026-03-12T00:35:58Z", "closedAt": "2025-12-01T10:08:22Z" }, "assignedTo": "sage.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Inventory import from FreeBSD fails — “Out of range value for column 'capacity'”", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHello,\n\nI encountered an error when sending an inventory from a FreeBSD server using GLPI Agent 1.15 to GLPI 11.0.2.\n\nThe agent runs normally, but during data submission the server returns a 500 Internal Server Error.\n\nAgent output:\n[debug] Full inventory kept\n[error] [http client] communication error: 500 Internal Server Error, MySQL query error: Out of range value for column 'capacity' at row 1 (1264) in SQL query \"INSERT INTO glpi_items_deviceharddrives (deviceharddrives_id, itemtype, items_id, is_dynamic, serial, capacity, locations_id, states_id, enti\n[error] [http client] 9A8F090B: server error: MySQL query error: Out of range value for column 'capacity' at row 1 (1264) in SQL query \"INSERT INTO glpi_items_deviceharddrives (deviceharddrives_id, itemtype, items_id, is_dynamic, serial, capacity, locations_id, states_id, enti\n[debug] Remote inventory task execution disabled: no remote setup\n\nServer output:\nglpi-server | 192.168.32.1 - - [12/Nov/2025:15:45:02 +0300] \"POST / HTTP/1.1\" 500 883 \"-\" \"GLPI-Agent_v1.15\"\n\nuname -a:\nFreeBSD venera.zenon-vm.local 14.3-RELEASE-p5 FreeBSD 14.3-RELEASE-p5 releng/14.3-n271450-382f54740ee4 virt amd64\n\nglpi-agent --force --debug --logger=stderr:\n[debug] Logger backend Stderr initialized\n[debug] GLPI Agent (1.15)\n[debug] Configuration directory: /usr/local/etc/glpi-agent\n[debug] Data directory: /usr/local/share/glpi-agent\n[debug] Storage directory: /usr/local/var/glpi-agent\n[debug] Lib directory: /usr/local/share/glpi-agent/lib\n[debug] Available tasks:\n[debug] - Collect: 2.11\n[debug] - Deploy: 3.5\n[debug] - ESX: 2.14\n[debug] - Inventory: 1.22\n[debug] - NetDiscovery: 6.8\n[debug] - NetInventory: 6.8\n[debug] - RemoteInventory: 1.8\n[debug] - WakeOnLan: 2.2", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Database field type can be changed; but I'd like to make sure there is nothing wrong in inventoried data.\nHarddrive capacity from inventory must be in MB, it would mean your harddrive has a ~2000 TB capacity.\n\nPlease provide inventory data related to harddrive and tell us the current expected capacity of this drive.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521856122, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21900#issuecomment-3521856122", "createdAt": "2025-11-12T13:07:38Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "The server has two physical drives, each with a capacity of 1 TB.\n\n ACS-4 ATA SATA 3.x device\n 1000204886016\n ST1000NM000A-2J3100 TN03\n ada1\n WRF021GF\n disk\n\n ACS-2 ATA SATA 3.x device\n 1000204886016\n ST1000NM0033-9ZM173 SN04\n ada0\n Z1W4RM6J\n disk\n\nfrom dmesg:\nada0: ACS-2 ATA SATA 3.x device\nada0: 953869MB (1953525168 512 byte sectors)\n\nada1: ACS-4 ATA SATA 3.x device\nada1: 953869MB (1953525168 512 byte sectors)\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521919166, "author": "virt1122", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21900#issuecomment-3521919166", "createdAt": "2025-11-12T13:22:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "OK, so it seems like there is something wrong in source inventory file (cant' be sure because you did not provide it). If so, this is an Agent issue.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521950124, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21900#issuecomment-3521950124", "createdAt": "2025-11-12T13:28:55Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "Thank you for the clarification. I would like to add that the same FreeBSD server, when inventoried by GLPI 10.0.20 using the same agent version (1.15), did not produce this error — all hard drive capacities were recorded correctly. This suggests that the issue appears only with GLPI 11.0.2.\n\ninventory.xml\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3522074547, "author": "virt1122", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21900#issuecomment-3522074547", "createdAt": "2025-11-12T13:56:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21900, "url": "https://github.com/glpi-project/glpi/issues/21900", "author": "virt1122", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-12T12:53:23Z", "updatedAt": "2026-02-22T00:40:27Z", "closedAt": "2025-11-13T06:09:09Z" } }, { "title": "GLPI 11 - Error Itilcategory Code", "detail": "Affected version:\nGLPI 11\n\nIssue description:\nIn GLPI 10 I used the code that represents the ticket category in my rules::\n\n[Image omitted]\n\n[Image omitted]\n\nThis rule is just an example.\n\nAffected page:\nTicket.php\n\nReproduction steps:\nCreate ItilCategory with code\nCreate rule with this code\nOpen a ticket with this category\nAnd rule won't work", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you explain a bit more what \"See the magic rsrs\" means?\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3384390320, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21366#issuecomment-3384390320", "createdAt": "2025-10-09T06:55:01Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "JUst open a ticket with this category(category with code) and see that it is not working.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3387261684, "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21366#issuecomment-3387261684", "createdAt": "2025-10-09T19:41:36Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "I think I've found the issue, if I use a space in my category code, it doesn't work:\n[Image omitted]\nBut if I use remove the space:\n[Image omitted]\nThen the rule works - see the rule and the resulting ticket below:\n[Image omitted]\n[Image omitted]\n\nDo you think this is a bug? For now I will use codes without space\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3388000854, "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21366#issuecomment-3388000854", "createdAt": "2025-10-10T01:44:15Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "Hi team, any feedback about this bug?\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3429314755, "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21366#issuecomment-3429314755", "createdAt": "2025-10-21T19:52:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21366, "url": "https://github.com/glpi-project/glpi/issues/21366", "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [ { "sourceLogin": "stonebuzz", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-08T16:59:14Z", "updatedAt": "2026-02-15T00:42:14Z", "closedAt": "2025-11-06T10:03:55Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI Iventory : Computer Inventory Number set as No Asset Information -> unable to import using Fields Unicity", "detail": "Affected version:\nGLPI 10.0.20\n\nIssue description:\nHello, i'm using the Field Unicity for the Inventory Number.\nBut with the last update of GLPI, Computer Inventory Number is set to \" No Asset Information\" so i can not import any new Computer. Before it was just blank.\n\nReproduction steps:\nConfigure The Fields unicity to Active Yes and Unique fields = Inventory Number.\nImport a computer that does not exist.\nImport is not ok, error 500 item can not be created.\n\nEnvironment details:\nOperating system: Linux ff-glpi-2015 6.1.0-40-amd64 #​1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64\nPHP 8.2.29 apache2handler (Core, FFI, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, apcu, bz2, calendar,\n ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, imap, intl, json, ldap, libxml, mbstring, mysqli,\n mysqlnd, openssl, pcre, pdo_mysql, posix, random, readline, session, shmop, sockets, sodium, standard, sysvmsg, sysvsem,\n sysvshm, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib)\nSetup: max_execution_time=\"800\" memory_limit=\"1024M\" post_max_size=\"500M\" safe_mode=\"\" session.save_handler=\"files\"\n upload_max_filesize=\"500M\" disable_functions=\"\"\nSoftware: Apache (Apache Server at cds.formation.forem Port 443\n)\n Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36 Edg/141.0.0.0\nServer Software: Debian 12\n Server Version: 10.11.14-MariaDB-0+deb12u2\n Server SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n Parameters: ocs@localhost/ocsweb\n Host info: Localhost via UNIX socket\n\nPHP version (8.2.29) is supported.PHP version (8.2.29) is supported.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nmysqli extension is installed.mysqli extension is installed.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, json, simplexml, xmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, json, simplexml, xmlreader, xmlwriter.\ncurl extension is installed.curl extension is installed.\ngd extension is installed.gd extension is installed.\nintl extension is installed.intl extension is installed.\nzlib extension is installed.zlib extension is installed.\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nDatabase engine version (10.11.14) is supported.Database engine version (10.11.14) is supported.\nNo files from previous GLPI version detected.No files from previous GLPI version detected.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/lib/glpi/_cache has been validated. Write access to /var/lib/glpi/_cron has been validated. Write access to /var/lib/glpi has been validated. Write access to /var/lib/glpi/_dumps has been validated. Write access to /var/lib/glpi/_graphs has been validated. Write access to /var/lib/glpi/_lock has been validated. Write access to /var/lib/glpi/_pictures has been validated. Write access to /var/lib/glpi/_plugins has been validated. Write access to /var/lib/glpi/_rss has been validated. Write access to /var/lib/glpi/_sessions has been validated. Write access to /var/lib/glpi/_tmp has been validated. Write access to /var/lib/glpi/_uploads has been validated.Write access to /var/lib/glpi/_cache has been validated.\nWrite access to /var/lib/glpi/_cron has been validated.\nWrite access to /var/lib/glpi has been validated.\nWrite access to /var/lib/glpi/_dumps has been validated.\nWrite access to /var/lib/glpi/_graphs has been validated.\nWrite access to /var/lib/glpi/_lock has been validated.\nWrite access to /var/lib/glpi/_pictures has been validated.\nWrite access to /var/lib/glpi/_plugins has been validated.\nWrite access to /var/lib/glpi/_rss has been validated.\nWrite access to /var/lib/glpi/_sessions has been validated.\nWrite access to /var/lib/glpi/_tmp has been validated.\nWrite access to /var/lib/glpi/_uploads has been validated.\n\nWeb server root directory configuration seems safe.Web server root directory configuration seems safe.\nSessions configuration is secured.Sessions configuration is secured.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nexif extension is installed.exif extension is installed.\nldap extension is installed.ldap extension is installed.\nopenssl extension is installed.openssl extension is installed.\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2, Phar, zip.\nZend OPcache extension is installed.Zend OPcache extension is installed.\nFollowing extensions are installed: ctype, iconv, mbstring, sodium.Following extensions are installed: ctype, iconv, mbstring, sodium.\nWrite access to /var/www/glpi/marketplace has been validated.Write access to /var/www/glpi/marketplace has been validated.\nTimezones seems loaded in database.Timezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Can you provide any relevant log (php-error.log) with the error you got ?\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460480390, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21679#issuecomment-3460480390", "createdAt": "2025-10-29T09:07:59Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I cannot reproduce with provided instructions. Try without plugins, and if issue persists, provide logs as requested.\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460546619, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21679#issuecomment-3460546619", "createdAt": "2025-10-29T09:24:52Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Here is the log from the glpi agent :\n[Wed Oct 29 08:48:22 2025][error] [http client] communication error: 500 Internal Server Error, Unable to create item.;Enregistrement impossible pour Numéro d'inventaire = No Asset InformationUn autre élément existe[LAF-483811 - ID : 5\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460579236, "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21679#issuecomment-3460579236", "createdAt": "2025-10-29T09:32:58Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "We need GLPI logs.\nThere is no \"No Asset Information\" in GLPI core; no idea where it comes from.\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460594558, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21679#issuecomment-3460594558", "createdAt": "2025-10-29T09:37:01Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21679, "url": "https://github.com/glpi-project/glpi/issues/21679", "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-29T08:00:54Z", "updatedAt": "2026-02-07T00:37:23Z", "closedAt": "2025-10-29T10:05:54Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "User forms simplified mode: the user cannot enter the computer name in a form.", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWhen I’m in form creation mode, the computer names are displayed correctly. However, when the user tries to use this form, they can’t enter the computer name. traduit\n\n1. form creation mode\n\n[Image omitted]\n\n[Image omitted]\n\n2. User forms mode simplifield : the user cannot enter the computer name in a form.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Jesse Bennett, thanks for the report.\n\nIndeed, the user should be able to see his own computers here (but not all computers as this would be a security issue).\nLooking into it.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432603175, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21509#issuecomment-3432603175", "createdAt": "2025-10-22T14:18:38Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Note that you may use the \"User device\" question type as a workaround:\n\n[Image omitted]\n\nThis question work as expected but note that it returns all types of assets, not just computers.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432637996, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21509#issuecomment-3432637996", "createdAt": "2025-10-22T14:24:14Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Ping Skyler Adler Skyler Adler\n\nWe will have to discuss the behavior of the getAssignableVisiblityCriteria method criteria to see how we can fix this for helpdesk users.\n\nRight now, this method block all results if the user doesn't have any of the following rights:\n\n[Image omitted]\n\nThis doesn't work for self service users because the READ_OWNED right is specific to central users (so it can't be enabled).\n\nWe have to a pick a solution:\n\n1. Allow READ_OWNED to be set for helpdesk users (downside: might include side effect if the right is used elsewhere, maybe the user will end up having access to the computer view from some part of the UI or the API which we probably don't want to as assets are not supposed to be visible from the helpdesk? also it will need to be manually enabled for each profiles if we decide to disable it by default)\n\n2. Add a specific behavior for getAssignableVisiblityCriteria when we are in the helpdesk. No rights checks, we just return the items owned by the users or his groups (downside: can't be disabled).\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432713361, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21509#issuecomment-3432713361", "createdAt": "2025-10-22T14:39:07Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "when you enable Simplified mode you are loosing Assets tab in Self-service profile. maybe thats why that problem occurs?\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3435143499, "author": "n0womann0cry", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21509#issuecomment-3435143499", "createdAt": "2025-10-23T05:24:30Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21509, "url": "https://github.com/glpi-project/glpi/issues/21509", "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-16T07:30:47Z", "updatedAt": "2026-02-05T00:39:42Z", "closedAt": "2025-10-27T17:23:20Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 11.0.1 : Problem with the \"Known Email Domain\" rule in mail collectors", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHello,\n\nI'm experiencing a problem with the \"Rules for assigning a ticket created via a mail collector\" rule, particularly with the \"Known Email Domain > is > yes\" criterion.\n\nDuring my tests, the rule consistently fails to validate a domain that is properly registered in the entity, such as \"abc-auto.com.\" After several attempts, the test remains invalid.\n\nI suspect that the hyphen character \"-\" in the domain name may not be correctly interpreted, thus preventing the domain from being detected as known.\n\nCan you verify if this is a bug or if there is a special treatment to apply to this type of domain?\n\nThank you in advance for your help.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try #21563. I just add a new test; I'm not 100% sure it will fix the issue.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3424779606, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21561#issuecomment-3424779606", "createdAt": "2025-10-21T05:44:12Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "(BTW, if the proposed fix is correct, I guess this is broken on v10 already)\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3424782058, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21561#issuecomment-3424782058", "createdAt": "2025-10-21T05:44:58Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "Thank you but I don't understand how to apply these modifications to my production version while waiting for the next update because the modified files are test files not present in version 11.0.1\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3425371409, "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21561#issuecomment-3425371409", "createdAt": "2025-10-21T08:21:31Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "You only have to apply changes on src/RuleMailCollectorCollection.php\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3425765773, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21561#issuecomment-3425765773", "createdAt": "2025-10-21T10:07:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21561, "url": "https://github.com/glpi-project/glpi/issues/21561", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-20T19:13:09Z", "updatedAt": "2026-02-02T00:39:35Z", "closedAt": "2025-10-24T13:02:35Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "/status.php shouldn't depend on the API being enabled", "detail": "Affected version:\n11.0.0\n\nIssue description:\nSince version 11.0.0, accessing /status.php responds with a 403 if the API is not enabled. This endpoint is often used as a healthcheck to decide which instances are healthy and ready to serve requests. So now, there's now way to do this without forcing the API to be enabled.\n\nReproduction steps:\n1. Ensure the API is disabled\n2. Try to call /status.php", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The status endpoints were not discussed (#20805), but I don't know how open this is supposed to be. This isn't technically any kind of internal feature and is strictly used through the REST API for external services/apps.\n\nIn reality, there are already good controls on how much of the API is usable besides the global enable toggle. There are no OAuth clients by default, and access to the main API can be blocked by simply not giving any OAuth clients the \"api\" or \"graphql\" scopes.\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3371425548, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21304#issuecomment-3371425548", "createdAt": "2025-10-06T12:36:29Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "Maybe a new /health.php would be needed, with no information at all, just a 200 code when evrything is OK (and which wouldn't rely on the API being enabled) ?\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3371440884, "author": "dani", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21304#issuecomment-3371440884", "createdAt": "2025-10-06T12:40:55Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Some relevant information about my opinion about using status codes to indicate service health can be found in #20766. Although if we are talking about a separate endpoint that only cares about the overall health, then maybe it is not an issue. I'm not so thrilled about the thought of adding redundant endpoints though.\n\nI am curious about the use cases where a global toggle is desired over the inherent restrictions of OAuth clients (or the lack of clients by default).\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3374508408, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21304#issuecomment-3374508408", "createdAt": "2025-10-06T22:40:30Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "The default for the API being disabled, it means in the default config, there's no simple healthcheck to use. I've worked around it by running php /app/bin/console -n config:set enable_hlapi 1 when my container starts\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3375811441, "author": "dani", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21304#issuecomment-3375811441", "createdAt": "2025-10-07T08:41:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21304, "url": "https://github.com/glpi-project/glpi/issues/21304", "author": "dani", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" }, { "sourceLogin": "orthagh", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-06T12:31:16Z", "updatedAt": "2026-01-31T00:35:43Z", "closedAt": "2025-10-22T08:29:12Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Error when running mailgate cron after adding Google account with oauthimap plugin", "detail": "Affected version:\n11.0.1\n\nIssue description:\nAfter installing and enabling the oauthimap plugin, I added a Google account for mail collection. When the scheduled mailgate task runs, it fails with the following error\n\nReproduction steps:\n1. Install and enable the oauthimap plugin.\n2. Add a Google account through the plugin configuration.\n3. Wait for cron to execute it.\n\nEnvironment details:\nGLPI Docker image glpi/glpi:11.0.1\n\nAdditional context:\nFrom the Oauth authorization → Diagnose section in the plugin configuration, the connection test is successful and shows no errors.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi Hayden Bennett\n\nhave you correctly set this option\n\n[Image omitted]\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400921302, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21465#issuecomment-3400921302", "createdAt": "2025-10-14T09:26:56Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "Hi Hayden Bennett\n\nhave you correctly set this option\n\n[Image omitted]\n\nI don’t have any of those options selected. I’m using the authentication method created by the oauthimap plugin instead.\n\n[Image omitted]\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400968549, "author": "albertogalisteo", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21465#issuecomment-3400968549", "createdAt": "2025-10-14T09:37:31Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "From a CLI context (automated task), the process is successfully triggered, and the plugin correctly returns the type imap-oauth-PROVIDER_ID.\n\nThis value is then properly processed afterward.\n\nI’m unable to reproduce or explain your issue — are there any additional errors in the GLPI logs?\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401426082, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21465#issuecomment-3401426082", "createdAt": "2025-10-14T11:56:48Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "From a CLI context (automated task), the process is successfully triggered, and the plugin correctly returns the type imap-oauth-PROVIDER_ID.\n\nThis value is then properly processed afterward.\n\nI’m unable to reproduce or explain your issue — are there any additional errors in the GLPI logs?\n\nI can see the following warning before the error\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401511476, "author": "albertogalisteo", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21465#issuecomment-3401511476", "createdAt": "2025-10-14T12:20:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21465, "url": "https://github.com/glpi-project/glpi/issues/21465", "author": "albertogalisteo", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [ { "sourceLogin": "Rom1-B", "anonymizedEmail": "jordan.blair@peppermint.local" }, { "sourceLogin": "stonebuzz", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-14T09:15:28Z", "updatedAt": "2026-01-29T00:37:16Z", "closedAt": "2025-10-20T08:40:31Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI 11 - Various issues migrating forms from Form Builder to the native version", "detail": "Affected version:\n11.0.0\n\nIssue description:\nThe form is being migrated in parts, and display options with conditionals are not being migrated.\nMigrated forms are also not saving the request when opening a new ticket, getting stuck on the same screen.\n\n#Suggestion: Add the option to link the groups object to actors, or add the option to restrict groups in the actors type field, previously available in the form builder.\n\n#News: I noticed that the Behaviors plugin is causing a 500 error when responding to native GLPI forms.", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please write in English (automatic translations are OK).\n\nHaving issues reported all in English helps ensure that searching for existing/already reported issues is easier.\nAlso, the community and development team is international so having a common language helps us too.\n\nEscreva em inglês (traduções automáticas são aceitáveis).\n\nRelatar problemas em inglês ajuda a facilitar a pesquisa de problemas existentes/já relatados.\nAlém disso, a comunidade e a equipa de desenvolvimento são internacionais, portanto, ter um idioma comum também nos ajuda.\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3383297259, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21367#issuecomment-3383297259", "createdAt": "2025-10-08T21:27:13Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "I updated the entire issue to English, to make it easier to understand and search.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385541280, "author": "afpes", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21367#issuecomment-3385541280", "createdAt": "2025-10-09T11:59:18Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The form is being migrated in parts, and display options with conditionals are not being migrated. Migrated forms are also not saving the request when opening a new ticket, getting stuck on the same screen.\n\nWe need more information, like logs, javascript errors in browser.\n\n#News: I noticed that the Behaviors plugin is causing a 500 error when responding to native GLPI forms.\n\nPlugins issues must be reported on plugin repository.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385626855, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21367#issuecomment-3385626855", "createdAt": "2025-10-09T12:24:14Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "[Image omitted]\n\n1 of the interface's problematic points: In the author type field, we are unable to perform searches.\n\n[Image omitted]\n\n2nd point: when trying to save the form, no error is displayed on the screen, or in the browser console, but it does not save.\n\nIn the logs I didn't find much that could help, the one that had the most recent data was php-errors.log\n\n[2025-10-09 13:21:35] glpi.WARNING: * User Warning: Invalid relations declared between \"glpi_plugin_order_othertypes\" and \"glpi_plugin_order_others\" table. Target field \"plugin_order_othertypes_id\" is not a foreign key field of \"PluginOrderOthertype\". at DbUtils.php line 2232\n Backtrace :\n ./src/DbUtils.php:2232\n ./src/autoload/dbutils-aliases.php:628 DbUtils->getDbRelations()\n ./src/CommonDBTM.php:915 getDbRelations()\n ./src/CommonDBTM.php:839 CommonDBTM->cleanRelationData()\n ./src/CommonDBTM.php:2152 CommonDBTM->deleteFromDB()\n ./src/RuleMatchedLog.php:156 CommonDBTM->delete()\n ./src/Glpi/Inventory/MainAsset/MainAsset.php:963 RuleMatchedLog->cleanOlddata()\n ./src/RuleImportAsset.php:978 Glpi\\Inventory\\MainAsset\\MainAsset->rulepassed()\n ./src/Rule.php:1456 RuleImportAsset->executeActions()\n ./src/RuleCollection.php:1505 Rule->process()\n ./src/Glpi/Inventory/MainAsset/MainAsset.php:609 RuleCollection->processAllRules()\n ./src/Glpi/Inventory/Inventory.php:843 Glpi\\Inventory\\MainAsset\\MainAsset->handle()\n ./src/Glpi/Inventory/Inventory.php:448 Glpi\\Inventory\\Inventory->handleItem()\n ./src/Glpi/Inventory/Request.php:389 Glpi\\Inventory\\Inventory->doInventory()\n ./src/Glpi/Inventory/Request.php:91 Glpi\\Inventory\\Request->inventory()\n ...lpi/Agent/Communication/AbstractRequest.php:434 Glpi\\Inventory\\Request->handleAction()\n ...lpi/Agent/Communication/AbstractRequest.php:341 Glpi\\Agent\\Communication\\AbstractRequest->handleJSONRequest()\n ./src/Glpi/Controller/InventoryController.php:96 Glpi\\Agent\\Communication\\AbstractRequest->handleRequest()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\InventoryController->index()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ...tener/CatchInventoryAgentRequestListener.php:77 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ...ymfony/event-dispatcher/EventDispatcher.php:260 Glpi\\Kernel\\Listener\\RequestListener\\CatchInventoryAgentRequestListener->onKernelRequest()\n ...ymfony/event-dispatcher/EventDispatcher.php:220 Symfony\\Component\\EventDispatcher\\EventDispatcher::S\n\n[Content truncated.]\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3386643396, "author": "afpes", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21367#issuecomment-3386643396", "createdAt": "2025-10-09T16:38:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21367, "url": "https://github.com/glpi-project/glpi/issues/21367", "author": "afpes", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-08T19:17:57Z", "updatedAt": "2026-01-23T00:33:07Z", "closedAt": "2025-10-14T13:06:34Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI 11 - Error upgrade glpi_profilerights", "detail": "Affected version:\n10.0.20\n\nIssue description:\nHello,\n\nI'm trying to upgrade 10.0.20 to 11.0.1 and i'm facing theses errors :\n\n[2025-10-09 16:04:55] glpi.WARNING: * Warning: Array to string conversion at Migration.php line 1227\n Backtrace :\n ./src/Migration.php:1227\n ...te_10.0.x_to_11.0.0/changesatisfactions.php:129 Migration->addRight()\n ...stall/migrations/update_10.0.x_to_11.0.0.php:64 require()\n ./src/Update.php:256 update100xto1100()\n ./src/Glpi/Controller/InstallController.php:123 Update->doUpdates()\n ...ts/AsyncOperationProgressControllerTrait.php:83 Glpi\\Controller\\InstallController->Glpi\\Controller\\{closure}()\n ./vendor/symfony/http-kernel/HttpKernel.php:101 Glpi\\Controller\\InstallController->Glpi\\Controller\\Traits\\{closure}()\n ...ymfony/http-foundation/StreamedResponse.php:106 Symfony\\Component\\HttpKernel\\HttpKernel::Symfony\\Component\\HttpKernel\\{closure}()\n ./vendor/symfony/http-foundation/Response.php:423 Symfony\\Component\\HttpFoundation\\StreamedResponse->sendContent()\n ./src/Glpi/Kernel/Kernel.php:295 Symfony\\Component\\HttpFoundation\\Response->send()\n ./public/index.php:72 Glpi\\Kernel\\Kernel->sendResponse()\n\n[2025-10-09 16:04:55] glpi.ERROR: * MySQL query error: Unknown column 'Array' in 'WHERE' (1054) in SQL query \"SELECT name, rights FROM glpi_profilerights WHERE ((name = 'change' AND rights & Array = Array)) AND profiles_id = '8'\".\n Backtrace :\n ./src/DBmysql.php:371\n ./src/DBmysqlIterator.php:123 DBmysql->doQuery()\n ./src/DBmysql.php:1040 DBmysqlIterator->execute()\n ./src/Migration.php:1235 DBmysql->request()\n ...te_10.0.x_to_11.0.0/changesatisfactions.php:129 Migration->addRight()\n ...stall/migrations/update_10.0.x_to_11.0.0.php:64 require()\n ./src/Update.php:256 update100xto1100()\n ./src/Glpi/Controller/InstallController.php:123 Update->doUpdates()\n ...ts/AsyncOperationProgressControllerTrait.php:83 Glpi\\Controller\\InstallController->Glpi\\Controller\\{closure}()\n ./vendor/symfony/http-kernel/HttpKernel.php:101 Glpi\\Controller\\InstallController->Glpi\\Controller\\Traits\\{closure}()\n ...ymfony/http-foundation/StreamedResponse.php:106 Symfony\\Component\\HttpKernel\\HttpKernel::Symfony\\Component\\HttpKernel\\{closure}()\n ./vendor/symfony/http-foundation/Response.php:423 Symfony\\Component\\HttpFoundation\\StreamedResponse->sendContent()\n ./src/Glpi/Kernel/Kernel.php:295 Symfony\\Component\\HttpFoundation\\Response->send()\n ./public/index.php:72 Glpi\\Kernel\\Kernel->sendResponse()\n\nphp -v\nPHP 8.3.26 (cli) (built: Oct 1 2025 20:30:36) (NTS)\n\nDo you know what is the probleme ?", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "we have a need to run phpstan on migration files. This probably deserve an issue Skyler Adler\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3388901917, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21390#issuecomment-3388901917", "createdAt": "2025-10-10T08:40:13Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "GLPI updates are already supposed to be tested. One of the tests even does an upgrade from GLPI 0.80 to the latest version. I am not sure why it didn't catch this.\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3389207951, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21390#issuecomment-3389207951", "createdAt": "2025-10-10T10:14:10Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "Thanks fixed with\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3389595858, "author": "kevin-m87", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21390#issuecomment-3389595858", "createdAt": "2025-10-10T11:40:28Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "You may want to run the DB schema check command as well just to make sure there aren't partial DB schema changes.\nRun as web server user (www-data?):\nbin/console database:check_schema_integrity\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3389626612, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21390#issuecomment-3389626612", "createdAt": "2025-10-10T11:44:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21390, "url": "https://github.com/glpi-project/glpi/issues/21390", "author": "kevin-m87", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-09T14:20:59Z", "updatedAt": "2026-01-22T00:34:31Z", "closedAt": "2025-10-13T10:45:57Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "POST /Assistance/Ticket/{id}/Timeline/Followup returns an error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI'm trying to automate ticket follow-up, but when I send a POST request to the /Assistance/Ticket/{id}/Timeline/Followup or /Assistance/Ticket/{id}/Timeline/Solution endpoints in Swagger or CURL, I always get a 404 error (although the follow-up or solution is added).\n\nMy request is as follows:\n\nThe error :\n\nReproduction steps:\n1. Go to Swagger at\n2. Setup OAuth2 authorizations with the \"Authorize\" button\n3. Go to [POST] /Assistance/Ticket/{id}/Timeline/Followup endpoint\n4. Put existing ticket ID in the ID field\n5. Add simple request body like this one :", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The error is not from the API. The v2 API does not use Symfony for routing to the endpoints, but for some reason it seems to be stealing the request for you. It also doesn't make sense that you are seeing a GET request for the new resource unless you are making that request yourself.\n\nPlease try with plugins disabled.\n\nOriginal response date: 2026-06-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4649892490, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24506#issuecomment-4649892490", "createdAt": "2026-06-08T14:15:48Z" } }, { "userEmail": "harper.bennett@peppermint.local", "text": "Hello Taylor Adler\n\nMy test is already with all plugins disabled.\nYes, that seems very strange to me. In addition, I can't reproduce this issue on a fresh installation of GLPI.\n\nEDIT: Fresh installation with Apache2 but I can reproduce with Nginx + PHP-FPM\n\nOriginal response date: 2026-06-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4650924081, "author": "clemmsy", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24506#issuecomment-4650924081", "createdAt": "2026-06-08T16:06:14Z" } }, { "userEmail": "harper.bennett@peppermint.local", "text": "Some additional information:\nI've only ever tried with Swagger and Powershell (Invoke-RestMethod), not curl. These tools follow redirections, and in this case the API sent me an HTTP 302 response (see the attached Wireshark screenshot).\n\n[Image omitted]\n\nOriginal response date: 2026-06-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4661647484, "author": "clemmsy", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24506#issuecomment-4661647484", "createdAt": "2026-06-09T16:05:40Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The HLAPI (v2 High-Level API) does not send 302 responses when creating resources either. In fact, the only time the HLAPI would send a 302 is for authenticating with the Authorization Code OAuth grant to direct the client to the given redirect URL. It sounds like your web server may be seeing the Location response header and forcing the status code change. Maybe there are some nginx settings that needs disabled for the GLPi API routes \"/api.php\" (HLAPI) and \"/apirest.php\" (Legacy).\n\nOriginal response date: 2026-06-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4686219348, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24506#issuecomment-4686219348", "createdAt": "2026-06-12T00:18:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24506, "url": "https://github.com/glpi-project/glpi/issues/24506", "author": "clemmsy", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-08T14:07:01Z", "updatedAt": "2026-07-06T13:26:47Z", "closedAt": "2026-07-06T13:26:47Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Security tab empty", "detail": "Issue description:\nFrom Setup > General > Security tab, the page is completely empty\n\n[Image omitted]", "priority": "medium", "type": "bug", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Check logs and/or switch to debug mode; you probably will have more information. Check also your browser console output.\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4707987385, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24563#issuecomment-4707987385", "createdAt": "2026-06-15T12:36:37Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The security tab isn't meant to exist anymore as it is in Setup > Security now. Probably a bad rebase kept it around.\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4708049817, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24563#issuecomment-4708049817", "createdAt": "2026-06-15T12:44:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Check logs and/or switch to debug mode; you probably will have more information. Check also your browser console output.\n\nNothing in debug mode. Nothing in the logs either. As for the console, I don't know what you want me to do.\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4708064349, "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24563#issuecomment-4708064349", "createdAt": "2026-06-15T12:46:42Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I had javascript issues in mind; but if the tab should no longer exists, that's another problem :D\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4708075676, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24563#issuecomment-4708075676", "createdAt": "2026-06-15T12:48:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24563, "url": "https://github.com/glpi-project/glpi/issues/24563", "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "beta / rc", "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-15T12:35:28Z", "updatedAt": "2026-06-17T18:47:51Z", "closedAt": "2026-06-17T18:47:51Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Incorrect sorting behavior between Last update and Title columns", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.23\n\nIssue description:\nModule: Ticket list view / Sorting feature\nDescription:\nIn the ticket list view, tickets are correctly sorted by default using the Last update column (newest to oldest).\nWhen the user clicks the Last update column header to reverse the sort order (oldest to newest), the sorting works correctly.\nHowever, when clicking again on the Last update column header to return to the original sorting order, the system unexpectedly switches to sorting by the Title column instead of sorting again by Last update.\nSteps to reproduce:\n\nOpen the ticket list.\nObserve that the default sorting uses the Last update column (Newest → Oldest).\nClick the Last update column to sort (Oldest → Newest).\nClick the Last update column again.\nThe list is now sorted by Title instead of Last update.\n\nExpected behavior:\nClicking again on the Last update column header should sort the tickets again by Last update in descending order (Newest → Oldest).\nActual behavior:\nThe sorting unexpectedly switches to alphabetical sorting using the Title column.\nImpact:\nUsers cannot reliably sort tickets by the Last update field, which introduces confusion and may affect ticket management efficiency.", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate in GLPI the latest GLPI 10 or 11 versions.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3897510383, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23094#issuecomment-3897510383", "createdAt": "2026-02-13T14:26:17Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Hello, this is probably due to the nested filters on the tickets because when I reset the view, it returns to normal as expected. What information do you need to verify this?\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3897546224, "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23094#issuecomment-3897546224", "createdAt": "2026-02-13T14:34:07Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "When using multiple sorted columns, the behavior when holding down the Ctrl key is to toggle between Ascending -> Descending -> None.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3897850988, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23094#issuecomment-3897850988", "createdAt": "2026-02-13T15:33:59Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Not on the sorted columns, the filters :\n\n[Image omitted]\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3898572365, "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23094#issuecomment-3898572365", "createdAt": "2026-02-13T18:04:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23094, "url": "https://github.com/glpi-project/glpi/issues/23094", "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-12T10:21:13Z", "updatedAt": "2026-04-15T05:58:48Z", "closedAt": "2026-04-15T05:58:43Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Pasted images in ticket follow-ups are embedded as Base64 instead of saved as attachments", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.23 and 11.0.5\n\nIssue description:\nIn GLPI 10.0.23, we are still facing an issue similar to #20265 / #22596, even after the fix mentioned by Skyler Adler and Jordan Blair\n\n[Image omitted]\n\nWhen adding a new ticket follow-up and pasting or inserting an image, the image is not saved as an attachment. Instead, it is embedded directly in the follow-up content as Base64.\n\nAs a result:\n- Image is not stored as a document/attachment\n- Follow-up content becomes very large\n- Potential impact on performance, readability, and storage\n- Behavior is inconsistent with expected image handling\n\nReproduction steps:\n1. Open an existing ticket\n2. Create a new follow-up\n3. Paste an image\n4. Add the follow-up", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.blair@peppermint.local", "text": "Hello, any update on this Skyler Adler, Jordan Blair?\n\nWe've multiple GLPI instances in version 10.0.23 with this same bug.\n\nOriginal response date: 2026-02-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3927792672, "author": "Berlinst", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23110#issuecomment-3927792672", "createdAt": "2026-02-19T14:54:10Z" } }, { "userEmail": "kendall.blair@peppermint.local", "text": "Hello\n\nWe're experiencing something like that. And when the image is big, it cant even load the page.\n\n[Image omitted]\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3991158774, "author": "marcoabgm", "anonymizedAuthorEmail": "kendall.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23110#issuecomment-3991158774", "createdAt": "2026-03-03T13:40:23Z" } }, { "userEmail": "finley.blair@peppermint.local", "text": "I also confirm that in my 10.0.23 environment, the same problem occurred with images when pasting screenshots taken directly from Windows 11 into the body of the tracking request. A few days ago, I also saw a case of a tracking response via email that ended up with basecode 64. It seems to be related to a failure to load the image into GLPI, but GLPI still has the raw code to replace the image we would see.\n\n[Image omitted]\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4011440435, "author": "erique-souza", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23110#issuecomment-4011440435", "createdAt": "2026-03-06T12:22:08Z" } }, { "userEmail": "logan.blair@peppermint.local", "text": "This issue also occurs in 11.0.5 (upgraded from 10) when pasted from certain sources but not others.\nI need to verify with 11.0.6\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4012487118, "author": "tdozbun-reno", "anonymizedAuthorEmail": "logan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23110#issuecomment-4012487118", "createdAt": "2026-03-06T15:42:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23110, "url": "https://github.com/glpi-project/glpi/issues/23110", "author": "Berlinst", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-13T11:36:30Z", "updatedAt": "2026-04-13T13:00:32Z", "closedAt": "2026-04-13T13:00:32Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Asset definitions - unable to set Users in Dropdown field", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHello.\nWhen I try to create custom field for _Asset definitions_ I've noticed that the behavior differs from what is described in the documentation.\nAccording to the documentation, it should be possible to create a dropdown field that uses the _Users_ list.\n\n[Image omitted]\n\nHowever, when I try to create this field, that option is missing.\n[Image omitted]\n\nRegards.\n\nReproduction steps:\n1. Go to _Setup_ -> _Asset definitions_\n2. Create new one or use existing asset\n3. Fields -> Custom fields -> New field\n4. Set label\n5. Type: _Dropdown_\n6. Check _Multiple values_\n7. In item type there is no _Users_", "priority": "low", "type": "feature", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I don't know where the list in the documentation came from, but this has always only shown assets and standard \"dropdown\" types (Setup > Dropdowns).\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3473581166, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21732#issuecomment-3473581166", "createdAt": "2025-10-31T15:24:20Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Is it currently possible to define a custom field in Asset definitions that will contain multiple users?\nIf not, will this be possible in the future, as stated in the documentation?\n\nI am referring to a field that I can create in the Computers category using the fields plugin. Currently, this plugin does not support adding fields to Asset definitions.\n[Image omitted]\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3473945854, "author": "michal1298", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21732#issuecomment-3473945854", "createdAt": "2025-10-31T16:41:02Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "The same issue exists in GLPI 11.0.2.\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3496916661, "author": "michal1298", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21732#issuecomment-3496916661", "createdAt": "2025-11-06T12:05:45Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "The same issue exists in GLPI 11.0.4\n\nOriginal response date: 2025-12-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3660031597, "author": "cofig", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21732#issuecomment-3660031597", "createdAt": "2025-12-16T11:19:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21732, "url": "https://github.com/glpi-project/glpi/issues/21732", "author": "michal1298", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [ "enhancement", "need user doc" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-31T15:08:50Z", "updatedAt": "2026-03-26T20:16:35Z", "closedAt": "2026-03-26T20:16:35Z" } }, { "title": "Follow up don't work", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWhen a ticket is created, if the technician in charge adds a follow-up, the requester is notified by email and sees the follow-up, but the technician does not. If the requester adds a follow-up, the technician is notified by email but does not see the message in the discussion thread. Clearing the cache does not change anything.", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello, i cannot reproduce, it's not very clear what this issue is about. Could you please try to reproduce with all your plugins suspended, and in the case you still have a problem, come back to us with more details ?\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3484647316, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21765#issuecomment-3484647316", "createdAt": "2025-11-04T08:48:38Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "When a user creates a ticket, the ticket appears correctly in both the user's and the technician's consoles. Each party is notified by email when a ticket is created.\n\nIf the user adds a follow-up to their ticket, the technician is notified by email but does not see the user's addition in the discussion thread.\n\nIf the technician adds a follow-up to the ticket, the user is notified by email and sees the technician's follow-up. Furthermore, the technician does not see their own addition in the discussion thread. (See screenshots.)\n\nI have no plugins activated.\n\nAttached are two screenshots of the same ticket. The first is from the user's perspective and the second from the technician's perspective.\n\n[Image omitted]\n[Image omitted]\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3484769452, "author": "candaes", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21765#issuecomment-3484769452", "createdAt": "2025-11-04T09:10:56Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Please post a screenshot(s) of the Assistance tab for your \"Support tickets\" profile under Administration > Profiles. Specifically the Tickets and Followups/Tasks sections.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3500068090, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21765#issuecomment-3500068090", "createdAt": "2025-11-07T01:25:11Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "Original response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3520556476, "author": "candaes", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21765#issuecomment-3520556476", "createdAt": "2025-11-12T08:07:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21765, "url": "https://github.com/glpi-project/glpi/issues/21765", "author": "candaes", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-03T10:44:13Z", "updatedAt": "2026-02-22T00:40:24Z", "closedAt": "2025-11-13T01:12:59Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "System tab HTTP500 error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAfter upgrading from 11.0.4 -> 11.0.6 I get an HTTP500 error when trying to show the content of the System tab under Setup. All other tabs and views shows without a problem.\n\n[Image omitted]\n\nReproduction steps:\n1. Upgrade from 11.0.4 to 11.0.6\n2. Go to Setup -> General -> System\n\nEnvironment details:\nphp-errors.log\n\nmigration_to_11.0.6.log\nmigration_to_11.0.5.log", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "I upgraded from 11.0.4 to 11.0.6 following thses steps:\n\n1. Stop the site \"glip\" (note the spelling) in IIS.\n2. Back up all contents of \"C:\\glpi\" to \"C:\\Install\\GLPI Upgrades\\Upgrade Backups[version number of the GLPI you are copying]\".\n3. Delete everything in the \"C:\\glpi\" folder.\n4. Copy the contents of the extracted upgrade (glpi-11.0.6.tgz) file to \"C:\\glpi\".\n5. Copy the contents of \"\\config\" from the backup folder in step 2 to \"C:\\glpi\\config\" (the files \".htaccess\", \"config_db.php\", and \"glpicrypt.key\").\n6. Copy \"web.config\" from \"\\public\" in the backup folder from step 2 to \"C:\\glpi\\public\".\n7. Copy all plugins from \"\\marketplace\" in the backup folder from step 2 to \"C:\\glpi\\marketplace\".\n8. Copy all files in \"\\files\" from the backup folder from step 2 to \"C:\\glpi\\files\".\n9. Copy \"cacert.pem\" from the backup folder from step 2 to \"C:\\glpi\".\n10. Start the site \"glip\"\n11. Go through the upgrade wizard\n12. Log in\n13. Enable all plugins\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4005785059, "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23379#issuecomment-4005785059", "createdAt": "2026-03-05T15:13:28Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The upgrade process doesn't seem to be the issue, but the source code integrity information it is timing out on doesn't seem to have changed since 11.0.1 either. When I added this information, I noted in the PR that it took less than a second for it to check for changed files. Perhaps there is something else that is taking up most of the allowed execution time?\n\nAre you using LDAP, SQL replicas, or a mail server by chance?\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4005994841, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23379#issuecomment-4005994841", "createdAt": "2026-03-05T15:44:45Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Having been away for a moment I now can indeed access the page. Can it be a background process that needed to finish? Also, I do have a mail collector running as well as an LDAP connected user collection.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4006069719, "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23379#issuecomment-4006069719", "createdAt": "2026-03-05T15:55:46Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "I was away overnight and now the issue is manifesting itself again, i.e. when initially trying to view the \"System\" tab I get the 500 error. After a while (5-10 mins) a refresh indeed shows the system page correctly.\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4011297448, "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23379#issuecomment-4011297448", "createdAt": "2026-03-06T11:51:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23379, "url": "https://github.com/glpi-project/glpi/issues/23379", "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-03-05T15:05:40Z", "updatedAt": "2026-07-05T00:53:36Z", "closedAt": "2026-03-26T22:10:37Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Call to a member function getFromDB() on false\" at CommonItilObject_Item.php line 160", "detail": "Affected version:\nGLPI 11.0.2\n\nIssue description:\nwhen I enter a change for a generic object I get an error message\n\nReproduction steps:\nI have install plugin Field and behavior", "priority": "medium", "type": "support", "createdByEmail": "jordan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the bug and it is not limited specifically to custom assets.\n\nThere seems to be two different methods trying to handle adding the link.\nCommonITILObject::handleItemsIdInput is called first and seems to add the link between the asset and change properly using the items_id array in the input.\nChange::post_addItem also tries handling, but using _from_items_id and _from_itemtype input properties which seem empty and it fails.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3500010940, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21829#issuecomment-3500010940", "createdAt": "2025-11-07T00:57:02Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Seems like a post Twig migration issue\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501026834, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21829#issuecomment-3501026834", "createdAt": "2025-11-07T07:01:21Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot reproduce the bug.\nWhich change are you doing ?\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3552856279, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21829#issuecomment-3552856279", "createdAt": "2025-11-19T13:59:59Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Skyler Adler a twig issue is fixed on\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3552878710, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21829#issuecomment-3552878710", "createdAt": "2025-11-19T14:05:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21829, "url": "https://github.com/glpi-project/glpi/issues/21829", "author": "aumongplf", "anonymizedAuthorEmail": "jordan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-06T10:33:38Z", "updatedAt": "2026-06-26T01:05:46Z", "closedAt": "2026-03-17T12:32:20Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI crashes when opening the impact analysis", "detail": "Affected version:\n10.0.20\n\nIssue description:\nI have documented our IT infrastructure in GLPI.\nAfter I made some changes, removed assets, added new ones and linked them, GLPI started to freeze for a few assets when I open the Impact analysis tab.\n\nIn debug mode, I get these messages for those assets:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nPlease provide GLPI logs, so we could analize the full stack trace of the errors.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3597115500, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22157#issuecomment-3597115500", "createdAt": "2025-12-01T15:15:18Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "The \"glpi/files/_log\" folder is empty on my system. How can I enable logging? Under System > General setup, the log level is set to 5.\n\nOriginal response date: 2025-12-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3600635605, "author": "FreeMacs", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22157#issuecomment-3600635605", "createdAt": "2025-12-02T07:37:01Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The \"glpi/files/_log\" folder is empty on my system. How can I enable logging? Under System > General setup, the log level is set to 5.\n\nIt means that GLPI is configured to store logs somewhere else (it corresponds to the GLPI_LOGS_DIR value in the Setup > General > System > Information about system installation and configuration section).\nWithout these logs cannot investigate on your issue.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606495553, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22157#issuecomment-3606495553", "createdAt": "2025-12-03T11:52:15Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "I would have found that in the PHP error log:\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607120596, "author": "FreeMacs", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22157#issuecomment-3607120596", "createdAt": "2025-12-03T14:25:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22157, "url": "https://github.com/glpi-project/glpi/issues/22157", "author": "FreeMacs", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-01T15:04:08Z", "updatedAt": "2026-06-15T01:13:39Z", "closedAt": "2026-03-06T19:43:34Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Image is processed after being deleted from followup (WYSIWYG)", "detail": "Affected version:\nv11\n\nIssue description:\nIf an image (screenshot) is added to the WYSIWYG followup editor and then removed (leaving the update without any images) the file is still being uploaded and linked as an attachment tot the ticket flow.\n\nReproduction steps:\nCreate a followup\nPaste an image in the WYSIWYG editor after some text. Delete the image from the editor and press save.\n\nEnvironment details:\nn.a.\n\nAdditional context:\nno", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It seems a little more complex than just removing the image from the file input when deleted in the textbox. If the user uses the undo action to restore the image after it is deleted, the file upload won't be restored too and the image will be left as a base64 image data blob instead of being replaced. When you try to view the image if it is too large, GLPI will probably fail with a PREG_BACKTRACK_LIMIT_ERROR and block the entire timeline UI.\n\nIn fairness, the undo/redo issue already exists if you remove the image by deleting the file upload from the list instead of removing the image directly.\n\nOriginal response date: 2025-12-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3700027133, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22276#issuecomment-3700027133", "createdAt": "2025-12-30T17:30:24Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Hello Taylor Bennett\n\nfile is still being uploaded and linked as an attachment tot the ticket flow\n\nHow is the file attached ? Maybe similar to ?\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3714702893, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22276#issuecomment-3714702893", "createdAt": "2026-01-06T13:28:59Z" } }, { "userEmail": "riley.blair@peppermint.local", "text": "Not sure if its similar. The image is pasted as a blob into the wysiwyg. This triggers the document being uploaded by GLPI. It seems the document does not remain a inline blob, but a separate document as you would expect to prevent database clutter. If the document is removed from the wysiwyg, the image is removed from the wysiwyg but not from the upload field. The author can remove the document manually if he realizes the previously removed document remains and is able to recognise it as the deleted document. If the post has multiple documents the deleted document is likely to remain and as a result uploaded to the post as a separate document. You can repeat (paste, delete) this proces in the wysiwyg and the result will be multiple duplicates being 'linked' to the post but the deleted ones remain. This behaviour might lead to a dataleak if the deleted document isnt deleted manually and included in the notifications.\n\n[Image omitted]\n\np.s. im donuts...\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3715365466, "author": "ChrisGralike", "anonymizedAuthorEmail": "riley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22276#issuecomment-3715365466", "createdAt": "2026-01-06T16:26:54Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Taylor Bennett please test proposed fix #22643\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3789642221, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22276#issuecomment-3789642221", "createdAt": "2026-01-23T10:49:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22276, "url": "https://github.com/glpi-project/glpi/issues/22276", "author": "DonutsNL", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-06T14:01:52Z", "updatedAt": "2026-05-07T00:55:21Z", "closedAt": "2026-01-26T10:09:52Z" }, "assignedTo": "jordan.blair@peppermint.local" }, { "title": "Equipment import rules are not working correctly", "detail": "Affected version:\n11.0.3\n\nIssue description:\nGood afternoon.\nThe rules for assigning objects are not working correctly:\n1. I have a rule: IP addresses that start with 192.168.100. should be assigned to the Fortex > Valishevo organization, but are assigned only to the Fortex parent organization\n\n[Image omitted]\n\n[Image omitted]\n\n2. Network printers follow the location rule every other time. According to the rule I mentioned above, the location of the object should be reassigned in accordance with the rule, i.e. the rule should be the highest in priority, but for some printers the location is entered from the SNMP data, which is not true.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide rules and inventory file that can be used to reproduce.\n\nAlso - sorry - but most of us do not read anything else than latin languages; provided screenshots are almost unreadable.\n\nOriginal response date: 2026-01-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3710438464, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22503#issuecomment-3710438464", "createdAt": "2026-01-05T13:31:21Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "Пожалуйста, предоставьте правила и файл инвентаризации, которые можно использовать для воспроизведения проблемы.\n\nКроме того, извините, но большинство из нас не читает ничего, кроме латыни; представленные скриншоты практически нечитаемы.\n\nHi, here are the inventory rules.:\nrules (3).xml\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737276740, "author": "tattami", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22503#issuecomment-3737276740", "createdAt": "2026-01-12T07:54:00Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "An inventory file is also required.\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737306111, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22503#issuecomment-3737306111", "createdAt": "2026-01-12T08:02:37Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "An inventory file is also required.\n\nDo you mean the inventory file from the agent? I also found that the rules don't work because most computers don't have network ports detected, although everything worked in version 10.0.11. p.s. We installed 11.0.3 from 0 and installed glpi-agent 1.15\nAt the same time, all data is entered correctly on Agent 1.4.\n\nOriginal response date: 2026-01-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3758684295, "author": "tattami", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22503#issuecomment-3758684295", "createdAt": "2026-01-16T08:11:16Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22503, "url": "https://github.com/glpi-project/glpi/issues/22503", "author": "tattami", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-30T06:55:25Z", "updatedAt": "2026-04-30T00:55:29Z", "closedAt": "2026-01-19T06:47:15Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "OAuth clients UI error when oauth.pem/pub files are missing", "detail": "Affected version:\n11bf\n\nIssue description:\nWhen the files oauth.pem / oauth.pub no longer exist in the config directory, accessing the page “Setup > OAuth clients” (in dev mode) triggers an error.\n\nshell\n\nAffected page:", "priority": "medium", "type": "bug", "createdByEmail": "cameron.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Can I work on this ?\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3747204568, "author": "felipee-monteiro", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22591#issuecomment-3747204568", "createdAt": "2026-01-14T01:00:56Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Can I work on this ?\n\nYes, feel free :)\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3753546989, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22591#issuecomment-3753546989", "createdAt": "2026-01-15T08:33:25Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Thanks !\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3754865095, "author": "felipee-monteiro", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22591#issuecomment-3754865095", "createdAt": "2026-01-15T13:34:05Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "I can't reproduce Skyler Adler\n\nOriginal response date: 2026-01-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3757740005, "author": "felipee-monteiro", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22591#issuecomment-3757740005", "createdAt": "2026-01-16T01:59:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22591, "url": "https://github.com/glpi-project/glpi/issues/22591", "author": "flegastelois", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [ { "sourceLogin": "felipee-monteiro", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "bug", "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-08T11:02:29Z", "updatedAt": "2026-04-27T00:52:24Z", "closedAt": "2026-01-16T08:53:53Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Relative date only giving negative options for Assets", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen searching on a date field in Assistance we have both + and - relative date options, but in Assets it only shows - options\n\nReproduction steps:\nGo to Assets, Computers\nClick Search\nChoose a date field, and before or after\nYou get relative dates like - 1 day, or - 6 months, but no positive options\n\nEnvironment details:\nGLPI: 11.0.4 ( => /var/www/glpi)\nInstallation mode: TARBALL\nCurrent language: en_US\nSource Integrity: 1 files changed\n A: front/cookiefile", "priority": "medium", "type": "support", "createdByEmail": "cameron.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please include more specific instructions to recreate the issue. Which specific field are you testing?\nDates like \"Creation date\" and \"Last update\" only make sense when referring to a past date.\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3688111069, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22477#issuecomment-3688111069", "createdAt": "2025-12-23T22:17:21Z" } }, { "userEmail": "cameron.blair@peppermint.local", "text": "Specifically I am looking to use Financial & Administrative Information - Date of Inventory/Asset Release\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3688117942, "author": "rrintoulsrsd", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22477#issuecomment-3688117942", "createdAt": "2025-12-23T22:21:35Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "\"Date of Inventory/Asset Release\" does not seem like a field that exists in GLPI natively. The closest is the \"Date of last physical inventory\" which also only makes sense as a past date. Do you have plugins installed?\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3688213116, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22477#issuecomment-3688213116", "createdAt": "2025-12-23T23:36:59Z" } }, { "userEmail": "cameron.blair@peppermint.local", "text": "Sorry, I thought it was a built in field, not sure which plugin it is coming from\nAdvanced Forms\nAlerts\nAutoExportSearches\nBehaviours\nData injection\nGLPI Inventory\nOauth IMAP\nPrint to pdf\nSuppliers imports\n\nMaybe this should be moved to a feature request then?\n\nOriginal response date: 2025-12-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3689879920, "author": "rrintoulsrsd", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22477#issuecomment-3689879920", "createdAt": "2025-12-24T14:18:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22477, "url": "https://github.com/glpi-project/glpi/issues/22477", "author": "rrintoulsrsd", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "assignees": [], "labels": [ "translation" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-23T20:30:28Z", "updatedAt": "2026-04-04T00:40:44Z", "closedAt": "2025-12-24T15:30:10Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Check if minified files are still used", "detail": "Issue description:\nI think minified JS files are no longer being but they are still generated in the production archive.\n\nMaybe we should remove them then?", "priority": "high", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "As far a I know, they're still used if they're present; see Html::getMiniFile() and FrontEndAssetExtension::jsPath().\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607397485, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22208#issuecomment-3607397485", "createdAt": "2025-12-03T15:25:33Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "They should be used when using the js_path Twig function.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607397746, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22208#issuecomment-3607397746", "createdAt": "2025-12-03T15:25:37Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I haven't checked the code but I've compared two production instances:\n\nGLPI 10 prod:\n\n[Image omitted]\n\nGLPI 11 prod:\n\n[Image omitted]\n\nAnd if I modify the common.js file on the GLPI 11 prod to add a console.log statement, it is printed in the console (which suggest the min file is not used).\n\nSo maybe there is something more to investigate here? Unless it is the prod I am testing on which may not be setup correctly.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607430210, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22208#issuecomment-3607430210", "createdAt": "2025-12-03T15:32:42Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Is debug mode enabled?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607449141, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22208#issuecomment-3607449141", "createdAt": "2025-12-03T15:36:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22208, "url": "https://github.com/glpi-project/glpi/issues/22208", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-03T15:22:45Z", "updatedAt": "2026-03-28T00:40:14Z", "closedAt": "2025-12-17T15:48:03Z" } }, { "title": "access submitted forms generated with formcreators", "detail": "Affected version:\n11.0.0\n\nIssue description:\nmigrated forms from formcreators to native forms, but now i can't see the previous submitted forms, whre could locate the previous submitted forms?\n\nReproduction steps:\n1. updated to glpi 11\n2. migrate formcreators to native with php bin/console migration:formcreator_plugin_to_core\n3. i can see the migrated forms\n4. i can't locate the previous submitted forms with formcreator plugin\n\nAdditional context:\nWe need access to the previous submitted forms because we use it for evidence for audits ISO/IATF, we did registered all the maintenance for the computers.\n\nthere are the migrated forms:\n[Image omitted]\n\nThe following image shows the submenu for each form. Adding a section to view submitted forms would be helpful, as the current system configuration only generates form submissions to record scheduled maintenance on equipment within a specific period, without creating tickets:\n[Image omitted]\n\nThis is the migration status of my forms; we have migrated the forms, but it should be noted that we still cannot access the submitted forms that were created prior to the migration/update:\n\n[Image omitted]\n\ni hope can help us with this \"issue\", i think GLPI is great system with a huge potential, we had used it from at least 5-6 years ago.\n\nif you need more information let me know.\n\nthanks in advance.\n\nregards.", "priority": "medium", "type": "support", "createdByEmail": "cameron.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "rowan.blair@peppermint.local", "text": "In fact, you can't see the answers to a test form either. Is there any way to see the answers?\nI would also like to help with the solution. GLPI is the best solution for tickets and inventory on the market. If you would like to run any tests, we would be happy to do so. Thank you!\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3500003926, "author": "SeBytev3", "anonymizedAuthorEmail": "rowan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21840#issuecomment-3500003926", "createdAt": "2025-11-07T00:53:02Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Many issues have been fixed in versions 11.0.1 and 11.0.2 on forms migration. Please first try to update your v10 database with latest stable release.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501020066, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21840#issuecomment-3501020066", "createdAt": "2025-11-07T06:58:07Z" } }, { "userEmail": "rowan.blair@peppermint.local", "text": "At this time, we have version 11.0.2 installed.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501933441, "author": "SeBytev3", "anonymizedAuthorEmail": "rowan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21840#issuecomment-3501933441", "createdAt": "2025-11-07T11:12:17Z" } }, { "userEmail": "cameron.blair@peppermint.local", "text": "I updated from 11.0.0 to 11.0.2 but still can't found an option where can see the submitted forms previous the migration. If you need additional information, let me know.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3514195764, "author": "j-guevara-m", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21840#issuecomment-3514195764", "createdAt": "2025-11-10T22:38:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21840, "url": "https://github.com/glpi-project/glpi/issues/21840", "author": "j-guevara-m", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms", "question" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-06T16:56:06Z", "updatedAt": "2026-03-28T00:40:09Z", "closedAt": "2025-12-17T15:48:23Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "RTL languages display issues", "detail": "Issue description:\nThe icons move to the correct position, except for one case (Network Devices) which still remains misplaced\nBefore (icons misplaced):\n\n[Image omitted]\n\nAfter (with Debug mode enabled):\n\n[Image omitted]\n\nThere are also some RTL (Right-to-Left) layout issues:\n\nThe Assets menu in RTL does not appear completely\n\n[Image omitted]\n\nWhile in English (LTR), it appears correctly:\n\n[Image omitted]\n\nThe sidebar menu in RTL should appear on the right, not on the left\n\n[Image omitted]\n\nIn End User View (Self-service), layout also breaks in RTL mode\n\n[Image omitted]\n\nand this in english\n\n[Image omitted]\n\n_Originally posted by Drew Bennett in", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Drew Bennett please check #21628. Remember you have to enable debug mode to see changes.\n\nI found a few more issues I've also fixed.\n\nOriginal response date: 2025-10-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3442874926, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21620#issuecomment-3442874926", "createdAt": "2025-10-24T12:27:50Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "i check the 4 files and do the change it's great now thanks\n\nI also noticed a few other small RTL layout issues:\n1. Window titles appear under the logo in the “Add new item” windows when using RTL:\n\n[Image omitted]\n\nLTR it's OK\n\n[Image omitted]\n\n2. Sidebar menu direction issues:\n\nThe collapse arrow points in the wrong direction. In RTL, it currently points left (>) when collapsing the menu.\n\nand find menu also arrow points in the wrong direction — in RTL it should points to the left (<=), not the right.\n\n[Image omitted]\n\n3. Search field alignment:\n-The search bar has square edges instead of rounded ones.\n-It’s centered instead of being aligned to the left side in RTL.\n-Some form fields also have cut-off edges in RTL mode\n\n[Image omitted]\n\nIn English (LTR), the layout is correct:\n\n[Image omitted]\n\nand this some translation issue\nI translated that strings in the project on app.transifex.com but these particular words are still displayed in English in GLPI maybe in all other languages\n\n[Image omitted]\n[Image omitted]\n\nOriginal response date: 2025-10-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3447873034, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21620#issuecomment-3447873034", "createdAt": "2025-10-25T23:52:12Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Thank you for the feedback. I'll take an eye to fix remaining issues.\n\n3. Search field alignment: -The search bar has square edges instead of rounded ones. -It’s centered instead of being aligned to the left side in RTL. -Some form fields also have cut-off edges in RTL mode\n\nI saw those issues already, but I was not able to fix :(\nI'll probably left a separate ticket open.\n\nand this some translation issue I translated that strings in the project on app.transifex.com but these particular words are still displayed in English in GLPI maybe in all other languages\n\nYes, this is another problem, which already has been reported; see:\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3449618796, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21620#issuecomment-3449618796", "createdAt": "2025-10-27T05:47:16Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "With #22215 and #22318; all reported issues should have been fixed\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3636966726, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21620#issuecomment-3636966726", "createdAt": "2025-12-10T12:54:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21620, "url": "https://github.com/glpi-project/glpi/issues/21620", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-23T11:42:59Z", "updatedAt": "2026-03-23T00:42:53Z", "closedAt": "2025-12-10T12:54:49Z" } }, { "title": "On transfert list execution MySQL Error", "detail": "Affected version:\n11.0.4\n\nIssue description:\nDuring transfert from an entity to another for a computer i've this error :\n\nReproduction steps:\nTransfert computer from an entity to another with complete default option without touch anything.", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.bennett@peppermint.local", "text": "In php error i also have this one (don't know if it's linked)\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630869023, "author": "PowerMike-BZH", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22291#issuecomment-3630869023", "createdAt": "2025-12-09T07:55:36Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Seems like an issue with a connected Monitor; but I'm not able to reproduce.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630883580, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22291#issuecomment-3630883580", "createdAt": "2025-12-09T08:00:49Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with plugins disabled.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630884848, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22291#issuecomment-3630884848", "createdAt": "2025-12-09T08:01:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Looking at the code, I've identified a wrong case; so alternatively, you can also try following patch (not on a production environment):\n\nI'm not at all sure it's correct...\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630903100, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22291#issuecomment-3630903100", "createdAt": "2025-12-09T08:07:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22291, "url": "https://github.com/glpi-project/glpi/issues/22291", "author": "PowerMike-BZH", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-09T07:52:55Z", "updatedAt": "2026-03-20T00:39:12Z", "closedAt": "2025-12-09T19:24:08Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "GLPI 11.0.3 : issue to change language", "detail": "Affected version:\n11.0.3\n\nIssue description:\nI cant change to any language, it was working fine prior this version.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please include the requested log output information (files/_log folder by default).\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606763803, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22198#issuecomment-3606763803", "createdAt": "2025-12-03T13:05:12Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "I have a similar error (for some users only) when trying to open a ticket. Maybe it's the same root cause. In my case, the php-error.log shows\n\n[2025-12-03 13:46:05] glpi.CRITICAL: * Uncaught PHP Exception RuntimeException: \"Empty IN are not allowed\" at DBmysqlIterator.php line 612\n Backtrace :\n ./src/DBmysqlIterator.php:612\n ./src/DBmysqlIterator.php:578 DBmysqlIterator->analyseCriterion()\n ./src/DBmysqlIterator.php:309 DBmysqlIterator->analyseCrit()\n ./src/DBmysqlIterator.php:124 DBmysqlIterator->buildQuery()\n ./src/DBmysql.php:1061 DBmysqlIterator->execute()\n ./src/CommonDBRelation.php:1950 DBmysql->request()\n ./src/CommonDBRelation.php:2100 CommonDBRelation::getDistinctTypes()\n ./src/CommonItilObject_Item.php:542 CommonDBRelation::countForMainItem()\n ./src/CommonGLPI.php:357 CommonItilObject_Item->getTabNameForItem()\n ./src/Ticket.php:841 CommonGLPI->addStandardTab()\n ./src/CommonGLPI.php:319 Ticket->defineTabs()\n ./src/CommonGLPI.php:948 CommonGLPI->defineAllTabs()\n ./src/CommonGLPI.php:1288 CommonGLPI->showTabsContent()\n ./src/CommonDBTM.php:6565 CommonGLPI->display()\n ./front/ticket.form.php:252 CommonDBTM::displayFullPageForItem()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606773644, "author": "dani", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22198#issuecomment-3606773644", "createdAt": "2025-12-03T13:07:35Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I have a similar error (for some users only) when trying to open a ticket. Maybe it's the same root cause. In my case, the php-error.log shows\n\nThis is not an error related to the language selection, please open a new dedicated issue.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606789114, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22198#issuecomment-3606789114", "createdAt": "2025-12-03T13:10:58Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "php-errors.log\naccess-errors.log\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606821432, "author": "AHTW4051", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22198#issuecomment-3606821432", "createdAt": "2025-12-03T13:19:01Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22198, "url": "https://github.com/glpi-project/glpi/issues/22198", "author": "AHTW4051", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-03T12:58:37Z", "updatedAt": "2026-03-14T00:36:53Z", "closedAt": "2025-12-03T14:11:04Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "PREG_BACKTRACK_LIMIT_ERROR when viewing ticket with large images", "detail": "Affected version:\n11.0.2\n\nSummary:\nViewing a ticket containing pasted inline images (large screenshots copied directly into the editor) causes GLPI 11.x to crash with PREG_BACKTRACK_LIMIT_ERROR. The ticket becomes unreadable until the malformed [Image omitted] tag is manually removed.\n\nHow to reproduce:\n1. Create a ticket as super‑admin.\n2. Paste a large image directly into the text editor (inline Base64).\n3. Save, then reopen the ticket.\n\nObserved behavior:\n* Page fails to load.\n* Error thrown:\n\nRoot cause:\n* Creating a ticket with multiple large images either causes the ticket to be inaccessible, crash some frontend glpi features (see below) or show an error to the user saying an error arised.\n[Image omitted]\n[Image omitted]\n\nExpected behavior:\nGLPI should safely handle or reject corrupted inline images instead of crashing.\n\nNotes:\n* PHP limits (upload_max_filesize and post_max_size) were already set to 50M.\n* Additional PCRE limits were increased:\n * pcre.backtrack_limit = 5000000\n * pcre.recursion_limit = 500000\n These did not solve the issue.\n* The ticket cannot be opened at all when created with large inline images: it either becomes inaccessible immediately or cannot be created.\n* Removing the ticket entirely is the only workaround when the corrupted inline image prevents loading.", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "The image is supposed to be transformed into a document when saving is done. The issue is probably that this image was not transformed into a document.\n\nHow is the ticket created?\nIs there any active plugin? If you have active plugin, could you try to reproduce this issue by suspending the plugins execution and recreate a new ticket with large images?\n\nOriginal response date: 2025-11-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3546842932, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21967#issuecomment-3546842932", "createdAt": "2025-11-18T10:41:11Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "I suspended the execution of plugins on our GLPI, and cleared the php-errors.log. Here is it after retrying to add a too large image and creating a ticket (as a super admin, as it doesn't let you in technician or user profiles) :\nNote that logs are in French and might need to be translated first\nphp-errors (1).log\n\nOriginal response date: 2025-11-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3548560377, "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21967#issuecomment-3548560377", "createdAt": "2025-11-18T16:45:40Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nWhat is the size of your image? Could you provide an image that can be used to reproduce?\nI tried to reproduce with a 15MB PNG from but creating a ticket from the standard interface is working as expected. The image is converted into a document and is displayed correctly.\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558399683, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21967#issuecomment-3558399683", "createdAt": "2025-11-20T14:38:26Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "on your screenshot the image size limit is \"200 Mio max\" where on my end it's set to 2. Might be the reason why it's working on yours\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3559658646, "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21967#issuecomment-3559658646", "createdAt": "2025-11-20T19:18:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21967, "url": "https://github.com/glpi-project/glpi/issues/21967", "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-11-18T09:34:37Z", "updatedAt": "2026-03-12T00:36:07Z", "closedAt": "2025-12-01T08:28:04Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "\"Reset rules\" button is masked by \"Back to top\" one", "detail": "Affected version:\n11.0.2\n\nIssue description:\nThe \"Reset rules\" button is partially masked by another one in the \"Update and import rules\" Administration panel.\n\nThen new users can't by default guess what's the purpose of this button:\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "You can see the label after the left menu is collapsed but then the arrow button maks partially the \"Test rules engine\" button:\n\n[Image omitted]\n\nOriginal response date: 2025-11-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3589851861, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22108#issuecomment-3589851861", "createdAt": "2025-11-28T16:21:12Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Indeed, and that's not the only page where the \"back to top\" button cause that issue.\n\nOriginal response date: 2025-11-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3589963889, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22108#issuecomment-3589963889", "createdAt": "2025-11-28T17:08:41Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The button is not present anymore on search pages, yes ?\nFor the remaining pages where it presents, I think we could remove it completely.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3596820848, "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22108#issuecomment-3596820848", "createdAt": "2025-12-01T14:25:41Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "It only appears if the page itself scrolls. Some other places have other scrollable containers like the search table.\nI don't know how many places this button appears anymore.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3596868685, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22108#issuecomment-3596868685", "createdAt": "2025-12-01T14:34:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22108, "url": "https://github.com/glpi-project/glpi/issues/22108", "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-28T16:18:23Z", "updatedAt": "2026-03-12T00:35:52Z", "closedAt": "2025-12-01T16:46:03Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Form : Lost visibility of all section after duplicate section", "detail": "Affected version:\n11.0.1\n\nIssue description:\nIn form page, after multiple section, and configure her visibility, with a question about an element of response of question.\n\nIf i duplicate a section with type of visibilty, i lose all configuration of all section. All with empty parameter.", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue.\n\nOriginal response date: 2025-10-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3422029185, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21553#issuecomment-3422029185", "createdAt": "2025-10-20T13:17:12Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "It's only on section who have a condition of visibility about question who have a type of response \"Element\".\n\nI think, it-s like this issues #21420, because in my form i can't add question who have a type of response \"Element\"\nI can do with only one question , because : A workaround for me, it's to duplicate exemple form \"Demander un service\"\n\nOriginal response date: 2025-10-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3422217498, "author": "TxX8N8LN", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21553#issuecomment-3422217498", "createdAt": "2025-10-20T14:03:50Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "It's not only when i duplicate, if i modify one visibility and save, randomly other lost their configuration\n\nOriginal response date: 2025-10-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3422287202, "author": "TxX8N8LN", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21553#issuecomment-3422287202", "createdAt": "2025-10-20T14:18:23Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Devon Blair, if you have step by step instructions (starting with a brand new form) on how to reproduce this, it would really help.\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3437376927, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21553#issuecomment-3437376927", "createdAt": "2025-10-23T14:35:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21553, "url": "https://github.com/glpi-project/glpi/issues/21553", "author": "TxX8N8LN", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-20T13:04:34Z", "updatedAt": "2026-03-06T00:42:11Z", "closedAt": "2025-11-06T09:59:39Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "GLPI Server >= 11, Undefined array key \"url_base\" at Html.php, 400 Bad Request", "detail": "Affected version:\n11.0.1\n\nIssue description:\nA fresh installation of GLPI Server >= 11 on Rocky Linux 9.3 (Blue Onyx) results in a 400 Bad Request error when the web installation is accessed.\n\nEnvironment details:\nN / A\n\nThis is my Apache vHost Configuration:\n\nAdditional context:\nA completely fresh installation of GLPI Server 10.0.20 runs without any problems.", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please ensure the URL of application config option is set in Setup > General on the General setup tab.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3499982677, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21839#issuecomment-3499982677", "createdAt": "2025-11-07T00:41:23Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "Please ensure the URL of application config option is set in Setup > General on the General setup tab.\n\nIt's impossible to access the Web Installer. The Page results in a 400 Bad Request. I followed the official Installation Instructions for on-prem Installations but as already mentioned, it results in a 400 Bad Request error.\n\nThanks for your Time.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3502037045, "author": "danyalberchtoldlf", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21839#issuecomment-3502037045", "createdAt": "2025-11-07T11:32:37Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The error log you attached only contains a warning, and a warning is not blocking. It is generated in the error page rendering, so it means that GLPI serves the error page content.\n\nIs there any vritual host configured to serve the /var/www/html content? It could conflict with the virtual host configuration you mentioned.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3510499807, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21839#issuecomment-3510499807", "createdAt": "2025-11-10T09:45:08Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "The error log you attached only contains a warning, and a warning is not blocking. It is generated in the error page rendering, so it means that GLPI serves the error page content.\n\nIs there any vritual host configured to serve the /var/www/html content? It could conflict with the virtual host configuration you mentioned.\n\nThanks for your time and response. Your hint was right. I put my applications always behind a reverse proxy. I found out that we've to allow GLPI handle HTTP as HTTPS when behind a proxy. $_SERVER['HTTPS'] = 'on';. Whats your opinion about the configuration when behind a reverse proxy. Thanks.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3528070409, "author": "danyalberchtoldlf", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21839#issuecomment-3528070409", "createdAt": "2025-11-13T14:24:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21839, "url": "https://github.com/glpi-project/glpi/issues/21839", "author": "danyalberchtoldlf", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-06T15:45:25Z", "updatedAt": "2026-03-01T00:44:22Z", "closedAt": "2025-11-20T07:12:55Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI 11: after updating to 11.0.1 some Windows RDS hosts stoped update data.", "detail": "Affected version:\n11.0.1\n\nIssue description:\nAfter updating GLPI to 11.0.0 and the inventory plugin to 1.6.0, some Windows RDS hosts among identical ones stopped updating data on the server. The agent logs show the following:\n\n[Wed Oct 29 09:38:15 2025][error] [http client] communication error: 500 Internal Server Error, MySQL query error: Data too long for column 'contact' at row 1 (1406) in SQL query \"UPDATE glpi_computers SET last_inventory_update = '2025-10-29 09:38:14', contact = 'user1@domain/user2@domain/user3@domain/user4\n[Wed Oct 29 09:38:15 2025][error] [http client] server error: MySQL query error: Data too long for column 'contact' at row 1 (1406) in SQL query \"UPDATE glpi_computers SET last_inventory_update = '2025-10-29 09:38:14', contact = 'user1@domain/user2@domain/user3@domain/user4\n\nAfter deleting the server in GLPI and re-importing it, the server is created without errors.\nBut the next inventory ends with the same error.\nWhen manually updating from json in the web interface, the same error occurs.\n\nReproduction steps:\nThis can be reproduced on some RDS hosts from a set of identical ones.", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide an exmaple inventory file.\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460765736, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21686#issuecomment-3460765736", "createdAt": "2025-10-29T10:22:39Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "More precisions: maybe could we handle that kind of case GLPI side, but that sounds strange Agent sends that kind of result. Also, this does not seems specific to v11, but rather Agent (or inventoried computer related).\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460774265, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21686#issuecomment-3460774265", "createdAt": "2025-10-29T10:24:37Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "action_inventory_content with_error.json\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460971159, "author": "dudkitt", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21686#issuecomment-3460971159", "createdAt": "2025-10-29T11:10:46Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "UPD: On RDS hosts that import without errors, there is only one user in the users section JSON.\nGLPI-agent 1.15\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461086489, "author": "dudkitt", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21686#issuecomment-3461086489", "createdAt": "2025-10-29T11:40:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21686, "url": "https://github.com/glpi-project/glpi/issues/21686", "author": "dudkitt", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-29T10:11:58Z", "updatedAt": "2026-02-12T00:38:52Z", "closedAt": "2025-11-03T16:04:58Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI 11.0.1 - Error while migrating forms", "detail": "Affected version:\n11\n\nIssue description:\nI'm trying to migrate the forms from my old version 10.0.20 but I'm getting the error below:\n\nAny ideas?\n\nReproduction steps:\nIn the server I type: sudo -u www-data /var/www/html/glpi/bin/console migration:formcreator_plugin_to_core", "priority": "medium", "type": "support", "createdByEmail": "sage.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Sage Bennett,\n\nThis error probably mean there is some unexpected data in your formcreator tables.\n\nCould you please send us the result of this SQL query?\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460814003, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21670#issuecomment-3460814003", "createdAt": "2025-10-29T10:33:48Z" } }, { "userEmail": "sage.bennett@peppermint.local", "text": "Hello Sage Bennett,\n\nThis error probably mean there is some unexpected data in your formcreator tables.\n\nCould you please send us the result of this SQL query?\n\nselect * from glpi_plugin_formcreator_conditions where show_value is null;\n\nhere\n\n[Image omitted]\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460964841, "author": "infraoderco", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21670#issuecomment-3460964841", "createdAt": "2025-10-29T11:09:00Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Thanks, I think I see what's going on. Working on it.\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461025180, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21670#issuecomment-3461025180", "createdAt": "2025-10-29T11:25:49Z" } }, { "userEmail": "sage.bennett@peppermint.local", "text": "Thanks, I think I see what's going on. Working on it.\n\nOkey, thanks =)\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461029265, "author": "infraoderco", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21670#issuecomment-3461029265", "createdAt": "2025-10-29T11:26:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21670, "url": "https://github.com/glpi-project/glpi/issues/21670", "author": "infraoderco", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-28T12:19:53Z", "updatedAt": "2026-02-07T00:37:17Z", "closedAt": "2025-10-29T13:08:35Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Form question type not updated when changing from Selection to Item - Docker", "detail": "Affected version:\nGLPI 11.0.0-rc4\n\nIssue description:\nIn GLPI 11.0.0-rc4, when creating a form question of type Selection, the field is saved correctly. However, if the question type is later modified to Item, the system does not save the change and the question remains as the original type.\n\n[Image omitted]\n[Image omitted]\n[Image omitted]\n[Image omitted]\n[Image omitted]\n\nReproduction steps:\nCreate a new form in GLPI.\n\nAdd a question with type set to Selection.\n\nSave the form.\n\nEdit the same question and change its type to Item.\n\nSave the form again.\n\nExpected Result:\nThe question type should be updated to Item after saving.\n\nActual Result:\nThe question remains as type Selection, and the modification is not applied.", "priority": "medium", "type": "bug", "createdByEmail": "kai.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This is really weird, I don't see how it could happen.\n\nAre you sure you are modifying the correct question ? In your 3rd image we see a text question above but I don't see it in the preview.\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-09-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3291708567, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20977#issuecomment-3291708567", "createdAt": "2025-09-15T11:33:32Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Here's the video showing how I did it\n\nOriginal response date: 2025-09-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3292437679, "author": "stwartelearte", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20977#issuecomment-3292437679", "createdAt": "2025-09-15T14:21:46Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I understand better now, thanks for the video.\n\nWhen you save the form after changing the type, I noticed that the success pop up does not appear.\nThis mean there is probably an error on the server when you are trying to save, can you check your logs please?\n\nOriginal response date: 2025-09-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3296191552, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20977#issuecomment-3296191552", "createdAt": "2025-09-16T07:23:35Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "The only thing that doesn't pop up is when I change it to Item in Forms. It pops up normally on any other item. Is there still a permission issue?\n\nOriginal response date: 2025-09-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3320029300, "author": "stwartelearte", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20977#issuecomment-3320029300", "createdAt": "2025-09-22T16:25:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20977, "url": "https://github.com/glpi-project/glpi/issues/20977", "author": "stwartelearte", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [ { "sourceLogin": "ccailly", "anonymizedEmail": "jordan.blair@peppermint.local" }, { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "beta / rc", "bug", "forms", "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-11T20:45:31Z", "updatedAt": "2026-02-01T00:44:54Z", "closedAt": "2025-10-23T14:38:37Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Arabic language", "detail": "Contribution description:\nhi\nCan you Adding Arabic Iraq to the Language Selection List and naming it (العربية العراق)\nar_IQ.po and change (العربية) ar_SA.po to (العربية السعودية) Because I am working on Arabic translation", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please check It adds several new translated languages:\n* ar_IQ\n* ar_SY\n* az_AZ\n* bn_BD\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3424693608, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21559#issuecomment-3424693608", "createdAt": "2025-10-21T05:09:43Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "good now.\nCan you force the numbers to stay aligned to the left regardless of RTL or LTR, or make the icons flip to the left when using RTL\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n[Image omitted]\n[Image omitted]\n[Image omitted]\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3425206230, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21559#issuecomment-3425206230", "createdAt": "2025-10-21T07:39:44Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This is something completely different, I've converted your comment as a new issue.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3425451510, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21559#issuecomment-3425451510", "createdAt": "2025-10-21T08:42:04Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "okay thanks\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3425462763, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21559#issuecomment-3425462763", "createdAt": "2025-10-21T08:45:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21559, "url": "https://github.com/glpi-project/glpi/issues/21559", "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "translation" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-20T16:39:13Z", "updatedAt": "2026-01-30T00:37:46Z", "closedAt": "2025-10-21T11:40:29Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Agent tag not reset when no more set", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAfter a submitted inventory with tag set has been submitted, the tag is kept if tag is removed from the following inventory.\n\nReproduction steps:\n1. Import an inventory with tag set: tag-issue-with-tag.json\n2. Check the asset in glpi and see it has a tag\n3. Import an inventory from the same asset and with the same deviceid but this time with no tag: tag-issue-no-tag.json\n4. Check the asset in glpi and see the previous tag has been kept\n\nThis is also the case with xml inventory: tag-issue-with-tag.xml vs tag-issue-no-tag.xml\n\nAdditional context:\nThis only happens when deviceid remains the same. The use case is when you reconfigure an agent on a computer to remove the previously tag and after it submitted at least one inventory.", "priority": "medium", "type": "maintenance", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "Provided inventories has been forged to reproduce the case but I also tested with real inventory.\n\nOriginal response date: 2026-04-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4168611316, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23721#issuecomment-4168611316", "createdAt": "2026-04-01T09:00:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "So, network (inventories|discoveries) *can* add a TAG, it's stored with the agent. But that's not correct, since the agent is linked on the Computer if it's part of the inventory, I'm not sure its tag should be changed.\n\nI'm not sure how TAG from a net(inv|disco) should be handled. Any idea how that was supposed to work when it's been implemented?\nI guess it should not be stored in the agent configuration; but maybe it should be kept to be used in rules, or similar.\n\nSkyler Adler Elliot Bennett\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4197130876, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23721#issuecomment-4197130876", "createdAt": "2026-04-07T07:01:42Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi Skyler Adler\n\nno network (inventories|discoveries) _can't_ add a tag. Tag will only be used during computer inventories.\n\nHere are 2 cases that glpi must support in _the case a tag has firstly been set in a computer inventory and so glpi sets it on related glpi agent object_:\n 1. it must NOT be reset if a network/discovery inventory is submitted by the same agent\n 2. it must be reset if the tag is no more set on future computer inventories from the same agent\n\nThe second case means the tag configuration has been removed from glpi-agent configuration.\n\nIs that clear enough ?\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4236604822, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23721#issuecomment-4236604822", "createdAt": "2026-04-13T13:08:12Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "no network (inventories|discoveries) _can't_ add a tag. Tag will only be used during computer inventories.\n\nI was talking about a tag information in the XML fle; not about GLPI side.\n\n1. it must NOT be reset if a network/discovery inventory is submitted by the same agent\n\nSo, if a \"TAG\" can be present in a network inv/disco, can you give an example XML?\n\n2. it must be reset if the tag is no more set on future computer inventories from the same agent\n\nThat is what #23782 address.\n\nOriginal response date: 2026-04-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4241881721, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23721#issuecomment-4241881721", "createdAt": "2026-04-14T07:03:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23721, "url": "https://github.com/glpi-project/glpi/issues/23721", "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "inventory", "need technical doc" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-01T08:59:19Z", "updatedAt": "2026-04-14T10:00:51Z", "closedAt": "2026-04-14T10:00:51Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Rest API - Invalid key supplied", "detail": "Affected version:\n11.0.0-beta4\n\nIssue description:\nServer gives 500 (Internal Server Error) after trying to attempt an authentication via API using both of the methods (by authorization code or by password)\n\nAffected page:\n\nReproduction steps:\n1. Call REST API through any API platform or via /api.php/v2/doc\n2. Error 500 is given\n\nAdditional context:\nNot a fresh install (upgraded from a glpi 10 > glpi11-beta3 > glpi11-beta4). Also tested in beta 1 and 3 and it still gives the same error. Legacy API disabled.", "priority": "medium", "type": "support", "createdByEmail": "reese.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.bennett@peppermint.local", "text": "I have the same issue, no keys get generated on windows, despite user having RW on all the subdirectories, I don't find anything related to this in the documentation and no command to regenerate the keys either, how can I try to regenerate those to debug the issue?\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3455842645, "author": "SteadEXE", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19819#issuecomment-3455842645", "createdAt": "2025-10-28T10:50:10Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "In my migration from 10 to 11 those file also didnt got created.\n\nI also ask if there's anyway to recreate them\n\nNow that we have the instance in production reinstall is not an option :-)\n\nThanks\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3553370319, "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19819#issuecomment-3553370319", "createdAt": "2025-11-19T15:34:46Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I reviewed the code and I am pretty sure that when these files are not generated, an exception is thrown and probably an error message is shown during the update. Could you check your php-errors.log file to see if you have the trace of the error?\n\nAlso, we should provide a way to regenerate the OAuth server key files, in case they are lost, but also to be able to regenerate new keys if the existing ones are compromised.\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3556269992, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19819#issuecomment-3556269992", "createdAt": "2025-11-20T07:11:35Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "Just encountered the same issue on a Windows Server.\nMy openssl was wrongly configured, the migration displayed an error. See for more details :\n\nI fixed my SSL since, and tried to manually generate keys in _oauth folder.\nHowever it doesn't seem to fix the issue.\n\nI have the exact same error, and i dont know how to regenerate keys properly or how to recover from this.\nSkyler Adler , is there a way to regenerate the Oauth server key files ?\n\nOriginal response date: 2026-02-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3884447603, "author": "NoxWorld2660", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19819#issuecomment-3884447603", "createdAt": "2026-02-11T13:28:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 19819, "url": "https://github.com/glpi-project/glpi/issues/19819", "author": "stevanborges", "anonymizedAuthorEmail": "reese.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-05-26T22:50:36Z", "updatedAt": "2026-07-09T00:48:38Z", "closedAt": "2026-03-30T08:28:28Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Copy and Paste image to validation comment fails", "detail": "Affected version:\n10.0.18 / 11.0.0-dev\n\nIssue description:\nWhen adding a comment to a validation request and inserting a image which is \"too large\" the comment will not be saved.\n\nI replaced the long Base64 String within the error message. The screenshot was just the whole desktop of the user.\n\nIn GLPI 10: No error message shown to user, fails silently and just shows error message in sql-errors.log\n\nIn GLPI 11:\nShows error and also logs the same error message but in php-errors.log\n\n[Image omitted]\n\nReproduction steps:\n1. Have a validation request in a ticket\n2. Add a comment to approve/refuse and add a larger image via Copy&Paste\n3. Try to save", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Handling images in text fields is done in a double add/update process.\nFirst, the followup/validation/etc is added to the DB as-is with the image data blob.\nThen, if the add/update succeeds, in the post_addItem/post_updateItem process the image is actually uploaded and the content of the textbox is updated to refer to the image URL instead.\n\nIt works for followups because the content column is longtext (4 billion characters) while the text fields for validations are only text (65,535 characters) and therefore not sufficiently long enough to store the intermediate content.\n\nThe easiest solution would be changing all text columns that could contain images to mediumtext or longtext.\nI don't fully know the reason it was done in two passes but it may not be desired to immediately save the images as documents before it is known that the add/update will actually succeed.\n\nOriginal response date: 2025-11-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3592510481, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20265#issuecomment-3592510481", "createdAt": "2025-11-30T12:28:47Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I confirm the issue.\n\nTo reproduce:\n - set the GLPI document limit to a low value (e.g. 2MB);\n - open a form, type some text in the description, and drag and drop a big image (e.g. 15MB) in the description field;\n - -> a \"file too big\" error is displayed, but the image remains in the description;\n - validate the form;\n - -> the item is created, but the image is not converted into a document and opening the ticket triggers an error.\n\nThe JS logic must be fixed to remove the image from the description when the upload fails.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3595238312, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20265#issuecomment-3595238312", "createdAt": "2025-12-01T08:27:41Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The root cause has been fixed by #22187. This will not fix the data already present in database, but doing this would be too complex.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612651219, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20265#issuecomment-3612651219", "createdAt": "2025-12-04T14:55:46Z" } }, { "userEmail": "taylor.blair@peppermint.local", "text": "Its is not ideal, but I did remove the inline image from ticket via API and the ticket now works again.\n\nGet session token:\n\nGET\n\nUpdate ticket content:\n\nPUT -d {\n \"input\": {\n \"id\": 44444,\n \"content\": \"keep text without image\"\n }\n}\n\nHope it helps.\n\nOriginal response date: 2026-03-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4092575803, "author": "vnirocha", "anonymizedAuthorEmail": "taylor.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20265#issuecomment-4092575803", "createdAt": "2026-03-19T18:57:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20265, "url": "https://github.com/glpi-project/glpi/issues/20265", "author": "SimonTheIman", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-07-10T05:45:00Z", "updatedAt": "2026-03-20T07:45:29Z", "closedAt": "2025-12-04T14:55:46Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Degraded performance in GLPI 11 latest commit during common operations", "detail": "Affected version:\nGLPI 11 latest commit\n\nIssue description:\nContext:\n\n* GLPI 11 latest commit\n* No plugins installed\n\nI am observing some performance issues in the Tickets section, particularly when updating a ticket\n\n- Browser console\n\nDebug mode OFF\n\n[Image omitted]\n\nDebug Mode ON\n\n[Image omitted]\n\n- Symfony console\n\nDebug mode OFF\n\n[Image omitted]\n\nDebug mode ON\n\n[Image omitted]\n\n- GLPI console\n\n[Image omitted]\n\n[Image omitted]\n\n compared to creating a new ticket, which appears faster.\n\n- Browser console\n\nDebug mode OFF\n\n[Image omitted]\n\nDebug Mode ON\n\n[Image omitted]\n\n- Symfony console\n\nDebug mode OFF\n\n[Image omitted]\n\nDebug mode ON\n\n[Image omitted]\n\n- GLPI console\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\nCreate a ticket and then return to it to perform an update", "priority": "high", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The Symfony profiler is less useful in this case I think, which is why I was curious about the GLPI profiler.\n\nFor example on my side, I am seeing the initialization of the cache taking a lot longer than expected.\n[Image omitted]\n\nOriginal response date: 2025-09-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3302668289, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20948#issuecomment-3302668289", "createdAt": "2025-09-17T12:03:13Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I would need to see the GLPI debug profiler information for someone experiencing the slowdowns. Right now, I don't know if I am seeing the same kind of slowdowns or if I have something in my local environment causing cache issues.\n\nOriginal response date: 2025-09-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3344648228, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20948#issuecomment-3344648228", "createdAt": "2025-09-29T02:36:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "For some time, we haven’t had a reader. In consultation with the PS team, I assume that a commit or cache clear may have resolved the issue, at least temporarily.\n\nOriginal response date: 2025-09-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3346062075, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20948#issuecomment-3346062075", "createdAt": "2025-09-29T09:59:36Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "My issue was with xdebug.start_upon_error being enabled. During cache initialization it tries calling some translation functions, when the translator isn't even initialized yet, and even though translation exceptions are silently caught and ignored, it was causing a few hundred ms of performance overhead on any request that booted the kernel.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3411698371, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20948#issuecomment-3411698371", "createdAt": "2025-10-16T16:29:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20948, "url": "https://github.com/glpi-project/glpi/issues/20948", "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "beta / rc", "performance" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-10T09:20:13Z", "updatedAt": "2026-01-29T00:37:13Z", "closedAt": "2025-10-20T08:41:23Z" } }, { "title": "GLPI 11.0.5 – Unable to upload custom images (Helpdesk / custom icons)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nAfter upgrading GLPI from 11.0.4 to 11.0.5, it is no longer possible to upload custom images used for:\n\nHelpdesk custom scenes\n\ncustom UI icons / illustrations\n\nThe same images and configuration worked correctly in GLPI 11.0.4.\n\nUploads now fail or are silently rejected, with no clear error message in the UI, and the image is not applied or displayed.", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "devon.blair@peppermint.local", "text": "I think there's some problem with the rendering of the default image; it only appears in certain browser zoom settings, like this:\n\n[Image omitted]\n\nOriginal response date: 2026-02-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3972965753, "author": "jardeljsv", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22987#issuecomment-3972965753", "createdAt": "2026-02-27T13:28:00Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Morgan Bennett,\n\nWithout any clear errors in the logs it will be hard for us to investigate this issue.\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4110849649, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22987#issuecomment-4110849649", "createdAt": "2026-03-23T14:01:55Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "Update / Possible root cause\n\nAfter further investigation, the issue might be related to the upgrade procedure rather than a direct GLPI bug.\n\nDuring the upgrade from 11.0.4 to 11.0.5, the entire public/ directory from the previous installation was copied into the new one.\n\nSince this directory contains compiled frontend assets (Vue.js, JS, CSS), which are likely version-dependent, this could potentially introduce inconsistencies between the frontend and the backend.\n\nThis might explain the observed behavior:\n\n* Helpdesk tiles becoming non-interactive (pointer-events-none)\n* Custom image uploads failing or being ignored\n* UI customization not working as expected\n\nAfter restoring the original public/ directory from a clean 11.0.5 installation and only copying static assets (such as public/pics/), the issue no longer occurred.\n\nQuestion\n\nCould this behavior be related to frontend build incompatibilities between versions?\nIs there a recommended approach to safely preserve custom assets in the public/ directory during upgrades?\n\nAny clarification or best practices would be appreciated.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4116186570, "author": "hakimbedja", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22987#issuecomment-4116186570", "createdAt": "2026-03-24T08:08:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "You should not have copied the old public directory; see upgrade guide\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4116328715, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22987#issuecomment-4116328715", "createdAt": "2026-03-24T08:33:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22987, "url": "https://github.com/glpi-project/glpi/issues/22987", "author": "hakimbedja", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-03T13:36:54Z", "updatedAt": "2026-07-03T00:50:03Z", "closedAt": "2026-03-24T08:33:29Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "build:compile_scss in bad path", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen I tried to compile scss I get this error\n\nD:\\Sites\\glpi-test>php bin\\console build:compile_scss\nUnable to write compiled CSS in \"D:\\Sites\\glpi-test/public/css_compiled/D:\\Sites\\glpi-test\\css_core_palettes.min.css\".\n\nAll glpi-test was writable to check the problem, but it's identical\n\nMay be this path is misformed in PHP", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "The build:compile_scss is indeed not compatible with Windows FS paths.\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3811295769, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22868#issuecomment-3811295769", "createdAt": "2026-01-28T13:24:24Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "Do I have to solve the problem myself ? in my fork ?\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3811357269, "author": "Sevengroup-IT", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22868#issuecomment-3811357269", "createdAt": "2026-01-28T13:38:01Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Do I have to solve the problem myself ? in my fork ?\n\nIt is clearly not on the top of our priorities, so the best solution is indeed to try to fix it by yourself.\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3811367948, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22868#issuecomment-3811367948", "createdAt": "2026-01-28T13:40:22Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "I know, that's not a priority.\n\nCan I purpose the solution when I will found it ?\n\nDe : Cédric Anne *@*.*>\nEnvoyé : mercredi 28 janvier 2026 14:41\nÀ : glpi-project/glpi *@*.*>\nCc : INFORMATIQUE Service *@*.*>; Author *@*.*>\nObjet : Re: [glpi-project/glpi] build:compile_scss in bad path (Issue #22868)\n\n[]cedric-anne left a comment (glpi-project/glpi#22868)\n\nDo I have to solve the problem myself ? in my fork ?\n\nIt is clearly not on the top of our priorities, so the best solution is indeed to try to fix it by yourself.\n\n-\nReply to this email directly, view it on GitHub, or unsubscribe.\nYou are receiving this because you authored the thread.Message ID: *@*.@*.*>>\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3811378772, "author": "Sevengroup-IT", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22868#issuecomment-3811378772", "createdAt": "2026-01-28T13:42:39Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22868, "url": "https://github.com/glpi-project/glpi/issues/22868", "author": "Sevengroup-IT", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-28T13:09:11Z", "updatedAt": "2026-06-14T01:11:06Z", "closedAt": "2026-03-05T15:16:58Z" } }, { "title": "\"Anomymize support agents\" - does not work correctly with the names of regular users who approve ticket", "detail": "Affected version:\n10.0.19\n\nIssue description:\nWhen sending an approval request to a regular user, the ticket author does not see the approver's full name. The approver's name is also mistakenly replaced with \"helpdesk user\".\n\nSelf-service interface regular user:\n[Image omitted]\n\nGLPI cofiguration:\n[Image omitted]", "priority": "low", "type": "feature", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "emerson.bennett@peppermint.local", "text": "Please tell me if this problem will be fixed?\n\nOriginal response date: 2025-09-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3299624245, "author": "ak47d", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20780#issuecomment-3299624245", "createdAt": "2025-09-16T17:03:08Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I'm working on it.\n\nIn a nutshell, _regular user 2_ is not a _support agent_ but has the _self service_ profile so it shouldn't be anonymized.\nIs this correct ?\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3451817706, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20780#issuecomment-3451817706", "createdAt": "2025-10-27T15:15:34Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "Yes, that's right.\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3675242028, "author": "ak47d", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20780#issuecomment-3675242028", "createdAt": "2025-12-19T14:17:11Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Sorry for the long delay.\nAt the moment, with the option, any user is anonymized. It's not depending on the fact that it's an helpdesk user or a regular user. We currently don't have a (simple) way to determine if the name should be anonymized or not.\n\nOn which technical base do you need this anonymized to be processed/bypassed ?\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3714069498, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20780#issuecomment-3714069498", "createdAt": "2026-01-06T10:11:37Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20780, "url": "https://github.com/glpi-project/glpi/issues/20780", "author": "ak47d", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-08-25T21:58:42Z", "updatedAt": "2026-05-21T01:03:32Z", "closedAt": "2026-02-09T08:15:04Z" } }, { "title": "[11.0.6][API] State visibility not added when status created", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello,\n\nWhen I add a new state with API, the state is created but there is no records created in glpi_dropdownvisibilities table.\n\nWhat I expected:\nWhen I add a new state with API, visibility state records are created.\n\nReproduction steps:\n1. Create a status with api\ncurl -s -X 'POST' \"${API_V2_URL}/Dropdown/State\" \\\n-H 'accept: application/json' \\\n-H 'Authorization: Bearer '\"${TOKEN_V2}\"'' \\\n-H 'Content-Type: application/json' \\\n-d '{\n \"name\": \"'\"${STATUS}\"'\",\n \"is_recursive\": false,\n \"comment\": \"\"\n}'\n=> the status is created but there is no entry for the new status in glpi_dropdownvisibilities table.\n2. Go to ${API_V2_URL}/front/state.php\n=> the status is here, with all visibilities to \"No\". Click to save : entries in glpi_dropdownvisibilities table are created.\n\n1. Create a status with Web GUI=> the status is created and there is entries for the new status in glpi_dropdownvisibilities table.\n\nEnvironment details:\nOffline server.", "priority": "medium", "type": "support", "createdByEmail": "cameron.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "That is expected. You created a State resource, not State_Visibilities. No visibility is expected to be added by default.\n\nOriginal response date: 2026-03-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4055002017, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23471#issuecomment-4055002017", "createdAt": "2026-03-13T13:16:33Z" } }, { "userEmail": "cameron.blair@peppermint.local", "text": "Ok thanks. But if I try to create a \"State visibility\":\n\nI get : \"You do not have the necessary permissions to perform this action\"\n\nOriginal response date: 2026-03-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4055078434, "author": "ebourgui", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23471#issuecomment-4055078434", "createdAt": "2026-03-13T13:29:34Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "In theory it should be something like this, but indeed it seems it was never implemented.\n\nOriginal response date: 2026-03-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4055136021, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23471#issuecomment-4055136021", "createdAt": "2026-03-13T13:40:05Z" } }, { "userEmail": "cameron.blair@peppermint.local", "text": "I've tried too but with no luck...\nSo I will continue to update manually the visibility of my states.\nThank you Curtis for your answers.\n\nOriginal response date: 2026-03-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4055180550, "author": "ebourgui", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23471#issuecomment-4055180550", "createdAt": "2026-03-13T13:47:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23471, "url": "https://github.com/glpi-project/glpi/issues/23471", "author": "ebourgui", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-13T12:50:13Z", "updatedAt": "2026-07-16T00:41:17Z", "closedAt": "2026-04-06T13:31:21Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Unable to add pasive device to rack", "detail": "Affected version:\n11.0.4\n\nIssue description:\nCreated new rack.\nCreated couple of passive devices by 'clone' option from other element.\nTrying to add passive device to rack, after selecting 'passive device' from 'item type' dropdown, there isn't any entry in 'item' dropdown - only 'the results could not be loaded' text.\n\nI get same results when creating passive element from scratch (by 'hand'). Same when try to add any passive device to already existing rack.\n\nWhen I try to add other item types to rack - no problem, i can se computers, pdus, peripherials etc.", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "\"the results could not be loaded'\" means there is an error, there is certainly an entry in the logs. Enabling debug mode may give more information.\nYou should first try without any plugin if the issue is reproducible.\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3742233259, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22640#issuecomment-3742233259", "createdAt": "2026-01-13T06:28:29Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "After disabling all plugins - same result.\nDebug set to E_ALL in php.ini.\nDebug enabled in glpi.\n\nNo errors, php-errors.log is not creating.\n\nalso cache files cleared\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3742464429, "author": "yild", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22640#issuecomment-3742464429", "createdAt": "2026-01-13T07:23:03Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Is this still happening with GLPI 11.0.6?\n\nOriginal response date: 2026-03-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3994351018, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22640#issuecomment-3994351018", "createdAt": "2026-03-04T00:10:27Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "Yes, after updating to 11.0.6 problem still exists.\n\nFurther more, if I de-attach passive element from existing rack I can't re-attach it again, list of passive devices is empty even when trying to add passive device for the same rack.\n\nIn debug mode I can't identify which sql query is for passive devices.\n\nOriginal response date: 2026-03-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4019701071, "author": "yild", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22640#issuecomment-4019701071", "createdAt": "2026-03-08T18:11:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22640, "url": "https://github.com/glpi-project/glpi/issues/22640", "author": "yild", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-13T06:21:12Z", "updatedAt": "2026-06-21T01:13:32Z", "closedAt": "2026-03-12T06:46:27Z" } }, { "title": "Php-Errors Inventory agent - Undefined array key \"date_mod\" at CommonDBTM.php line 1862", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.6\n\nIssue description:\nAgent 1.16\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please test if you reproduce without any plugins. If you can, we need a way to reproduce; looks like this is related to your data (maybe something in locks table).\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4036884270, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23443#issuecomment-4036884270", "createdAt": "2026-03-11T06:42:22Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Hello\n\nI have 335 lines (dating from 2024) in the locked fields corresponding to the date_mod field - I deleted them to see if I still have the errors.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4038599400, "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23443#issuecomment-4038599400", "createdAt": "2026-03-11T11:33:51Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please use english only here.\nWaiting for your feedback.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4038857392, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23443#issuecomment-4038857392", "createdAt": "2026-03-11T12:23:17Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Hello\n\nGood news\n\nNo more errors\n\nBut i have this :\n\n[Image omitted]\n\nSame behavior or new ticket ?\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4047221873, "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23443#issuecomment-4047221873", "createdAt": "2026-03-12T14:30:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23443, "url": "https://github.com/glpi-project/glpi/issues/23443", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-03-10T17:11:41Z", "updatedAt": "2026-06-21T01:13:08Z", "closedAt": "2026-03-12T14:44:45Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Feature request – Add “Observer Group” column in simplified interface ticket list", "detail": "Contribution description:\nHello,\n\nIn GLPI 11, when a user is using the simplified interface (self-service) and views the list of their tickets, it is not possible to modify the default column selection displayed in the ticket list.\n\nFor our use case, we need to display an additional column: Observer Group.\n\nCurrently:\n\nThe simplified interface does not allow administrators to configure which columns are displayed by default.\n\nThe Observer Group field is not available in the column/search selection, while other group-related fields (such as requester group) can appear.\n\nExpected behavior:\n\nAllow administrators to configure the default columns displayed in the ticket list for the simplified interface.\n\nMake the Observer Group field available as a selectable column.\n\nThis would allow users to quickly see which observer groups are associated with their tickets directly from the ticket list.\n\nThank you.", "priority": "low", "type": "feature", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "That's an interesting point you brought up. I was going to reinforce it as a suggestion too, but upon further analysis, I realized that this new view has already been included and can be changed by the superadmin. Here's how:\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4008262074, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23387#issuecomment-4008262074", "createdAt": "2026-03-05T22:36:43Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "Thank you for your feedback. However, on my end, this small icon only appears in administrator mode and allows configuration of the global and personal display of standard user profiles. But under a profile with a simplified helpdesk interface, it's not possible to customize the column display.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4008291453, "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23387#issuecomment-4008291453", "createdAt": "2026-03-05T22:43:50Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "[Image omitted]\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4008302387, "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23387#issuecomment-4008302387", "createdAt": "2026-03-05T22:47:03Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "As a superadmin, you need to access support > tickets and select the third option or the option labeled helpdesk from the view button. After selecting it, just add the new column and close it. After that, you will see that it will appear in the self-service profile.\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4008438463, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23387#issuecomment-4008438463", "createdAt": "2026-03-05T23:27:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23387, "url": "https://github.com/glpi-project/glpi/issues/23387", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-05T22:11:12Z", "updatedAt": "2026-05-31T00:19:31Z", "closedAt": "2026-05-31T00:19:31Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "LDAP config HS migration V10->V11", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nLDAP config was fine in version V10.0.23 running out of docker\nSame config migrated to DOCKER and upgraded to V11.0.5 is not working.\n\nPHP User Warning (512): Unable to start TLS connection to LDAP server x.x.x.x:389 error: Connect error (-11) extended error: error:0A000086:SSL routines::certificate verify failed (unable to get local issuer certificate) err string: error:0A000086:SSL routines::certificate verify failed (unable to get local issuer certificate) at AuthLDAP.php line 2996 in ./src/AuthLDAP.php at line 2996\n\n[Image omitted]\n\nEnvironment details:\n[Image omitted]\n\n[Image omitted]\n\nAdditional context:\nThanks :)", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "It's requested to write in english only.\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3818606388, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22904#issuecomment-3818606388", "createdAt": "2026-01-29T16:00:34Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "Hi, updated and translated :) Thanks\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3818648693, "author": "vincentguajioty", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22904#issuecomment-3818648693", "createdAt": "2026-01-29T16:07:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Same config migrated to DOCKER and upgraded to V11.0.5 is not working.\n\nWell, a major app upgrade and a major change to environment is often a cause of problems.\n\nYour error message indicates an SSL certificate verification issue. That does not seem a GLPI issue, rather a system one. Maybe due to docker, I have no idea.\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3822211385, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22904#issuecomment-3822211385", "createdAt": "2026-01-30T07:07:53Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "yep in fact. But in order to have a working service, could be greate to be able to import in the docker the right certificate. or to tell GLPI to ignore certificate. This should be part of the app bundle.\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3822240499, "author": "vincentguajioty", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22904#issuecomment-3822240499", "createdAt": "2026-01-30T07:17:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22904, "url": "https://github.com/glpi-project/glpi/issues/22904", "author": "vincentguajioty", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-29T15:57:34Z", "updatedAt": "2026-05-11T00:58:56Z", "closedAt": "2026-01-30T07:07:53Z" } }, { "title": "Attach (upload) a file to ticket has disapeared from default Form", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHi,\nMaybe a config issue, but since our upgrade to latest GLPI 11, our users cannot upload files anymore to the new forms.\n\n[Image omitted]\n\nMy GLPI_VAR_DIR is writeable, user profiles are OK, that occurs even with the admin account.\n\nAny idea ?\nThanks", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "finley.bennett@peppermint.local", "text": "Got same problem here, tested on a full install or in a docker install, same problem\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798297586, "author": "werewolf004", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22798#issuecomment-3798297586", "createdAt": "2026-01-26T07:56:32Z" } }, { "userEmail": "finley.bennett@peppermint.local", "text": "Hi,\nA colleague found the problem. In fact, when we are in simplified mode, we no longer open a ticket directly but instead fill out a form that will generate the creation of a ticket.\nTo do this, you need to go to Administration, then Forms. By default, we have \"Report an incident\" and \"Request a service\". You just need to edit them, then in \"Form\", add a new field using the \"+\" button (which corresponds to adding a question) at the bottom, and choose \"File\" as the type. This allows you to re-enable the ability to attach a file in the form, which will create the ticket when using the simplified view.\n(sorry for my bad english)\n\nFrench:\nUn collègue a trouver le problème, en fait quand on est en mode simplifié, on n'ouvre plus un ticket mais on rempli un formulaire qui lui va générer la création d'un ticket. Pour ce faire, il faut aller dans Administration puis Formulaires, on a par défaut \"Signaler un incident\" et \"Demander un service\", il suffit de les éditer puis dans \"Formulaire\" il suffit d'ajouter via le \"+\" (qui correspond a ajouter une question) en bas, puis on choisi comme type \"Fichier\", cela permet d'ajouter de nouveau la possibilité d'ajouter un fichier dans le formulaire qui créera le ticket quand on est en vue simplifié\n\nOriginal response date: 2026-01-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3803890331, "author": "werewolf004", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22798#issuecomment-3803890331", "createdAt": "2026-01-27T08:45:05Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Looks like this is not a bug then\n\nOriginal response date: 2026-01-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3803949943, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22798#issuecomment-3803949943", "createdAt": "2026-01-27T08:56:34Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Hello, thank you for your feedback.\nThe default ticket creation form has been replaced by two native forms (Report an incident and Request a service).\nTo add attachments, the easiest way is to manually add a File question as you described.\nThe attached files will be automatically attached to the ticket created.\n\nAt the same time, I have made a proposal to add this question by default so that future version upgrades (V10 => V11) will not be affected as you have been.\n\nIn your case, since the migration has already been completed, you must add the question manually.\n\nOriginal response date: 2026-01-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3804481897, "author": "ccailly", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22798#issuecomment-3804481897", "createdAt": "2026-01-27T10:54:01Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22798, "url": "https://github.com/glpi-project/glpi/issues/22798", "author": "labiloute", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [ { "sourceLogin": "ccailly", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-22T12:30:27Z", "updatedAt": "2026-05-08T00:54:25Z", "closedAt": "2026-01-27T08:56:34Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Unable to assign service levels to ticket", "detail": "Issue description:\nDescription:\nWhen attempting to assign service levels to a ticket, the action does not work.\n\nSteps to Reproduce:\n\nOpen the ticket in the system.\n\nAttempt to assign a service level.\n\nObserve that the service level is not applied.\n\nExpected Behavior:\nThe selected service level should be successfully assigned to the ticket and reflected in the ticket details.\n\nActual Behavior:\nThe system does not assign the selected service level, and no error message is displayed.\n\nEnvironment:\n\nGLPI version: 11.0.4\n\nPHP version: 8.4\n\nDatabase type and version: MariaDB 10.6.22\n\nBrowser: Google Chrome\n\nAttachment:", "priority": "medium", "type": "support", "createdByEmail": "hayden.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "avery.blair@peppermint.local", "text": "Same problem\n\nOriginal response date: 2025-12-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3645948210, "author": "Izzaya0212", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22275#issuecomment-3645948210", "createdAt": "2025-12-12T10:43:51Z" } }, { "userEmail": "sage.blair@peppermint.local", "text": "Same issue with 11.0.2\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3669487177, "author": "krishnaavril", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22275#issuecomment-3669487177", "createdAt": "2025-12-18T10:07:59Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The right to assign SLA to tickets is now a separate permission from the permission to update tickets. Please confirm your user's profiles have the \"Assign\" right for SLM under Administration > Profiles > Your profile > Setup tab.\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696244914, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22275#issuecomment-3696244914", "createdAt": "2025-12-29T11:19:59Z" } }, { "userEmail": "sage.blair@peppermint.local", "text": "Thanks Taylor Adler\n\nIt's working now!\n\nOriginal response date: 2026-01-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3705306720, "author": "krishnaavril", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22275#issuecomment-3705306720", "createdAt": "2026-01-02T13:19:37Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22275, "url": "https://github.com/glpi-project/glpi/issues/22275", "author": "asscjr", "anonymizedAuthorEmail": "hayden.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-06T01:06:46Z", "updatedAt": "2026-04-13T00:48:53Z", "closedAt": "2026-01-02T19:59:27Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Strange symbols after update 10.0.19 to 11.0.4", "detail": "Affected version:\n11.0.4\n\nIssue description:\nGood afternoon.\n\nAfter migrating to 11.0.4 and installing and updating the following plugins:\n\nFields Version 1.23.1\nBehaviours 3.0.1\nData Injection 2.15.2\nGLPI Inventory 1.6.4\nVIP 1.9.1\n\nI've noticed that some fields in GLPI contain strange symbols.\n\nSuch as ---- ‎,, or in some cases ‎\n\nFrom what little I've been able to see, I know it's related to the Fields plugin, but even though I've disabled all of that in the plugin settings, these symbols are still appearing in some fields.\n\nCould someone please tell me how to remove them?\n\nThank you.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please include the GLPI setup information requested in the bug template.\n\nPlease also:\n- Test with all plugins disabled\n- Test with another browser and/or clear the browser cache\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3687140581, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22454#issuecomment-3687140581", "createdAt": "2025-12-23T15:58:49Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Good afternoon.\n\nI'll tell you what I did, but it didn't work.\n\nI disabled all plugins.\n\nI tried it with Edge, Chrome, and Firefox.\n\nNothing I tried worked.\n\nNow I'm happy to say that I did something that worked, but I don't know what fixed it.\n\nFrom a fresh installation of 11.0.4, I copied absolutely all the directories and files from the clean installation except for the following:\n\nglpi\\config\nglpi\\files\nglpi\\plugins\nglpi\\public\\pics\n\nEverything else was copied and overwritten.\n\nAnd yes, it works.\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3687618248, "author": "Senninha1974", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22454#issuecomment-3687618248", "createdAt": "2025-12-23T18:49:45Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "How did you initially update to 11.0.4?\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3688210315, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22454#issuecomment-3688210315", "createdAt": "2025-12-23T23:34:14Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Good morning\n\nI followed the normal process.\n\nI stopped IIS.\n\nI renamed the current folder to glpi.old.\nI placed the extracted folder from version 11.0.4 in the directory where my websites are located in IIS.\n\nThen I copied the following from the old installation:\n\n\"config\" = \"Complete config directory\"\n\n\"files\" = \"Complete files directory\"\n\n\"public\\pics\" = \"Complete pics subdirectory within public\"\n\n\"public\\index.php\" = \"Index.php file within public\"\n\n\"public\\web.config\" = \"Web.config file within public\"\n\nFinally, I modified the css_glpi.min.css file to change two colors. That's all.\n\nI modified the GLPI path in IIS, changing the entry (which in version 10.0.19) from \\glpi to \\glpi\\public.\n\nI accessed the GLPI website, and it automatically launched the update process. It started updating the database (I think it performed two updates), and after a while (2-3 minutes), it gave me an error message saying there was an unexpected error (without any further information). I understand that the strange symbols appeared during this process.\n\nI closed everything and reopened GLPI (and started seeing the strange symbols on the login screen; I only see them when it's a field that can be modified). I logged in and checked the version, which clearly stated 11.0.4.\n\nOriginal response date: 2025-12-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3688892058, "author": "Senninha1974", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22454#issuecomment-3688892058", "createdAt": "2025-12-24T07:06:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22454, "url": "https://github.com/glpi-project/glpi/issues/22454", "author": "Senninha1974", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-19T21:16:51Z", "updatedAt": "2026-04-12T00:48:10Z", "closedAt": "2026-01-01T16:58:54Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI constants : GLPI_PLUGINS_DIR constant overload is not taken into account in GLPI_PLUGINS_DIRECTORIES.", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHello/Good evening everyone,\n\nIn the context of a GLPI installation respecting HFS, the overload of the following constants GLPI_VAR_DIR, GLPI_LOG_DIR, GLPI_SYSTEM_CRON and GLPI_MARKETPLACE_DIR are correctly taken into account and work.\n\nHowever, the overload of the GLPI_PLUGINS_DIR constant is indeed affected by the application but not taken into account in the array constant: GLPI_PLUGINS_DIRECTORIES.\n\nPlugins installed automatically through the Marketplace are successfully downloaded to the path defined by GLPI_MARKETPLACE_DIR and are functional, but plugins installed manually to the path defined by GLPI_PLUGINS_DIR are not taken into account.\n\nOnly plugins manually installed in the path defined by \"GLPI_ROOT /plugins\" (typically /var/www/glpi/plugins) are considered.\n\nIs this normal, or not?\n\nI am happy to provide any further information.\n\nSincerely.\n\nReproduction steps:\nThe constants are overridden by this configuration:\n\n- [ /var/www/glpi/inc/downstream.php ]\n\nAnd...\n\n- [ /etc/glpi-8081/local_define.php ]", "priority": "medium", "type": "support", "createdByEmail": "remy.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I don't see any version of GLPI that had \"GLPI_PLUGINS_DIR\" as a configurable constant. You should override \"GLPI_PLUGINS_DIRECTORIES\" instead and include both your marketplace and plugin paths in that array.\n\nOriginal response date: 2025-12-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3702694228, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22516#issuecomment-3702694228", "createdAt": "2025-12-31T18:43:14Z" } }, { "userEmail": "remy.bennett@peppermint.local", "text": "Good evening (from France) Curtis,\n\nThank you for your reply.\n\nI'll investigate why I went down the wrong path with this _ghost constant_!\n\nCould you confirm the syntax for declaring the GLPI_PLUGINS_DIRECTORIES array constant:\n\ndefine('GLPI_PLUGINS_DIRECTORIES', array('/var/lib/glpi/marketplace','/var/lib/glpi/plugins'));\n\nIt doesn't seem to be working right now.\n\nThank you in advance for your feedback, which could enrich the GLPI documentation regarding this double declaration topic.\n\nOriginal response date: 2025-12-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3702907135, "author": "homebrewtainy", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22516#issuecomment-3702907135", "createdAt": "2025-12-31T21:10:49Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "This is working for me in my local_define.php if I check Setup > General > System tab.\n\nOriginal response date: 2025-12-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3702925558, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22516#issuecomment-3702925558", "createdAt": "2025-12-31T21:29:40Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I'm not sure if it matters, but you could try clearing the GLPI cache.\nWhen you have debug mode enabled for your user, go to Setup > General > Performance tab and click \"Reset\" under the \"User data cache\" section.\n\nOriginal response date: 2025-12-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3702934281, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22516#issuecomment-3702934281", "createdAt": "2025-12-31T21:39:45Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22516, "url": "https://github.com/glpi-project/glpi/issues/22516", "author": "homebrewtainy", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-31T17:46:12Z", "updatedAt": "2026-04-11T00:42:32Z", "closedAt": "2025-12-31T18:43:14Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "npm audit failed (11.0/bugfixes)", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Linked PR is wrong, we also need to udpate the npm package.\n\nOriginal response date: 2025-12-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3659596218, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22362#issuecomment-3659596218", "createdAt": "2025-12-16T09:27:40Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I guess we will have to wait before a new version fixes this issue, see\n\nOriginal response date: 2025-12-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3660469296, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22362#issuecomment-3660469296", "createdAt": "2025-12-16T13:14:09Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "So we should maybe just close this one?\n\nOriginal response date: 2025-12-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3660825031, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22362#issuecomment-3660825031", "createdAt": "2025-12-16T14:25:26Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "So we should maybe just close this one?\n\nI guess dependabot will open a PR when a fix will be ready. Anyway, as long as this dependency will be identified as vulnerable, a new issue will be opened every monday.\n\nOriginal response date: 2025-12-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3660843962, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22362#issuecomment-3660843962", "createdAt": "2025-12-16T14:29:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22362, "url": "https://github.com/glpi-project/glpi/issues/22362", "author": "github-actions[bot]", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-15T10:03:13Z", "updatedAt": "2026-03-27T00:43:27Z", "closedAt": "2025-12-16T14:29:14Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Bug in the simplified view when viewing a closed ticket.", "detail": "Affected version:\n11.0.1\n\nIssue description:\nGood afternoon.\n\nI'm having a problem with the simplified view when trying to view a closed ticket.\n\nThe ticket layout is disorganized. I thought it was due to the CSS customization I had applied to the entity, but the problem persists even without the CSS customization.\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "cameron.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nPlease try to upgrade to GLPI 11.0.4 to see if the problem persists.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3638102650, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22332#issuecomment-3638102650", "createdAt": "2025-12-10T17:07:28Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I don't reproduce on the lastest version.\n\nPlease note that it might also be caused by a plugin.\n\nOriginal response date: 2025-12-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3641051473, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22332#issuecomment-3641051473", "createdAt": "2025-12-11T09:32:48Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "Good morning.\n\nWe updated to version 11.0.4, and the layout error persists.\n\nOriginal response date: 2025-12-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3641648263, "author": "VinnyOF1912", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22332#issuecomment-3641648263", "createdAt": "2025-12-11T12:15:45Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "Even after disabling all plugins, the error persists, and strangely, it only happens with 'Closed' tickets; 'Solved' tickets are fine.\n\nI've already removed the CSS customization I had placed on the Entity, and the error still occurs.\n\nOriginal response date: 2025-12-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3641668116, "author": "VinnyOF1912", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22332#issuecomment-3641668116", "createdAt": "2025-12-11T12:21:07Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22332, "url": "https://github.com/glpi-project/glpi/issues/22332", "author": "VinnyOF1912", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-10T16:56:44Z", "updatedAt": "2026-03-22T00:41:34Z", "closedAt": "2025-12-11T15:10:03Z" } }, { "title": "It is not possible to change what is assigned to the ticket.", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWith the ticket created, when I try to change the assigned technician, it doesn't delete the ticket; I can only add another technician.\n\na video demonstrating the problem\n\nReproduction steps:\ngo to ticket\ntry change assigend to", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "casey.blair@peppermint.local", "text": "Also, on the same ticket screen, it's not possible to change the requester.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3596739817, "author": "RuanBojarski", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22142#issuecomment-3596739817", "createdAt": "2025-12-01T14:08:17Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Please test with plugins disabled.\nAlso, please include the requested log and GLPI setup information.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3596807185, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22142#issuecomment-3596807185", "createdAt": "2025-12-01T14:22:30Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "I tested it with the plugins disabled, and it worked as it should. After that, I disabled and enabled them, and discovered that the additional fields were what caused the problem.\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3597067986, "author": "RuanBojarski", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22142#issuecomment-3597067986", "createdAt": "2025-12-01T15:07:43Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "What can I do to solve this?\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3597086663, "author": "RuanBojarski", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22142#issuecomment-3597086663", "createdAt": "2025-12-01T15:11:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22142, "url": "https://github.com/glpi-project/glpi/issues/22142", "author": "RuanBojarski", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-01T13:57:08Z", "updatedAt": "2026-03-14T00:37:10Z", "closedAt": "2025-12-03T11:54:30Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI 11 - Error when assigning items to a ticket", "detail": "Affected version:\n11\n\nIssue description:\nWhen trying to assign a item with a ticket, I get the message \"Results cant be loaded\"\nInvestigating the log file I get this error\n\n[2025-11-17 10:32:10] glpi.CRITICAL: * Uncaught PHP Exception RuntimeException: \"MySQL query error: Unknown column 'groups_id' in 'WHERE' (1054) in SQL query \"SELECT * FROM glpi_computers WHERE groups_id IN ('38') AND ((glpi_computers.entities_id = '0' OR (glpi_computers.is_recursive = '1' AND glpi_computers.entities_id IN ('0')))) AND is_deleted = '0' AND is_template = '0' ORDER BY name\".\" at DBmysql.php line 371\n Backtrace :\n ./src/DBmysql.php:371\n ./src/DBmysqlIterator.php:123 DBmysql->doQuery()\n ./src/DBmysql.php:1040 DBmysqlIterator->execute()\n ./src/Dropdown.php:4312 DBmysql->request()\n ./ajax/getDropdownMyDevices.php:42 Dropdown::getDropdownMyDevices()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\nThe column groups_id doesn't exist in glpi_computers table\n\nReproduction steps:\n1. Open a ticket\n2. got to Items\n3. Try to add an item assigned with requester", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "harper.blair@peppermint.local", "text": "Quick update,\nI've discovered that if user is present on a group the devices do not appear, if user is in a group devices do not appear...\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3541694937, "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21953#issuecomment-3541694937", "createdAt": "2025-11-17T12:54:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I cannot reproduce the issue on current 11.0/bugfixes branch. Try with a nightly build if you reproduce.\n\nif user is present on a group the devices do not appear, if user is in a group devices do not appear...\n\nSorry, I do not understand.\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3551588049, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21953#issuecomment-3551588049", "createdAt": "2025-11-19T09:05:35Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "I'll try to explain and I've narrow it down to the option:\nIf the Profiles -> Assistance - See hardware of my groups is selected you can only add an item if you are on the same group than the requester, if not the requester items do not appear.\n\nIf I disable that option all works well\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3551696544, "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21953#issuecomment-3551696544", "createdAt": "2025-11-19T09:26:26Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "#21983 may fix your issue. I did not take time to test it for the moment.\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3551716987, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21953#issuecomment-3551716987", "createdAt": "2025-11-19T09:30:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21953, "url": "https://github.com/glpi-project/glpi/issues/21953", "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-17T10:38:01Z", "updatedAt": "2026-03-13T00:38:25Z", "closedAt": "2025-12-02T09:56:56Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Ethernet Port Connection Error: “The results could not be loaded” internal server error", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen I try to connect an Ethernet port to another network device, the message \"The results could not be loaded\" appears.\n\nHowever, if I click on the information icon (\"i\"), the correct list is displayed.\n\nI checked the error logs, and they show the following:\n[Image omitted]\n\nReproduction steps:\n1. Go to a device with ethernet ports (for exemple a switch)\n2. Go to ethernet ports and open one\n3. Try to connect a device\n\nAdditional context:\nGlpiInfo.txt", "priority": "medium", "type": "support", "createdByEmail": "robin.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide GLPI logs.\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3584752940, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22084#issuecomment-3584752940", "createdAt": "2025-11-27T08:42:44Z" } }, { "userEmail": "logan.blair@peppermint.local", "text": "I have same error: php-errors.log gives this error:\n\n [2025-11-27 16:51:50] glpi.CRITICAL: * Uncaught PHP Exception Error: \"Cannot use object of type Glpi\\DBAL\\QuerySubQuery as array\" at Dropdown.php line 2964\n Backtrace :\n ./src/Dropdown.php:2964\n ./ajax/getDropdownValue.php:48 Dropdown::getDropdownValue()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3586387960, "author": "indrekteppan", "anonymizedAuthorEmail": "logan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22084#issuecomment-3586387960", "createdAt": "2025-11-27T15:13:15Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This issue already has been fixed. Try with nightly build; it will be part of 11.0.3 release next week.\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3586420459, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22084#issuecomment-3586420459", "createdAt": "2025-11-27T15:20:22Z" } }, { "userEmail": "remy.bennett@peppermint.local", "text": "Skyler Adler can you provide the link to the patch?\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3586457849, "author": "tizianosartori", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22084#issuecomment-3586457849", "createdAt": "2025-11-27T15:29:36Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22084, "url": "https://github.com/glpi-project/glpi/issues/22084", "author": "Gabri374", "anonymizedAuthorEmail": "robin.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-11-27T08:29:55Z", "updatedAt": "2026-03-08T00:39:29Z", "closedAt": "2025-11-27T15:20:22Z" } }, { "title": "SQL “Out of range value” error when a dictionary rule assigns an empty", "detail": "Affected version:\n11.0.0\n\nIssue description:\nOn GLPI v11, I get a MySQL error when a dictionary rule under Edition uses the Assign action but no edition is selected (empty). This error completely blocks ESX / VM inventory imports (VMs + OS detection).\nIn v10, the same rule did not cause this error — the inventory worked fine.\n\n[error] [http client] server error: MySQL query error: Out of range value for column 'operatingsystemeditions_id' at row 1 (1264) in SQL query \"UPDATE glpi_items_operatingsystems SET operatingsystemeditions_id = '-1', date_mod = '2025‑10‑09 10:18:57' WHERE id = '52675'\".\n\nIt appears that GLPI is trying to set operatingsystemeditions_id = -1 when no edition is chosen, which is outside the permitted range, leading to failure. Because this happens during the inventory process, the entire ESX/VM import is halted.\n\nReproduction steps:\n1. Go to Administration > Dictionaries > Edition\n2. Add or edit a rule\n3. Create criteria\n4. In Action, select Assign\n5. Leave the assigned value empty (i.e. no edition chosen)\n6. Trigger an ESX inventory import (VMs + OS detection)\n7. The database update with operatingsystemeditions_id = -1 is attempted → error on glpi-agent", "priority": "medium", "type": "maintenance", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I've not checked if I can reproduce, but I doubt this is a specific v11 issue; it should already exists on v10.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3384949720, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21379#issuecomment-3384949720", "createdAt": "2025-10-09T09:21:13Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "I didn't have this problem with v10. I import +993 VMs this way.\n\nIn detail, for example, the edition reported is generally 32 or 64. I don't want it to import this; it's reported by the agent installed on the machines.\n\nThere's definitely something wrong with it importing because of this. My latest inventory dates aren't incrementing in any case.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3384983463, "author": "PorteBannana", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21379#issuecomment-3384983463", "createdAt": "2025-10-09T09:30:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I didn't have this problem with v10. I import +993 VMs this way.\n\nHum... OK, thanks for the feedback.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3385633726, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21379#issuecomment-3385633726", "createdAt": "2025-10-09T12:26:21Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "Edit: When I disable the “Create computer for virtual machine” option in the inventory settings, my VMs are no longer inventoried, but at least my ESXi hosts continue to function correctly.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3424637215, "author": "PorteBannana", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21379#issuecomment-3424637215", "createdAt": "2025-10-21T04:35:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21379, "url": "https://github.com/glpi-project/glpi/issues/21379", "author": "PorteBannana", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [ "inventory" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-09T08:34:20Z", "updatedAt": "2026-02-26T00:37:10Z", "closedAt": "2025-11-17T07:09:22Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Fatal error when ini_set is restricted", "detail": "Affected version:\n11.0.0\n\nIssue description:\nException when trying to import an xml report from the web interface.\n\nReproduction steps:\n1. Migration from GLPI 10.0.20 with database upgrade\n2. Activation of glpiinventory 1.6.0\n3. Generate a report from a server Debian 12.0 (bookworm) with GLPI-Agent 1.15-1 (all.deb)\n4. Administration -> GLPI Inventory -> Task -> Import File (xml format)", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce issue uploading an invnetory file using web UI.\n\nAlso, the indicated line in Request.php does not correspond in 11.0 files. Make sure all files have been correctly uploaded.\n\nIf you can reproduce on a new 11.0 instance, we'll need an inventory file example to reproduce on our side.\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3382307860, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21357#issuecomment-3382307860", "createdAt": "2025-10-08T16:18:37Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Hello,\n\nI upgraded the Debian to Trixie and using now php8.4.\nI tried versions 11.0.0, 11.0.1 and 11.0.2 of GLPI, the problem persists.\n\nI added some echo in php code to isolate, the problem is related to the call of \"use function Safe\\ini_set;\"\n\nFor example, I had to comment this in \"front/css.php\" (line 41) to correct the display or the default theme aura is broken.\n\nFor inventory import to works, I had to comment lines of code in \"src/Glpi/Agent/Communication/AbstractRequest.php\" because of the use of ini_set (line 300) for memory_limit.\n\nDo you have an idea why this call doesn't work anymore when upgrading to GLPI 11 ?\nPlease do not close until the problem is identified.\n\nBest regards.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3522536481, "author": "CyrilVanErsche", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21357#issuecomment-3522536481", "createdAt": "2025-11-12T15:30:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Issues are close when non reproducible and when there is no feedback.\n\nThe real issue is far from the one reported; and is due to restrictions on using ini_set on your side - and does affect much more than the inventory.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3525689087, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21357#issuecomment-3525689087", "createdAt": "2025-11-13T06:17:48Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Micah Bennett\n\nDo you have some php_admin_value directive in your apache/nginx configuration to the memory_limit configuration value ? In this case, you could try to replace it by a php_value directive, that would allow GLPI to override it where it is required.\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3526528835, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21357#issuecomment-3526528835", "createdAt": "2025-11-13T08:50:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21357, "url": "https://github.com/glpi-project/glpi/issues/21357", "author": "CyrilVanErsche", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-08T14:45:44Z", "updatedAt": "2026-02-26T00:37:04Z", "closedAt": "2025-11-17T09:25:51Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "API v2 doesn't work with certain user", "detail": "Affected version:\nGLPI 11.0.2\n\nIssue description:\nI’m using Postman to test GLPI’s v2 APIs. I’m trying to log in with a local user, password, client_id, and client_secret, but the login doesn’t work when I use a local user with superadmin rights. However, it works with an LDAP user. What’s strange is that if I disable the LDAP user, the API request still works and returns the access_token. I thought there might be an issue with local users, so I created a specific LDAP user called \"api-glpi\", but that also doesn’t work. What’s the logic behind why some users work and others don’t?\n\nAffected page:\n\nReproduction steps:\nuse postman\nuse the link below", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Why are the OAuth parameters in the query string?\nTry POST /api.php/token and put the parameters in the request body as JSON.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521259570, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21894#issuecomment-3521259570", "createdAt": "2025-11-12T10:39:44Z" } }, { "userEmail": "taylor.bennett@peppermint.local", "text": "Because it was the first attempt I had made, and it worked with my user account.\n\n[Image omitted]\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521310447, "author": "trisosamu", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21894#issuecomment-3521310447", "createdAt": "2025-11-12T10:50:34Z" } }, { "userEmail": "taylor.bennett@peppermint.local", "text": "I tried as you said, and it works with the other user as well. I guess it’s a password issue at this point. Putting it in the connection string might cause problems.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521341558, "author": "trisosamu", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21894#issuecomment-3521341558", "createdAt": "2025-11-12T10:57:35Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Because it was the first attempt I had made, and it worked with my user account.\n\nThe new API is very permissive, maybe too permissive, about where data comes from, but as a note it is not a good idea to send sensitive information as part of the URL because it could be logged.\n\nTry using the request body with both users. If it works, I would guess that one of the passwords just has a special character that needs URL encoded when used in the URL.\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3521344708, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21894#issuecomment-3521344708", "createdAt": "2025-11-12T10:58:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21894, "url": "https://github.com/glpi-project/glpi/issues/21894", "author": "trisosamu", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-12T10:24:54Z", "updatedAt": "2026-02-21T00:37:15Z", "closedAt": "2025-11-12T10:57:35Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Ticket is automatically set to \"Processing (assigned)\" when created from self-service portal", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHey there,\n\nSince updating to GLPI 11, it seems like tickets created from the self-service page are automatically set to the \"Processing (assigned)\" state, even though no technician has assigned the ticket to themselves.\n\nIs this a bug or a feature? ^^\n\nEDIT: it seems like this is only happening when the user is using the root entity to create the ticket. When using children entities, it works. I tried looking for rules but couldn't find anything interesting.\n\nThanks a lot for your help.", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.bennett@peppermint.local", "text": "Okay, it seems that the problem comes from the ticket template that the root entity uses, which is different from the one that the other entities use. That being said, I've compared both templates (the root entity uses the Default one, the other entities use a custom one), but they are practically the same. What could it be?\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3512299652, "author": "ayygurl", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21871#issuecomment-3512299652", "createdAt": "2025-11-10T15:14:41Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Do you have any plugins enabled? Are there any Business Rules for Tickets that may set the status of the ticket?\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3512791314, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21871#issuecomment-3512791314", "createdAt": "2025-11-10T16:48:17Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "If it’s using the default template, you need to remove the status from the predefined fields in the template. But beyond that, you should also check if there’s any rule assigning a technician, group, or even a rule that’s setting the status to “in progress” when the ticket is created. Keep in mind that “in progress” is the status GLPI sets when a technician or group is linked to the ticket, but this could be getting forced through a template, rule, form target, etc.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3512931645, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21871#issuecomment-3512931645", "createdAt": "2025-11-10T17:10:17Z" } }, { "userEmail": "taylor.bennett@peppermint.local", "text": "Bypassed all my plugins -> didn't change anything\nAs for the business rules, we only have rules that change the observers or observer groups.\n\nThat being said, I removed the \"group of technicians\" field from the predefined fields in the default template, and now the template is working as intended. The reason I didn't think about trying that earlier, is because this field is also in my other template, and that template works as intended.\n\nOut of curiosity, I added the \"groupe of technicians\" field back in the default template, and now even with that, the template still works as intended. I'm guessing this was a weird bug.\n\nThank you very much for your help!\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3512999250, "author": "ayygurl", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21871#issuecomment-3512999250", "createdAt": "2025-11-10T17:23:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21871, "url": "https://github.com/glpi-project/glpi/issues/21871", "author": "ayygurl", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-10T10:39:38Z", "updatedAt": "2026-02-19T00:40:33Z", "closedAt": "2025-11-10T17:23:03Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Glpi11 doesn't display MiniDashboard", "detail": "Affected version:\n11.0.1\n\nIssue description:\nProfile except super-admin doesn't display mini dashboard on the top of the ticket list.\nis it a bug?\n\nOption:\n[Image omitted]\n\nprofile: fself-service\n[Image omitted]\n\nprofile: Super-admin\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Not a bug. Only standard interface profiles can view dashboards.\nSee #13248\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3469298515, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21703#issuecomment-3469298515", "createdAt": "2025-10-30T17:48:29Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "As you can see, it is standard interface but not Simplified interface\n\n[Image omitted]\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3470882783, "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21703#issuecomment-3470882783", "createdAt": "2025-10-31T00:58:20Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "anything update?\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3478668155, "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21703#issuecomment-3478668155", "createdAt": "2025-11-03T01:52:42Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "Not a bug. Only standard interface profiles can view dashboards. See #13248\n\nCan you check the screenshot?\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3478668500, "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21703#issuecomment-3478668500", "createdAt": "2025-11-03T01:53:07Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21703, "url": "https://github.com/glpi-project/glpi/issues/21703", "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-30T01:42:15Z", "updatedAt": "2026-02-15T00:42:03Z", "closedAt": "2025-10-30T17:48:29Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Parse date in MailCollector GLPI 11.0.1", "detail": "Affected version:\nGLPI 11.0.1 Copyright (C) 2015-2025 Teclib' and contributors\n\n🐛 Erro ao processar cabeçalho de e-mail com fuso horário duplicado / Error when processing email\n\n[Content truncated.]:\nVersão / Version: GLPI 11.0.1 Copyright (C) 2015-2025 Teclib' and contributors\nArquivo / File: src/MailCollector.php\nLinha aproximada / Approx. line: 1364\nFunção / Function: MailCollector->getHeaders()\nTipo de problema / Label suggestion: bug, mailgate, datetime\n\n---\n\n🇬🇧 Description (English):\nWhen running mail collection (cronMailgate), GLPI throws:\n\nThis happens when the Date: header contains two timezone definitions, for example:\n\nThe PHP strtotime() function (used by Safe\\strtotime()) cannot parse this format and fails, stopping the entire mail collection.\n\n🧩 Root Cause:\nThe extra (GMT-04:00) at the end of the header creates ambiguity in timezone parsing, resulting in an invalid date.\n\n✅ Suggested Fix:\nClean the header before parsing:\n\nThis prevents exceptions and ensures mail collection continues smoothly even with redundant timezone annotations.\n\n---\n\n🧾 Example comparison:\n| Header | Result | Notes |\n|--------|--------|-------|\n| Date: Wed, 22 Oct 2025 17:19:22 +0000 | ✅ Works | Standard RFC 2822 format |\n| Date: Wed, 22 Oct 2025 11:44:56 -0400 (GMT-04:00) | ❌ Fails | Duplicated timezone |\n\n---\n\n💡 Additional note:\nA simple patch in MailCollector.php prevents the error and logs invalid headers for later analysis without breaking the mail collection process.\n\n---", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Which email client is sending these invalid headers?\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3433858272, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21610#issuecomment-3433858272", "createdAt": "2025-10-22T19:12:31Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "I don't know which email client is sending these invalid headers. However,\nI'm receiving these emails in my inbox and have run several tests to\nidentify the issue.\n\nAfter a *detailed analysis of the email headers*, it was determined that\nthe message *was not sent by a human client* (such as Outlook, Thunderbird,\nGmail, or Roundcube),\nbut rather by an *automated government system* known as *SDP* (*Digital\nProtocol/Service System*), using the following infrastructure:\n\n -\n\n *SMTP Server:* smtpsistema.[internal-domain]\n -\n\n *Mail Agent:* Postfix\n -\n\n *Mail Library (likely):* JavaMail\n -\n\n *Delivery Gateway:* webmail.[internal-domain] (using *amavis* +\n *OpenDKIM* for filtering and authentication)\n\nIn summary, the message was *automatically generated by an internal\ncorporate system*, not by a conventional email client.\n\nThanks,\nJober\n\nEm qua., 22 de out. de 2025 às 15:12, Curtis Conard <\n*@*.*> escreveu:\n\n*cconard96* left a comment (glpi-project/glpi#21610)\n\nWhich email client is sending these invalid headers?\n—\nReply to this email directly, view it on GitHub\n,\nor unsubscribe\n\n.\nYou are receiving this because you authored the thread.Message ID:\n*@*.*>\n\n--\nAtenciosamente\n\n*Jober Cavalcante*\nDesenvolvedor de sistemas\n+55 67 98401-2248\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3433886110, "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21610#issuecomment-3433886110", "createdAt": "2025-10-22T19:20:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide an EML file that can be added to tests suite.\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3435530197, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21610#issuecomment-3435530197", "createdAt": "2025-10-23T07:29:35Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "I can’t share the full .eml file because it contains sensitive data, but\nhere’s the email header with all sensitive information removed:\n\n2025-10-22 13:29:50 *@*.*\nReturn-Path:\nReceived: from IP_REDACTED (LHLO DOMAIN_REDACTED) (IP_REDACTED) by\nmbox4.DOMAIN_REDACTED with LMTP; Wed, 22 Oct 2025 11:48:03 -0400 (AMT)\nReceived: from DOMAIN_REDACTED (localhost [127.0.0.1]) by DOMAIN_REDACTED\n(Postfix) with ESMTPS id REDACTED; Wed, 22 Oct 2025 11:47:17 -0400 (-04)\nReceived: from localhost (localhost [127.0.0.1]) by DOMAIN_REDACTED\n(Postfix) with ESMTP id REDACTED; Wed, 22 Oct 2025 11:47:17 -0400 (-04)\nAuthentication-Results: DOMAIN_REDACTED (amavis); dkim=pass (KEY_REDACTED)\n header.d=DOMAIN_REDACTED\nReceived: from DOMAIN_REDACTED ([127.0.0.1]) by localhost (DOMAIN_REDACTED\n[127.0.0.1]) (amavis, port 10026) with ESMTP id REDACTED; Wed, 22 Oct 2025\n11:47:17 -0400 (-04)\nReceived: from HOST_REDACTED (HOST_REDACTED [IP_REDACTED]) by\nDOMAIN_REDACTED (Postfix) with ESMTPS id REDACTED; Wed, 22 Oct 2025\n11:47:17 -0400 (-04)\nReceived: from HOST_REDACTED (HOST_REDACTED [IP_REDACTED]) by HOST_REDACTED\n(Postfix) with ESMTPSA id REDACTED; Wed, 22 Oct 2025 11:44:56 -0400 (-04)\nDKIM-Filter: OpenDKIM Filter vX.XX.XX HOST_REDACTED REDACTED\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=DOMAIN_REDACTED;\ns=default;\n t=TIMESTAMP_REDACTED; bh=HASH_REDACTED;\n h=Date:From:To:In-Reply-To:Subject:From;\n b=SIGNATURE_REDACTED\nDate: Wed, 22 Oct 2025 11:44:56 -0400 (GMT-04:00)\nFrom: \"SENDER_NAME_REDACTED\"\nTo: EMAIL_REDACTED, EMAIL_REDACTED\nMessage-ID: *@*.*_REDACTED>\nIn-Reply-To: *@*.*_REDACTED>\nSubject: SUBJECT_REDACTED\nMIME-Version: 1.0\nContent-Type: multipart/mixed;\n boundary=\"----=_Part_REDACTED\"\nSdp-System-Mail: yes\nSdp-Instance-Id: INSTANCE_ID_REDACTED\n\nEm qui., 23 de out. de 2025 às 03:29, Johan Cwiklinski <\n*@*.*> escreveu:\n\n*trasher* left a comment (glpi-project/glpi#21610)\n\nPlease provide an EML file that can be added to tests suite.\n—\nReply to this email directly, view it on GitHub\n,\nor unsubscribe\n\n.\nYou are receiving this because you authored the thread.Message ID:\n*@*.*>\n\n--\nAtenciosamente\n\n*Jober Cavalcante*\nDesenvolvedor de sistemas\n+55 67 98401-2248\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3437249386, "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21610#issuecomment-3437249386", "createdAt": "2025-10-23T14:11:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21610, "url": "https://github.com/glpi-project/glpi/issues/21610", "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [ "mail collector" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-22T17:56:45Z", "updatedAt": "2026-02-07T00:37:44Z", "closedAt": "2025-10-29T08:22:28Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "[UI] question/remark about the tooltip styles", "detail": "Affected version:\n11.0.0\n\nIssue description:\nHello,\n\nI have a question about the tooltip styles. I have a computer with big cursors for accessibility purpose.\n\nOn some pages, I can see the tooltip like this :\n\nand it can't see them on some pages :\n\nWhy the style is not consistent on all the pages ?\n\n(tested on diffrent browsers and OS)", "priority": "medium", "type": "support", "createdByEmail": "finley.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "In facts, there is a third one:\n\n[Image omitted]\n\nThe second tooltip (on followup creation date) is just a browser default tooltip - while the first one is a \"real\" tooltip from our UI framework.\n\nIndeed, this should be more consistent.\n\nOriginal response date: 2025-10-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3365414416, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21273#issuecomment-3365414416", "createdAt": "2025-10-03T11:58:19Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "In facts (after I've checked on my instanxe) in your screenshot, both are \"bootstrap tooltips\" (what's expected). But that does not change the problem ;)\n\nOriginal response date: 2025-10-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3365745785, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21273#issuecomment-3365745785", "createdAt": "2025-10-03T13:46:26Z" } }, { "userEmail": "finley.blair@peppermint.local", "text": "ok, I'll TRY to change the behaviors in front files if it's not too hard and nobody from the team will work on this. I'll make a PR if I can do the changes\n\nOriginal response date: 2025-10-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3365963448, "author": "vboucard", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21273#issuecomment-3365963448", "createdAt": "2025-10-03T14:38:09Z" } }, { "userEmail": "finley.blair@peppermint.local", "text": "I think I was a little too optimistic 👉👈\n\nthe codebase is huge ! .... i don't have time to do it...\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3375490419, "author": "vboucard", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21273#issuecomment-3375490419", "createdAt": "2025-10-07T07:06:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21273, "url": "https://github.com/glpi-project/glpi/issues/21273", "author": "vboucard", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-03T11:25:27Z", "updatedAt": "2026-02-06T00:37:10Z", "closedAt": "2025-10-28T07:58:29Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Inventory Stacked Cisco Switch", "detail": "GLPI Version:\n11.0.1\n\nPlugin version:\n1.6.0\n\nIssue description:\nHello,\n\nI created my switches in network devices and I added a network port to set an ip address for thoses switch.\nI set the correct community on SNMP credentials\n\nI installed an agent version 1.15 on glpi server that can access to the switch.\n\nI set all necessary configuration in glpi inventory plugin to run network inventory (SNMP) on my switches.\n\nWhen the switches are alone (single switch not stacked), everything run smooth with GLPI inventory plugin.\nThey are populated correctly.\nWhen they are stacked (2 or more switches being accessed through the same IP), the agent can see the switch, can query it but is not updating it.\nThe log of the agent launch me an error during the netinventory :\n[http client] communication error: 500 Internal Server Error, Safe\\preg_match(): Argument glpi-project/glpi-inventory-plugin#2 ($subject) must be of type string, null given, called in /var/www/glpi/src/Glpi/Inventory/Asset/NetworkPort.php on line 834\n\nI tried to fresh install the latest version of GLPI and inventory plugin without any customization and I got the same error.\n\nI add the php-error.log to the ticket.\n\nThank you.\n\nRegards,", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide correct log trace.\n\nAgent returns Error, Safe\\preg_match(): Argument ($subject) must be of type string, null given; and provided log is about Undefined property: stdClass::$name at NetworkPort.php - not the same.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409936878, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21516#issuecomment-3409936878", "createdAt": "2025-10-16T05:22:35Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Also, please provide an inventory file we can use to reproduce\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409936886, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21516#issuecomment-3409936886", "createdAt": "2025-10-16T05:23:26Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "Hello, I attached you all the required files.\nTell me if you need anything else\n\nglpi-agent.log\nphp-error.log\nswitch.xml\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409936905, "author": "ChandlerBing82", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21516#issuecomment-3409936905", "createdAt": "2025-10-16T08:38:13Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Your XML file contains one (at least) port without any information:\n\nThis one cause an issue; which probably exists from a while.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409936919, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21516#issuecomment-3409936919", "createdAt": "2025-10-16T09:08:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21516, "url": "https://github.com/glpi-project/glpi/issues/21516", "author": "ChandlerBing82", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-15T14:33:54Z", "updatedAt": "2026-02-06T00:36:55Z", "closedAt": "2025-10-28T09:23:11Z" } }, { "title": "GLPI 11 - Forms allow selecting unauthorized actors for the action", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHi, we tried without plugins and found that some issues were resolved. However, we still have others.\n\nWhen we add the authors field, the option to insert items that are not classified for a ticket is displayed. Consequently, when opening a ticket, the error appears:\n\n[Image omitted]\n\n[Image omitted]\n\nAgain I say that it would be interesting to have the option to select only groups as authors, or to allow the group type field to be linked in the call", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.blair@peppermint.local", "text": "GLPI 11.0.1\nHello Devon Bennett .\nIn my case, no group is enabled to be a requester on a ticket. To test if what you report also happens to me, I have tried to select a group as a requester on a new or ongoing ticket, and no group appears to select as a requester. Only Users.\n\nCreating a form and using the requesting actor variable, when testing it allows selecting requesting users and groups regardless of the group configuration. It is a bug.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3402231131, "author": "willysaurio", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21480#issuecomment-3402231131", "createdAt": "2025-10-14T14:45:02Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "Hi Willy, groups are usually at the bottom of the list. I don't know if there are any other restrictions that need to be applied.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3402278528, "author": "afpes", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21480#issuecomment-3402278528", "createdAt": "2025-10-14T14:54:09Z" } }, { "userEmail": "micah.blair@peppermint.local", "text": "Hi Willy, groups are usually at the bottom of the list. I don't know if there are any other restrictions that need to be applied.\n\nMy initial test was with creating or modifying a simple ticket. Then I realized that your image was of a form.\nFrom the form, it should not be possible to select a group that has a NO configured as the requester.\nIn my opinion, it is a form error to allow groups that are not authorized as applicants to be selected.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3402321360, "author": "willysaurio", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21480#issuecomment-3402321360", "createdAt": "2025-10-14T15:04:41Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "Exactly.\n\nIn my case, I like to link tickets to groups so I can then see which groups have the most issues. A single user can represent more than one group, which is why we use it this way.\n\nI even suggested creating a group-specific field to link to the ticket, as was the case in the old forms plugin before GLPI version 11.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3402363690, "author": "afpes", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21480#issuecomment-3402363690", "createdAt": "2025-10-14T15:13:16Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21480, "url": "https://github.com/glpi-project/glpi/issues/21480", "author": "afpes", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-14T13:12:47Z", "updatedAt": "2026-02-05T00:39:44Z", "closedAt": "2025-10-27T15:45:11Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "Import of dictionaries", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWhen importing the xml file of dictionaries for partners' only, I got a crash at first, then tried again several times, it succeeded but stopped by 112, when I dot it on a 10th version, I obtain 130 issues.\nPlus, there is a display bug of the amount showing :\nWe should be able to see in a glance the total amount as follows (10th version)\n\n[Image omitted]\nwhereas, we now see the total amount shown per display table\n\n[Image omitted]\n\nEnvironment details:\n11.0.1 linux", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I'm looking into the list UI part.\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3389349140, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21403#issuecomment-3389349140", "createdAt": "2025-10-10T10:53:10Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Hello, the pagination issue has been fixed in #21406.\n\nFor the xml with the import errors, could you provide us the file here or on the GLPI support.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400662382, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21403#issuecomment-3400662382", "createdAt": "2025-10-14T08:19:57Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Alright then, I'll pass it trhough glpi support as it is a file only for partner's you provided us a while ago\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400744706, "author": "agnesmorin-itgouv", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21403#issuecomment-3400744706", "createdAt": "2025-10-14T08:41:17Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Hello Drew Bennett, I played the import multiple time and I didn't get any errors.\nThe pagination issue has been fixed and should be available in next glpi release.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3406296403, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21403#issuecomment-3406296403", "createdAt": "2025-10-15T12:54:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21403, "url": "https://github.com/glpi-project/glpi/issues/21403", "author": "agnesmorin-itgouv", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-10T08:57:49Z", "updatedAt": "2026-01-29T00:37:10Z", "closedAt": "2025-10-14T12:58:33Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Cannot authenticate with API", "detail": "Affected version:\nGLPI 11.0.2-dev\n\nIssue description:\nWhen I try to authenticate against the API using the password flow I get an HTTP500 internal server error.\n\nReproduction steps:\n1. Enable the new API.\n2. Create an OAUTH client using the Password flow with scope api.\n3. Navigate to the API endpoints swagger page.\n4. Click on Authorize\n5. Fill in the form using the client id, client secret and scopes configured in step 2. User and password is glpi and glpi respectively (default un/pw from fresh installation).\n6. Click 'Authorize'\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide logs.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401750133, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21479#issuecomment-3401750133", "createdAt": "2025-10-14T13:14:26Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "I cleared all logs before trying to authenticate. This is the full php-errors.log after trying to authenticate as per this issue:\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401789895, "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21479#issuecomment-3401789895", "createdAt": "2025-10-14T13:19:34Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "I forgot to mention I have a C# client app that authenticates against the API. It worked against version 11.0.0 but now fails with the same exception. The issues started with version 11.0.1.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401819948, "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21479#issuecomment-3401819948", "createdAt": "2025-10-14T13:23:10Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "1. Make sure the oauth key files were generated in the config folder. Should be an oauth.pem and oauth.pub.\n2. There is a known issue with several copyable fields where they don't function properly when viewing/copying. When trying to copy the client secret, you may not actually be copying the right value (or anything potentially).\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401822435, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21479#issuecomment-3401822435", "createdAt": "2025-10-14T13:23:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21479, "url": "https://github.com/glpi-project/glpi/issues/21479", "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-14T13:10:58Z", "updatedAt": "2026-01-23T00:33:03Z", "closedAt": "2025-10-14T13:33:56Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "#[DisableCsrfChecks()] no longer works", "detail": "Affected version:\n11.0.1\n\nIssue description:\nIm trying to adopt the samlsso (glpisaml) plugin to the latest version of GLPI. While working with the GLPI11 beta release i was able tot disable the Csrf checking by adding the decorator: #[DisableCsrfChecks()] in the plugins controller. The code looks like:\n\nWith the glpi11 release this isnt working anymore. The csrf check is applied on external IdP SamlResponses resulting in an not allowed error.\n\nI noticed GLPI uses the 'security_level: 0' param in its own routes but this doesnt seem to be implemented via the Symphony Route Attribute that the plugin uses.\n\nLong story short, what would be the current 'correct' way to disable CsrfChecks on a specific plugin routes?\n\nThanks in advance.\n\nReproduction steps:\nCode snippet results in CsrfCheck failed error on plugin endpoint.\n\nEnvironment details:\nGlpi 11.0.1 running in Ubuntu, Apache2, PHP8.4-Fpm,Mysql.\n\nAdditional context:\nHeaders are shown on top of plugin screens in the GLPI UI:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "While working with the GLPI11 beta release i was able tot disable the Csrf checking by adding the decorator: #[DisableCsrfChecks()] in the plugins controller\n\nThe attribute was removed because it is no longer needed. It seems to me that stateless endpoints, which don't use a session, should automatically skip CSRF checking now and plugins can register stateless URLs (See #20189).\n\nI noticed GLPI uses the 'security_level: 0' param in its own routes\n\nAre you talking about the HL API routes? This was the only place I saw that uses this parameter in a route attribute. The High-Level API does not use Symfony, but rather a custom routing solution. I did the HL API code before the work started on using Symfony routing for regular GLPI code and although I evaluating using Symfony for this case I did not believe it would be the right solution at the time.\n\nHeaders are shown on top of plugin screens in the GLPI UI\n\nI haven't seen this.\n\nOriginal response date: 2025-10-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3394273673, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21414#issuecomment-3394273673", "createdAt": "2025-10-12T12:09:00Z" } }, { "userEmail": "taylor.bennett@peppermint.local", "text": "Taylor Adler thanks for eachting out during your precious weekend :)\n\nThe presented solution...\n\nshould be added to the setup.php or hook.php?\n\nI know that (because i allready tested it) calling SessionManager::registerPluginStatelessPath(PLUGIN_NAME, '#^/front/acs/#'); from setup.php > function plugin_init_samlsso() : void doesnt work. Presumably because its called after setting up the session.\n\nMaybe, given the function name 'plugin_name_expl()' it seems it belongs in the hook.php as functions in the setup.php all have the plugin name in the end of the function names. xD Ill start in hook.php.\n\nOriginal response date: 2025-10-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3394327572, "author": "DonutsNL", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21414#issuecomment-3394327572", "createdAt": "2025-10-12T12:40:25Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "should be added to the setup.php or hook.php?\n\nI have no idea. Probably hook.php.\n\nOriginal response date: 2025-10-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3394361635, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21414#issuecomment-3394361635", "createdAt": "2025-10-12T12:59:42Z" } }, { "userEmail": "taylor.bennett@peppermint.local", "text": "The added function in hook.php is ignored. Adding the boot function to setup.php is being called and causes the following exception.\n\nIf i comment the new lines out from the setup.php I get the expected not allowed csrf error.\n\nOriginal response date: 2025-10-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3394374448, "author": "DonutsNL", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21414#issuecomment-3394374448", "createdAt": "2025-10-12T13:06:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21414, "url": "https://github.com/glpi-project/glpi/issues/21414", "author": "DonutsNL", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-10T14:18:04Z", "updatedAt": "2026-01-22T00:35:02Z", "closedAt": "2025-10-13T05:57:19Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Add specific users as observer in forms", "detail": "Affected version:\n11\n\nIssue description:\nHi all,\nWe recently updated to GLPI 11 and we wait it specificaly for forms.\nI created different forms, accessible to all users but I can't add a specific actor for the destination in the observer field.\nThe user list is missing more than 90% of our users and the search function seems to not work.\nUsers are imported from LDAP, it list only a few of them.\nSeems not to be linked to entity, because the users that are shown are in different entities and some of them are in the root entity.", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you check if it is fixed by #21322 ?\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3376922021, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21326#issuecomment-3376922021", "createdAt": "2025-10-07T13:33:32Z" } }, { "userEmail": "robin.bennett@peppermint.local", "text": "Here what I've done to the file :\n\nReplaced #[SecurityStrategy(Firewall::STRATEGY_NO_CHECK)] ------> #[SecurityStrategy(Firewall::STRATEGY_AUTHENTICATED)]\n\nAdded those line :\n'page' => $request->request->getInt('page', 1),\n'page_size' => $request->request->getInt('page_limit', -1),\n\nReboot the server, any change\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3377056963, "author": "TOMAGITINT", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21326#issuecomment-3377056963", "createdAt": "2025-10-07T14:04:51Z" } }, { "userEmail": "robin.bennett@peppermint.local", "text": "I just find that\nThe form is in the root entity and visibile to other child entity.\nThe user that I want to add are visible only if i'm in the child entity they are in.\nIn our usage, also as the admin of this GLPI, I use it to view the whole structure\n\nBut the fact that in the mode to view the whole structure, some users that are not in the root entity are visible is weird\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3377081572, "author": "TOMAGITINT", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21326#issuecomment-3377081572", "createdAt": "2025-10-07T14:10:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "If you're not able to apply the patch from #21322, you can use latest nightly build that already includes it.\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3380154981, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21326#issuecomment-3380154981", "createdAt": "2025-10-08T07:42:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21326, "url": "https://github.com/glpi-project/glpi/issues/21326", "author": "TOMAGITINT", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-07T13:24:20Z", "updatedAt": "2026-01-22T00:34:44Z", "closedAt": "2025-10-10T06:36:25Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "many of the same MAC addresses create a hub > hub link that is connecto to a natwork port on the switch.", "detail": "Affected version:\n10.0.20\n\nIssue description:\nGLPI inventories a switch and, on some access ports that truly learn a single MAC address, it creates “Unmanaged asset: Hub” + “Hub link” and then lists the same MAC multiple times under that Hub link.\nThe real endpoint (computer or printer) already exists in GLPI and should be linked directly to the switch port, but GLPI still builds a Hub object and a many-entry list containing duplicated copies of the same MAC.\nGLPI inventories network devices (switches), but on some single ports it automatically creates an “Unmanaged asset: Hub” and a “Hub link”, even though only one device is connected to that port. As a result, the switch port shows “Connected to: Hub > Hub link” instead of the specific device ( in hub link i have same mac address\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nOn port Gi1/0/12, the connected device is already inventoried in GLPI as a computer (asset ID 710934) with MAC address 34:17:eb:d6:33:04.\n\nWhen manually remove this HUB port ( delete permanently ) and run snmp inventory again i get same HUB > Hub link with same list ports.\n\n when i run glpi-netinventory --host 192.168.0.40 --credentials version:2c,community:public > ptlink-0-40.txt and chet it i have only one mac address on that port\n\nptlink-0-40.txt\n\nI have many of such problems ( one mac address multiplyed 2-5 times.\n\n[Image omitted]\n here we have printer on port Gi1/0/18 (b4:b5:2f:f2:9e:99) in glpi this asset exists.\n\nI found two similar threads on the forum and on GitHub.\n\nbut i have the latest version of glpi 10.0.20", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I'm not able to reproduce. Using provided inventory file gives me the following ports connections displayed (tested on v11 - but ports connection management did not change since v10):\n\n[Image omitted]\n\nThat seem OK, no?\n\nOften, existing data can cause issues in ports inventory. Could you test to drop all ports, then run again an inventory, and see if problem still happen?\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3405258051, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21464#issuecomment-3405258051", "createdAt": "2025-10-15T08:45:44Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "I verified the problem myself. I removed all HUB > Hub Link devices and their ports from the Undamaged Resources list. I manually specified specific computers and switches on the switch's network ports. After re-inventorying, the manual settings on the switch's network ports disappeared, but the HUBs returned. The HUB has 2-5 ports and the same MAC address.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\ni delete permanently all unmanaged assets and all HUB port from this hubs i delete also . But after rerun glpi-agent with task net inventory i get in glpi the same HUB number and the same ports inside\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3406463424, "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21464#issuecomment-3406463424", "createdAt": "2025-10-15T13:29:59Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I'm still not able to reproduce. Either we miss a step/info to reproduce, or database existing contents are in cause. We need a way to reproduce on an empty instance.\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3455439899, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21464#issuecomment-3455439899", "createdAt": "2025-10-28T09:28:47Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "I have noticed the same issue occurring across multiple switches. Every time the switches are inventoried or an SNMP scan is run, certain ports generate a 'HUB > Hub' link under unmanaged assets. I do not understand how this is possible, because the MAC addresses are identical. As shown in the screenshot, I am certain that there is only one camera physically connected to this specific port. Why is the same MAC address being multiplied, causing the system to falsely detect and create a HUB?\n\n[Image omitted]\nSometimes the hub has no mac on network ports\n\n[Image omitted]\n\nafter last cleaning 5 months ago i have almost 13000 such hubs - unually inside from 2 to 20 created network ports but in some cases even many thousends .....\n\nHUB is being created in a very strange way. There are no import rules defined for this behavior, and looking at the asset's history, I can see a creation/update log on every single activity or scan\n\n[Image omitted]\n\nnow i have more one milion ports\ncant find which rule is used to create hub and network ports in it\n\nOriginal response date: 2026-05-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4563546535, "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21464#issuecomment-4563546535", "createdAt": "2026-05-28T11:28:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21464, "url": "https://github.com/glpi-project/glpi/issues/21464", "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-14T08:47:13Z", "updatedAt": "2026-06-08T11:31:12Z", "closedAt": "2026-06-08T11:31:12Z" } }, { "title": "SQL Error 1054 when searching linked Custom Assets (missing alias.name column)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.4\n\nIssue description:\nI am writing in this field because I am experiencing the same issue.\nI created two custom assets:\n\n[Image omitted]\n\n[Image omitted]\n\nNow, when I go to onglet Parc -> Carte SIM and a search using the user name (for example), the server crashes, and only resetting the browsing data allows the page to be accessible again.\nThe link points to:\n\n[Image omitted]\n\nI noticed that if I remove the custom field column “Forfait”, the search works correctly.\n\n[Image omitted]\n\nI am also including the PHP error that occurs afterward\n\nI remain available if you need any additional information.\nThank you in advance. :D", "priority": "medium", "type": "support", "createdByEmail": "sage.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I edit the description to remove link to external site that request extension installation in browser. Please avoid that.\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3788888098, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22771#issuecomment-3788888098", "createdAt": "2026-01-23T08:00:25Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce. Maybe try with a 11.0 nightly build.\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3788950795, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22771#issuecomment-3788950795", "createdAt": "2026-01-23T08:09:28Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I also cannot recreate the issue. Have you been able to test on the latest GLPI 11?\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4139338442, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22771#issuecomment-4139338442", "createdAt": "2026-03-27T01:07:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No feedback since issue creation, closing. We'll reopen if needed when we'll have feedback.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4140770469, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22771#issuecomment-4140770469", "createdAt": "2026-03-27T07:40:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22771, "url": "https://github.com/glpi-project/glpi/issues/22771", "author": "Toyama007", "anonymizedAuthorEmail": "sage.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-21T10:55:20Z", "updatedAt": "2026-05-27T20:24:25Z", "closedAt": "2026-03-27T07:40:54Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "mailgate import email long titre", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHello,\nI'm reporting a minor bug I noticed involving an automated email with an extremely long subject line (1406 characters!!!). This caused the mailgate's SQL insertion to crash, resulting in an error. Deleting this email from Outlook will resolve the issue, but I assume adding a safeguard in the code would handle this properly without needing to dive into the logs.\n\nEnvironment details:\nglpi docker en compose, o365 + authIMAP", "priority": "medium", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "kai.bennett@peppermint.local", "text": "Cannot test without the authimap plugin, nothing else enabled\n\nOriginal response date: 2026-03-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3985225433, "author": "alfredit", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23321#issuecomment-3985225433", "createdAt": "2026-03-02T15:52:43Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please write in english only\n\nOriginal response date: 2026-03-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3985512273, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23321#issuecomment-3985512273", "createdAt": "2026-03-02T16:42:20Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Translation done ;)\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3989368198, "author": "alfredit", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23321#issuecomment-3989368198", "createdAt": "2026-03-03T08:03:30Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I think this was fixed for 11.0.6 with #23159. Would you be able to test this again with the latest release?\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993393232, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23321#issuecomment-3993393232", "createdAt": "2026-03-03T20:35:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23321, "url": "https://github.com/glpi-project/glpi/issues/23321", "author": "alfredit", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-02T15:51:02Z", "updatedAt": "2026-05-23T20:07:13Z", "closedAt": "2026-03-05T14:54:25Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "perf(database): fix/tune query performance regressions in Ticket HL API — missing composite indexes, full-table scans on externalid, and unbounded GROUP_CONCAT joins", "detail": "Summary:\nI would like to address and document database-level performance regressions in GLPI 11.x that cause significant query load when the Ticket HL API (/Assistance/Ticket) is consumed at moderate-to-high frequency. The issues manifest as 400+ QPS on MariaDB/MySQL, with individual queries examining 800–14,000+ rows per execution due to missing composite indexes, a full-table scan on externalid, and an unbounded GROUP_CONCAT + LEFT JOIN expansion in the core ticket listing query.\n\nReproduced on both a self-hosted Kubernetes environment (MariaDB 10.x, ~14,000 tickets) and AWS RDS (MySQL 8.0.44, ~4,700 tickets). Measurable impact exists even at small dataset sizes.\n\n---\n\nEnvironment:\n| Property | Value |\n|---|---|\n| GLPI version | 11.0.4 |\n| Database (on-prem) | MariaDB 10.x on Kubernetes |\n| Database (cloud) | MySQL 8.0.44 on AWS RDS |\n| Dataset size | 3,500 – 14,200 tickets |\n| Observed QPS under load | 400+ |\n| API surface affected | GET /Assistance/Ticket, GET /Assistance/Ticket/{id}/Timeline/* |\n\n---\n\nIssue description:\nglpi_tickets has no index on externalid. Any integration that looks up tickets by external reference — a common pattern when bridging GLPI with third-party systems — causes a full table scan on every request.\n\nEvidence:\ntype: ALL, key: NULL — every row read on every lookup. On 14,000 tickets with 2,222 executions in one collection window: ~31 million rows examined for this query shape alone. Scales linearly with ticket count.\n\nResult after fix:\ntype: ref, rows: 1 — index lookup instead of full scan.\n\n---\n\nIssue description:\nThe core ticket list query fetches a fully denormalized row for every ticket, with GROUP_CONCAT aggregations over user_recipient, user_editor, category, and location. This runs on every GET /Assistance/Ticket call regardless of which fields the consumer needs.\n\nEvidence:\nExtracted query shape:\n\nRoot cause:\nNo field projection at the API layer. GROUP_CONCAT forces a temporary table + filesort on every request. 720 executions × 29ms = ~21 seconds of total DB time in a single 3-minute observation window.\n\nDatabase-layer mitigation:\nNote: The GROUP_CONCAT expansion is a structural issue in the HL API query builder. The proper application-layer fix is field projection support (e.g. ?fields=id,status,externalid) so consumers that do not need denormalized join data do not trigger the full aggregation pipeline. Tracked separately below.\n\n---\n\nIssue description:\nThe HL API supports RSQL filtering via ?filter=. The most common patterns — filtering by status, itilcategories_id, date_creation — are not covered by any composite index. Existing single-column indexes have cardinality of 1–2 after ANALYZE TABLE, so the optimizer ignores them and falls back to full scans. They still impose write overhead on every INSERT/UPDATE.\n\nFix:\nComposite indexes provide combined cardinality the optimizer can use even when individual columns have low selectivity.\n\n---\n\nIssue description:\nWith no cache backend configured, GLPI re-validates its schema on every request:\n\ninformation_schema is a virtual schema that cannot be indexed. Every execution is a full metadata scan. With no cache this runs on every single API request.\n\nFix:\nOnce configured, schema validation is cached and this query load drops to near zero. Cache backend configuration should be treated as a required production step in the installation guide, not optional.\n\nReferences:\n- MariaDB InnoDB buffer pool:\n- GLPI cache config: php bin/console cache:configure --help\n- MySQL performance_schema digest tables:\n\n---\n\n*All measurements taken on live production systems under normal/high load using performance_schema.events_statements_summary_by_digest. No artificial benchmarking was used.*", "priority": "medium", "type": "support", "createdByEmail": "kendall.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "1. Not every field is indexed because more indexes means bigger tables and worse write performance. External ID is not a field used for filtering by GLPI itself. If you need an index on it, it can be done manually, but I don't know how useful it is for all GLPI users.\n2. \"regardless of which fields the consumer needs\" If that is a concern for your needs, the GraphQL API exists for that reason. Especially with the GraphQL changes coming in the next 11.0 release, the DB access is kept minimal to just the required fields.\n3. See number 1\n4. (5) This is not related to the API and I am aware these queries can be relatively slow (1-2ms) and are not cached. The list of tables is never cached, only memoized. If it were cached, I don't know if it would be any faster for most GLPI users who probably left the caching system using the filesystem instead of switching to Redis.\n\nOriginal response date: 2026-04-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4287952410, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23973#issuecomment-4287952410", "createdAt": "2026-04-21T10:52:09Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "1. Not every field is indexed because more indexes means bigger tables and worse write performance. External ID is not a field used for filtering by GLPI itself. If you need an index on it, it can be done manually, but I don't know how useful it is for all GLPI users.\n\n2. \"regardless of which fields the consumer needs\" If that is a concern for your needs, the GraphQL API exists for that reason. Especially with the GraphQL changes coming in the next 11.0 release, the DB access is kept minimal to just the required fields.\n\n3. See number 1\n\n4. (5) This is not related to the API and I am aware these queries can be relatively slow (1-2ms) and are not cached. The list of tables is never cached, only memoized. If it were cached, I don't know if it would be any faster for most GLPI users who probably left the caching system using the filesystem instead of switching to Redis.\n\nYes, I understand your point of view, but on my opinion - as this platform is getting more and more popular these specifications should be mentioned somewhere in the documentation, because it will be easier for devs to find the root cause of a lot of problems (like me when integrating it with a lot other well used services like flink, kafka, novu, etc. I'm just sharing them to the community so you can know the case and it's weaknesses and maybe if you decide to include them in some guide/documentation or mention them somewhere. ; )\n\nAnd about the \"worse write performance\" for the 1, 3st problem, most of the operations the regular users and devs in glpi makes is searches when displaying info for tickets/problem in the UI or through the API / summarize and etc... for me the external_id is mandatory field which is wide used from users when integrating with other managed systems and the ticket should have a relation to some other object/different way of recognizing tickets besides regular id / status / name - it is very useful.\n\nOriginal response date: 2026-04-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4287996666, "author": "pypetrov", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23973#issuecomment-4287996666", "createdAt": "2026-04-21T10:59:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I close because this does not seems a bug. You probably can use suggestions website; or forums.\nMost of the change you propose on index may probably be refused anyway.\n\nIf you find real missing index, please open a PR to add them correctly - adding too much index is not a good solution as stated Curtis.\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4311922371, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23973#issuecomment-4311922371", "createdAt": "2026-04-24T09:00:04Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "i cannot open a PR, because im not a contributor, i want to open a PR about the external id, because it is a mandatory field and i think most of the glpi integrations rely on the external_id search and this should be mentioned:\n Pull request creation failed. Validation failed: must be a collaborator\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4313178283, "author": "pypetrov", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23973#issuecomment-4313178283", "createdAt": "2026-04-24T12:34:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23973, "url": "https://github.com/glpi-project/glpi/issues/23973", "author": "pypetrov", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-04-21T09:09:10Z", "updatedAt": "2026-04-24T12:43:39Z", "closedAt": "2026-04-24T09:00:04Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Project creation date inherits template creation date instead of actual creation date", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen creating a new project from a project template, the project creation date is incorrectly set to the date when the template was created, instead of the actual date when the new project is created.\n\nThis behavior is confusing and not practical in daily usage, as the creation date of a project should logically reflect when the project itself was created, not when its template was defined.\n\nReproduction steps:\nGo to Tools → Projects.\n\nCreate a project template and save it.\n\nWait some time (for example several days).\n\nCreate a new project using this template.\n\nOpen the newly created project.\n\nCheck the creation date of the project.", "priority": "medium", "type": "support", "createdByEmail": "finley.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce. Just created a project template, set its creation and modification date 1 year in the past, and create a new project from this template. New project has correct creation and modification dates.\n\n[Image omitted]\n\nOn the form, creation date is not set at all (that's a bug):\n[Image omitted]\n\nTry without plugins, and with 11.0 nightly build if you still reproduce.\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3776470515, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22764#issuecomment-3776470515", "createdAt": "2026-01-21T06:51:44Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "On the form, creation date is not set at all (that's a bug): [Image omitted]\n\nI made a mistake: it looks like the \"creation date\" field in this form is not the creation_date field, but date one.\nNot sure the label is correct (at least it confuses me), but that's another problem.\n\nIf your issue is about this one, and since there is no default, best is probably not to set it in a template; or verbatim value will be took. Maybe a nonsense, but not a bug (a correct fix would be to remove this field from template IMHO.)\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3776507678, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22764#issuecomment-3776507678", "createdAt": "2026-01-21T07:05:26Z" } }, { "userEmail": "finley.blair@peppermint.local", "text": "Thank you for your quick response.\n\nAfter investigating the issue at database level, I can confirm that the problem is related to the change in the displayed field: the UI now uses the date field instead of date_creation.\nThis change has broken the way project creation dates were handled previously.\n\nAs a test, I set the date field to NULL on the project template. However, when creating a new project from this template, the field remains empty: the actual project creation date (current date/time) is not automatically set.\n\nAs a result, we now have to manually fill in this field in order to sort projects by creation date, which was not required before.\n\nIn my opinion, if the date field is used to display the “creation date” in the UI, it should be automatically initialized to the current datetime (or to date_creation) when a project is created, especially when it is created from a template.\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3779157808, "author": "blainvillem", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22764#issuecomment-3779157808", "createdAt": "2026-01-21T16:01:07Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I have no idea if that change was an error or if it was intended, and I do not have time to investigate for now.\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3782906274, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22764#issuecomment-3782906274", "createdAt": "2026-01-22T07:17:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22764, "url": "https://github.com/glpi-project/glpi/issues/22764", "author": "blainvillem", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-20T17:20:15Z", "updatedAt": "2026-04-24T06:52:37Z", "closedAt": "2026-04-24T06:52:37Z" } }, { "title": "Unexpected error in ticket form when actor is empty", "detail": "Affected version:\n11.0.0-beta\n\nIssue description:\nWhen a ticket has no actor, it shows \"An unexpected error has occurred.\" It happens in tickets already created without an actor or if you clear the actor field from a ticket that has an actor.\n\nWhen requester is blank, ticket form works normally.\n\nAffected page:\n\nReproduction steps:\n1. Go to Assistance > Tickets\n2. Click into a ticket that has no actor\n3. Get \"An unexpected error has occurred.\"\n\n1. Go to Assistance > Tickets\n2. Click into a ticket that has an actor\n3. Edit main ticket box (the green one)\n4. Change \"By\" user to no user (\"-----\")\n5. Save\n6. Get \"An unexpected error has occurred.\"\n\nAdditional context:\n(Not a fresh installation, it's an update from a populated GLPI 10)", "priority": "medium", "type": "support", "createdByEmail": "reese.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "dakota.blair@peppermint.local", "text": "Hi everyone Skyler Adler Skyler Adler,\nThe problem is still present when a user is missing from table users.\nFor unknow reason we have a lot of tickets with an user that not exist anymore in the system (table users).\nSo this workaround is not sufficient on this case :\n{% if users_id %}\n{{ include('components/user/picture.html.twig', {'users_id': users_id}, with_context = false) }}\n{% endif %}\nWhat can we do ? Shoud we bring a fix or just remove users that not exist anymore on all tickets with that problem.\nIs it normal for a deleted user to remain attached to tickets ?\nThanks.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3406237013, "author": "efpbe", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19457#issuecomment-3406237013", "createdAt": "2025-10-15T12:44:26Z" } }, { "userEmail": "reese.blair@peppermint.local", "text": "Skyler Adler Skyler Adler manually applying #21917 did not fix this particular issue for us (although it is unclear to me why it occurs in the first place). Maybe the following workaround can still be useful to someone else:\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605690231, "author": "jmechnich", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19457#issuecomment-3605690231", "createdAt": "2025-12-03T08:41:53Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Reese Blair you have to remove the cache when a Twig file has been edited (or switch to debug mode).\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605812077, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19457#issuecomment-3605812077", "createdAt": "2025-12-03T09:11:00Z" } }, { "userEmail": "reese.blair@peppermint.local", "text": "Reese Blair you have to remove the cache when a Twig file has been edited (or switch to debug mode).\n\nI used the cache:clear command so that also the change above went into effect.\n\nAnyhow, the release 11.0.3 fixed the issue for me (maybe it contained another necessary commit not mentioned in this thread).\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3615814930, "author": "jmechnich", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19457#issuecomment-3615814930", "createdAt": "2025-12-05T08:34:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 19457, "url": "https://github.com/glpi-project/glpi/issues/19457", "author": "stevanborges", "anonymizedAuthorEmail": "reese.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-04-14T21:56:37Z", "updatedAt": "2026-03-16T00:44:25Z", "closedAt": "2025-11-13T13:48:42Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Deleted computers are automatically restored from trash after GLPI Agent inventory", "detail": "Affected version:\n10.0.17\n\nIssue description:\nWhen I delete a computer from the inventory in GLPI 10.0.17, it is correctly moved to the trash.\nHowever, if the same computer runs another inventory via GLPI Agent (native inventory), it is automatically restored from trash to the active inventory list.\n\nReproduction steps:\n1. Use GLPI 10.0.17 with native inventory (GLPI Agent).\n2. Delete a computer from the inventory.\n3. It moves to trash as expected.\n4. Wait for the same computer to run a new inventory via GLPI Agent.\n5. The computer is restored automatically from trash.\n\nEnvironment details:\n- GLPI version: 10.0.17\n- Inventory: Native Inventory (GLPI Agent)\n- Agent version: GLPI-Agent v1.10\n\nAdditional context:\nThis behavior is problematic because:\n- It prevents keeping the trash clean.\n- Deleted assets can reappear without administrator consent.\n- It creates confusion for asset lifecycle management.\n\nExpected behavior:\n\nOnce a computer is deleted and moved to the trash, it should not be restored automatically by the agent inventory.\nAlternatively, an option could allow administrators to choose whether or not to allow restoration from trash by incoming inventories.", "priority": "medium", "type": "support", "createdByEmail": "finley.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "parker.blair@peppermint.local", "text": "Hi! This is an issue and unclear behaviour also for several of my customers, it depends on how GLPI is used.\nAs Finley Blair says, it is an issue because things get \"trashed\" to be able to archive them somehow for sometime...\nThus I see it more as a missing \"archive\" feature. That is, having old versions of an asset, which are never brought \"alive\" automatically, and which should be displayd only on a specific search.\nE.g. devices which have a \"2nd live\" somewhere else in another independent sub-company/customer (the old entry needs to be kept, a new one should be created), or devices/VMs that are no more under support, but should be kept in archive, in places where matching is by name (for several reasons) and names are sometimes reused, etc... (don't argue with \"that should not be done\" ;-) )\nThis would be more flexible and more clear than a global option for restoring trashed items.\n\nAnother, maybe much simpler, idea could be to be able to add to the asset import/update rules a condition \"in trash yes/no\" or an action \"update if in trash\"/\"move out of trash\" or similar\n\nThanks!\nMirko\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3380797355, "author": "Mirkk", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19628#issuecomment-3380797355", "createdAt": "2025-10-08T10:11:18Z" } }, { "userEmail": "kai.blair@peppermint.local", "text": "Could you please advise—is there any way to block automatic inventory for certain computers if it's impossible to uninstall the agent and there's no access to the PCs?\n\nPreviously, with FusionInventory, it was possible to block data collection from a specific agent and either move the computer to the trash bin or delete it entirely.\n\nHowever, after migrating to GLPI Agent for inventory and upgrading to GLPI 11+, I've encountered an issue where numerous computers have reappeared from oblivion. Moving them to the trash bin doesn't help—they just reappear in the main list. Similarly, deleting them doesn't solve the problem either, as they simply get recreated when new inventory data arrives.\n\nHow can I block data collection from specific agents? Or how can I prevent certain computers from being inventoried, even if new data keeps coming in? Is there any way to achieve this?\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3389413734, "author": "AbyssMoon", "anonymizedAuthorEmail": "kai.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19628#issuecomment-3389413734", "createdAt": "2025-10-10T11:08:57Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "From rule import, you could add a criterion based on the device ID (agent name) and set the action to 'Refuse without log'.\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3389954821, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19628#issuecomment-3389954821", "createdAt": "2025-10-10T12:59:32Z" } }, { "userEmail": "parker.blair@peppermint.local", "text": "Try adding a condition that looks at the Status, on the import rule\n\nBeslik *@*.*> schrieb am Fr., 10. Okt. 2025, 13:09:\n\n*AbyssMoon* left a comment (glpi-project/glpi#19628)\n\nCould you please advise—is there any way to block automatic inventory for\ncertain computers if it's impossible to uninstall the agent and there's no\naccess to the PCs?\nPreviously, with FusionInventory, it was possible to block data collection\nfrom a specific agent and either move the computer to the trash bin or\ndelete it entirely.\nHowever, after migrating to GLPI Agent for inventory and upgrading to GLPI\n11+, I've encountered an issue where numerous computers have reappeared\nfrom oblivion. Moving them to the trash bin doesn't help—they just reappear\nin the main list. Similarly, deleting them doesn't solve the problem\neither, as they simply get recreated when new inventory data arrives.\nHow can I block data collection from specific agents? Or how can I prevent\ncertain computers from being inventoried, even if new data keeps coming in?\nIs there any way to achieve this?\n—\nReply to this email directly, view it on GitHub\n,\nor unsubscribe\n\n.\nYou are receiving this because you commented.Message ID:\n*@*.*>\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3389970248, "author": "Mirkk", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19628#issuecomment-3389970248", "createdAt": "2025-10-10T13:03:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 19628, "url": "https://github.com/glpi-project/glpi/issues/19628", "author": "blainvillem", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-05-02T07:33:26Z", "updatedAt": "2026-01-22T00:34:38Z", "closedAt": "2025-05-22T07:47:32Z" } }, { "title": "ERROR_UNKNOWN when listing Consumable of a ConsumableItem via API", "detail": "Affected version:\n10.0.18\n\nIssue description:\nThe following request fails when you're not on Root entity\nGET:\n\nReproduction steps:\n1 : When connected to the API on Root entity, the request gets a list => OK\n2 : Change entity with changeActiveEntities/?entities_id=XXXX (XXX => Entity where you will have the same result\n3 : resend the same request will obtain ERROR_UNKNOWN => KO\n\nEnvironment details:\nGLPI : 10.0.18\nOS : RedHat : 9.5\nMariaDB : 11.4.7", "priority": "medium", "type": "support", "createdByEmail": "cameron.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please test on the latest 10.0.X or 11.0.X release. I can no longer see this issue on the 11.0/bugfixes branch.\n\nOriginal response date: 2025-12-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3691337971, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20117#issuecomment-3691337971", "createdAt": "2025-12-25T11:19:22Z" } }, { "userEmail": "remy.blair@peppermint.local", "text": "Please test on the latest 10.0.X or 11.0.X release. I can no longer see this issue on the 11.0/bugfixes branch.\n\nThanks, IIRC with the new API in version 11, we no longer had this problem. I'll take a look on the last v10 release\n\nOriginal response date: 2025-12-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3691669895, "author": "MrYamous", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20117#issuecomment-3691669895", "createdAt": "2025-12-25T18:50:12Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The legacy API still exists in GLPI 11 as a separate solution, it is just not recommended if the new \"high-level\" API does what you need.\n\nOriginal response date: 2025-12-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3691676673, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20117#issuecomment-3691676673", "createdAt": "2025-12-25T19:03:11Z" } }, { "userEmail": "remy.blair@peppermint.local", "text": "The legacy API still exists in GLPI 11 as a separate solution, it is just not recommended if the new \"high-level\" API does what you need.\n\nYes but in our corporate context we have some delay before upgrading to v11 unfortunately.\nOn 10.0.22 the issue still exists.\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737372561, "author": "MrYamous", "anonymizedAuthorEmail": "remy.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20117#issuecomment-3737372561", "createdAt": "2026-01-12T08:25:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20117, "url": "https://github.com/glpi-project/glpi/issues/20117", "author": "CHRPAR", "anonymizedAuthorEmail": "cameron.adler@peppermint.local", "assignees": [], "labels": [ "api", "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-06-26T10:39:32Z", "updatedAt": "2026-04-23T00:51:03Z", "closedAt": "2026-01-05T09:59:38Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "The content of a new ticket is reset when we change the category.", "detail": "Affected version:\n10.0.20\n\nIssue description:\nWhen we create a new ticket, if the content contains some text, everything is erased when we change the category. The bug seems to occur only when we change the main category or select a subcategory from a different main category.\n\nEverything works fine when we change other fields in the right column. The page refreshes, but the content remains in the Description field.\n\nAffected page:\n[website]/front/ticket.form.php\n\nReproduction steps:\n1. Go to the new ticket page.\n2. Fill in the Title and Description fields.\n3. Change the category of the ticket.\n4. Change the category again, but choose one from another main category (for example, from _IT > Access_ to _Microsoft > Account_).\n5. The Description field is reset.", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nWhat is the configuration of the ticket template that is supposed to be applied for this category?\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3489728358, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21788#issuecomment-3489728358", "createdAt": "2025-11-05T07:27:33Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Hi!\n\nWe don’t have any default templates applied to the categories. We only have a general one configured under Entities > Default entity _(which has our company’s name)_ > Assistance.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3489765317, "author": "Aruileen85", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21788#issuecomment-3489765317", "createdAt": "2025-11-05T07:40:49Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "What is the configuration of this template (predefined fields for instance)?\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3489776848, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21788#issuecomment-3489776848", "createdAt": "2025-11-05T07:44:09Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Well, I checked the category configurations more carefully, and it turns out someone had added the default template to certain categories. Only a few categories were misconfigured, but that was enough to cause the issue.\n\nThank you for your help, and sorry for the time spent — I should have checked each category more carefully, one by one.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3489801209, "author": "Aruileen85", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21788#issuecomment-3489801209", "createdAt": "2025-11-05T07:52:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21788, "url": "https://github.com/glpi-project/glpi/issues/21788", "author": "Aruileen85", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-05T06:52:16Z", "updatedAt": "2026-02-14T00:38:49Z", "closedAt": "2025-11-05T07:54:04Z" } }, { "title": "TTR fields not filled from forms to changes", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen creating changes using forms, the TTR date is not filled.\nUsing Formcreator (legacy) it was filled by the field from form\n\nReproduction steps:\nCreate a form which creates a change (destination change)\nField date in the form\nTTR is not among the properties available (like template and so on)", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "casey.blair@peppermint.local", "text": "legacy (using formcreator)\n\n[Image omitted]\n\nin glpi v11.0.5\n[Image omitted]\nTTR misses\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4162130903, "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23696#issuecomment-4162130903", "createdAt": "2026-03-31T12:02:11Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "It is found under the \"Service levels\" section:\n\n[Image omitted]\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4162303634, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23696#issuecomment-4162303634", "createdAt": "2026-03-31T12:31:10Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "For tickets : OK\nbut not for change ? : there is no 'Service levels under changes ?' although zone time_to_resolve still exists in glpi_changes table\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4162518890, "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23696#issuecomment-4162518890", "createdAt": "2026-03-31T13:07:02Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Indeed, you are right. I'm looking into it but it should be easy to add.\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4163179662, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23696#issuecomment-4163179662", "createdAt": "2026-03-31T14:43:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23696, "url": "https://github.com/glpi-project/glpi/issues/23696", "author": "EC2311", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-31T12:00:45Z", "updatedAt": "2026-07-17T00:43:43Z", "closedAt": "2026-04-07T07:18:33Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "Forms - Fields with visible condition do not appear in destination", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen a visible condition is applied to a form field, the answer entered in this field does not appear in the destination ticket.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. Create a form with a visible condition on a field\n2. Complete the form with this field answered\n3. The destination ticket does not contain the answer to this field", "priority": "medium", "type": "support", "createdByEmail": "kendall.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Kendall Bennett,\n\nI am not able to reproduce the issue, am I missing something?\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4111061217, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23210#issuecomment-4111061217", "createdAt": "2026-03-23T14:30:17Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "I tried another form after submitting the ticket and got the same bug. I already tested if the forms which were migrated from the plugin were the only ones affected or if it was all forms. But even a small form created from scratch was affected.\n\nMaybe try using a checkbox instead of a text field.\nI'll try with the same form as yours next week when I'm back from vacation.\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4128567291, "author": "LeoDef", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23210#issuecomment-4128567291", "createdAt": "2026-03-25T17:51:45Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "This confirms my doubts. It works perfectly when i'm using a text field. But when I try with a checkbox, the name field disappears in the corresponding ticket.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4160288487, "author": "LeoDef", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23210#issuecomment-4160288487", "createdAt": "2026-03-31T06:38:06Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Thanks for the detail, I confirm the issue 👍.\nLooking into it.\n\nOriginal response date: 2026-04-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4170360741, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23210#issuecomment-4170360741", "createdAt": "2026-04-01T14:07:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23210, "url": "https://github.com/glpi-project/glpi/issues/23210", "author": "LeoDef", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-23T14:46:39Z", "updatedAt": "2026-07-12T00:46:18Z", "closedAt": "2026-04-02T08:41:51Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Actors on Forms", "detail": "Affected version:\n11.0.4\n\nIssue description:\nFormcreator “Actors” sets requester correctly, but solution approval is sent to the form submitter instead of the requester\n\nWhen I use the “Actors” field in Formcreator to set the ticket requester to a user selected in the form:\n\nThe ticket is created successfully.\n\nThe Requester on the ticket is correctly set to the user selected in the form.\n\nHowever, when the ticket is solved, the solution approval is requested from the user who submitted/opened the ticket (the form submitter), not from the Requester (the user selected via the “Actors” field).\n\nExpected behavior\nThe solution approval should be sent to the Requester (the user set by the form “Actors” field).\n\nActual behavior\nThe solution approval is sent to the form submitter / ticket creator, even though the ticket requester is a different user.\n\nSteps to reproduce\n\nCreate a Formcreator form.\n\nAdd an Actors field and set it to define the Requester based on a user selected in the form.\n\nSubmit the form as User A (form submitter).\n\nConfirm the ticket is created with Requester = User B (selected in the form).\n\nSolve the ticket and trigger solution approval.\n\nNotice the approval request goes to User A, not User B.\n\n[Image omitted]\n\n[Image omitted]\n\nTicket opened and my Requester is the user selected on my forms, but when I solve this ticket, the approval solution is to user openeed a ticket not to a requester\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I've created this form:\n\n[Image omitted]\n\nWith this configuration:\n\n[Image omitted]\n\nI submit the form like this:\n\n[Image omitted]\n\nAnd add a solution:\n\n[Image omitted]\n\nThen, as the requester, I can approve the solution without issues:\n\n[Image omitted]\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3778434396, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22703#issuecomment-3778434396", "createdAt": "2026-01-21T14:30:27Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Am I missing something?\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3778435217, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22703#issuecomment-3778435217", "createdAt": "2026-01-21T14:30:38Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do note that the \"creator\" of the ticket is not the same as the requester:.\n\n[Image omitted]\n\nI'll fix it but unsure that it relate to your issue as I don't have any problem with the solution approval.\n\nEdit: unsure if it should be fixed, some people might see it more logical that way.\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3778446200, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22703#issuecomment-3778446200", "createdAt": "2026-01-21T14:32:29Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This issue seem stale, I'll close it for now (feel free to open a new one if it is still ongoing).\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4111068548, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22703#issuecomment-4111068548", "createdAt": "2026-03-23T14:31:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22703, "url": "https://github.com/glpi-project/glpi/issues/22703", "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-16T13:50:42Z", "updatedAt": "2026-07-02T01:02:48Z", "closedAt": "2026-03-23T14:31:17Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "LDAP CLI synchronization fails with \"Undefined array key\" (basedn, login_field)", "detail": "Affected version:\n11.0.4\n\nIssue description:\nDescribe the bug\nAfter upgrading to the latest version, the LDAP user synchronization via UI ( fails. The script throws PHP Warnings about undefined array keys for critical LDAP configurations (basedn, login_field, condition), causing the synchronization to abort or fail to find users.\n\nIt seems related to recent changes in src/AuthLDAP.php where direct access to $authldap->fields[...] is used instead of the getter methods. In the CLI context, the $fields array appears to be incomplete or not fully hydrated when these lines are executed.\n\nTo reproduce\nSteps to reproduce the behavior:\n1. Setup a valid LDAP directory.\n2. Run the synchronization command via CLI:\n php bin/console glpi:ldap:synchronize_users 1 --allow-superuser\n3. See the error in the console output.\n\nExpected behavior\nThe synchronization should read the LDAP configuration from the database and sync users without PHP warnings, as it did in previous versions.", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.blair@peppermint.local", "text": "[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3676463261, "author": "SamuelMTeixeira", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22452#issuecomment-3676463261", "createdAt": "2025-12-19T20:21:39Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Possibly triggered by #22013 but caused by missing checks somewhere else.\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3687184743, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22452#issuecomment-3687184743", "createdAt": "2025-12-23T16:12:50Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Just to add more context to the issue:\n\nIf I navigate to \"Add from an external source\" (/front/user.form.php?new=1&ext_auth=1), enter a username, and click \"Import from directories\", the user is successfully retrieved from LDAP using the current configuration.\n\nThis confirms that the LDAP parameters in the database are correct and the connection is working, but the configuration array seems to be lost or not hydrated properly during the CLI execution.\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3687422090, "author": "SamuelMTeixeira", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22452#issuecomment-3687422090", "createdAt": "2025-12-23T17:26:07Z" } }, { "userEmail": "reese.blair@peppermint.local", "text": "Hello,\n\nI'm reporting a related issue to this one, as it seems similar but with some differences. This is my first time contributing to a GitHub issue, so please let me know if I need to adjust anything or provide more details (e.g., full logs, exact versions, OS configs).\n\nEnvironment\n • Dev Server (working correctly):\n ◦ GLPI Version: 11.0.5 (updated shortly after release)\n ◦ OS: Debian 13\n ◦ PHP: 8.4\n ◦ LDAP: Single connection configured; user import via LDAP Directory Link works perfectly.\n • Production Server (issue occurring):\n ◦ GLPI Version: Recently upgraded from 10.0.18 to 11.0.5\n ◦ OS: Debian 12 (tested upgrading to Debian 13, issue persisted)\n ◦ PHP: 8.2 (tested upgrading to PHP 8.4, issue persisted)\n ◦ LDAP: Single connection configured, identical to dev server.\n\nBoth servers have the exact same LDAP configurations.\n\nIssue Description\n\nAfter upgrading the production server to 11.0.5, everything functions normally except for importing users via the LDAP Directory Link (Administration > Users > LDAP Directory Link > Import New Users). Searching for a user returns \"No results found.\"\nThis matches some aspects of the original issue, but includes additional errors in the logs (username redacted as \"USERNAME\"):\n\nSteps to Reproduce\n 1. Configure a single LDAP directory in GLPI 11.0.5.\n 2. Navigate to Administration > Users > LDAP Directory Link > Import New Users.\n 3. Search for a known user.\n 4. Observe \"No results found\" and check logs for the warnings above.\n\nWorkaround\n\nAdding a second LDAP directory resolves the issue on production. This introduces a dropdown to select the LDAP source on the import new users page, and searches then succeed for both directories.\n\nObservations\n • The issue doesn't occur on the dev server with a single LDAP config.\n • Upgrading production to match dev (Debian 13 + PHP 8.4) didn't fix it.\n • It seems like having only one LDAP config might be missing some backend handling for the lookup/filter, which gets resolved when a second config triggers the dropdown.\n\nThis might help narrow down the root cause. Happy to provide more info or test patches!\n\nThanks!\nF\n\nOriginal response date: 2026-02-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3885476521, "author": "Fortis007", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22452#issuecomment-3885476521", "createdAt": "2026-02-11T16:18:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22452, "url": "https://github.com/glpi-project/glpi/issues/22452", "author": "SamuelMTeixeira", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-19T19:32:14Z", "updatedAt": "2026-06-29T01:07:10Z", "closedAt": "2026-03-20T09:10:32Z" } }, { "title": "Entity creation error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHi,\nmy user can't create \"correctly\" a new entity (root) , i tested myself it's the same, it create it but no one have permission on it (me too) , on debug mode i've got this Missing READ right. Cannot view the item. L'action que vous avez réalisée n'est pas autorisée.\" , it's like the same problem at this one\n\nReproduction steps:\ncreate a new entity\nand try to access it", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Were you connected to the root entity with the recursive/child entities option? You cannot create entities you wouldn't immediately have permission to view.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993371258, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23325#issuecomment-3993371258", "createdAt": "2026-03-03T20:31:11Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "i'm currently connected as admin with recursive permission on root entity\n\n[Image omitted] and when i try to access the entity that i created , i got the error of read access, and i see entity only on \"root entity\" configuration,\n\n[Image omitted] the entity that make the error appear black without link\n\nOriginal response date: 2026-03-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3996794482, "author": "sothmani", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23325#issuecomment-3996794482", "createdAt": "2026-03-04T11:01:00Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Are you actually connected recursively though?\n\n[Image omitted]\n\nIn this screenshot you can see it says I am connected to the \"Root Entity (tree structure)\" which means I have visibility on the root entity and all child entities.\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4012010471, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23325#issuecomment-4012010471", "createdAt": "2026-03-06T14:17:35Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "we updated from 11.0.5 to 11.0.6 it's like it fix the problem. it was weird problem\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4038227495, "author": "sothmani", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23325#issuecomment-4038227495", "createdAt": "2026-03-11T10:37:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23325, "url": "https://github.com/glpi-project/glpi/issues/23325", "author": "sothmani", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-03T09:44:17Z", "updatedAt": "2026-06-20T01:05:42Z", "closedAt": "2026-03-11T10:37:26Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "v11.0.4: UI issues in Profiles and Notifications configuration", "detail": "Affected version:\n11.0.4\n\nIssue description:\nSeveral display issues have been observed in the GLPI interface. They appear to be UI-related and reproducible.\n\n1. Users list pagination not respected\nPath: Administration > Profiles > Users\n\nWhen setting \"Entries to display\" to 40 (or any value greater than 10), the list still displays only 10 users maximum.\nThe pagination setting is not applied to the displayed list.\n[Image omitted]\n\n2. Groups list not displayed in notification recipients\nPath: Configuration > Notifications > Notifications > [notification] > Destinataires > Groupe\n\nThe groups dropdown no longer displays the list of available groups.\nOnly the label \"Group:\" is shown, without any selectable entries.\n[Image omitted]\n\n3. Incorrect recipients count displayed\nPath: Configuration > Notifications > Notifications > [notification] > Destinataires\n\nThe interface indicates 3 recipients, while only 2 recipients are actually listed and visible.\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please open one bug report per bug in the future.\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696581241, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22346#issuecomment-3696581241", "createdAt": "2025-12-29T13:47:11Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate issues 2 and 3.\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696587115, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22346#issuecomment-3696587115", "createdAt": "2025-12-29T13:49:13Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Please open one bug report per bug in the future.\n\nNo problem, will do.\n\nI cannot recreate issues 2 and 3.\n\nI guess it's on my side then.\n\nOriginal response date: 2026-02-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3919371938, "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22346#issuecomment-3919371938", "createdAt": "2026-02-18T08:22:45Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I checked again and could not recreate issues 2 and 3. I'll close this issue since the first part was broken off into a separate issue.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4027041991, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22346#issuecomment-4027041991", "createdAt": "2026-03-09T21:29:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22346, "url": "https://github.com/glpi-project/glpi/issues/22346", "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-12T09:56:25Z", "updatedAt": "2026-06-18T01:10:22Z", "closedAt": "2026-03-09T21:29:53Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Entity Transfer issue in GLPI 11.0.7", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nHello,\nI am unable use the transfer of entity functionality. A success message appears but nothing happens.\nMore information bellow :", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please test #24560\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4705532262, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24459#issuecomment-4705532262", "createdAt": "2026-06-15T07:24:11Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Finally, I misread the code; I do not understand how this can happen with a non broken database.\nPlease run the command to check db consistency.\n\nOriginal response date: 2026-06-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4705742979, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24459#issuecomment-4705742979", "createdAt": "2026-06-15T07:54:27Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Hi, this is the result of db:check :\n\nOriginal response date: 2026-06-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4726523134, "author": "valentin-ibc", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24459#issuecomment-4726523134", "createdAt": "2026-06-17T05:56:44Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "As I suspected, your database is broken. Not much that can be done, you'll probably just have to fix it on your side, until the check command is clean.\n\nOriginal response date: 2026-06-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4726576011, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24459#issuecomment-4726576011", "createdAt": "2026-06-17T06:05:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24459, "url": "https://github.com/glpi-project/glpi/issues/24459", "author": "valentin-ibc", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-03T10:12:56Z", "updatedAt": "2026-06-17T06:05:57Z", "closedAt": "2026-06-17T06:05:57Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "List of accepted image file extension for upload not honoring document type setting", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI can't upload the following WebP image as a \"Rack pictures\" or \"Other pictures\" for a Computer model (/front/computermodel.form.php).\n\nWikipedia-logo-v2-webp.webp\n\nWhen I drag-n-drop it (or use the OS's file explorer) I get the \"Filetype not allowed\" error message in the progress bar.\n\nWebP type is enabled for upload in Setup > Dropdowns > Document types (/front/documenttype.form.php?id=73), I've also filled-in the MIME type (\"image/webp\").\n\nAffected page:\n\nReproduction steps:\n1. Download this WebP image on some file system\n2. Go to /front/computermodel.form.php\n3. Click \"Browse\" on any file input under \"Pictures\" header\n4. Select the WebP image in the OS file explorer\n5. Validate\n\nAdditional context:\nIn the src/Html.php the list of accepted extension is hard-coded to .gif,.png,.jpg,.jpeg, it does not use upload-enabled document types:", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "avery.bennett@peppermint.local", "text": "The PR #14872 seems to allow it but it looks like it missed this form field.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3951490855, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23224#issuecomment-3951490855", "createdAt": "2026-02-24T12:39:15Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I managed to get the upload working but, at least in my setup, the image display is not working. As far as I can tell (xdebug isn't working on those requests), the mime is not properly identified and remains \"null\" and it causes a PHP warning which may be breaking the response data.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3953275736, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23224#issuecomment-3953275736", "createdAt": "2026-02-24T16:25:36Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "With this fix it works (fine upload and display) 👍 .\n\nOriginal response date: 2026-02-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3973713228, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23224#issuecomment-3973713228", "createdAt": "2026-02-27T15:58:16Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "Thanks 👍\n\nOriginal response date: 2026-03-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3996777504, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23224#issuecomment-3996777504", "createdAt": "2026-03-04T10:57:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23224, "url": "https://github.com/glpi-project/glpi/issues/23224", "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-24T12:34:23Z", "updatedAt": "2026-06-13T01:09:23Z", "closedAt": "2026-03-04T10:09:35Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "[Bug] \"Duration\" field is non-editable for planning events over 2 days", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nIn the Planning view, the \"Duration\" (Durée) field for external events becomes a simple static text (non-editable) when the duration exceeds 2 days or when a multi-day selection is made using the mouse. This prevents any further modification of the event's duration without having to delete and recreate it.\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\nfront/planning.php\n\nReproduction steps:\nGo to the Planning menu.\n\nSwitch to Week view.\n\nPerform a mouse selection directly on the grid to cover a 3-day period (e.g., drag from Monday to Wednesday).\n\nIn the creation window that opens, observe that the Duration field is fixed text (e.g., \"3 days 0 hours...\") instead of a selection field.\n\nSave the event.\n\nClick on the event again to edit it: the field is still stuck in text mode, making any duration update impossible.\n\nAdditional context:\nThe bug seems related to an automatic UI switch to a raw display format as soon as the \"days\" unit exceeds 2, or during initialization via direct grid selection. If 1 day is selected manually, the dropdown field is present and working correctly.", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Probably related to so it would not be a bug per se, but a UX issue.\n\nThe limitation was added as workaround to Select2 being slow with large selection lists.\n\nMy current suggestion for changing this UI to avoid performance issues, avoid sending massive amounts of elements in the page response, and the usability issues of a dropdown for duration, is to use a masked number field similar to how other software like FreshBooks handles it (in their time tracking).\n\nPrototype UI of task form with masked duration field:\n[Image omitted]\n\nThe UI in the screenshot limits it to 99 hours, but it could be expanded to 3 digit hours or DD:HH:MM format.\n\nOriginal response date: 2026-02-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3914658657, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23146#issuecomment-3914658657", "createdAt": "2026-02-17T13:16:49Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Thanks for these explanations Taylor Adler . I now understand that the 50h limit was implemented to avoid Select2 performance issues.\n\nHowever, from a user perspective, this remains a blocking issue. Currently, if an event lasts more than 2 days, the duration field becomes completely non-editable, forcing us to delete and recreate the event just to change a date or time.\n\nIs the implementation of the masked number field already planned for a specific milestone ?\n\nOriginal response date: 2026-02-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3915304294, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23146#issuecomment-3915304294", "createdAt": "2026-02-17T15:14:36Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "I have a fix that addresses the blocking aspect of this issue while respecting the performance constraints.\n\nInstead of displaying static text when the duration exceeds 50h, the form now automatically switches the dropdown to 'Specify an end date' mode. This restores full editability of the event via the end date picker.\n\nNote on UX: I'm aware that entering an end date can be slightly counter-intuitive for multi-day events.\n\nExample: To create a full 3-day event from Feb 17 to Feb 19, the user must set the end date to Feb 20 at 00:00:00.\n\nWhile this is not perfectly user-friendly, it has the merit of making the event editable again immediately, providing a functional bridge until the masked number field mentioned by Taylor Adler is implemented.\n\nEvent on 2 days :\n\n[Image omitted]\n\nEvent on 3 days :\n\n[Image omitted]\n\nOriginal response date: 2026-02-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3915492344, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23146#issuecomment-3915492344", "createdAt": "2026-02-17T15:49:05Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Is the implementation of the masked number field already planned for a specific milestone ?\n\nNo, I should have clarified that more. The screenshot you see is from a personal project, due to a difference of opinion about the design of GLPI, where I am completely rewriting the entire GLPI UI as a Single-Page Application based on the new API without any of the legacy code, improved accessibility and hopefully improved user experience.\n\nSome of the things I implement in the other UI may be ported over here, but it isn't a guarantee. I am not in charge of GLPI design, just a contracted developer with a lot of opinions, and other people may have a different opinion for improving this part.\n\nOriginal response date: 2026-02-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3916976796, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23146#issuecomment-3916976796", "createdAt": "2026-02-17T20:38:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23146, "url": "https://github.com/glpi-project/glpi/issues/23146", "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-17T12:57:04Z", "updatedAt": "2026-06-05T01:05:54Z", "closedAt": "2026-02-24T13:35:37Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "v11.0.4: Adding \"Profile: Utilisateur\" to notification exclusions has the opposite effect", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen adding \"Profile: Utilisateur\" to the Exclusions field in a notification rule, GLPI does not exclude this profile. Instead, it unexpectedly adds the profile as a recipient of the notification. This results in users receiving notifications they should be excluded from.\n\nExpected behavior:\nUsers with the \"Utilisateur\" profile should be excluded from the notification.\n\nObserved behavior:\nUsers with the Utilisateur profile receive the notification as if they were explicitly added as recipients. In our case, this caused every employee who had ever logged into GLPI (except IT staff with higher profiles such as Technician) to receive the ticket notification.\n\nReproduction steps:\n1. Navigate to:\n Setup > Notifications > [any notification] > Recipients\n2. Add a standard recipient (e.g., Requester).\n3. In the Exclusions field, add:\n Profile: Utilisateur\n4. Save the notification configuration.\n5. Trigger the conditions for the notification.\n\nAdditional context:\nWe have the OAuth IMAP and samlsso plugins enabled.", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.blair@peppermint.local", "text": "Same issue for me.\nIf profile is in exclusion all users with this profile gets emails even they not match reciepients.\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3743034195, "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22309#issuecomment-3743034195", "createdAt": "2026-01-13T09:04:15Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Drew Blair Jamie Blair\n\ncan you try this -> #23027\n\nBest regards\n\nOriginal response date: 2026-02-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3854159620, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22309#issuecomment-3854159620", "createdAt": "2026-02-05T14:50:31Z" } }, { "userEmail": "logan.blair@peppermint.local", "text": "Hello Skyler Adler , what GLPI version include this fix?\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3876983914, "author": "alesnav", "anonymizedAuthorEmail": "logan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22309#issuecomment-3876983914", "createdAt": "2026-02-10T11:17:59Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The next one -> GLPI 11.0.5\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3877515809, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22309#issuecomment-3877515809", "createdAt": "2026-02-10T13:11:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22309, "url": "https://github.com/glpi-project/glpi/issues/22309", "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [ { "sourceLogin": "Herafia", "anonymizedEmail": "jesse.blair@peppermint.local" } ], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-09T15:51:37Z", "updatedAt": "2026-05-22T01:01:41Z", "closedAt": "2026-02-10T13:40:56Z" }, "assignedTo": "jesse.blair@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Webhook POST empty", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nwebhook is fired with POST.\npayload is default.\n\n\nboth files shows only ARRAY().\n$_POST is empty.", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "There isn't enough information here.\n\nWhat itemtype and event is the webhook configured for? Is it using the default payload or a custom one? What information is shown for the webhook in the queue?\n\nAlso, you need to provide the information requested in the bug report template like the log output and GLPI setup information.\n\nFeel free to edit your report and re-open, or make a post on the community forum for support.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3880326418, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23070#issuecomment-3880326418", "createdAt": "2026-02-10T19:45:06Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "What means: \"not planned\"?\nAs i wrote, payload is default an in the queue i can see the expected payload as json.\nI tried ticket and change, trigger=new as type.\n\nIf i write the variables in the URL and use GET instead of POST, i get the data in my php-script from $_GET.\nIf i change back to POST, $_POST is an empty array.\n\nSo i have a dirty workaround. But why is $_POST empty?\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3880620522, "author": "magheinz", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23070#issuecomment-3880620522", "createdAt": "2026-02-10T20:45:46Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "It is marked not planned because this isn't a bug with GLPI, and if it was there was not enough information in the original report to take action on it.\n\nYou will never see JSON content in $_POST because PHP doesn't automatically parse JSON content. You have to get is from file_get_contents('php://input') and decode it yourself. If you need more help, feel free to make a post on the community forum and I or someone in the community will try to help you more. GitHub issues are for bugs only.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3880678421, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23070#issuecomment-3880678421", "createdAt": "2026-02-10T20:59:27Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "Ok, so it's a missunderstanding on my site.\nSorry about the circumstances.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3880754594, "author": "magheinz", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23070#issuecomment-3880754594", "createdAt": "2026-02-10T21:15:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23070, "url": "https://github.com/glpi-project/glpi/issues/23070", "author": "magheinz", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-10T13:44:10Z", "updatedAt": "2026-05-22T01:01:32Z", "closedAt": "2026-02-10T19:45:06Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "11.0.5 Bug - Change", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nRecently upgraded from 11.0.4 to 11.0.5.\n\nI've been using the same template for at least a year now, if not longer.\n\nThis morning after upgrading, I tried to enter in a change. I was told 'Required Fields were not filled in. Please correct: Description.\" It is obv\n\n[Image omitted]\n\niously wrong.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "hayden.blair@peppermint.local", "text": "I modified the default template a long time ago.\n\nIt had this in it (for the description):\n\nI deleted the description entirely, saved the template and went back and recreated a test change. It successfully saved.\n\nOriginal response date: 2026-02-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3835740844, "author": "bturnbough81", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22965#issuecomment-3835740844", "createdAt": "2026-02-02T15:13:21Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Seems this issue is solved\n\nOriginal response date: 2026-02-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3839590065, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22965#issuecomment-3839590065", "createdAt": "2026-02-03T07:31:40Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Issue is NOT RESOLVED.\n\nNow I can’t even create a new, blank change and paste in the following text:\n\n*@*.*:/home/bic# apt upgrade\nReading package lists... Done\nBuilding dependency tree... Done\nReading state information... Done\nCalculating upgrade... Done\nThe following NEW packages will be installed:\n linux-headers-6.8.0-94 linux-headers-6.8.0-94-generic linux-image-6.8.0-94-generic linux-modules-6.8.0-94-generic\n linux-modules-extra-6.8.0-94-generic linux-tools-6.8.0-94 linux-tools-6.8.0-94-generic\nThe following upgrades have been deferred due to phasing:\n libgbm1 libgl1-mesa-dri libglx-mesa0 mesa-libgallium mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers\nThe following packages will be upgraded:\n alsa-ucm-conf dirmngr fwupd gir1.2-glib-2.0 gir1.2-glib-2.0-dev gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpgconf gpgsm gpgv\n i965-va-driver keyboxd klibc-utils kpartx libavahi-client3 libavahi-common-data libavahi-common3 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm2\n libfwupd2 libgirepository-2.0-0 libglib2.0-0t64 libglib2.0-bin libglib2.0-data libglib2.0-dev libglib2.0-dev-bin libheif-plugin-aomdec\n libheif-plugin-aomenc libheif-plugin-libde265 libheif1 libklibc libnuma1 libpng-dev libpng-tools libpng16-16t64 libpython3.12-minimal\n libpython3.12-stdlib libpython3.12t64 libsodium23 libssl-dev libssl3t64 libtasn1-6 libtasn1-6-dev libtasn1-doc libva-drm2 libva-x11-2 libva2\n libxml2 libxslt1.1 linux-firmware linux-generic linux-headers-generic linux-image-generic linux-libc-dev linux-tools-common multipath-tools numactl\n openssl python3-distupgrade python3-pyasn1 python3-urllib3 python3.12 python3.12-minimal screen snapd thermald ubuntu-release-upgrader-core\n va-driver-all\n74 upgraded, 7 newly installed, 0 to remove and 7 not upgraded.\n48 standard LTS security updates\nNeed to get 805 MB of archives.\nAfter this operation, 309 MB of additional disk space will be used.\nDo you want to continue? [Y/n]\n*@*.*:/home/bic# apt autoremove\nReading package lists... Done\nBuilding dependency tree... Done\nReading state information... Done\nThe following packages will be REMOVED:\n linux-headers-6.8.0-88 linux-headers-6.8.0-88-generic linux-image-6.8.0-88-generic linux-modules-6.8.0-88-generic linux-modules-extra-6.8.0-88-generic linux-tools-6.8.0-88\n linux-tools-6.8.0-88-generic\n0 upgraded, 0 newly installed, 7 to remove and 7 not upgraded.\nAfter this operation, 302 MB disk space will be freed.\nDo you want to continue? [Y/n]\n\nThan\n\n[Content truncated.]\n\nOriginal response date: 2026-02-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3842130052, "author": "bturnbough81", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22965#issuecomment-3842130052", "createdAt": "2026-02-03T15:51:51Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "See and then.\n\nOriginal response date: 2026-02-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3845724252, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22965#issuecomment-3845724252", "createdAt": "2026-02-04T07:02:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22965, "url": "https://github.com/glpi-project/glpi/issues/22965", "author": "bturnbough81", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-02T15:09:07Z", "updatedAt": "2026-05-16T00:54:13Z", "closedAt": "2026-02-03T07:31:40Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI 11.0.4 - Task Time not correct", "detail": "Affected version:\n11.0.4\n\nIssue description:\nI have problems with time set on tasks and tasks displayed time\n\n[Image omitted]\n\n[Image omitted]\n\n10 minutes on one and 9 seconds on the other\n\nAffected page:\n\nReproduction steps:\n1. create a task\n2. add a time\n3. save\n4. see the time displayed\n\nAdditional context:\nThere was a issue and I've replaced the files on my instance but it wasn't solved", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "There was a issue #22238 and I've replaced the files on my instance but it wasn't solved\n\nWell, just replacing a few files may not be enough, try with a complete nightly build.\n\nSee also\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3771937710, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22747#issuecomment-3771937710", "createdAt": "2026-01-20T09:43:01Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "Skyler Adler will do a nighty install in 10 minutes and report back.\n\nRegarding the comment, I've noticed this on new tasks not checked the old ones\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3771959271, "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22747#issuecomment-3771959271", "createdAt": "2026-01-20T09:48:08Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "If you change a Twig template in GLPI when it is in production mode, without there being a regular version update, you may have the old version cached on the server and being used. You can try clearing the GLPI server cache (User data cache) in debug mode from Setup > General > Performance tab.\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3772026657, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22747#issuecomment-3772026657", "createdAt": "2026-01-20T10:04:09Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "Hello again,\n\nTaylor Adler thank you for that information I did not know it, I've restarted the apache2 service but the problem remained. Learned something,\n\nRegarding the nightly build, I've updated with it and it solved the task time problem.\n\nThank you both for quick help\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3772049056, "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22747#issuecomment-3772049056", "createdAt": "2026-01-20T10:08:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22747, "url": "https://github.com/glpi-project/glpi/issues/22747", "author": "brusilva84", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-20T09:37:00Z", "updatedAt": "2026-05-15T00:57:20Z", "closedAt": "2026-01-20T10:08:34Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Error navigating between processors", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen I tried to switch between processors, the error occurred.\n\n[Image omitted]\n\nThis happens\n\n[Image omitted]\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I confirm the issue\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744701596, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22647#issuecomment-3744701596", "createdAt": "2026-01-13T14:38:21Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "This extends even further to all types of components.\n\n[Image omitted]\n Not .log related\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744795613, "author": "CYAsistemas", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22647#issuecomment-3744795613", "createdAt": "2026-01-13T14:54:13Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Can I work on this ? Skyler Adler\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3749422031, "author": "felipee-monteiro", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22647#issuecomment-3749422031", "createdAt": "2026-01-14T12:49:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Jordan Blair feel free; yes.\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3749461677, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22647#issuecomment-3749461677", "createdAt": "2026-01-14T13:00:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22647, "url": "https://github.com/glpi-project/glpi/issues/22647", "author": "CYAsistemas", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [ { "sourceLogin": "felipee-monteiro", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-13T14:36:08Z", "updatedAt": "2026-04-26T00:52:13Z", "closedAt": "2026-01-15T07:42:16Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Adding custom field dropdowns to views causes SQL query error", "detail": "Affected version:\nGLPI 11.0.4\n\nIssue description:\nIf you add custom fields to an asset, and use those fields as columns in a view, the query crashes. While normal fields such as date works, using dropdowns causes the Twig template to expect tables which are not there.\n\nThe tables queried are glpi_customdropdowns_*, but even as I have multiple of these custom dropdown fields, not a single table of that scheme does exist in my MySQL database.\n\nReproduction steps:\n1. Create a \"Custom Fields\" set on an asset, for example \"Software\"\n2. Add the custom dropdown field in the set\n3. Navigate to the software list and edit the view\n4. Add the custom dropdown field to be displayed in the view\n5. SQL query crash\n\nAdditional context:\nIf you have this problem, you can fix the view by editing the table glpi_displaypreferences and removing the field causing the problem.", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce on my side, using an up-to-date 11.0/bugfixes branch. Maybe the issue already has been solved, you may try with a recent nightly build (and alos without plugins, but I doubt this is the issue here).\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3744781275, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22648#issuecomment-3744781275", "createdAt": "2026-01-13T14:51:07Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Based on your suggestion I have tried on the 11.0 nightly build _(identifies as 10.5-dev)_ and still get the problem. Further investigation has revealed that it is caused if the \"Additional Fields\" plugin is on. Of course makes sense, because the whole error is caused by adding a custom dropdown field to the view.\n\nDeactivating this plugin removes the SQL error, and of course also the possibility to add custom fields dropdowns.\n\nI attached a short video of the problem as well.\n\nview_sql_error.zip\n\nSo maybe I have used the wrong github project, assuming that additional fields were a full part of GLPI 11 now. Would it be better to post this in the plugin project instead?\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3748669014, "author": "Supersonic431", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22648#issuecomment-3748669014", "createdAt": "2026-01-14T09:43:24Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Additional fields is still a plugin, it's not GLPI v11 native. SO yes, please report the issue on the plugin; this is not related to core :)\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3748768490, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22648#issuecomment-3748768490", "createdAt": "2026-01-14T10:08:34Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Will do. Thank you nevertheless for your time and so quick response. :)\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3748857162, "author": "Supersonic431", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22648#issuecomment-3748857162", "createdAt": "2026-01-14T10:29:36Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22648, "url": "https://github.com/glpi-project/glpi/issues/22648", "author": "Supersonic431", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-13T14:42:05Z", "updatedAt": "2026-04-25T00:46:25Z", "closedAt": "2026-01-14T10:08:34Z" } }, { "title": "Duplicate form ID on Rules page", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen browsing any rule subpage from (e.g. Authorizations assignment rules) it triggers an error on Web Browser stating that there are two elements with the same ID. No visible issues on UI, only on Browser Console:\n\n[Image omitted]\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Can i work on this issue ? Taylor Adler\n\nOriginal response date: 2026-01-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3733764297, "author": "felipee-monteiro", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22611#issuecomment-3733764297", "createdAt": "2026-01-11T00:45:35Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Can i work on this issue ? Taylor Adler\n\nSure 🙂. Feel free to open a pull request when ready.\n\nOriginal response date: 2026-01-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3733765344, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22611#issuecomment-3733765344", "createdAt": "2026-01-11T00:46:56Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I can't reproduce\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737211037, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22611#issuecomment-3737211037", "createdAt": "2026-01-12T07:30:33Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the issue. These kinds of messages used to be directly in the console but were moved a few years ago to the new Issues tab. I'm not sure Firefox reports these issues anywhere.\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737557195, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22611#issuecomment-3737557195", "createdAt": "2026-01-12T09:14:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22611, "url": "https://github.com/glpi-project/glpi/issues/22611", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "felipee-monteiro", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-10T22:37:41Z", "updatedAt": "2026-04-23T00:50:48Z", "closedAt": "2026-01-12T14:45:31Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "TicketTask creation via REST API v2 fails with 500 error when group_tech is provided", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen creating a TicketTask via the High-Level API endpoint /api.php/Assistance/Ticket/{id}/Timeline/Task, the group_tech field is not correctly mapped to the database column groups_id_tech.\n\nThe API schema specifies group_tech: {id: integer($int64)}, but the value is inserted as the literal string 'Array' instead of extracting the id value.\n\nExpected behavior:\nThe task should be created with groups_id_tech = 52 in the database.\n\nObserved behavior:\nAPI either returns 500 Internal Server Error or does not assign the group_tech id (if given directly as an integer).\n\nAdditional Details:\nThe OpenAPI schema correctly documents group_tech: {id: integer($int64)} but the mapping logic doesn't handle this.\n\nReproduction steps:\n1. Authenticate to API.\n3. Create a ticket (or re-use an existing one).\n4. Create a task inside the ticket.\n5. POST to /api.php/Assistance/Ticket/{ticket_id}/Timeline/Task with payload (make sure ticket_id and group_id exist):\n\nResult: 500 Internal Server Error with MySQL error about 'Array' in groups_id_tech column\n\nAdditional context:\nI'm a very big beginner in REST API coding so I very much apologize in advance if this is user error. I will be using legacy API for now as it seems to have more of the features that I need currently (such as the missing assignment of items to tickets).", "priority": "medium", "type": "support", "createdByEmail": "logan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Try:\n\"group_tech\": [52]\n\nThe API needs adapted still to properly support POST/PATCH requests that match the OpenAPI schema in the case of multiple values. A similar change was recently done to support both formats for single dropdown/link values like:\n\"location\": 5 AND \"location\": {\"id\": 5)\n\nOriginal response date: 2025-11-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3592651341, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22082#issuecomment-3592651341", "createdAt": "2025-11-30T15:04:44Z" } }, { "userEmail": "logan.bennett@peppermint.local", "text": "Try: \"group_tech\": [52]\n\nThe API needs adapted still to properly support POST/PATCH requests that match the OpenAPI schema in the case of multiple values. A similar change was recently done to support both formats for single dropdown/link values like: \"location\": 5 AND \"location\": {\"id\": 5)\n\nI have tried this, but I would receive an internal 500 error\n\nHere's the relevant logs when trying to POST to /Assistance/Ticket/{{id}}/Timeline/Task:\nwith body:\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3594059940, "author": "lotusflowr", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22082#issuecomment-3594059940", "createdAt": "2025-12-01T00:37:00Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Only one group_tech is allowed for ticket tasks, so it is \"group_tech\": 52.\nAnyways, the alternate form \"group_tech\": {\"id\": 52} was implemented in #21877 for 11.0.3.\n\nOriginal response date: 2025-12-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3691443037, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22082#issuecomment-3691443037", "createdAt": "2025-12-25T13:26:19Z" } }, { "userEmail": "logan.bennett@peppermint.local", "text": "thank your for your time ❤️\n\nOriginal response date: 2026-01-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3733633849, "author": "lotusflowr", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22082#issuecomment-3733633849", "createdAt": "2026-01-10T22:34:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22082, "url": "https://github.com/glpi-project/glpi/issues/22082", "author": "lotusflowr", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-27T05:29:36Z", "updatedAt": "2026-04-21T00:49:02Z", "closedAt": "2025-12-25T13:26:19Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "GLPI 11: Rules not running", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHi!\n\nI am trying to create a rule to assign computers to an entity based on the Inventory TAG, but the rule does not seem to be working.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you provide the requested information (GLPI setup for instance) and provide the inventory file corresponding to your computer so we could check if we can reproduce the issue?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606817164, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22085#issuecomment-3606817164", "createdAt": "2025-12-03T13:18:07Z" } }, { "userEmail": "jamie.bennett@peppermint.local", "text": "I am experiencing a similar issue with version 11.0.2. When an item already has an entity assigned, changing the rule to assign it to another entity does not have any effect on the item.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611654318, "author": "PowerMike-BZH", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22085#issuecomment-3611654318", "createdAt": "2025-12-04T11:19:18Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Dear Skyler Adler\n\nThe GLPI application is version 11.0.2. It is running on Debian 13 with PHP 8.3.\nThis is a fresh installation and is still using the default settings.\nDo you require any specific information?\n\nWe are using GLPI-Agent v1.15 for Windows and macOS (this works fine).\n\nBest regards,\nBence\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612334852, "author": "Csabence92", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22085#issuecomment-3612334852", "createdAt": "2025-12-04T13:43:31Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Please test on the latest GLPI 11 release and ensure you have a default entity transfer strategy set for the root entity/child entities under Administration > Entities > Your entity > Assets tab. If the issue still exists, please check the GLPI error log(s) after the asset gets re-inventoried.\n\nOriginal response date: 2025-12-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3691456195, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22085#issuecomment-3691456195", "createdAt": "2025-12-25T13:43:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22085, "url": "https://github.com/glpi-project/glpi/issues/22085", "author": "Csabence92", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-27T11:36:17Z", "updatedAt": "2026-04-16T00:51:38Z", "closedAt": "2026-01-05T09:57:08Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "no display elements when create tickets template", "detail": "Affected version:\n11.0.1\n\nIssue description:\nerror.pdf\n\nReproduction steps:\n1. create asset definitions\n2. create fields\n3. appply profiles\n4. create ticket template\n5. select predefined fields\n6. no display element fields\n\nEnvironment details:\nfresh install", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Are no custom asset items listed in the dropdown or does it show a \"no results found\" message? Please include the log output and GLPI setup information requested in the bug template.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3408246565, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21507#issuecomment-3408246565", "createdAt": "2025-10-15T20:56:15Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "no display fields in combo\n\n[Image omitted]\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3408425433, "author": "maxhinostrozaarias-lang", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21507#issuecomment-3408425433", "createdAt": "2025-10-15T21:47:56Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Asset definition -Datos del socio o cliente has a two fields\n\n[Image omitted]\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3408430685, "author": "maxhinostrozaarias-lang", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21507#issuecomment-3408430685", "createdAt": "2025-10-15T21:49:16Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I do not see a bug here. You showed a custom asset definition with some fields, but did not show that any items exist for this new custom asset definition. The dropdown you showed in the template that shows \"no results found\" is to select an item to associate with the ticket by default, not related to the fields of the selected type.\n\nAnyways, I still cannot recreate the issue. I have several custom asset definitions created with items for each and they all show properly for the predefined associated elements dropdowns.\n\nPlease test on the latest 11.0.X version.\n\nOriginal response date: 2025-12-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3691356537, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21507#issuecomment-3691356537", "createdAt": "2025-12-25T11:42:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21507, "url": "https://github.com/glpi-project/glpi/issues/21507", "author": "maxhinostrozaarias-lang", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-15T20:37:37Z", "updatedAt": "2026-04-16T00:51:35Z", "closedAt": "2026-01-05T09:58:12Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Content-Type WebHook", "detail": "Affected version:\n11.0.2\n\nIssue description:\nI create WebHook for a new ticket event (POST request). When Webhook sends to server, request does not contains Content-Type header with \"application/json\" value. Due this, i.e. NodeJs Express, don't parse body cause of missing content-type.", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Did you add this header to the webhook configuration?\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696589048, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22497#issuecomment-3696589048", "createdAt": "2025-12-29T13:49:57Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "Yep.\nP.S. Just try to delete \"qwe\" header. Then I press Save. It says that all good, but after page refresh \"qwe\" appeares again.\n\n[Image omitted]\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696687517, "author": "Gizmodo", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22497#issuecomment-3696687517", "createdAt": "2025-12-29T14:32:03Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "I create a new webhook. Add Content-type header. Invoke it and all works.\nIt turns out that if you add headers to a network request in an already created WebHook, they won't be sent when you click the \"Resend\" button. But if you prepare the configuration in advance, before the first trigger, everything works as expected.\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696703387, "author": "Gizmodo", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22497#issuecomment-3696703387", "createdAt": "2025-12-29T14:39:16Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "All headers (along with most other info about the webhook) are added to the queued webhook info when it gets triggered. If you change the headers for the webhook, the queued webhooks will only have the headers present at the time they were triggered.\n\nFor the issue deleting headers, I confirm.\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696764279, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22497#issuecomment-3696764279", "createdAt": "2025-12-29T15:03:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22497, "url": "https://github.com/glpi-project/glpi/issues/22497", "author": "Gizmodo", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-29T13:41:43Z", "updatedAt": "2026-04-16T00:50:59Z", "closedAt": "2026-01-05T10:35:43Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Bug in criteria code for \"Tickets waiting for your approval\" button", "detail": "Affected version:\n11.0.2\n\nIssue description:\nThere's a bug in criteria code for \"Tickets waiting for your approval\" button.\n\n$opt['criteria'][1] is a subgroup of criteria, so this is not effective:\n\nCriteria for \"validation aprobator\" should be added within the subgroup like this:\n\nAnd therefore, the second criteria in the subgroup should have a link item:", "priority": "medium", "type": "support", "createdByEmail": "finley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you please open a pull request with your proposal?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607700722, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22057#issuecomment-3607700722", "createdAt": "2025-12-03T16:24:26Z" } }, { "userEmail": "finley.bennett@peppermint.local", "text": "Hi,\n\nCould you please open a pull request with your proposal?\n\nHere it is:\n\nOriginal response date: 2025-12-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3649247673, "author": "akindemirci", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22057#issuecomment-3649247673", "createdAt": "2025-12-13T11:45:18Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "> Hi,\n> Could you please open a pull request with your proposal?\n\nHere it is: akindemirci#1\n\nPull request must be opened on glpi-project/glpi, not on your fork.\n\nOriginal response date: 2025-12-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3653514891, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22057#issuecomment-3653514891", "createdAt": "2025-12-15T06:10:18Z" } }, { "userEmail": "finley.bennett@peppermint.local", "text": "Sorry, here it is:\n\nOriginal response date: 2025-12-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3655191816, "author": "akindemirci", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22057#issuecomment-3655191816", "createdAt": "2025-12-15T11:45:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22057, "url": "https://github.com/glpi-project/glpi/issues/22057", "author": "akindemirci", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-25T09:09:51Z", "updatedAt": "2026-03-27T00:43:38Z", "closedAt": "2025-12-16T08:26:07Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Ticket - Associated Form Items Not Visible", "detail": "Affected version:\n11.0.1 and 11.0.2\n\nIssue description:\nIssue:\nWhen I associate a form with a ticket, it doesn’t appear under the Ticket Tabs items.\n\nExpected behavior:\nThe associated form should be visible in the Ticket Tabs section.\n\n[Image omitted]\n\nAdditional context:\nThe form is correctly listed in the Ticket Lists, but it’s missing from the Tabs view.\n\n[Image omitted]\n\nReproduction steps:\n1. Create a new form.\n2. Submit a response using that form.\n3. Go to the Ticket List and locate the generated ticket.\n4. Open the ticket and check the Item Tabs section.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It is hard to say in what way it is a bug (but it seems to be to be one) because these kinds of linked items are reserved for assets, specifically those in the ticket_types array internally. Forms are not meant to be linked this way manually and instead the existing association logic was reused. Behavior is therefore going to be inconsistent. If Forms were added to the right place to be able to support linking them to tickets, then users could manually link tickets to arbitrary forms which is also not desired.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3513681108, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21875#issuecomment-3513681108", "createdAt": "2025-11-10T19:58:32Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "It is hard to say in what way it is a bug (but it seems to be to be one) because these kinds of linked items are reserved for assets, specifically those in the ticket_types array internally. Forms are not meant to be linked this way manually and instead the existing association logic was reused. Behavior is therefore going to be inconsistent. If Forms were added to the right place to be able to support linking them to tickets, then users could manually link tickets to arbitrary forms which is also not desired.\n\nIn the case of it appearing as a number on the item badge, it's internally associated and counted even if it doesn't appear.\n\n[Image omitted]\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3528148544, "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21875#issuecomment-3528148544", "createdAt": "2025-11-13T14:43:05Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Hayden Blair,\n\nForms are not meant to be displayed in this tab as it is only for assets (you can see columns like \"serial number\" which make no sense for a form).\n\nHowever, the form will be shown in the main tab:\n\n[Image omitted]\n\nIn GLPI 11.0.4, we have fixed the counter on the tab so the linked forms will not be taken into account:\n\n[Image omitted]\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3627143715, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21875#issuecomment-3627143715", "createdAt": "2025-12-08T14:15:32Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Hi AdrienClairembault,\n\nRegarding the ticket items tab, I was referring to the counter showing \"1\nitem\" when a ticket is opened via a form, even though the tab itself is\nempty when clicked.\n\nIt seems the counter is incorrectly including the linked form in its total,\neven though forms are not meant to be displayed there.\n\nThank you for clarifying that forms are only shown in the main tab and for\nthe information about the fix in GLPI 11.0.4 to prevent the counter from\nincluding linked forms.\n\nBest regards,\n\nJober Cavalcante\n\nEm seg., 8 de dez. de 2025 às 10:15, Adrien Clairembault <\n*@*.*> escreveu:\n\n*AdrienClairembault* left a comment (glpi-project/glpi#21875)\n\nHello Hayden Blair ,\nForms are not meant to be displayed in this tab as it is only for assets\n(you can see columns like \"serial number\" which make no sense for a form).\nHowever, the form will be shown in the main tab:\nimage.png (view on web)\n\nIn GLPI 11.0.4, we have fixed the counter on the tab so the linked forms\nwill not be taken into account:\nimage.png (view on web)\n\n—\nReply to this email directly, view it on GitHub\n,\nor unsubscribe\n\n.\nYou are receiving this because you were mentioned.Message ID:\n*@*.*>\n\n--\nAtenciosamente\n\n*Jober Cavalcante*\nDesenvolvedor de sistemas\n+55 67 98401-2248\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3627163567, "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21875#issuecomment-3627163567", "createdAt": "2025-12-08T14:19:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21875, "url": "https://github.com/glpi-project/glpi/issues/21875", "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms", "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-10T18:59:42Z", "updatedAt": "2026-03-20T00:39:41Z", "closedAt": "2025-12-09T07:38:29Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Is the new task card size in the call correct? GLPI 11 RC5", "detail": "Contribution description:\nGood evening everyone, during call handling tests on GLPI 11 rc5, I noticed that the task card has a much larger blank space than in version 10.\n\nVersion 10 :\n\n[Image omitted]\n\nVersion 11 Rc5 :\n\n[Image omitted]\n\nMy question is whether this will actually be the new size of this card or whether it is out of scale.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "The impression it gives is that the idea is to take advantage of the empty space that was previously in version 10, but then I thought it would be good to report it to hear your thoughts on the matter.\n\nOriginal response date: 2025-09-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3325957828, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21114#issuecomment-3325957828", "createdAt": "2025-09-24T00:12:07Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Seems related to #14238\n\nOriginal response date: 2025-09-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3344616964, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21114#issuecomment-3344616964", "createdAt": "2025-09-29T02:15:11Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Looking at #14238, this was intended.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611065785, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21114#issuecomment-3611065785", "createdAt": "2025-12-04T09:24:38Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "ok, thanks for reply Skyler Adler\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612978092, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21114#issuecomment-3612978092", "createdAt": "2025-12-04T16:04:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21114, "url": "https://github.com/glpi-project/glpi/issues/21114", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "question", "ui" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-09-23T22:42:13Z", "updatedAt": "2026-03-15T00:44:36Z", "closedAt": "2025-12-04T09:24:38Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Saved Search - Cannot save private search for ticket with a profile of standard interface.", "detail": "Affected version:\n11.0.2\n\nIssue description:\nSince update to the version 11.0.2, a user cannot save a private search. I tried to find the possibility to authorize it from the pannel in Administration > Profile > Tools but I can only manage rights for Public saved search\n\nAffected page:\n\nReproduction steps:\n1. With a non admin user\n2. Go to tickets\n3. Open search panel\n4. click on save the current search\n5. Give it a name\n6. Click on add", "priority": "medium", "type": "support", "createdByEmail": "remy.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "parker.blair@peppermint.local", "text": "Having the same problem with same access-error log\n\nI did some testing and found the following:\nWhen I assign the right \"Tools->Public saved searches: Read, Update, Create\" to my profile, I am able to create private searches again, but in theory this right should not be required for private searches.\nTo delete the private search I don't need to have the right \"Tools->Public saved searches: Purge\" assigned, so this is working fine.\n\nThe right is called \"bookmark_public\" and is taken from src/SavedSearch.php\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3595230417, "author": "flex-pgum", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22089#issuecomment-3595230417", "createdAt": "2025-12-01T08:25:15Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI think #22010 fixes this issue.\nRemy Adler Parker Blair , could you confirm?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606810956, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22089#issuecomment-3606810956", "createdAt": "2025-12-03T13:16:35Z" } }, { "userEmail": "parker.blair@peppermint.local", "text": "Hi Skyler Adler, I applied the changes from #22010, after that it worked again as expected.\nIs this fix already included in the recently released 11.0.3 or will it be included in 11.0.4?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606872796, "author": "flex-pgum", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22089#issuecomment-3606872796", "createdAt": "2025-12-03T13:30:51Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This fix is included in GLPI 11.0.3.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606949432, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22089#issuecomment-3606949432", "createdAt": "2025-12-03T13:49:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22089, "url": "https://github.com/glpi-project/glpi/issues/22089", "author": "BioulacJe", "anonymizedAuthorEmail": "remy.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-27T12:50:10Z", "updatedAt": "2026-03-14T00:37:04Z", "closedAt": "2025-12-03T13:49:27Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "HLAPI In RSQL filter error multibyte strings", "detail": "Affected version:\n11.0.1\n\nIssue description:\nI found that RSQL like 'name=like=*ç*' return empty array.\nIn function tokenize length of query finded by mb_strlen, but next code use direct $query[$pos].\n\nand next code :\n\nAs fix I change $char to mb_substr with 1 step position.\n\nLexer.php\n\nPS. Replace text with as whole file.", "priority": "medium", "type": "support", "createdByEmail": "bailey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Could you open a pull request with your changes?\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3490956457, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21807#issuecomment-3490956457", "createdAt": "2025-11-05T12:29:59Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "I'l try\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491095144, "author": "Mikhail-D", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21807#issuecomment-3491095144", "createdAt": "2025-11-05T13:03:19Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "It was not possible to quickly set up the environment, and apparently there are not enough rights contributor. In main post attach file. I found 1 error with escape chars and clear err.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3493250340, "author": "Mikhail-D", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21807#issuecomment-3493250340", "createdAt": "2025-11-05T20:30:43Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I opened PR #21845 with your changes and attributed the commit to you.\n\nI found 1 error with escape chars and clear err.\n\nCould you elaborate on this?\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3499375323, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21807#issuecomment-3499375323", "createdAt": "2025-11-06T21:00:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21807, "url": "https://github.com/glpi-project/glpi/issues/21807", "author": "Mikhail-D", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-05T12:26:53Z", "updatedAt": "2026-03-01T00:44:31Z", "closedAt": "2025-11-20T06:06:20Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI 11 : Forms / Destinations : Unable to change Form Name", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHello,\n\ni am trying to create different ticket based on different choices in the form.\nIn the old forms plugin I was able to create different tickets with different names 👍\nLike :\n\n- Sharedmailbox [Création]\n- Sharedmailbox [Modification]\n\nThe title was adapted based on form selection.\n\nI am trying to change manually the form name but after saving it changes back again to the standard.\n\nbest regards,\nKim", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "The Form Name is not getting saved, I get no error when saving but when I come back again to the item it changed back to the default\n\nOriginal response date: 2025-11-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3520769423, "author": "kimi1983", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21868#issuecomment-3520769423", "createdAt": "2025-11-12T08:53:04Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Hello Elliot Bennett,\n\nThis is not a bug, but rather a misunderstanding of how tags work in form destinations.\n\nWhen you see the form name in the ticket title field, you're actually looking at a tag (like ##form.name##) that dynamically inserts the form's name. When you try to modify the text, you're only temporarily changing the display of the tag, but the tag itself remains in place. After saving, the tag is re-evaluated and displays the form name again.\n\n### To set a custom static ticket title:\n\n- Click on the text input\n- Delete/remove the entire tag (don't just edit its text)\n- Type your desired ticket title directly (e.g., \"Sharedmailbox [Création]\" or \"Sharedmailbox [Modification]\")\n- Save your destination\n\n### You can also mix static text with tags if needed. For example:\n\n- Static text: Sharedmailbox [Création] - followed by a tag like #Answer: XX if you want to include an answer from the form\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3541190360, "author": "ccailly", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21868#issuecomment-3541190360", "createdAt": "2025-11-17T11:01:32Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "oh my bad...tried it out and it worked.\nThx\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3541694410, "author": "kimi1983", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21868#issuecomment-3541694410", "createdAt": "2025-11-17T12:53:55Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Close\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3541695475, "author": "kimi1983", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21868#issuecomment-3541695475", "createdAt": "2025-11-17T12:54:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21868, "url": "https://github.com/glpi-project/glpi/issues/21868", "author": "kimi1983", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-10T07:25:42Z", "updatedAt": "2026-02-26T00:36:58Z", "closedAt": "2025-11-17T12:54:12Z" } }, { "title": "GLPI 11 - TeamMember returning err 500", "detail": "Affected version:\nGLPI 11.0.1\n\nIssue description:\nI'm trying to use the /Assistance/Ticket/{id}/TeamMember endpoint to add requesters to a ticket, but whenever I try to submit I receive a error 500\n\n[Image omitted]\n\nI've tried multiple payloads but none of the work.\n\n[Image omitted]\n\nalso documentation dosen't show how we are suposed to set the user id. I've tried multiple formats also.\n\nAny help would be apreciated.\n\nTks very much.", "priority": "medium", "type": "support", "createdByEmail": "cameron.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide logs.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3430534063, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21583#issuecomment-3430534063", "createdAt": "2025-10-22T05:14:36Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "Logs are shown in the description. There is no information on the apache log.\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3438906996, "author": "AAponciano", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21583#issuecomment-3438906996", "createdAt": "2025-10-23T20:01:54Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Body should be:\n\nAPI documentation for creating/updating the team members seems incomplete and there is missing handling of textual representations of roles (requester, assigned, etc).\n\nOriginal response date: 2025-10-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3444222045, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21583#issuecomment-3444222045", "createdAt": "2025-10-24T17:38:44Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Fixed with #21632 and #21633\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3524634004, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21583#issuecomment-3524634004", "createdAt": "2025-11-13T01:07:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21583, "url": "https://github.com/glpi-project/glpi/issues/21583", "author": "AAponciano", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-21T20:20:27Z", "updatedAt": "2026-02-22T00:40:33Z", "closedAt": "2025-11-13T01:07:48Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Webhook/API error - on create/update with GLPI Agent", "detail": "Affected version:\n11.0.1\n\nIssue description:\nDuring the execution of the inventory by an agent, all the webhooks triggered by the inventory generate a SQL error and are not executed.\n\nWhen assets are created or updated manually, the webhooks work normally.\nUnder normal circumstances, the webhooks should be triggered just as they are when an asset is manually created or updated.\n\n[Image omitted]\n\nAs shown in the picture, no webhook is triggered during the daily automatic updates performed by the agent.\n(See logout put below)\n\nNote: The change in system file are error.log() to see value at search time\n\nReproduction steps:\n1. Fresh install of GLPI 11.0.1 with GLPI Agent 1.15 installed on computer\n2. Create a Webhook on create and/or on update of a asset (computer for exemple)\n3. Run a inventory with the agent\n4. Go to the php-error.log to see the SQL Error", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I'm not sure that will fix your issue; but please try with GLPI 11.0.2 if you reproduce.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491303156, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21811#issuecomment-3491303156", "createdAt": "2025-11-05T13:45:24Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "The bug seem to be fix with the installation of the 11.0.2! Nice work.\nI receive another error, but from the API this time... does the GLPI Agent need the OAuth2 credential to work with the webhook?\n\nHere the php-error.log for the API Error:\n\nglpi.ERROR: * Caught RuntimeException: Failed to get API response from /Assets/Computer/33: HTTP 500\n Backtrace :\n ./src/Webhook.php:504\n ./src/Webhook.php:1170 Webhook->getAPIResponse()\n ./src/CommonDBTM.php:1811 Webhook::raise()\n ./src/Glpi/Inventory/MainAsset/MainAsset.php:952 CommonDBTM->update()\n ./src/RuleImportAsset.php:978 Glpi\\Inventory\\MainAsset\\MainAsset->rulepassed()\n ./src/Rule.php:1456 RuleImportAsset->executeActions()\n ./src/RuleCollection.php:1505 Rule->process()\n ./src/Glpi/Inventory/MainAsset/MainAsset.php:609 RuleCollection->processAllRules()\n ./src/Glpi/Inventory/Inventory.php:843 Glpi\\Inventory\\MainAsset\\MainAsset->handle()\n ./src/Glpi/Inventory/Inventory.php:448 Glpi\\Inventory\\Inventory->handleItem()\n ./src/Glpi/Inventory/Request.php:389 Glpi\\Inventory\\Inventory->doInventory()\n ./src/Glpi/Inventory/Request.php:91 Glpi\\Inventory\\Request->inventory()\n ...lpi/Agent/Communication/AbstractRequest.php:434 Glpi\\Inventory\\Request->handleAction()\n ...lpi/Agent/Communication/AbstractRequest.php:341 Glpi\\Agent\\Communication\\AbstractRequest->handleJSONRequest()\n ./src/Glpi/Controller/InventoryController.php:96 Glpi\\Agent\\Communication\\AbstractRequest->handleRequest()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\InventoryController->index()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ...tener/CatchInventoryAgentRequestListener.php:77 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ...ymfony/event-dispatcher/EventDispatcher.php:260 Glpi\\Kernel\\Listener\\RequestListener\\CatchInventoryAgentRequestListener->onKernelRequest()\n ...ymfony/event-dispatcher/EventDispatcher.php:220 Symfony\\Component\\EventDispatcher\\EventDispatcher::Symfony\\Component\\EventDispatcher\\{closure}()\n ...symfony/event-dispatcher/EventDispatcher.php:56 Symfony\\Component\\EventDispatcher\\EventDispatcher->callListeners()\n ./vendor/symfony/http-kernel/HttpKernel.php:157 Symfony\\Component\\EventDispatcher\\EventDispatcher->dispatch()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:7\n\n[Content truncated.]\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491678166, "author": "WBergeron", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21811#issuecomment-3491678166", "createdAt": "2025-11-05T14:54:19Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Well, you error is not at all the same as the origin. Seems like you should have additional logs on that API error; I do not know API at all, I cannot help.\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3495502437, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21811#issuecomment-3495502437", "createdAt": "2025-11-06T07:30:08Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "It's hard to follow several problems in a same github issue. Initial issue is resovled with 11.0.2; so please open a new issue with all details with your new error (including all logs).\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3495891394, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21811#issuecomment-3495891394", "createdAt": "2025-11-06T08:41:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21811, "url": "https://github.com/glpi-project/glpi/issues/21811", "author": "WBergeron", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-05T13:42:20Z", "updatedAt": "2026-02-15T00:42:26Z", "closedAt": "2025-11-06T08:41:08Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "An unexpected error occurred when accessing \"Assets/Computers\"", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWe very recently upgraded our GLPI version (From 10.0.19 to 11.0.1) and we started getting a weird error that prevents us from using GLPI to search for computers in our database :\n\nAn unexpected error occurred\nReturn to previous page\nTop of the page\n\nI believe this only started happening ever since we installed the newest version, and the migration seemed to have happened without any issue as well.\nWe typically use GLPI Inventory with the GLPI Agent installed on all the computers we have.\nIt seems that once the issue occurs, the page still refuses to display properly until the browser is completely cleared of its cache, even when removing all the search terms.\n\nDiagnostic information:\nThere doesn’t seem to be anything relevant to this issue in the GLPI logs, but I noticed some errors in my browser’s console that could potentially help figure out what’s going on.\n[Image omitted]\n\nThere is also this error that pops up in php-errors.log but it might be completely unrelated :\n\nReproduction steps:\n1. Go to \"Assets/Computers\"\n2. Change the first search field to \"does not contain\"\n3. Type a search criteria\n4. Add another rule and type another criteria\n5. Click search. The page gives me an error\n\n[Image omitted]\n\nEnvironment details:\nGLPI: 11.0.1 ( => /var/www/glpi)\nInstallation mode: TARBALL\nCurrent language: en_US\nSource Integrity: 1 files changed\n A: inc/downstream.php\n\nOperating system: Linux ServerGLPI2 6.1.0-40-amd64 #​1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64\n\nPHP: 8.3.26 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm,\ntokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"600\" max_input_vars=\"1000\" memory_limit=\"64M\" post_max_size=\"256M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"256M\"\n\nWeb server: Apache/2.4.65 (Debian) (Apache/2.4.65 (Debian) Server at helpdesk.latestedebuch.fr Port 443)\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:144.0) Gecko/20100101 Firefox/144.0\n\nDatabase:\n\nServer Software: Debian 12\n\nServer Version: 10.11.14-MariaDB-0+deb12u2\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi_adm@127.0.0.1/glpi\n\nHost info: 127.0.0.1 via TCP/IP\n\nRequirements:\nPHP version (8.3.26) is supported.PHP version (8.3.26) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (10.11.14) is supported.Database engine version (10.11.14) is\nsupported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/lib/glpi/files/_cache has been validated. Write access to\n/var/lib/glpi/files/_cron has been validated. Write access to /var/lib/glpi/files has been validated. Write access to\n/var/lib/glpi/files/_graphs has been validated. Write access to /var/lib/glpi/files/_lock has been validated. Write access to\n/var/lib/glpi/files/_pictures has been validated. Write access to /var/lib/glpi/files/_plugins has been validated. Write access\nto /var/lib/glpi/files/_rss has been validated. Write access to /var/lib/glpi/files/_sessions has been validated. Write access\nto /var/lib/glpi/files/_tmp has been validated. Write access to /var/lib/glpi/files/_uploads has been validated.Write access\nto /var/lib/glpi/files/_cache has been validated.\nWrite access to /var/lib/glpi/files/_cron has been validated.\nWrite access to /var/lib/glpi/files has been validated.\nWrite access to /var/lib/glpi/files/_graphs has been validated.\nWrite access to /var/lib/glpi/files/_lock has been validated.\nWrite access to /var/lib/glpi/files/_pictures has been validated.\nWrite access to /var/lib/glpi/files/_plugins has been validated.\nWrite access to /var/lib/glpi/files/_rss has been validated.\nWrite access to /var/lib/glpi/files/_sessions has been validated.\nWrite access to /var/lib/glpi/files/_tmp has been validated.\nWrite access to /var/lib/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed:\nctype, iconv, sodiu\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "morgan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.blair@peppermint.local", "text": "Hello\nI'm facing exactly the same problem with version 11.0.10.\nThe server configuration is OK and the problem appeared when moving from 10.0.20 to 11.0.0.\nUpdate to 11.0.1 has not changed this problem.\nThank you for your support\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3406501994, "author": "cyab-ux", "anonymizedAuthorEmail": "taylor.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21491#issuecomment-3406501994", "createdAt": "2025-10-15T13:39:19Z" } }, { "userEmail": "kai.blair@peppermint.local", "text": "buenas, de casulidad ya se tiene alguna solucion con el siguiente error:\nAn unexpected error occurred\n\nen la version 11.0.1\n\n[Image omitted]\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409202423, "author": "makiaveliko92", "anonymizedAuthorEmail": "kai.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21491#issuecomment-3409202423", "createdAt": "2025-10-16T05:11:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Kai Blair please write in english only.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409210380, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21491#issuecomment-3409210380", "createdAt": "2025-10-16T05:16:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Kai Blair also, since your screnshot is the GLPI installation, and current issue is not at all related to installation, I'm pretty sure this is out of the scope of current ticket.\nThe correct way ois to search in already existing issues for your problem, and if it's not yet reported, to open a new issue - in english - with all requested information.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409215050, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21491#issuecomment-3409215050", "createdAt": "2025-10-16T05:19:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21491, "url": "https://github.com/glpi-project/glpi/issues/21491", "author": "bastien33260", "anonymizedAuthorEmail": "morgan.adler@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-15T08:21:36Z", "updatedAt": "2026-02-08T00:48:58Z", "closedAt": "2025-10-30T13:31:50Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "GLPI 11.0.1: Error trying to add a custom field (Fields and Assets) to the global view computers.php", "detail": "Affected version:\n11.0.1\n\nIssue description:\nError trying to add a custom field to the global view of computers.php\n\nTested from my production version and from a free GLPI Cloud instance; in both cases, the error was replicated (Version 11.0.1).\n\nNote: Please apologize if this isn't the correct way to report a bug or if the error is due to misuse of the plugin. In version 10.0.10, it worked correctly. Thank you in advance. My English isn't very good.\n\nAffected page:\n/front/computer.php\n\nReproduction steps:\nI'm trying to add an additional field to the global view in /front/computer.php\n\n1. Using the Additional Fields plugin, I added an additional field to the Computers asset\n\n[Image omitted]\n\n2. A custom asset called Precio_Interno was previously created.\n\n[Image omitted]\n\n[Image omitted]\n\n3. From the custom asset, I'll only use the asset_name_type to include it as an additional field in Computers.\n\n[Image omitted]\n\n4. So far, everything is functional without errors; I can save and view the fields.\n\n[Image omitted]\n\n5. Adding the additional field to the custom view generates this error.\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello i'm trying to reproduce your steps for reproducing your error. But i'm stuck at step 3. Can you provide me an URL or more details on your scenario from this step ?\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3431004384, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21589#issuecomment-3431004384", "createdAt": "2025-10-22T08:14:37Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I suspect this issue comes from a plugin, not GLPI core.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3431113215, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21589#issuecomment-3431113215", "createdAt": "2025-10-22T08:38:45Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "Hello i'm trying to reproduce your steps for reproducing your error. But i'm stuck at step 3. Can you provide me an URL or more details on your scenario from this step ?\n\nIn step 3, I added a record to the \"Price_Internal\" custom asset, adding a name and asset type.\n\nThen in step 4, I included the \"price_internal\" type as an additional field in computer.php.\n\nThank you for your support.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432118041, "author": "SebastianUDI", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21589#issuecomment-3432118041", "createdAt": "2025-10-22T12:28:27Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "I suspect this issue comes from a plugin, not GLPI core.\n\nYes, I suspect the same thing, I'll wait a bit and if it's not a core issue then I'll post the report in the plugin creator's repository, thanks for your help.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432127310, "author": "SebastianUDI", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21589#issuecomment-3432127310", "createdAt": "2025-10-22T12:30:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21589, "url": "https://github.com/glpi-project/glpi/issues/21589", "author": "SebastianUDI", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-22T04:12:46Z", "updatedAt": "2026-02-07T00:37:29Z", "closedAt": "2025-10-29T09:55:54Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI 11 - Form submission fails when sections have conditional visibility settings", "detail": "Affected version:\n11.0.1\n\nIssue description:\nI've encountered an error in a form where I have several sections that are displayed conditionally. On the final step of the form, when clicking 'Submit' to create the ticket, GLPI displays an error message.\n\nHowever, if I navigate back to the dropdown selection, choose the other option (which displays a different section), and then submit, the form is sent successfully.\n\nI did not test this with the 'single page' render layout, only 'section by section'.\n\nThe main problem is that nothing is recorded in the logs, which made it very difficult to understand what was going wrong.\n\nPlease see the GIF below.\n\nReproduction steps:\n1. Create any new form.\n2. In the first section, add a dropdown question with at least two options (e.g., Option A, Option B).\n3. Create two new sections (e.g., Section A, Section B).\n4. Configure the visibility of each new section to be conditional on the option selected in the first question (e.g., selecting Option A shows Section A; selecting Option B shows Section B).\n5. View the form, select the first option (Option A), and proceed. In this section, try to submit the form. It will fail.\n6. Go back one page, select the second option (Option B), proceed to its corresponding section, fill it out, and submit. This time, it will work successfully.", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Hayden Bennett, I think this is already fixed by\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461775276, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21696#issuecomment-3461775276", "createdAt": "2025-10-29T14:13:53Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "Hello Skyler Adler. Is there a different workaround while the bugfix is not officially released?\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461874243, "author": "coca-mann", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21696#issuecomment-3461874243", "createdAt": "2025-10-29T14:29:07Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "You can apply the changes on your instance using the patch command, or download the nightly 11.0 release that contains all the merged fixes:\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3461920096, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21696#issuecomment-3461920096", "createdAt": "2025-10-29T14:36:57Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "I updated my GLPI version using the Nightly Build, and the problem was resolved. I will keep this version in production until the official release is available.\n\nThank you Skyler Adler! I will be closing this issue.\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3462368224, "author": "coca-mann", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21696#issuecomment-3462368224", "createdAt": "2025-10-29T15:45:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21696, "url": "https://github.com/glpi-project/glpi/issues/21696", "author": "coca-mann", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-29T14:11:21Z", "updatedAt": "2026-02-07T00:36:56Z", "closedAt": "2025-10-29T15:45:17Z" } }, { "title": "GLPI 11 queuednotificationcleanstaleajax not work", "detail": "Affected version:\n11.0.1\n\nIssue description:\nI've noticed that the automatic action \"queuednotificationcleanstaleajax\" not work. I've active the linux cron, running with the user of server \"www-data\":\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "GLPI 10.0.1 is very old. Did you mean version 11.0.1?\n\nDo you have anything in the GLPI logs (files/_log folder) around the time the automatic action is running/supposed to run?\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3452119751, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21660#issuecomment-3452119751", "createdAt": "2025-10-27T16:11:00Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "sorry Taylor Adler, is GLPI 11.0.1\n\n- cron.log:\n\n[Image omitted]\n\n- Logs in GLI:\n\n[Image omitted]\n\nIn the file php-error.php not watch error.\n\nRegards!\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3452167413, "author": "german-giraldom", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21660#issuecomment-3452167413", "createdAt": "2025-10-27T16:20:49Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "What is \"Validity period of notifications (in days)\" set to in the browser notification settings \"front/notificationajaxsetting.form.php\"?\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3457434880, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21660#issuecomment-3457434880", "createdAt": "2025-10-28T16:38:22Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "hi Taylor Adler , I hadn't validated that part, was in 30.\nI set it to 1 and executed the action, they were successfully removed.\nThanks!\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3458515640, "author": "german-giraldom", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21660#issuecomment-3458515640", "createdAt": "2025-10-28T21:16:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21660, "url": "https://github.com/glpi-project/glpi/issues/21660", "author": "german-giraldom", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-27T16:08:49Z", "updatedAt": "2026-02-06T00:36:41Z", "closedAt": "2025-10-28T21:16:20Z" } }, { "title": "GLPI 11 dont save location on ticket", "detail": "Affected version:\n11.0.0 and 11.0.1\n\nIssue description:\nAfter setting the \"Location\" field as the first one to be filled in the ticket creation form, I noticed that when creating a ticket using a post-only user, the location value is no longer saved.", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Skyler Bennett, could you share a few screenshots to help us understand this issue?\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400849561, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21443#issuecomment-3400849561", "createdAt": "2025-10-14T09:09:23Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "Skyler Adler\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400865198, "author": "dmcoelho", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21443#issuecomment-3400865198", "createdAt": "2025-10-14T09:13:06Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Thanks, I reproduce the issue 👍\nWorking on it.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400998806, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21443#issuecomment-3400998806", "createdAt": "2025-10-14T09:46:21Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "~Fixed by #21443~\n\nedit: I meant #21467\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401336305, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21443#issuecomment-3401336305", "createdAt": "2025-10-14T11:28:00Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21443, "url": "https://github.com/glpi-project/glpi/issues/21443", "author": "dmcoelho", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-13T09:40:10Z", "updatedAt": "2026-01-23T00:33:09Z", "closedAt": "2025-10-14T11:28:00Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "GLPI 11 - using newprofile=1 in the url to force self service profile doesn't work anymore", "detail": "Affected version:\n11.0.1\n\nIssue description:\nIn GLPI 10, using the url front/ticket.php?newprofile=1 allowed users with several profiles to switch automatically to the serlf-service one\n\nThis is removed in GLPI 11 (and by the way, simplied interface users don't have access to regular ticket creation anymore)\n\nIs there a way to do that ? Looking quickly in the code didn't show me a way to reproduce the old behavior", "priority": "medium", "type": "support", "createdByEmail": "jordan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Profile switching is no longer handled by a query parameter. It wasn't really intended to be a feature used like this. See the comments in #18057 which changed it.\n\nand by the way, simplied interface users don't have access to regular ticket creation anymore\n\nThis is also not a bug. The decision was made to block direct ticket form access and instead utilize forms. A form for a request and a form for an incident are included by default and should be similar to the original ticket form.\n\nOriginal response date: 2025-10-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3394249369, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21400#issuecomment-3394249369", "createdAt": "2025-10-12T11:55:05Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "Hi Conrad,\n\nThanks for you reply. Let me explain why I was doing that : I have several users with multiple profiles. When following the \"Internal support\" link I give them (/Helpdesk), they get \"Forbidden access\" to the page and have to switch manually to Self-service profile to get access.\n\nIs there a way to avoid that ? I don't really need to switch profile, just to get access to regular Helpdesk\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396402525, "author": "CoRpO", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21400#issuecomment-3396402525", "createdAt": "2025-10-13T08:28:51Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi Conrad,\n\nThanks for you reply. Let me explain why I was doing that : I have several users with multiple profiles. When following the \"Internal support\" link I give them (/Helpdesk), they get \"Forbidden access\" to the page and have to switch manually to Self-service profile to get access.\n\nIs there a way to avoid that ? I don't really need to switch profile, just to get access to regular Helpdesk\n\nYou should be able to use the force_profile=X query parameter, with X corresponding to the profile ID.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396673581, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21400#issuecomment-3396673581", "createdAt": "2025-10-13T09:43:15Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "It's working perfectly. Thank you very much !\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396801965, "author": "CoRpO", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21400#issuecomment-3396801965", "createdAt": "2025-10-13T10:16:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21400, "url": "https://github.com/glpi-project/glpi/issues/21400", "author": "CoRpO", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-10T08:27:13Z", "updatedAt": "2026-01-22T00:34:35Z", "closedAt": "2025-10-12T11:55:05Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Bug in GLPI 10.0.24 validation responses", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.24\n\nIssue description:\nGood afternoon, everyone. I've identified a problem here:\n\nWhen you create a validation in the call and the user approves it, all other validations created from that point on will also have the “validated” status, even if the user has declined approval.\n\n[Image omitted]\n\nIn the example above, I created a validation and accepted it.\nThe status remained as “validated.”\n\nAfter I created a new one, it went to the “awaiting validation” status.\n\nAfter I rejected it, instead of going to “rejected,” it went to “validated.”\n\nI tested this on three different GLPI instances running version 10.0.24.\n\nBecause the first validation created was marked as approved, it is causing all future validations to also be marked as approved, even if the user rejects them at the time.\n\nBecause of this, it is affecting some rules when it is necessary to analyze the criteria for a rejected validation.\n\nP.S.: If the first validation is rejected, the next one can be granted or rejected normally.\n\nBut starting with the first one that is granted, all subsequent ones—even if created for different users and at different times during the call—retain the granted status, even if they are rejected at some point.\n\nI couldn't find any related logs.\n\nAffected page:\nfront/ticket.form.php?\n\nReproduction steps:\n1. Create a new validation and approve it.\n2. Try creating a new validation again for yourself or another user and ask them to reject it. Note that even if it is rejected, it will still appear as “approved” in the validation.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "On second thought, I remembered there’s the issue of the “minimum validation required,” which is usually set to 0% in the ticket and can be changed to 50% or 100%.\n\nThe problem arises when approval is required at specific stages in the ticket. For example, I might have a single user who rejected the first approval but approved the second one. And then later on, another user approves it.\n\nBut all responses count toward the overall approval, even those from the same user, rather than considering the last validation as the final one.\n\nIf that is the case, would this be a current limitation of GLPi when there is a need for approvals at different stages of the ticket and the validation field needs to be updated?\n\nI appreciate any response.\n\nOriginal response date: 2026-05-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4579948608, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24399#issuecomment-4579948608", "createdAt": "2026-05-29T21:16:06Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please first try with latest stable release.\n\nOriginal response date: 2026-06-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4609965368, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24399#issuecomment-4609965368", "createdAt": "2026-06-03T07:15:00Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Good evening, please disregard this issue. It’s not actually a problem; it’s just a limitation of how validations work in the call.\n\nGlobal validation adds up all rejections and approvals. It turns out that it doesn’t work if the user wants to create validation steps (each step with a different minimum approval threshold).\n\nI suggest adding this feature for more complex workflows involving approvals.\n\nTranslated with DeepL.com (free version)\n\nOriginal response date: 2026-06-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4703047880, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24399#issuecomment-4703047880", "createdAt": "2026-06-14T21:04:35Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Validation steps are already coming with GLPI 12.\n\nOriginal response date: 2026-06-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4703073433, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24399#issuecomment-4703073433", "createdAt": "2026-06-14T21:12:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24399, "url": "https://github.com/glpi-project/glpi/issues/24399", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-29T20:20:09Z", "updatedAt": "2026-06-14T21:12:20Z", "closedAt": "2026-06-14T21:04:35Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Closed ticket layout collapses in helpdesk interface when satisfaction survey is expired or external", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen a ticket is in Closed status and viewed from the helpdesk (self-service) interface, the two-column layout collapses completely. The .itil-right-side panel ends up nested inside .itil-left-side instead of being a sibling element, breaking the layout.\n\nThis does NOT happen with other statuses (New, Processing, Pending, Resolved).\n\nExpected layout (all other statuses):\n\n.row.itil-object\n├── .itil-left-side ← timeline/conversation\n└── .itil-right-side ← fields panel\n\nActual layout (Closed status, expired survey):\n\n.row.itil-object\n└── .itil-left-side\n└── .itil-right-side ← BUG: nested inside left side\n\nRoot cause identified:\nIn templates/components/itilobject/timeline/timeline.html.twig (lines 231–242), the survey block opens a and wrapper. Their closing tags () are delegated to buttons.html.twig inside itilsatisfaction.html.twig — but buttons.html.twig is only rendered when the survey is not expired. In all expired cases and for external survey type, those tags are never closed, leaving .itil-timeline unclosed and causing .itil-right-side to be nested inside .itil-left-side.\n\nAffected code paths in itilsatisfaction.html.twig:\n\n| Condition | buttons.html.twig rendered? | Layout broken? |\n|---|---|---|\n| External survey (url is defined) | No | Yes |\n| expired=true AND no answer | No | Yes |\n| expired=true AND has answer | No | Yes |\n| expired=false | Yes | No |\n\nReproduction steps:\n1. Configure an entity with satisfaction surveys enabled and a short duration (e.g., 5 days)\n2. Close a ticket older than the configured duration\n3. Log in as a self-service (helpdesk) user\n4. Open the closed ticket\n5. Observe the collapsed layout — fields panel disappears or renders incorrectly\n\nAdditional context:\nA fix has been identified and tested on 11.0.6. The solution is to add explicit closing tags in itilsatisfaction.html.twig for the three code paths where buttons.html.twig is not rendered. A pull request with the fix will follow this issue.", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Is this related to #23441?\n\nOriginal response date: 2026-04-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4260800183, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23943#issuecomment-4260800183", "createdAt": "2026-04-16T14:21:01Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "Yes, it appears to be the same issue as #23441.\n\nI was able to identify the root cause and apply a fix that resolves the problem on our GLPI 11.0.6 instance.\n\nRoot cause: In templates/components/itilobject/timeline/timeline.html.twig, the survey block opens a and wrapper whose closing tags are delegated to buttons.html.twig inside itilsatisfaction.html.twig. However, buttons.html.twig is only rendered when the survey is not expired. In three cases (external survey, expired+no answer, expired+answered), those tags are never closed, leaving .itil-timeline unclosed and causing .itil-right-side to nest inside .itil-left-side.\n\nFix applied: Added explicit closing tags in itilsatisfaction.html.twig for the three affected code paths.\n\nI will submit a Pull Request with the fix shortly.\n\ngithub-issue.md\n\nOriginal response date: 2026-04-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4260880356, "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23943#issuecomment-4260880356", "createdAt": "2026-04-16T14:31:50Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Casey Bennett FYI, It looks like you opened your PRs on your fork of GLPI instead of the official GLPI repository.\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4413540971, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23943#issuecomment-4413540971", "createdAt": "2026-05-09T19:55:41Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "## Update: Fix Status and Playwright Test Analysis\n\n### PR Status ✅\nThe fix has been refined and is ready. The PR (#24186) has:\n- ✅ PHP Lint checks passing (8.2 and 8.5)\n- - ✅ Code normalized to UTF-8 LF without BOM\n- - - ✅ Duplicate files removed\n- - - - ✅ Minimal, focused changes (only necessary files modified)\n### Lint Failures Resolved ✅\nThe initial \"Licence header outdated\" error was caused by CRLF/BOM encoding issues, not content. These have been normalized across all modified files.\n\n### Playwright Test Error - Pre-existing ℹ️\nThe failing Playwright test (timeline-TicketTask not found) is NOT caused by our changes:\n\n- The element timeline-TicketTask is located in templates/components/itilobject/timeline/todo-list-summary.html.twig\n- - Our changes only touch itilsatisfaction.html.twig and timeline/timeline.html.twig\n- - - Our changes only add explicit closing tags and for the form wrapper\n- - - - These closing tags have no connection to the timeline element rendering\nConclusion: This is a pre-existing issue in GLPI unrelated to this fix. It should be investigated and reported separately.\n\n### Files Modified\n1. templates/components/itilobject/itilsatisfaction.html.twig - Added 3 closing tag pairs + clarifying comment\n2. 2. templates/components/itilobject/timeline/timeline.html.twig - Updated comment only\n### Recommendation\nThis fix correctly addresses the layout collapse issue (#23943). The Playwright error is independent and pre-existing. Ready for review and merge.\n\nOriginal response date: 2026-05-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4432215187, "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23943#issuecomment-4432215187", "createdAt": "2026-05-12T15:37:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23943, "url": "https://github.com/glpi-project/glpi/issues/23943", "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-16T14:15:52Z", "updatedAt": "2026-06-04T07:39:08Z", "closedAt": "2026-06-04T07:39:08Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Bug with the \"ALL\" search filter", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello,\nWhen I try to search for an item in the tickets using the filter:\n\n\"ALL\" contains \"solution approuvé\" (\"solution approuvé\" being the result of my search)\nI get the error message \"An error has occurred\"\n\nWhen I look at the logs in GLPI, I see this message in the \"php-error.log\" file:\n\n[2026-06-03 13:01:33] glpi.CRITICAL: * Uncaught PHP Exception RuntimeException: \"MySQL query error: Too many tables; MariaDB can only use 61 tables in a join (1116) in SQL query \"SELECT DISTINCT glpi_tickets.id AS id, 'user' AS currentuser,\n glpi_tickets.id AS ITEM_Ticket_2, glpi_tickets.name AS ITEM_Ticket_1, glpi_tickets.id AS ITEM_Ticket_1_id, glpi_tickets.id AS ITEM_Ticket_1_id, glpi_tickets.status AS ITEM_Ticket_1_status, glpi_entities.completename AS ITEM_Ticket_80, glpi_tickets.status AS ITEM_Ticket_12, GROUP_CONCAT(DISTINCT glpi_users_af1042e23ce6565cfe58c6db91f84692.id SEPARATOR '$$##$$') AS ITEM_Ticket_4, GROUP_CONCAT(DISTINCT CONCAT(glpi_tickets_users_019878060c6d5f06cbe3c4d7c31dec24.users_id, ' ', glpi_tickets_users_019878060c6d5f06cbe3c4d7c31dec24.alternative_email) SEPARATOR '$$##$$') AS ITEM_Ticket_4_2, GROUP_CONCAT(DISTINCT CONCAT(IFNULL(glpi_ticketvalidations.status, 'NULL'), '$#$', glpi_ticketvalidations.id) ORDER BY glpi_ticketvalidations.id SEPARATOR '$$##$$') AS ITEM_Ticket_55, GROUP_CONCAT(DISTINCT glpi_users_b1b92f6be5e70531688d870931e94a65.id SEPARATOR '$$##$$') AS ITEM_Ticket_5, GROUP_CONCAT(DISTINCT CONCAT(glpi_tickets_users_c6f7f58b9365babf7388e555e526efd5.users_id, ' ', glpi_tickets_users_c6f7f58b9365babf7388e555e526efd5.alternative_email) SEPARATOR '$$##$$') AS ITEM_Ticket_5_2, COUNT(DISTINCT glpi_itilfollowups.id) AS ITEM_Ticket_27, glpi_tickets.date AS ITEM_Ticket_15, glpi_itilcategories.completename AS ITEM_Ticket_7, glpi_tickets.priority AS ITEM_Ticket_3 FROM glpi_tickets LEFT JOIN glpi_entities ON (glpi_tickets.entities_id = glpi_entities.id) LEFT JOIN glpi_tickets_users AS glpi_tickets_users_019878060c6d5f06cbe3c4d7c31dec24 ON (glpi_tickets.id = glpi_tickets_users_019878060c6d5f06cbe3c4d7c31dec24.tickets_id AND glpi_tickets_users_019878060c6d5f06cbe3c4d7c31dec24.type = '1') LEFT JOIN glpi_users AS glpi_users_af1042e23ce6565cfe58c6db91f84692 ON (glpi_tickets_users_019878060c6d5f06cbe3c4d7c31dec24.users_id = glpi_users_af1042e23ce6565cfe58c6db91f84692.id) LEFT JOIN glpi_ticketvalidations ON (glpi_tickets.id = glpi_ticketvalidations.tickets_id) LEFT JOIN glpi_tickets_users AS glpi_tickets_users_c6f7f58b9365babf7388e555e526efd5 ON (glpi_tickets.id = glpi_tickets_users_c6f7f58b9365babf7388e555e526efd5.tickets_id AND glpi_tickets_users_c6f7f58b9365babf7388e555e526efd5.type = '2') LEFT JOIN glpi_users AS glpi_users_b1b92f6be5e70531688d870931e94a65 ON (glpi_tickets_users_c6f7f58b9365babf7388e555e526efd5.users_id = glpi_users_b1b92f6be5e70531688d870931e94a65.id) LEFT JOIN glpi_itilfollowups ON (glpi_tickets.id = glpi_itilfollowups.items_id AND glpi_itilfollowups.itemtype = 'Ticket') LEFT JOIN glpi_itilcategories ON (glpi_tickets.itilcategories_id = glpi_itilcategories.id) LEFT JOIN glpi_users AS glpi_users_users_id_lastupdater ON (glpi_tickets.users_id_lastupdater = glpi_users_users_id_lastupdater.id) LEFT JOIN glpi_documents_items ON (glpi_tickets.id = glpi_documents_items.items_id AND glpi_documents_items.itemtype = 'Ticket') LEFT JOIN glpi_documents AS glpi_documents_2d98e43dfecb07952ef329c36da01250 ON (glpi_documents_items.documents_id = glpi_documents_2d98e43dfecb07952ef329c36da01250.id) LEFT JOIN glpi_pendingreasons_items ON (glpi_tickets.id = glpi_pendingreasons_items.items_id AND glpi_pendingreasons_items.itemtype = 'Ticket') LEFT JOIN glpi_pendingreasons AS glpi_pendingreasons_a36a2b0326def287f74c16ff353b3194 ON (glpi_pendingreasons_items.pendingreasons_id = glpi_pendingreasons_a36a2b0326def287f74c16ff353b3194.id) LEFT JOIN glpi_tickettemplates ON (glpi_tickets.tickettemplates_id = glpi_tickettemplates.id) LEFT JOIN glpi_locations ON (glpi_tickets.locations_id = glpi_locations.id) LEFT JOIN glpi_itils_projects ON (glpi_tickets.id = glpi_itils_projects.items_id AND glpi_itils_projects.itemtype = 'Ticket') LEFT JOIN glpi_projects AS glpi_projects_58d1ddfe4485681a04da313df0a12066 ON (glpi_itils_projects.projects_id = glpi_projects_58d1ddfe4485681a04da313df0a12066.id) LEFT JOIN glpi_forms_destinations_answerssets_formdestinationitems AS glpi_forms_destinations_answerssets_formdestinationitems_668b84ad4010d3e81057676ae2459e01 ON (glpi_tickets.id = glpi_forms_destinations_answerssets_formdestinationitems_668b84ad4010d3e81057676ae2459e01.items_id AND glpi_forms_destinations_answerssets_formdestinationitems_668b84ad4010d3e81057676ae2459e01.itemtype = 'Ticket') LEFT JOIN glpi_forms_answerssets AS glpi_forms_answerssets_e9e4085b298e9527e8a0138c435a9e59 ON (glpi_forms_destinations_answerssets_formdestinationitems_668b84ad4010d3e81057676ae2459e01.forms_answerssets_id = glpi_forms_answerssets_e9e4085b298e9527e8a0138c435a9e59.id) LEFT JOIN glpi_items_tickets ON (glpi_tickets.i\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Not a bug. There is a limit at the DB level for the number of joins on a query and the All search option is disabled by default knowing that it is bad for performance and likely to hit this limit in most cases in modern GLPI. Use Items Seen instead with relevant columns showing or use specific criteria.\n\nOriginal response date: 2026-06-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4612996244, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24465#issuecomment-4612996244", "createdAt": "2026-06-03T13:46:10Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Hello,\nThe \"all\" filter can be useful if you're searching for an item within a ticket. How do you explain that it worked with the previous version mentioned?\n\nOriginal response date: 2026-06-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4613113351, "author": "Azgar1998", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24465#issuecomment-4613113351", "createdAt": "2026-06-03T13:57:49Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "New search options are being added constantly, which means new joins if they reference data from other tables, and GLPI 11 had 3 years worth of development/new features added.\n\nIf you are trying to search for timeline items with some text, it is vastly more efficient to add those criteria separately. If you do this often, you can save it as a saved search and just replace the text being searched rather than re-adding the criteria every time.\n\nOriginal response date: 2026-06-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4613403412, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24465#issuecomment-4613403412", "createdAt": "2026-06-03T14:26:06Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Can you search for an item within a ticket, for example, or within items like in a follow-up or validation? I haven't seen those specific filters in the user profile.\n\nOriginal response date: 2026-06-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4613793976, "author": "Azgar1998", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24465#issuecomment-4613793976", "createdAt": "2026-06-03T15:05:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24465, "url": "https://github.com/glpi-project/glpi/issues/24465", "author": "Azgar1998", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-06-03T13:38:46Z", "updatedAt": "2026-06-03T15:05:08Z", "closedAt": "2026-06-03T13:46:20Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Specific timezone gap error Europe/London 29/03/2025", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nI discovered it by accident when I was checking the error log related to a plugin that I am developing (in that time gap), with the support of Claude, it interprets the following:\n\n\"Error 1299: Invalid TIMESTAMP value is a DST bug—it's not directly related to the plugin but to the server's timezone. Your hosting provider, stackcp.net, uses Europe/London, and March 29, 2026, is precisely the day when UK clocks jump from 01:00 GMT to 02:00 BST. During that gap, the minutes 01:00–01:59 don't exist in that timezone, so MySQL rejects any TIMESTAMP with that value.\n\nThe solution: all calls to date('Y-m-d H:i:s') in the plugin replaced with gmdate('Y-m-d H:i:s'). gmdate() always returns UTC, which never has DST gaps. Files corrected: sync.class.php (8 calls), dashboard.php, and history_export.php (1 each).\n\nThe warnings from glpi_crontasklogs and glpi_logs that appear in the same log are from GLPI core, not the plugin — those need to be fixed by Teclib.\"\n\nReproduction steps:\nHave a server with Europe/London timezone", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "sage.blair@peppermint.local", "text": "done\n\nOriginal response date: 2026-03-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4150097491, "author": "NWCRES-tech", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23670#issuecomment-4150097491", "createdAt": "2026-03-29T12:48:36Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide a way to reproduce without plugins\n\nOriginal response date: 2026-03-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4153203107, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23670#issuecomment-4153203107", "createdAt": "2026-03-30T08:26:47Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "In the PHP error log I'm sharing, there are no third-party plugins installed. The bug itself relates to how MySQL interprets the non-existent time gap when daylight saving time changes in time zones like Europe/London. If a GLPI cron job is executed at that moment (regardless of whether it's from a plugin or GLPI's own code), it throws this SQL insertion error. As I mentioned, discovering it was accidental. To replicate it, you have to set the date to March 29th at 23:00 with a time zone like Europe/London, and have GLPI run cron jobs and log them. As I said, it's a very specific and random occurrence that will repeat itself exactly every year due to how MariaDB and MySQL handle dates.\n\nOriginal response date: 2026-03-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4157507326, "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23670#issuecomment-4157507326", "createdAt": "2026-03-30T19:12:49Z" } }, { "userEmail": "quinn.blair@peppermint.local", "text": "Hi, I encountered a problem that might be related. After last time change (time zone Prague CET/CEST, UTC +1/+2) many automatic actions that are scheduled to each hour or more frequent stopped executing. Last run time is saved as 2026-03-29 04:01:00 etc. which is weird because the time change is from 2 to 3. db:check is OK. cron.log mostly reports nothing to run. I am on 11.0.6, php 8.3, MariaDB 10.11.15. I haven't yet found a way to fix this. Can maybe changing the lastrun entry in db help, is it safe to do?\nEDIT: It seems it has been stuck in Running state, after manually changing to scheduled it seems to be working fine again.\n\nOriginal response date: 2026-04-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4171666757, "author": "Bohoaush", "anonymizedAuthorEmail": "quinn.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23670#issuecomment-4171666757", "createdAt": "2026-04-01T17:17:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23670, "url": "https://github.com/glpi-project/glpi/issues/23670", "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-29T08:38:02Z", "updatedAt": "2026-06-02T14:32:57Z", "closedAt": "2026-06-02T14:32:57Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Incorrect display of free space", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nGood afternoon. There are two identical laptops. The display of free space is not the same. There are differences in the order of partition display.\n\nAdditional context:\nOn version 10.0.19, it was also displayed. I didn't notice it before these devices started appearing en masse.", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "hayden.bennett@peppermint.local", "text": "To restore the normal display, follow these steps: 1. Go to the computer's card.\n2. Navigate to the \"Volumes\" section.\n3. Select the /sys/firmware/efi/efivars partition and move it to the trash.\n4. Go to the deleted partition and select \"Delete permanently.\"\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4215181826, "author": "Krovyakov-Ivan", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23761#issuecomment-4215181826", "createdAt": "2026-04-09T14:51:07Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "Please do not ignore my message. Please indicate that you have at least read it.\n\nOriginal response date: 2026-05-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4497700413, "author": "Krovyakov-Ivan", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23761#issuecomment-4497700413", "createdAt": "2026-05-20T11:05:01Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Community bug reports are always addressed on a best-effort basis and priority is given to bugs that affect usability/a large number of users. If you require timely support, please consider taking a GLPI subscription.\n\nThis report does not seem to be a bug per se. This list is not sorted and so it is shown in the order the volumes were added to the database and for whatever reason the order they were inventoried had changed for that one computer. This behavior also isn't limited to just this list.\n\nOriginal response date: 2026-05-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4498200407, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23761#issuecomment-4498200407", "createdAt": "2026-05-20T12:04:58Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "Thank you for your reaction.\n\nOriginal response date: 2026-05-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4498468251, "author": "Krovyakov-Ivan", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23761#issuecomment-4498468251", "createdAt": "2026-05-20T12:38:39Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23761, "url": "https://github.com/glpi-project/glpi/issues/23761", "author": "Krovyakov-Ivan", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-04-03T12:04:03Z", "updatedAt": "2026-05-21T06:54:05Z", "closedAt": "2026-05-21T06:54:05Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "[11.0.6] List all the connectable devices at computer connection tab", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhe you open a computer and navigated to the connections tab you can see all the connectable devices not only that are really connected to the computer\n\n[Image omitted]\n\n[Image omitted]\n\n (2 diferent computers with 1 and 1 connected device but the system shows all the 100+ screens that are in the inventory)\n\nReproduction steps:\n1 Open a computer page\n2 Navigate to connections\n\nEnvironment details:\nGLPI: 11.0.6 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_US\nOperating system: Linux glpi112. 5.15.0-125-generic #​135-Ubuntu SMP Fri Sep 27 13:53:58 UTC 2024 x86_64\n\nPHP: 8.3.23 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, apache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"218M\" session.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\" upload_max_filesize=\"218M\"\n\nWeb server: Apache/2.4.56 (Debian) (Apache/2.4.56 (Debian) Server at * Port 8012)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 11.2.6-MariaDB-ubu2204\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@glpi-mariadb/glpidb\n\nHost info: glpi-mariadb via TCP/IP\n\nRequirements:\nPHP version (8.3.23) is supported.\nOS and PHP are relying on 64 bits integers.\nSessions configuration is OK.\nAllocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader, xmlwriter.\nmysqli extension is installed\ncurl extension is installed\ngd extension is installed\nintl extension is installed\nmbstring extension is installed\nzlib extension is installed\nbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installed\nDatabase engine version (11.2.6) is supported.\nThe log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.\nexif extension is installed\nldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.\nZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.\nWrite access to /var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please test #23380; it should fix the issue.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4022054165, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23411#issuecomment-4022054165", "createdAt": "2026-03-09T08:34:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please test #23380; it should fix the issue.\n\nNote: use debug mode and remove cache after applying changes on twig files.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4022058245, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23411#issuecomment-4022058245", "createdAt": "2026-03-09T08:35:28Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Solved with the #23380 thx\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4022236206, "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23411#issuecomment-4022236206", "createdAt": "2026-03-09T09:07:14Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Issue should remain open until the PR is merged. The Issue will close automatically.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4030011356, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23411#issuecomment-4030011356", "createdAt": "2026-03-10T09:42:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23411, "url": "https://github.com/glpi-project/glpi/issues/23411", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-09T07:45:36Z", "updatedAt": "2026-05-19T07:59:20Z", "closedAt": "2026-03-11T13:33:20Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Document downloads buffer entire file into memory (regression from readfile() in 10.x)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.7 (also affects all 10.x releases since June 2023, commit 2137a5a81d)\n\nIssue description:\nToolbox::getFileAsResponse() reads the whole file into a PHP string before sending, so every Document download peaks at ≥ file size in memory and hits memory_limit for large attachments.\n\nThis is a regression. Before commit 2137a5a81d (June 2023), Toolbox::sendFile() ended with readfile($file) after an explicit ob_end_clean() loop - i.e. it streamed in chunks and the original authors deliberately avoided buffering. That commit rewrote sendFile() to return a Response object for the new HL API and, as a side effect, replaced readfile() with file_get_contents(). The 11.0 Symfony refactor in commit b11be7f781 preserved the buffering.\n\nCommits for reference:\n-\n-\n\nThe fix is to use Symfony's BinaryFileResponse on the download path - it streams via fpassthru, supports X-Sendfile / X-Accel-Redirect, and is still a Response so HL API composition keeps working.\n\nAffected page:\n/front/document.send.php?docid=\n\nReproduction steps:\n1. Set PHP memory_limit to a small value (e.g. 64M) to make the issue\n reproducible without uploading huge files.\n2. Upload a Document larger than the memory_limit (e.g. ~100 MB).\n Increase upload_max_filesize / post_max_size / GLPI's\n document_max_size as needed for the upload itself.\n3. Click the download link for that Document, or hit\n /front/document.send.php?docid= directly.\n4. Observe a PHP fatal error (\"Allowed memory size of N bytes\n exhausted\") in files/_log/php-errors.log instead of a streamed\n download. Smaller-but-still-large files complete but with peak PHP\n memory usage ≥ file size.\n\nCode-level confirmation: src/Toolbox.php lines 657-667 call\nfile_get_contents($path) and pass the result to a buffered\nSymfony Response.", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The HL API largely does not use the Symfony framework. Note that it uses Glpi\\Http\\Response which is based on \\GuzzleHttp\\Psr7\\Response and not Symfony\\Component\\HttpFoundation\\Response.\n\nYour solutions sounds OK in theory but it would need implemented in a way that would work with the API. You may open a pull request if you believe your solution would still work.\n\nOriginal response date: 2026-05-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4367500209, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24118#issuecomment-4367500209", "createdAt": "2026-05-04T00:00:26Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "Thank you for your answer. At the moment I don't have time to create a mental model of the glpi codebase and I worry that a AI generated fix would not meet the needed quality. So I have to decline.\n\nOriginal response date: 2026-05-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4370001321, "author": "0nelight", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24118#issuecomment-4370001321", "createdAt": "2026-05-04T09:46:41Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "A fix was attempted but was not quite working with the HLAPI due to the creation/unwrapped of responses in multiple places. In case I cannot get it working today, I am documenting my findings here for me to remember later or for another developer to understand.\n\nWith the attempted fix:\n1. The Toolbox::getFileAsResponse method was changed to return a Symfony StreamedResponse. So far, no issues; The headers_list() is empty and no headers are sent.\n2. When called from the HLAPI, the endpoints were changed to take the StreamedResponse and call sendContent on it inside a buffer.\n3. The StreamedResponse calls an anonymous function that reads and sends the file content using fread in 8kb chunks.\n4. After the first echo fread, the headers_list contains the Content-Type header with the value \"text/html\" and the headers are sent, invalidating the correct headers which were set for the response.\n\nNormally, calling send instead of sendContent on the StreamedResponse would allow the correct headers to be sent first, but the HLAPI needs the headers to remain unset until after it finished processing the request and executing the response middleware which adds required headers for CORS.\n\nOriginal response date: 2026-05-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4412490526, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24118#issuecomment-4412490526", "createdAt": "2026-05-09T12:13:19Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Fixed by #24183\n\nOriginal response date: 2026-05-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4468741064, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24118#issuecomment-4468741064", "createdAt": "2026-05-17T01:17:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24118, "url": "https://github.com/glpi-project/glpi/issues/24118", "author": "0nelight", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-03T20:28:58Z", "updatedAt": "2026-05-17T01:17:03Z", "closedAt": "2026-05-17T01:17:03Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Associating a document to another also associates the other document to itself", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAssociating an existing document A to another existing document B causes the document A to be associated to itself.\nNote: The document B also correctly gets associated to document A.\n\nAffected page:\n/front/document.form.php?id=B\n\nReproduction steps:\n1. Have (at least) 2 documents in \"Management > Documents\" (/front/document.php):\n * \"Quote A\" (/front/document.form.php?id=1)\n * \"Invoice B\" (/front/document.form.php?id=2)\n\n2. Open document \"Quote A\" (/front/document.form.php?id=1)\n3. Go to \"Documents\" tab\n4. Make sure document is not attached to any document (yet): the \"No results found\" text must be displayed.\n5. Open document \"Invoice B\" (/front/document.form.php?id=2)\n6. Go to \"Documents\" tab\n7. Make sure document is not attached to any document (yet): the \"No results found\" text must be displayed.\n8. Still on \"Documents\" tab for \"Invoice B\", in the \"Associate an existing document\" form, select \"Quote A\" document and click the \"Associate\" button.\n9. Get the confirmation notification \"Item successfully added: Document item - ID 2\"\n10. The attached document list (for \"Invoice B\") should now list \"Quote A\" document. 🟢\n11. Open document \"Quote A\" (/front/document.form.php?id=1)\n12. Go to \"Documents\" tab\n13. The attached document list (for \"Quote A\") is listing \"Quote A\" document (itself). ❌\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please test with changes proposed in #23873\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4249581057, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23844#issuecomment-4249581057", "createdAt": "2026-04-15T05:48:57Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "#23873 does fix the issue 👍\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4255298306, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23844#issuecomment-4255298306", "createdAt": "2026-04-15T20:38:22Z" } }, { "userEmail": "morgan.blair@peppermint.local", "text": "doesn't fix the issue.\nIf I associate an asset, it shows up correctly in the \"Associated items\". However, if I associate a document, it doesn't appear in the \"Associated items\". Instead, it gets placed in the \"Documents\" tab. This creates confusion because it mixes the linked documents with the actual original documents (files) of the item.\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4350100504, "author": "Ivanhoe81", "anonymizedAuthorEmail": "morgan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23844#issuecomment-4350100504", "createdAt": "2026-04-30T06:11:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "#23873 doesn't fix the issue. If I associate an asset, it shows up correctly in the \"Associated items\". However, if I associate a document, it doesn't appear in the \"Associated items\". Instead, it gets placed in the \"Documents\" tab. This creates confusion because it mixes the linked documents with the actual original documents (files) of the item.\n\nPlease open a new issue with all requested information.\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4350410449, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23844#issuecomment-4350410449", "createdAt": "2026-04-30T07:14:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23844, "url": "https://github.com/glpi-project/glpi/issues/23844", "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-13T11:29:53Z", "updatedAt": "2026-04-30T07:14:04Z", "closedAt": "2026-04-16T07:27:05Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Error CSS/Themes - Windows IIS", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nInstalación limpia en ISS con inconvenientes en el CSS/Temas.\nClean installation on IIS experiencing CSS/Theme loading issues.\n\n[Image omitted]\n\n[Image omitted]\n\nSe habilita \"modo depuración\" para registrar los errores. No se evidencia inconveniente, sin embargo en este modo los CSS/Temas cargan con normalidad.\nLog de errores de PHP sin registros.\n\nWhen debug mode is enabled to capture errors, the CSS/Themes load without problems. However, the PHP error log contains no entries.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jamie.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please write in English (automatic translations are OK).\n\nHaving issues reported all in English helps ensure that searching for existing/already reported issues is easier.\nAlso, the community and development team is international so having a common language helps us too.\n\nPor favor, escribe en inglés (se aceptan traducciones automáticas).\n\nInformar de los problemas en inglés facilita la búsqueda de problemas existentes o ya reportados.\nAdemás, la comunidad y el equipo de desarrollo son internacionales, por lo que tener un idioma común también nos ayuda.\n\nOriginal response date: 2026-04-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4346384752, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24068#issuecomment-4346384752", "createdAt": "2026-04-29T18:20:53Z" } }, { "userEmail": "robin.blair@peppermint.local", "text": "I have done the upgrade to and got the same problem.\nWindows server 2025 and IIS.\nUpgraded from a functioning 11.0.6 version.\n\nAll themes and boxes are a mess.\nCant create tickets becaus theres no box to type in. And the side panel to the right is loaded below and cant get ITL och user data.\n\n[Image omitted]\n\nBut everything seems to work as usual if debug mode is activated.\n\n[Image omitted]\n\nPersonal settings have the text outside its boxes.\n\n[Image omitted]\n\nOriginal response date: 2026-04-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4347375754, "author": "ToxicSmasher", "anonymizedAuthorEmail": "robin.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24068#issuecomment-4347375754", "createdAt": "2026-04-29T20:42:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This sounds like a cache issue; same issue as #24070\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4350016517, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24068#issuecomment-4350016517", "createdAt": "2026-04-30T05:52:44Z" } }, { "userEmail": "reese.blair@peppermint.local", "text": "I have the same problem and clean the cache don't resolve it\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4350288009, "author": "RegiloDeLaVega", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24068#issuecomment-4350288009", "createdAt": "2026-04-30T06:51:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24068, "url": "https://github.com/glpi-project/glpi/issues/24068", "author": "scmilhon", "anonymizedAuthorEmail": "jamie.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-04-29T18:10:36Z", "updatedAt": "2026-04-30T06:51:48Z", "closedAt": "2026-04-30T05:52:44Z" } }, { "title": "GLPI 11.0.x migration from genericobject to core - extreme increase in the size of the GLPI_LOG_DIR/php-errors.log file", "detail": "Issue description:\nDuring the migration from genericobject to core, GLPI logs a huge number of warnings:\n\nAs a result:\n... file/_log/php-errors.log ( GLPI_LOG_DIR.‘/php-errors.log’ )\nIt grows to astronomical sizes of tens of GB. (workaround - link this file to /dev/null during migration)\n\nFrom what I can tell, this log is hardcoded in the GLPI code, and I don’t see (is there no?) way to specify within GLPI itself what should be logged and what should be omitted in this file.", "priority": "medium", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Kind of duplicates #24007.\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4313523302, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24008#issuecomment-4313523302", "createdAt": "2026-04-24T13:24:05Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Skyler Adler Are you sure the RAM issue and the growing php-errors log file are the same thing?\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4313776669, "author": "Wolvverine", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24008#issuecomment-4313776669", "createdAt": "2026-04-24T14:03:45Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Maybe, maybe not. It depends on the full scope of the issue causing those warnings. I don't know how much help we can be with it either since the PHP script referenced is apparently one that you create yourself. At the very least we would need to know the content of the file around where the issue occurs.\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4313854501, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24008#issuecomment-4313854501", "createdAt": "2026-04-24T14:16:05Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Taylor Adler\nall is here:\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4314015426, "author": "Wolvverine", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24008#issuecomment-4314015426", "createdAt": "2026-04-24T14:41:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24008, "url": "https://github.com/glpi-project/glpi/issues/24008", "author": "Wolvverine", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-04-24T13:15:32Z", "updatedAt": "2026-04-24T14:44:52Z", "closedAt": "2026-04-24T13:24:05Z" } }, { "title": "RTL layout issues in 2FA TOTP inputs and Breadcrumb navigation", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen switching the interface language to an RTL language (e.g. Arabic), there are layout and behavior inconsistencies affecting both the 2FA TOTP input fields and the breadcrumb navigation.\n\n1. 2FA TOTP:\n- The first logical digit (digit 1 of 6) appears on the right side instead of the left.\n- Users naturally begin typing from the visually first field (rightmost in RTL).\n- The navigation logic appears to rely on DOM order (next() / prev()), which conflicts with the visual RTL layout and causes the rightmost field to be treated as the last one.\n- All input fields become disabled.\n- The user cannot correct or edit the entered code afterward.\nThis results in broken UX and prevents proper 2FA code entry in RTL languages.\n\n2. Breadcrumb navigation:\nIn RTL language mode, the breadcrumb separator is visually inverted.\nObserved:\nالرئيسية \\ المساعدة \\ تذاكر\n\nExpected:\nالرئيسية / المساعدة / تذاكر\n\nInstead of displaying the expected forward slash separator relative to reading direction.\nThis creates visual inconsistency in navigation compared to LTR mode and makes breadcrumb flow appear incorrect.", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue with the 2FA code entry. When in RTL mode when the page loads, the rightmost number input (which is read as the first one when sent to the server) is focused and typing or pasting a code properly fills from right to left.\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4215328143, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23232#issuecomment-4215328143", "createdAt": "2026-04-09T15:12:21Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Taylor Adler\nThanks for checking.\n\nI would like to clarify two important points:\n\n### 1. Numeric input direction (UX)\n\nEven in RTL languages like Arabic, numeric codes (such as OTP / 2FA) are always entered left-to-right (LTR).\n\nCurrently in RTL mode:\n- The inputs are visually arranged from right to left.\n- The first digit appears on the right side.\n- This is confusing because users expect to enter the code starting from the left, as with any numeric sequence.\n\n### 2. Actual blocking issue when typing from the left\n\nIn addition to the UX concern, there is a functional issue:\n\n- If the user starts entering the code from the leftmost field (as expected for numeric input),\n- The system immediately treats this field as the last one,\n- All input fields become disabled,\n- The user cannot correct or modify the code unless the page is refreshed.\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4234475879, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23232#issuecomment-4234475879", "createdAt": "2026-04-13T07:08:27Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Thank you. I wasn't aware numbers were read LTR even in RTL languages.\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4236113525, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23232#issuecomment-4236113525", "createdAt": "2026-04-13T11:44:44Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Thank you. I wasn't aware numbers were read LTR even in RTL languages.\n\nSame for me!\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4236175694, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23232#issuecomment-4236175694", "createdAt": "2026-04-13T11:56:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23232, "url": "https://github.com/glpi-project/glpi/issues/23232", "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "ui", "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-25T06:39:36Z", "updatedAt": "2026-04-15T05:47:57Z", "closedAt": "2026-04-15T05:47:57Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Missing attached document in followup notification", "detail": "Affected version:\n10.0.22\n\nIssue description:\nHi,\n\nVersion used : 10.0.22\n\nThe issue described bellow seems to have appeared since the version 10.0.21.\n\nWhen adding a reply with an attached document to a ticket, the notifcation sent doesn't add that document anymore as attached document in the mail.\n\nBut if we add another reply to that same ticket, the attached document will be finally attached in the next notification.\n\nReproduction steps:\n1. Go to a existant ticket\n2. Make a default reply and add a document\n3. Check the notification; that document will be missed", "priority": "medium", "type": "support", "createdByEmail": "reese.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.blair@peppermint.local", "text": "Could it be related to ?\n\nOriginal response date: 2026-01-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3734263656, "author": "cosmedd", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22595#issuecomment-3734263656", "createdAt": "2026-01-11T08:54:36Z" } }, { "userEmail": "reese.bennett@peppermint.local", "text": "Skyler Blair I confirm it seems to be the very same issue\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737377509, "author": "raymaill86", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22595#issuecomment-3737377509", "createdAt": "2026-01-12T08:27:13Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "Hi,\n\nWe upgraded to GLPI version 10.0.24 in order to fix the issue with sending email attachments. However, the problem is still not resolved.\n\nSometimes the attachments are correctly included in the email, but sometimes they are missing. In those cases, we have to reopen the ticket and recreate the solution so that the attachment is properly sent by email.\n\nThis issue is really problematic for us because we send resolutions to users who do not have direct access to GLPI.\n\nWe also noticed that this problem seems to occur only for email notifications sent to external users (users who do not have access to GLPI). They do receive the email, but the attachment is missing.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4029914794, "author": "xseth03", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22595#issuecomment-4029914794", "createdAt": "2026-03-10T09:30:57Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Do not comment on closed issues, open a new one with all requested information.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4029928335, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22595#issuecomment-4029928335", "createdAt": "2026-03-10T09:32:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22595, "url": "https://github.com/glpi-project/glpi/issues/22595", "author": "raymaill86", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-08T15:43:20Z", "updatedAt": "2026-03-10T09:32:53Z", "closedAt": "2026-01-12T08:33:28Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Error in ./src/CommonITILObject.php when creating a ticket with mandatory Group Technician or Technician field", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI When I create a new ticket using a template that includes the mandatory field \"Technician\" or \"Technician Group\", the following error appears.\n\nReproduction steps:\n1. Add mantatory field Technician or Group Technician to default template\n2. Open new ticket and fill in all required data", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Probably related to #22732\n\nOriginal response date: 2026-02-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3867385207, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23035#issuecomment-3867385207", "createdAt": "2026-02-08T15:15:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This is already fixed\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3869797151, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23035#issuecomment-3869797151", "createdAt": "2026-02-09T07:20:18Z" } }, { "userEmail": "quinn.blair@peppermint.local", "text": "I realise this was closed as a duplicate, but we are running 11.0.5 and I made the requester be a mandatory field. It crashed out making the ticket with the same error as what was originally posted.\n\nIf I take out the requester from being mandatory, it all works again\n\n[Image omitted]\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3988598694, "author": "mogzmogz", "anonymizedAuthorEmail": "quinn.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23035#issuecomment-3988598694", "createdAt": "2026-03-03T04:33:08Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Quinn Blair all is fixed for 11.0.6.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3989061614, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23035#issuecomment-3989061614", "createdAt": "2026-03-03T06:54:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23035, "url": "https://github.com/glpi-project/glpi/issues/23035", "author": "ahercon", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-02-06T08:57:52Z", "updatedAt": "2026-03-03T06:54:08Z", "closedAt": "2026-02-09T07:20:18Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Entity transfer does not update the entity in GLPI 11.0.2", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHello,\n\nI am encountering an issue in GLPI 11.0.2 when using the features “Add to a transfer list” and “Entity transfer.”\n\nThe transfer operation completes successfully without any error message, but the entity of the ticket does not change after the process.\n\nCould you please check this behavior?\nThank you!\n\nValentin\n\nReproduction steps:\nSteps to reproduce:\n\nSelect a ticket.\n\nChoose Add to a transfer list.\n\nPerform an Entity transfer on the ticket.\n\nThe action finishes successfully, but the entity remains unchanged.", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce. Try without plugins.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3570650715, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22047#issuecomment-3570650715", "createdAt": "2025-11-24T12:52:45Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "I do not reproduce. Try without plugins.\n\nI confirm we do not use any plugin. We migrated from GPLPI 10 and never expected this problem before.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3570659486, "author": "valentin-ibc", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22047#issuecomment-3570659486", "createdAt": "2025-11-24T12:55:02Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "I’m experiencing the same issue. From what I know, it started after we switched to 11.0.2 and still persists in 11.0.4. All plugins have been disabled.\n\nHere's my system info:\nGLPI version: 11.0.4\nOS: Ubuntu 22.04, PHP 8.5.0, MariaDB\nUser: Super-Admin, full permissions\nPlugins: All disabled\n\nTried:\nClean asset (no links, contracts, software)\nDifferent browsers, cleared cache/cookies\nChecked PHP session config and permissions\nGLPI cache cleared, Apache restarted\n\nError:\n“You don't have permission to perform this action. Return to previous page.”\nLogs show CSRF/session errors, no ACL errors\n\nCSRF/session errors:\n[2025-12-28 11:33:22] CSRF check failed for User ID: at /\nUser ID: Anonymous tried to execute an invalid request on /.\nBacktrace:\n./src/Session.php:1783\n...CheckCsrfListener.php:89 Session::checkCSRF()\n...EventDispatcher.php:260 Glpi\\Kernel\\Listener\\ControllerListener\\CheckCsrfListener->onKernelController()\n...\n\ntransfer.action.php failures\n[2025-12-28 21:05:25] User ID: 6 tried to execute an invalid request on /front/transfer.action.php.\nBacktrace:\n./front/transfer.action.php:49\n...LegacyFileLoadController.php:64 require()\n./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n...\n\nAny help will be much appreciated.\n\nOriginal response date: 2025-12-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3695092007, "author": "femachado", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22047#issuecomment-3695092007", "createdAt": "2025-12-28T22:14:43Z" } }, { "userEmail": "skyler.blair@peppermint.local", "text": "I’m experiencing the same issue. Do you know when the error will be fixed?\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3791596112, "author": "objectprogr", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22047#issuecomment-3791596112", "createdAt": "2026-01-23T18:10:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22047, "url": "https://github.com/glpi-project/glpi/issues/22047", "author": "valentin-ibc", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-11-24T12:27:57Z", "updatedAt": "2026-01-26T07:11:32Z", "closedAt": "2025-11-24T14:41:33Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Is setting a new directory location using variables functional in GLPI 11?", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nGood evening everyone, I decided to open this issue because I believe there is some inconsistency here in glpi 11, regarding changing the directory of the files, config, etc. folder from the default location to a new location, as the documentation recommends/suggests.\n\nWell, first let's look at the following:\n\nin GLPI 10, to point to a new directory for the files, for example, we know that there are two options: change the pointer in inc/based_config.php or create the downstream.php file pointing to the new path of the variables by creating local_define.php in /etc/glpi.\n\nSo far, so good.\n\nAs far as I have researched and am aware, GLPI 11 remains the same, except that the default file that used to be based_config.php is now another file called SystemConfigurator.php, located in /src/Glpi/Application.\n\nHowever, I noticed, for example, when changing the path of the files, whether pointing to the new SystemConfigurator.php file or creating downstream.php in /inc to point the files to /var/lib/glpi, it does not seem to work. I tested it on two GLPI versions 11.0.4, and both gave this error when pointing to the file directory, whether by default configuration or by downstream:\n\n[Image omitted]\n\nI followed the same procedures as in glpi 10 when there is interest in changing the default directory, even with revised permissions, etc., but there seems to be a problem.\n\nLogs: I did not find any relevant logs about this, and at the moment, glpi only returns to normal when I delete downstream.php from the inc folder or when I return the default directory to ‘/files’ in the SystemConfigurator.php file.\n\nI tested it in environments with Ubuntu 22/24, Apache, and PHP 8.2/PHP 8.4.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "I'm not sure if this is a bug, but I would appreciate some feedback because, following the documentation suggested since version 10, I haven't been able to reproduce the directory change functionality due to this issue. Thank you in advance!\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3894510153, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23103#issuecomment-3894510153", "createdAt": "2026-02-13T02:45:20Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Update: Guys, I did it! It seems like a simple thing, but I recreated downstream.php in /inc and then pointed to local_define in /etc/glpi, and it worked. Strange, because I compared it with the code in the documentation and it was the same haha.\n\nNow I'm just left with the following question: assuming I wanted to change the directory for the default file, how do I point to the default SystemConfigurator.php file that the files folder, for example, is a previous directory?\n\nIn version 10, based_config works fine when I leave it like this: ‘/../files’, but in glpi 11, when I do the same, it gives me a 500 error.\n\nJust let me know if I'm still doing it wrong. Pointing via downstream.php seems fine.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3894567966, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23103#issuecomment-3894567966", "createdAt": "2026-02-13T03:10:25Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Use inc/downstream.php to define a new config directory. Use local_define.php in your config directory for everything else.\n\nOriginal response date: 2026-03-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4135259979, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23103#issuecomment-4135259979", "createdAt": "2026-03-26T14:17:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23103, "url": "https://github.com/glpi-project/glpi/issues/23103", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-13T02:41:45Z", "updatedAt": "2026-07-05T00:53:42Z", "closedAt": "2026-03-26T14:17:08Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Rules for assigning permissions to a user", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nThe rules for assigning permissions to a user work in a somewhat random manner. For example, when I want to assign a default profile based on certain criteria, the same rule may work once, but when I delete my users and reimport them from LDAP, the rule no longer works.", "priority": "medium", "type": "support", "createdByEmail": "logan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "Here in my Lab 11.0.4 with AD connected, I was unable to reproduce the alleged problem. I created a rule to assign a profile to a specific entity, imported a user, and the rule worked. I deleted the user and re-imported it, and it worked. I deleted the user profile and synchronized it, and it also worked.\n\nAfter that, I changed the rule to include groups in the user registration, and it also worked for new imports.\n\nThe same applies when importing other users from the list, without any problems.\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3824982835, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22923#issuecomment-3824982835", "createdAt": "2026-01-30T18:05:00Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "General rule that uses the created LDAP directory as a criterion. In this example, I am associating a profile with a simplified interface, a specific entity, marking the user as active, and also associating a related test group.\n\n[Image omitted]\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3824995410, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22923#issuecomment-3824995410", "createdAt": "2026-01-30T18:07:48Z" } }, { "userEmail": "logan.bennett@peppermint.local", "text": "Thanks for your reply.\n\nThe problem was that in order for the default group rule to be taken into account, it already had to be assigned to a group.\n\nI have another issue. I assign a user to a subgroup via a rule. But I can't make that user responsible for that group. Is that normal?\n\nOriginal response date: 2026-02-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3829750473, "author": "r59g7z9yt7-ux", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22923#issuecomment-3829750473", "createdAt": "2026-02-01T00:10:15Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22923, "url": "https://github.com/glpi-project/glpi/issues/22923", "author": "r59g7z9yt7-ux", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-30T13:59:45Z", "updatedAt": "2026-05-14T00:59:55Z", "closedAt": "2026-02-02T06:57:29Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "The input is not a valid email address. Use the basic format local-part@hostname", "detail": "Affected version:\n10.0.17\n\nIssue description:\nI'm getting the error: Uncaught Exception Laminas\\Mail\\Exception\\InvalidArgumentException: The input is not a valid email address. Use the basic format local-part@hostname when the Collector Receiver try to read the mail in the mailbox.\n\nI review the followings tickets: and I found out that when there is an email in TO or CC that isn't in correctly format, the collector failed to add the follow-up, but it shouldn't happen the collector should bypass the incorrect email and just add the valid ones.\n\nI have this case:\n\nAnd the error logs in the next section", "priority": "medium", "type": "support", "createdByEmail": "micah.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "lane.blair@peppermint.local", "text": "Hi Skyler Adler, so this issue was resolved in the version 11.0.0? or which is the correct patch to apply?\nThanks!\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3488020069, "author": "martinaluna", "anonymizedAuthorEmail": "lane.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19037#issuecomment-3488020069", "createdAt": "2025-11-04T21:08:22Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This issue is still open, it's probably not fixed yet.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3489491313, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19037#issuecomment-3489491313", "createdAt": "2025-11-05T05:54:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi Skyler Adler, so this issue was resolved in the version 11.0.0? or which is the correct patch to apply? Thanks!\n\nWe did not found yet the time to fix it.\n\nIf you get this kind of invalid e-mail in your mailbox, you could try to find what application was used to sent it and report the issue to the application maintainer.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3489741722, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19037#issuecomment-3489741722", "createdAt": "2025-11-05T07:31:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 19037, "url": "https://github.com/glpi-project/glpi/issues/19037", "author": "jairockman", "anonymizedAuthorEmail": "micah.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-02-20T20:06:02Z", "updatedAt": "2026-04-23T00:50:57Z", "closedAt": "2026-01-12T09:04:23Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Automatic action doesn't work", "detail": "Affected version:\n11.0.1\n\nIssue description:\nqueuednotification automatic action doesn't work after upgrade from 10.0.18 to 11.0.1\n\nmode: CLI\nCrontab: */1 * * * * root php /var/www/html/glpi-cn/front/cron.php --allow-superuser", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jesse.bennett@peppermint.local", "text": "[Image omitted]\n\n[Image omitted]\n\nI upgrade on 10/26/2025, it works. after that, it doesn't work, I have to do it manual\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3455074731, "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21665#issuecomment-3455074731", "createdAt": "2025-10-28T08:02:56Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "root@AWHANSWEB01:~# php /var/www/html/glpi-cn/front/cron.php --allow-superuser --debug\n WARNING: running as root is discouraged.\n You should run the script as the same user that your web server runs as to avoid file permissions being ruined.\nExternal #1: Nothing to Launch\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3455136545, "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21665#issuecomment-3455136545", "createdAt": "2025-10-28T08:22:32Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "As described last message, if I run the command by manual in shell console, it took no effect although there are many items in the queue notification list.\nwhat's wrong? is it a bug or something wrong?\nThanks.\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3455433085, "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21665#issuecomment-3455433085", "createdAt": "2025-10-28T09:27:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21665, "url": "https://github.com/glpi-project/glpi/issues/21665", "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-28T07:54:19Z", "updatedAt": "2026-02-06T00:36:46Z", "closedAt": "2025-10-28T12:07:28Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "upgrade 10 to 11", "detail": "Affected version:\n11.0.0.1\n\nIssue description:\nI am migrating from the 10.0.20 version to the 11.0.0 version and further to the 11.0.1 version, but I encounter the following problem below the screenshot. the mail receiver section is also unavailable, and when I open this page, I receive the \"access error\" message\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI think you have just copied GLPI 11.0 files in the GLPI 10.0 directory. Some files were renamed and it results in duplicated code. You should delete the previous version source files before pushing the new version source files.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3397262336, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21447#issuecomment-3397262336", "createdAt": "2025-10-13T12:10:15Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The procedure for updating can be found here:\n\nOnly a few files/folders should be migrated between versions.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3397273558, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21447#issuecomment-3397273558", "createdAt": "2025-10-13T12:13:39Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "Yes, that's right, I did tar -xvzf glpi-*.tgz -C /var/www/glpi --strip-components 1\n\nthank you very much, It looks like I was inattentive, I'll give it a try and come back with feedback.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3397285851, "author": "Smiley-k", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21447#issuecomment-3397285851", "createdAt": "2025-10-13T12:17:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21447, "url": "https://github.com/glpi-project/glpi/issues/21447", "author": "Smiley-k", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-13T12:07:02Z", "updatedAt": "2026-01-22T00:34:29Z", "closedAt": "2025-10-13T12:46:03Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Incorrect relative time (\"weeks ago\") in Galician (gl_ES)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen using GLPI in Galician (gl_ES), the relative time displayed for items (e.g., \"fai X semanas\") is incorrect.\n\nExample:\n- Actual date: March 12, 2026\n- Current date: April 7, 2026\n- Expected: ~3–4 weeks ago\n- Displayed: \"fai 13 semanas\"\n\nComparison Screenshots:\n- English: ✅ correct\n[Image omitted]\n\n- Spanish: ✅ correct\n[Image omitted]\n\n- Galician: ❌ incorrect\n[Image omitted]\n\nReproduction steps:\n1. Set GLPI language to Galician (gl_ES)\n2. Create or view an item with a known timestamp\n3. Check the relative time display\n\nExpected behavior:\nRelative time should match the real difference (e.g., \"fai 3 semanas\")\n\nObserved behavior:\nRelative time is significantly incorrect (e.g., \"fai 13 semanas\")", "priority": "medium", "type": "support", "createdByEmail": "noel.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "If the issue is only on a specific language, this is certainly a translation issue. Translations are done on Transifex; you can fix there.\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4198497575, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23780#issuecomment-4198497575", "createdAt": "2026-04-07T11:03:52Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Transifex seems down for me but I confirm the translation has a \"1\" in front of the string placeholder when it shouldn't.\n\"fai 1%s semanas\"\nIt will need fixed on Transifex.\n\nEdit: There are other strings that have this \"1\" in front of the placeholder.\n\"fai 1%s minutos\", \"fai 1%s horas\", \"fai 1%s días\", \"fai 1%s semanas\", \"fai 1%s segundos\", \"fai 1%s meses\", and \"fai 1%s anos\".\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4198511641, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23780#issuecomment-4198511641", "createdAt": "2026-04-07T11:06:32Z" } }, { "userEmail": "kai.blair@peppermint.local", "text": "Hi,\n\nI confirm it is typo added to every relative date.\nThey should be fixed by now.\n\nRegards\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4198744888, "author": "OscarBeiro", "anonymizedAuthorEmail": "kai.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23780#issuecomment-4198744888", "createdAt": "2026-04-07T11:52:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23780, "url": "https://github.com/glpi-project/glpi/issues/23780", "author": "bcervinho", "anonymizedAuthorEmail": "noel.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-04-07T11:00:53Z", "updatedAt": "2026-07-17T00:43:34Z", "closedAt": "2026-04-07T11:03:52Z" } }, { "title": "Assets - Computers - Volumes Free Percentage only shows the percentage of the first disk", "detail": "Affected version:\n10.0.19\n\nIssue description:\nOn the main dashboard, when I add the Volumes - Free Percentage, it only displays the free percentage of the first disk, as shown in the image below\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "devon.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The issue is not present in GLPI 11.x\n\nWell present in GLPI 10.x\n\n[Image omitted]\n\nTo reproduce just create 2 volumes with for example the first one with only a few remaining space.\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3627608682, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20699#issuecomment-3627608682", "createdAt": "2025-12-08T15:47:34Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The issue is not present in GLPI 11.x\n\nWell present in GLPI 10.x\n[Image omitted]\n\nTo reproduce just create 2 volumes with for example the first one with only a few remaining space.\n\nOriginal issue reported in on the computer serach results, not in a tab.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630813563, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20699#issuecomment-3630813563", "createdAt": "2025-12-09T07:40:52Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Original issue reported in on the computer serach results, not in a tab.\n\nYes it's the first part of the screenshot ;) just been a bit too cropped.\nBut yes we can see that the listing is showing 5% (that is the value of C) instead of the global free percentage\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3631173516, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20699#issuecomment-3631173516", "createdAt": "2025-12-09T09:16:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20699, "url": "https://github.com/glpi-project/glpi/issues/20699", "author": "CPMurilo87", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-08-18T21:26:29Z", "updatedAt": "2026-07-09T00:48:48Z", "closedAt": "2026-03-30T07:45:57Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Creating A Problem from computer leads to error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nCreating a Problem from a computer object leads to an error.\n\nSee also #23111\n\nReproduction steps:\n1: Go to a computer object\n2. Choose Problem Tab\n3. press create new problem button\n4. fill in title and decription\n5. press save", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Could you test the changes in\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4004833051, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23369#issuecomment-4004833051", "createdAt": "2026-03-05T12:49:59Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I tested the commit and it works\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4005159347, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23369#issuecomment-4005159347", "createdAt": "2026-03-05T13:44:35Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "fixed by #23371\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4139217610, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23369#issuecomment-4139217610", "createdAt": "2026-03-27T00:32:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23369, "url": "https://github.com/glpi-project/glpi/issues/23369", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-05T10:59:20Z", "updatedAt": "2026-07-05T00:53:27Z", "closedAt": "2026-03-27T00:32:58Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Icon above text in create new group form", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen the option to create a new group is opened, the icon is above the text.\n\n[Image omitted]\n\nThe language of GLPI doesn't matter.", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This seems to be fixed on current 11.0/bugfixes branch (tested on firefox and chromium):\n\n[Image omitted]\n\nPlease try with a recent nightly build.\n\nOriginal response date: 2026-01-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3803427695, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22840#issuecomment-3803427695", "createdAt": "2026-01-27T06:51:47Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "continues in the last release 11.0.5\n\n[Image omitted]\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3812023784, "author": "CYAsistemas", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22840#issuecomment-3812023784", "createdAt": "2026-01-28T15:38:41Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "OK, I confirm; when it's opened in a modal. I do not have fix.\n\nOriginal response date: 2026-01-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3815890444, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22840#issuecomment-3815890444", "createdAt": "2026-01-29T07:11:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22840, "url": "https://github.com/glpi-project/glpi/issues/22840", "author": "CYAsistemas", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-26T18:39:58Z", "updatedAt": "2026-07-04T00:48:56Z", "closedAt": "2026-03-25T07:55:19Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "[11.0] Changing a ticket category don't change the ticket template", "detail": "Affected version:\n11.0.x-dev\n\nIssue description:\nAfter creating a ticket, if you change it's category the template linked to it is not updated.\n\nMaking some fields not visible for example.\n\nNo issue in GLPI 10.x\n\nMaybe it's the desired behavior but I found weird that if we change the category we don't follow anymore the new category templating rule (and no way to change the current ticket template so)\n\nReproduction steps:\n1. Create a ticket using a category with a template that hide Urgency/Impact field.\n2. Change the create ticket category to another one that has nothing hidden\n3. The field are still hidden, in the Ticket table the tickettemplates_id is still linked to one that was present originally", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.blair@peppermint.local", "text": "I have the same problem but with a different field; when I change the category, the template doesn't apply to the ticket.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4031989016, "author": "JeremieMercier", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22316#issuecomment-4031989016", "createdAt": "2026-03-10T14:46:47Z" } }, { "userEmail": "logan.blair@peppermint.local", "text": "Same problem here, have my ITIL Categories set up, my templates for each category predefining fields such as impact or description but when selected from the Self Service the ticket template does not apply changes.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4041207372, "author": "Pasdian", "anonymizedAuthorEmail": "logan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22316#issuecomment-4041207372", "createdAt": "2026-03-11T18:21:13Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Fixed by\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4073759258, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22316#issuecomment-4073759258", "createdAt": "2026-03-17T10:05:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22316, "url": "https://github.com/glpi-project/glpi/issues/22316", "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-10T08:53:25Z", "updatedAt": "2026-06-26T01:05:49Z", "closedAt": "2026-03-17T10:05:25Z" }, "assignedTo": "jordan.blair@peppermint.local" }, { "title": "Ticket editor toolbar still visible after ticket edition aborting", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen \"Rich text field layout\" is set to \"Classic (toolbar on top)\", if you edit a ticket, make appear the editor toolbar and abort the edition, the toolbar is still visible.\n\nDiagnostic information:\nAs the toolbar is still visible and you click on its tools, you'll see errors in browser console when you enable browser developer tools with F12.\n\nReproduction steps:\n1. Check you have \"Rich text field layout\" set to \"Classic (toolbar on top)\" in the Personalization section in \"My settings\" or globally:\n [Image omitted]\n2. Edit a ticket follow up:\n [Image omitted]\n3. Make text editor toolbar appears clicking on the 3 dots:\n [Image omitted]\n4. Abort ticket edition by clicking on the follow up upper right cross:\n [Image omitted]\n5. See the toolbar remains visible and active:\n [Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This was fixed in 11.0.6 by #23250. There was then a bug that caused modals to appear any time you clicked on the page depending on the TinyMCE content, which was fixed yesterday with #23418\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4030334563, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23432#issuecomment-4030334563", "createdAt": "2026-03-10T10:29:48Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi Taylor Adler\n\njust applying the 2 fixes on my 10.0.5 test instance is not sufficient to fix my issue. Are you sure this is not another problem ? Or do you see something else I can update ?\n\nI'll test on a glpi 10.0.6 this afternoon anyway.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4030421242, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23432#issuecomment-4030421242", "createdAt": "2026-03-10T10:41:13Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "😕 Indeed, there is *another* bug with this overflow menu not closing.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4030467548, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23432#issuecomment-4030467548", "createdAt": "2026-03-10T10:47:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23432, "url": "https://github.com/glpi-project/glpi/issues/23432", "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-10T10:18:49Z", "updatedAt": "2026-06-20T01:05:51Z", "closedAt": "2026-03-11T08:50:13Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "[LegacyApi][TicketValidation] Status not changing", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHi,\nI have found some report for this issue using the High level Api, which seems to be resolved according to the issue status and change log, but the issue still remains on legacy Api.\n\nWhile trying the new version of GLPI on a dev environment, I encountered an issue with the LegacyApi.\nI do not know if I'm able to form an issue about this since it is in fact \"Legacy\", but it should work same as before ?\n\nI created a Ticket using the interface, asked for an approval to a random user and tried to use the Api (which worked before) to change du status of the approval request.\nThe return from the LEGACY Api is :\n\n[\n {\n \"13466\": true,\n \"message\": \"\"\n }\n]\n\nfor the input :\n\n{\n \"input\": {\n \"id\": 13466,\n \"itils_validationsteps_id\": 11579,\n \"entities_id\": 3,\n \"users_id\": 7146,\n \"tickets_id\": 59168,\n \"users_id_validate\": 7146,\n \"itemtype_target\": \"User\",\n \"items_id_target\": 5245,\n \"itilvalidationtemplates_id\": 0,\n \"comment_submission\": \"tesat\",\n \"comment_validation\": \"tesat\",\n \"status\": 3,\n \"submission_date\": \"2026-02-11 16:55:31\",\n \"validation_date\": \"2026-02-11 16:55:31\",\n \"timeline_position\": 1,\n \"last_reminder_date\": null\n }\n}\n\nI tried this input on both URL that seems to work for me to use the LegacyApi :\n- \"\"\n- \"\"\nBut the status remain unchanged.\nI can't change the field \"validation_date\" or \"comment_validation\" either.\n\nReproduction steps:\n1. Install or update your Glpi to latest version\n2. Open legacy Api and setup a user which has access to ticket and TicketValidation Items\n3. Create a ticket and add an approval request\n4. Try to change the approval status with the\n\nAdditional context:\nSorry if you do not take bug reports for the Legacy Api, I tried to search for an information about reporting bugs for Legacy Api, but did not find any.", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Only the user that is being asked to answer the approval can change the status, approval comment and approval date. This is checked inside the CommonITILValidation::prepareInputForUpdate method and therefore applies to the web UI, legacy API and new API. The change you saw for the High-Level API was likely in reference to supporting the format status: {id: 2} in addition to status: 2 for dropdown fields.\n\nCan you confirm if the API user is the same as the one asked to answer the approval?\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993547874, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23218#issuecomment-3993547874", "createdAt": "2026-03-03T21:08:20Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "The Api user is (and always was) a generic user which will change the approval status.\nThe approval is directed to the user who makes the api call and we have the authorisation handled manually on our end. Later the action is made in GLPI using a generic user.\n\nWe could do it that way before the glpi Upgrade, is that a new change ?\nIs there any Work Around to keep my API the way it is ?\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4023250831, "author": "Tarru", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23218#issuecomment-4023250831", "createdAt": "2026-03-09T11:59:17Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "That isn't a supported use case at the moment, and unfortunately the legacy API has no compatibility promise/versioning because it is very closely tied to the internal logic of GLPI. That is why we made a new API that had more separation from the internal logic, but it still doesn't let you bypass permission restrictions.\n\nIt is not desired for users to be able to answer approval requests that were not asked of them and neither API is meant to allow bypassing permission checks. This is part of the reason why there is no support for the client credentials grant in the new API as it is not tied to an actual user.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4023483857, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23218#issuecomment-4023483857", "createdAt": "2026-03-09T12:42:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23218, "url": "https://github.com/glpi-project/glpi/issues/23218", "author": "Tarru", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "api", "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-24T09:46:57Z", "updatedAt": "2026-06-18T01:10:31Z", "closedAt": "2026-03-09T12:42:03Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "can't use api to add service levels with specific time like 2026-01-26 18:59:29 for ticket", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nI want to use api add a TTR time for ticket to record a expected completion time,like UI\n\n[Image omitted]\nbut api doc only had this args\n\"sla_ttr\": {\n \"id\": 0\n },\n \"sla_tto\": {\n \"id\": 0\n },\n \"ola_ttr\": {\n \"id\": 0\n },\n \"ola_tto\": {\n \"id\": 0\n },\n \"sla_level_ttr\": {\n \"id\": 0\n },\n \"ola_level_ttr\": {\n \"id\": 0\n },\n\nAffected page:\n/Assistance/Ticket/{id}", "priority": "medium", "type": "support", "createdByEmail": "kendall.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It seems like the properties relating to these dates are readOnly at the moment in the API and one may be missing too.\nThe available readonly properties for these are internal_resolution_date, internal_take_into_account_date, and resolution_date. These will need to have the readOnly flags removed and a new property for take_into_account_date will need added.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3799425397, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22834#issuecomment-3799425397", "createdAt": "2026-01-26T12:42:53Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "Can these fields be edited through the API in the future, and are there any recent plans or arrangements.thanks\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3799475118, "author": "xiahan0406-han", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22834#issuecomment-3799475118", "createdAt": "2026-01-26T12:55:45Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "This will be fixed in the 2.3 version of the API. It *should* be released in GLPI 11.0.7.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4027194647, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22834#issuecomment-4027194647", "createdAt": "2026-03-09T22:03:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22834, "url": "https://github.com/glpi-project/glpi/issues/22834", "author": "xiahan0406-han", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-26T11:43:11Z", "updatedAt": "2026-06-18T01:10:20Z", "closedAt": "2026-03-09T22:03:35Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Unexpected error on ticket preview", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nReproduction steps:\n1. Notifications > Templates\n2. Tickets\n3. Default Translation\n4. Preview\n5. Any ticket, any event gets the error", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please provide the full error you are getting from the PHP errors log file (files/_log/php-errors.log).\n\nOriginal response date: 2026-02-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3927589335, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23180#issuecomment-3927589335", "createdAt": "2026-02-19T14:18:34Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "glpi.CRITICAL: * Uncaught PHP Exception ValueError: \"Unknown format specifier \"i\"\" at NotificationTargetTicket.php line 72\n Backtrace :\n ./src/NotificationTargetTicket.php:72\n ./src/NotificationTargetTicket.php:72 sprintf()\n ./src/NotificationTemplate.php:289 NotificationTargetTicket->getSubjectPrefix()\n ./src/NotificationTemplateTranslation.php:489 NotificationTemplate->getTemplateByLanguage()\n ./src/NotificationTemplateTranslation.php:422 NotificationTemplateTranslation->showPreview()\n ./src/CommonGLPI.php:740 NotificationTemplateTranslation::displayTabContentForItem()\n ./ajax/common.tabs.php:108 CommonGLPI::displayStandardTab()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:71 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\nOriginal response date: 2026-02-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3933659071, "author": "pedroalves5770", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23180#issuecomment-3933659071", "createdAt": "2026-02-20T12:00:28Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Closing this issue because I found out it was a configuration error on my side, not a bug in the code. I used an incorrect format specifier (%i instead of %d) in my entity settings.\n\nSorry for the inconvenience!\n\nOriginal response date: 2026-02-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3933985649, "author": "pedroalves5770", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23180#issuecomment-3933985649", "createdAt": "2026-02-20T12:31:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23180, "url": "https://github.com/glpi-project/glpi/issues/23180", "author": "pedroalves5770", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-19T14:15:44Z", "updatedAt": "2026-06-01T01:10:01Z", "closedAt": "2026-02-20T12:31:22Z" } }, { "title": "Err 500 when trying to view an opened ticket in 11.0.5", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nFor a single ticket (opened by a mailgate, after the upgrade to 11.0.5), I can't open the main window with all the followups, I get a 500 err. Can't say for sure if it it existed before (but I never encountered this issue in previous versions). Not sure either if there's something specific about the content of this ticket (I'll try to take a look at the content in the DB)\n\nReproduction steps:\n1. Try the open the ticket (/front/ticket.form.php?id=xxxxx)\n2. See \"An error occurred\" message in red instead of the title/description/followups", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "noel.bennett@peppermint.local", "text": "The issue was du to a ~320KB inline image (as GLPI object\n\nother questions with conditional visibility of response on first question.\n\nSave.\n\nIn other computer, go back on the form, and just modify title of question 2 and save. And you lose all conditional visibility (and i lose hours and hours) It's very hard to work with this form.\n\nPlease stop close ticket, it's not resolve", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "The fix is not included in GLPI 11.0.4, you need to wait for 11.0.5:\n\n[Image omitted]\n\nIt will be released next week on the 28th of January.\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3778547364, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22745#issuecomment-3778547364", "createdAt": "2026-01-21T14:52:49Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Reopen asked by requeter; I did not check anything.\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3782955830, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22745#issuecomment-3782955830", "createdAt": "2026-01-22T07:31:53Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "It's work in 11.0.5, big thx !\n\nYou can close the issue!\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3870717235, "author": "TxX8N8LN", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22745#issuecomment-3870717235", "createdAt": "2026-02-09T10:06:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22745, "url": "https://github.com/glpi-project/glpi/issues/22745", "author": "TxX8N8LN", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-20T08:56:23Z", "updatedAt": "2026-05-21T01:03:27Z", "closedAt": "2026-02-09T10:11:58Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Bug: Mail Collector queue gets blocked by non-UTF-8 email content", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen collecting emails using Mail Collector, GLPI may stop processing the mailbox entirely if an email contains non-UTF-8 encoded characters (e.g. Latin-1 / ISO-8859-1).\n\nIf such an email is encountered, ticket creation fails due to a database encoding error, and the problematic email is never marked as processed. As a result, the Mail Collector continuously retries the same message and the mailbox queue becomes blocked, preventing all subsequent emails from being processed.\n\nThis leads to a complete halt of ticket creation via email until manual intervention is performed.\n\n[Image omitted]\n\nI isolate this bloque code in try...catch in Mailcollctor.php to jump to next mail, worked.\n\nJobs do Utimer Conferidos no Turno Matutino.eml\n\n[Image omitted]\n\nthe .EML I sent is working I edited it. The original not woking. I cant send the original\n\nReproduction steps:\nConfigure a Mail Collector\nSend an email with:\n\n- Charset ISO-8859-1 or Windows-1252\n- Accented characters in the email body (e.g. Américo, ação, informação)\n\nRun the Mail Collector\nTicket creation fails with a MySQL encoding error\nThe same email is retried indefinitely and new emails are no longer processed", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide EML file we can use to reproduce and add test case.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3872432125, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23058#issuecomment-3872432125", "createdAt": "2026-02-09T15:29:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "For windows 1252, this is probably a duplicate of #22997. ISO-8859-1 should work.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3872455123, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23058#issuecomment-3872455123", "createdAt": "2026-02-09T15:33:36Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "I tryed the file in #22997 the result was the same.\n\nI cant share the eml, if I edit the file the error desapear\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3872843760, "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23058#issuecomment-3872843760", "createdAt": "2026-02-09T16:52:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23058, "url": "https://github.com/glpi-project/glpi/issues/23058", "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-02-09T15:26:37Z", "updatedAt": "2026-05-21T01:03:21Z", "closedAt": "2026-02-09T22:34:33Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Problem with adding Linked assistance object ( ticket )", "detail": "Affected version:\n11.0.1\n\nIssue description:\nIn ticket window when we try to link this tickets together with another one through \"Link assistance object\" we can only select tickets from main entity ( organization) . We cant see any other tickets which are located in subentities.\nEven when we are working in specific subentity and we want Link assistance object ( ticket) from the same subentity we cannot see it.\n\nAdditional context:\nwe checked all permissions . we are trying on super-admin profile (with all permissions) and any other profile.", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Hello, did you verified you are in that subentity context ?\n\nMenu > Root entity > {Select your subentity}\n\n[Image omitted]\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3455569090, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21545#issuecomment-3455569090", "createdAt": "2025-10-28T10:00:30Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Hi,\nThe patch worked in 11.0.4 but not anymore in 11.0.5.\nWe cannot link anymore tickets between them if not in root entity.\nThanks\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3822746758, "author": "InformatiqueOLLN", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21545#issuecomment-3822746758", "createdAt": "2026-01-30T09:31:29Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Hello, the patch you saw, I guess based on the PR has now changed and you should look at\n\nOriginal response date: 2026-02-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3835460612, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21545#issuecomment-3835460612", "createdAt": "2026-02-02T14:27:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21545, "url": "https://github.com/glpi-project/glpi/issues/21545", "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [ { "sourceLogin": "froozeify", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-20T08:49:56Z", "updatedAt": "2026-05-17T01:00:09Z", "closedAt": "2026-02-05T13:52:49Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Login Events in Event log without user name", "detail": "Affected version:\n11.0.4\n\nIssue description:\nThe login event entries in the event log are missing the account names in GLPI Version 11.0.4. This was working with GLPI 10.0.22 as shown with older event entries in the database/event log.\n\nVersion 11.0.4 entries:\n[Image omitted]\n\nVersion 10.0.22 entries:\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot reproduce the bug with simple login or with MFA.\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3768972941, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22571#issuecomment-3768972941", "createdAt": "2026-01-19T15:44:51Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I had the problem once on my instance; but after a fatal error on login (no idea why, I did not reproduce after that, and my instance is a dev one, not so stable). Other attemps were all OK:\n\n[Image omitted]\n\nOf course, I've only tried with local database connection, no LDAP, MFA, plugin or so.\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3771454562, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22571#issuecomment-3771454562", "createdAt": "2026-01-20T07:37:36Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No feedback, I close\n\nOriginal response date: 2026-02-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3839597099, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22571#issuecomment-3839597099", "createdAt": "2026-02-03T07:33:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22571, "url": "https://github.com/glpi-project/glpi/issues/22571", "author": "AndiMb", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-06T07:24:13Z", "updatedAt": "2026-05-15T00:57:17Z", "closedAt": "2026-02-03T07:33:33Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Problem when transferring a computer to another entity", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.04\n\nIssue description:\nChanging the entity on computers does not work. I go to the Computers menu, select the items using the checkboxes, then go to “Actions” → “Add to transfer list” with the transfer mode set to “complete.” Then, i select the target entity, run the process, and it indicates \"Operation successful\". However, the computers have not changed entity.", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Make sure to test without any plugins, and with debug mode enabled.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798363112, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22823#issuecomment-3798363112", "createdAt": "2026-01-26T08:18:31Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "The execution of the plugins is correctly suspended. I ran the operation again in debug mode and encountered an SQL error:\n\nMySQL query error: Duplicate entry 'Computer-46-12186' for key 'unicity' (1062) in SQL query \"UPDATE glpi_items_softwareversions SET softwareversions_id = '12186' WHERE id = '18543'\". in ./src/DBmysql.php at line 392\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3799101575, "author": "chguigoz59", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22823#issuecomment-3799101575", "createdAt": "2026-01-26T11:28:43Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Issue has already been reported\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3799440929, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22823#issuecomment-3799440929", "createdAt": "2026-01-26T12:46:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22823, "url": "https://github.com/glpi-project/glpi/issues/22823", "author": "chguigoz59", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-26T08:14:59Z", "updatedAt": "2026-05-07T00:55:12Z", "closedAt": "2026-01-26T12:46:32Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Missing _filled_ tabler icons", "detail": "Affected version:\nmain\n\nIssue description:\nTabler icon suffixed _-filled_ are not valid anymore.\nI tried without success to fix it.\n\n[Image omitted]\n\nAffected page:\n/front/ruleticket.php\n\nReproduction steps:\ngo to one of rules list, status icon are missing.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Note: looks like this problem exists with latest tabler version, and is resolved with the previous one. That won't be the first time one of their release breaks something on our side; maybe just reverting for now is OK (unless we really need the latest version, which I doubt).\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3742146795, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22634#issuecomment-3742146795", "createdAt": "2026-01-13T06:10:30Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Check upstream:\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3743347766, "author": "orthagh", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22634#issuecomment-3743347766", "createdAt": "2026-01-13T09:56:35Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This has been fixed, and is now tested\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3788545656, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22634#issuecomment-3788545656", "createdAt": "2026-01-23T06:33:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22634, "url": "https://github.com/glpi-project/glpi/issues/22634", "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-12T15:53:14Z", "updatedAt": "2026-05-04T00:55:43Z", "closedAt": "2026-01-23T06:33:53Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI 11.0.4 - Saved Searches No Longer Retain Ticket Count Display After Upgrade (11.0.2 → 11.0.3 / 11.0.4)", "detail": "Affected version:\n11.0.4\n\nIssue description:\nAfter upgrading GLPI from version 11.0.2 to 11.0.3, and then to 11.0.4, we noticed a regression affecting the display of Saved Searches in the ticket module.\n\nPreviously, the saved searches displayed the ticket counters normally (e.g., \"My tickets (20)\", \"Unresolved tickets (213)\", etc.).\nHowever, starting from version 11.0.3, the counters no longer remain visible. Instead, GLPI automatically replaces them with the message:\n[Image omitted]\n\n[Image omitted]\n\nThis behavior did not occur in any previous version, including 11.0.2.\nThe issue happens even for simple or lightweight saved searches that have always displayed counters correctly until now.\n\nExpected behavior:\nSaved searches should continue to display their ticket counts, as they did in versions ≤ 11.0.2.\n\nObserved behavior:\nAll saved searches lose their counters.\n\nGLPI automatically replaces the counter with the “too heavy” warning, even for basic searches that previously worked without issue.\n\nReproduction steps:\n1. Upgrade GLPI from 11.0.2 → 11.0.3 → 11.0.4.\n2. Go to Tickets > Saved Searches.\n3. Observe that ticket counters are no longer displayed.\n4. The warning message appears even on lightweight searches.", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "dakota.bennett@peppermint.local", "text": "Usually, when this icon appears, we simply click the saved search once to initialize the counter, and it then remains displayed even when switching searches. Since the update, this no longer works.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612656341, "author": "OteJlo", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22244#issuecomment-3612656341", "createdAt": "2025-12-04T14:56:50Z" } }, { "userEmail": "riley.blair@peppermint.local", "text": "Same issue here !\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3613914580, "author": "GeistFighter", "anonymizedAuthorEmail": "riley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22244#issuecomment-3613914580", "createdAt": "2025-12-04T19:05:43Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm. The issue seems to be with a loose comparison when a search query executes in less than 1ms. A cast to int converts any float value between 0 and 1 (exclusive) to 0 and a loose comparison with null makes GLPI treat these fast searches as if the last execution time was not recorded yet.\n\nOriginal response date: 2025-12-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3694866582, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22244#issuecomment-3694866582", "createdAt": "2025-12-28T16:26:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22244, "url": "https://github.com/glpi-project/glpi/issues/22244", "author": "OteJlo", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-04T14:53:59Z", "updatedAt": "2026-04-16T00:51:14Z", "closedAt": "2026-01-05T10:17:18Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Error when deleting an asset created through Asset Definition", "detail": "Affected version:\n11.0.4\n\nIssue description:\n1.Created a test asset.\n2.I tried to delete it\n3.I got an error\n\nReproduction steps:\n1.Created a test asset.\n2.I tried to delete it\n3.I got an error\n\nEnvironment details:\nPlugins listfields Name: Additional fields Version: 1.23.1 State: Включен Install\nMethod: Marketplace\nadvancedplanning Name: advancedplanning Version: 1.1.1 State: Установлен / не активирован Install Method:\nMarketplace\narchisw Name: Apps structures Version: 3.0.24 State: Установлен / не активирован Install Method:\nMarketplace\narchibp Name: Business Processes Version: 2.0.13 State: Установлен / не активирован Install Method:\nMarketplace\npositions Name: Cartography Version: 7.0.2 State: Включен Install\nMethod: Marketplace\nconnections Name: Connections Version: 10.0.0 State: Установлен / не активирован Install Method:\nMarketplace\narchimap Name: Diagrams Version: 3.3.8 State: Включен Install\nMethod: Marketplace\nformcreator Name: Form Creator Version: 2.13.10 State: Установлен / не активирован Install Method:\nMarketplace\narchifun Name: Functional Areas Version: 2.3.2 State: Установлен / не активирован Install Method:\nMarketplace\ngenericobject Name: Generic Objects End-of-Life Up Version: 3.0.2 State: Установлен / не активирован Install Method:\nMarketplace\nglpiinventory Name: GLPI Inventory Version: 1.6.4 State: Включен Install\nMethod: Marketplace\naddressing Name: IP Addressing Version: 3.1.1 State: Включен Install\nMethod: Marketplace\nstatecheck Name: Statecheck Rules Version: 2.4.7 State: Установлен / не активирован Install Method:\nMarketplace\ntag Name: Tag Management Version: 2.14.2 State: Включен Install\nMethod: Marketplace\nuseditemsexport Name: Used items export Version: 2.5.2 State: Установлен / не активирован Install Method:\nMarketplace\nwebresources Name: Web Resources Version: 2.0.4 State: Не установленный Install Method:\nMarketplace\nadditionalalerts Name: Другие уведомления Version: 2.4.0 State: Не установленный Install Method:\nMarketplace\nnews Name: Оповещения Version: 1.12.5 State: Установлен / не активирован Install Method:\nMarketplace\npdf Name: Печать в PDF Version: 4.0.2 State: Установлен / не активирован Install Method:\nMarketplace\nmreporting Name: Подробные отчеты Version: 1.8.9 State: Установлен / не активирован Install Method:\nMarketplace", "priority": "medium", "type": "support", "createdByEmail": "remy.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "remy.bennett@peppermint.local", "text": "It is noticed that the error starts when the created asset has something selected on the \"Capacities\" tab. I tried it with \"Impact analysis\" enabled.\n\nI also noticed that my errors start the moment I turn on Impact analysis and click Save, and the same thing happens when I remove it and click save.\n\nOriginal response date: 2025-12-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3623203029, "author": "rean1mat0r", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22277#issuecomment-3623203029", "createdAt": "2025-12-07T20:33:46Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Just tested, I cannot reproduce.\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3625279320, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22277#issuecomment-3625279320", "createdAt": "2025-12-08T06:48:59Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I could see how this issue could occur if something modified the \"impact_enabled_itemtypes\" config value with a value with keys. Probably an issue with a plugin. The json_decode call does not force decoding it as an associative array, so it that case it would default to a stdClass.\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696502506, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22277#issuecomment-3696502506", "createdAt": "2025-12-29T13:20:24Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22277, "url": "https://github.com/glpi-project/glpi/issues/22277", "author": "rean1mat0r", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-07T20:26:38Z", "updatedAt": "2026-04-16T00:51:05Z", "closedAt": "2026-01-05T10:32:26Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "[11.0.4] field \"glpi object\" in forms", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHi,\n\ni have a form that integrate a field to choose a glpi object that point to application.\nWhen i see the preview of the form, i can see the dropdown field with all my application.\nBut in self service profile my users see an empty dropdown.", "priority": "medium", "type": "support", "createdByEmail": "emerson.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.blair@peppermint.local", "text": "Check assets in the self-service profile to see if the object has read access assigned\n\n[Image omitted]\n\nOriginal response date: 2025-12-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3665443845, "author": "willysaurio", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22348#issuecomment-3665443845", "createdAt": "2025-12-17T13:49:53Z" } }, { "userEmail": "micah.blair@peppermint.local", "text": "or check this\n\n[Image omitted]\n\nOriginal response date: 2025-12-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3665504251, "author": "willysaurio", "anonymizedAuthorEmail": "micah.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22348#issuecomment-3665504251", "createdAt": "2025-12-17T14:01:56Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "You'll also need to check this setting:\n\n[Image omitted]\n\nBy default, self service users are only allowed to see their own items.\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3674594812, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22348#issuecomment-3674594812", "createdAt": "2025-12-19T10:54:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22348, "url": "https://github.com/glpi-project/glpi/issues/22348", "author": "cyrakuse", "anonymizedAuthorEmail": "emerson.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-12T10:10:12Z", "updatedAt": "2026-04-09T00:37:31Z", "closedAt": "2025-12-29T12:25:39Z" } }, { "title": "License expiration alert not working", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHello,\n\nEnabled Licenses expiration alert before 30 days:\n[Image omitted]\n\nEnabled Automatic action:\n[Image omitted]\n\nConfigured Notification and recipients:\n[Image omitted]\n\n[Image omitted]\n\nCreated Test license:\n\n[Image omitted]\n\nWhen exciting nothing happening:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please test again with the license associated with a software.\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3687251730, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22468#issuecomment-3687251730", "createdAt": "2025-12-23T16:32:24Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Oh. Yes, when it's assigned to software it works. Thank you.\nSo it's not possible to get alert if it's not assigned to software?\n\nOriginal response date: 2025-12-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3694812871, "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22468#issuecomment-3694812871", "createdAt": "2025-12-28T15:07:02Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Oh. Yes, when it's assigned to software it works. Thank you. So it's not possible to get alert if it's not assigned to software?\n\nNo. It only looks for licenses linked to software and the software it is linked to cannot be a template or in the trash.\n\nOriginal response date: 2025-12-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3694819288, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22468#issuecomment-3694819288", "createdAt": "2025-12-28T15:16:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22468, "url": "https://github.com/glpi-project/glpi/issues/22468", "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-22T16:13:24Z", "updatedAt": "2026-04-08T00:44:48Z", "closedAt": "2025-12-28T15:16:16Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Can not change the Start date of task since GLPI 11.0.4", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen i try to update the Start date of task, i have this error\n\n[Image omitted]\n\nAlso, a error appear when i active the debug mode\n\n[Image omitted]\n\nI cleared the cache, but it's didn't fix the issue\n\nAlso the duration change to 68 day, even though I did not enter this value\n\n[Image omitted]\n\nReproduction steps:\n1. Go to the ticket\n2. Open a old task\n3. Try to change the date start\n\nAdditional context:\nWhen i try to get GLPI setup information, i have also this error\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed in\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3674017940, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22442#issuecomment-3674017940", "createdAt": "2025-12-19T08:08:38Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "I have applied the correction, but the error still exists.\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3674038097, "author": "zekuraz", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22442#issuecomment-3674038097", "createdAt": "2025-12-19T08:14:37Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Clean your cache.\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3674161931, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22442#issuecomment-3674161931", "createdAt": "2025-12-19T08:54:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22442, "url": "https://github.com/glpi-project/glpi/issues/22442", "author": "zekuraz", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-19T08:07:18Z", "updatedAt": "2026-03-30T00:45:32Z", "closedAt": "2025-12-19T08:08:38Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Merging Software not possible", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen I try to merge one or multiple software packages into the root software packages the select modal doesn't work.\n\nReproduction steps:\n1. Select a Software which exists in root entity\n2. Change the inheritance to \"Child entities\" and save\n3. goto the merge window\n4. select one or all entries in sub entities\n5. click the action button\n\nif you have not selected the last entry you get an error message that no item has been selected\n\nif you have selected the last entry in the list you get the drop down and can select merge, but after selecting merge you get an error message \"No selected items\".\n\nAdditional context:\nSelect all video:\n\nSelect single item and last item video", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide logs, as requested.\n\nOriginal response date: 2025-12-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3648123294, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22352#issuecomment-3648123294", "createdAt": "2025-12-12T20:58:41Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No relevant logs, but I debugged it and found the missing parts:\n\ndoesn't provide itemtype and id which is needed here:\n\nI allowed my self to create a pr #22354\n\nI don't know if I have to close this issue or it's done automatically or you close it anyway, the pr solves my issue, sorry if the pr is not the correct way.\n\nOriginal response date: 2025-12-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3648267191, "author": "HLeithner", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22352#issuecomment-3648267191", "createdAt": "2025-12-12T21:53:42Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "[...]\nI allowed my self to create a pr #22354\n\n👍\n\nI don't know if I have to close this issue or it's done automatically or you close it anyway, the pr solves my issue, sorry if the pr is not the correct way.\n\nIssues are closed automatically when related PR is merged; there is nothing more to do for now.\n\nOriginal response date: 2025-12-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3653496895, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22352#issuecomment-3653496895", "createdAt": "2025-12-15T06:07:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22352, "url": "https://github.com/glpi-project/glpi/issues/22352", "author": "HLeithner", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "HLeithner", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-12T17:47:21Z", "updatedAt": "2026-03-26T00:43:13Z", "closedAt": "2025-12-15T08:00:09Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "I can't add devices connected to another computer in the new forms.", "detail": "Issue description:\nHello everyone. In the old version of tickets, users could add a device not connected to their computer but registered in the system (via the Objects field, which displays a full list of devices). For example, to replace a cartridge in a shared printer or simply a printer not connected to their computer. This is no longer possible; the standard forms only show connected devices. I added a field where I listed all printers in the assets, but the inventory numbers, which were previously used to search for the desired printer, are missing. Without them, it just displays a list of printers with the same name, making it impossible to tell which one is which. This raises several questions.\n\n1. Is there a way to display inventory numbers in the lists?\n2. Is it possible to restore the old ticket forms for now?\n3. Any other suggestions for a workaround at this time?\n\nUPD. In the form editing menu, when I select \"Objects - GLPI Objects - Assets,\"\nthe inventory numbers and serial numbers are shown in the preview. However, when I save the form, they disappear, leaving only the names. Could this be a bug?\n\nBest regards.", "priority": "medium", "type": "support", "createdByEmail": "quinn.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Quinn Bennett\n\nTo allow the user to see items that are not his own, you must add this rigth:\n\n[Image omitted]\n\nRegarding the serial numbers, we have an ongoing internal support ticket for this so it should be fixed soon.\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3627191356, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21869#issuecomment-3627191356", "createdAt": "2025-12-08T14:26:36Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "Hi Skyler Adler\n\nYes, the permissions are set. The problem is with displaying inventory numbers. I'll wait for the update, thanks again!\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630778503, "author": "HiopsNerevar", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21869#issuecomment-3630778503", "createdAt": "2025-12-09T07:31:59Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed by #22327, it will be included in the 11.0.5 release.\n\nOriginal response date: 2025-12-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3641017671, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21869#issuecomment-3641017671", "createdAt": "2025-12-11T09:24:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21869, "url": "https://github.com/glpi-project/glpi/issues/21869", "author": "HiopsNerevar", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-10T09:05:14Z", "updatedAt": "2026-03-22T00:41:43Z", "closedAt": "2025-12-11T09:24:14Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "After saving the form, the asset attributes are no longer displayed", "detail": "Affected version:\n11.0.2\n\nIssue description:\nGood afternoon.\nI am facing a problem when creating a form.\nWhen adding a question to the form with the \"Assets - Printers\" type, I can see the \"serial number\" and \"inventory number\" attributes in the drop-down list. However, after clicking the \"Save and Preview\" button, these attributes are no longer displayed.\n\nReproduction steps:\n1. Created a new form\n2. Added a new question and selected its type \"item\" \"GLPI Objects\" \"Assets-Printers\"\n3. In dropdown list i can see name, serial number and inventory number of asset (see Forms_1.png)\n4. Click on \"Save and Preview\" button\n5. In dropdown list i cant see serial number and inventory number of asset anymore (see Forms_2.png)\n6. After returning to the question I no longer see the serial or inventory numbers in the dropdown list (see Forms_3.png)\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "elliot.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "logan.blair@peppermint.local", "text": "Waiting for a solution as well\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3595406133, "author": "mateuszkruczek", "anonymizedAuthorEmail": "logan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22118#issuecomment-3595406133", "createdAt": "2025-12-01T09:09:37Z" } }, { "userEmail": "riley.blair@peppermint.local", "text": "Confirm. Still not working as intended in version 11.0.4\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611603838, "author": "RogueSnipa", "anonymizedAuthorEmail": "riley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22118#issuecomment-3611603838", "createdAt": "2025-12-04T11:11:24Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed by #22327, it will be included in the 11.0.5 release.\n\nOriginal response date: 2025-12-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3641018050, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22118#issuecomment-3641018050", "createdAt": "2025-12-11T09:24:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22118, "url": "https://github.com/glpi-project/glpi/issues/22118", "author": "mshishko82", "anonymizedAuthorEmail": "elliot.adler@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-01T08:09:50Z", "updatedAt": "2026-03-22T00:41:40Z", "closedAt": "2025-12-11T09:24:20Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Problem with entity creation", "detail": "Affected version:\n11\n\nIssue description:\nHello,\n\nWhen i create an new entity, i have this message error (Debug mode)\n\nI test with my account (ldap) superadmin and glpi local admin account.\n\nThank you for your help.", "priority": "medium", "type": "support", "createdByEmail": "dakota.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI reproduced the issue, by selecting a specific entity in the entity selector and then try to create a child entity for it. Not being able to see the created entity make sense, as it is outside the entity scope.\nMaybe we should prevent the entity creation when the result entity will be out of the selected entities scope.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3406106082, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21497#issuecomment-3406106082", "createdAt": "2025-10-15T12:14:03Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "I attempted to implement Skyler Adler's suggestion by adding validation in src/Entity.php :\n\n- Added validation to block child entity creation when user lacks recursive access, using Session::haveRecursiveAccessToEntity() instead of session variables to avoid pollution\n- : Replaced manual session manipulation with Session::changeActiveEntities()\n\nWorks initially but fails after switching entities multiple times - session pollution suspected when toggling between Root and sub-entities.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3426190400, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21497#issuecomment-3426190400", "createdAt": "2025-10-21T11:46:38Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Skyler Adler Jordan Blair To fix this issue, I have 3 possibles ideas\n\n1. Since we are in an entities management, we could force switching the user to root entity (with recursive)\n2. When the user create a new entity, we switch the user to that active entity (will restrain the listing to the new one created so user won't be able to do much)\n3. When the user create a new entity, on the original entity, we enable the recursive (so user will be able to see all the child including the freshly created one).\n\nI'll personally go for the number 3, I don't know if you prefer using another (that are more aggressive on the entity change).\n\nI'll wait for your response before updating the code and writing the cypress test verifying that the new logic is well applied.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3467508534, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21497#issuecomment-3467508534", "createdAt": "2025-10-30T11:24:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21497, "url": "https://github.com/glpi-project/glpi/issues/21497", "author": "root-it74", "anonymizedAuthorEmail": "dakota.adler@peppermint.local", "assignees": [ { "sourceLogin": "froozeify", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-15T12:08:49Z", "updatedAt": "2026-03-20T00:39:35Z", "closedAt": "2025-12-09T07:47:07Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "v11.0.x Custom Field on Custom Asset causes exception when used as column header involving fields plugin", "detail": "Affected version:\n11.0.4\n\nIssue description:\nv11.0.x Custom Field on Custom Asset used as source for 'fields' plugin dropdown causes exception. All v11.0.x versions have displayed this error, it is not specific to 11.0.4\n\n- Creating custom asset is ok.\n- Creating custom field (dropdown) on the custom asset is ok\n- Using Fields plugin - create new additional field (dropdown) using the custom asset dropdown created above as the type of field. This works ok to here.\n- When then selecting the additional field (dropdown) above as a column to display in an asset list, the error below is displayed.\n\nAffected page:\n\nReproduction steps:\nUsing core functionality, navigate to setup-Asset definitions\n\n- Add New Asset Definition\n- Add a new custom field:\n- Label=Functional Location\n- system name is functional_location\n- Type=dropdown\n- Full Width=true\n- mandatory=no\n\nSave the field\nSave the custom asset.\n\nAt this point the Functional Location will contain a list that we wish to reference throughout the tool, without having to repopulate.\nUsing Additional Fields Plugin (v1.23) (setup->Additional Fields)\n\n- Using a block of type: Insertion in the form (before save button) (in this case, the block applies to Network Devices)\n- Choose Fields\n- Choose add\n- Label:-FLoc From Cust DropDown\n- Type: Choose the filed you created as part of the cusome asset: in this case its the 'Functional Location' field.\n- Multiple: no\n- Active:Yes\n- Read only:no\n- Mandatory:no\n\nSave the additional field\nAll working to here.\n\nNavigate to Assets->Network Devices\n\n- Select 'Select Default Items to show' for the view.\n- Find and select 'FLoc From Cust DropDown' from the available fields to display.\n- Add to the field list.\n\nThe error occurs as the network device list attempts to display with the new field included.\n\nTo date, the only way I can now get the 'Network Devices' view to display in the tool (including the 'Return to previous page' link, is to remove the field from the block:\n\n- Navigate to Setup->Additional fields\n- Open the block you previously added the 'FLoc From Cust DropDown' field to.\n- Choose 'Fields' tab\n- Click on 'FLoc From Cust DropDown'\n- Click 'Delete Permanently'\n\nNow navigate to Assets->Network devices\nThe Network Device list displays successfully without error.\n\nEnvironment details:\nFile attached\n\ndetailssummaryGLPI informationsumma.txt\n\nAdditional context:\nThis is an on-prem instance", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please report plugins issues plugin side\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3625304823, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22278#issuecomment-3625304823", "createdAt": "2025-12-08T07:00:17Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "I appreciate you may think this is a plugin issue. How can you create a custom dropdown and have that used on every asset type (custom or not) without the additional fields plugin? Could you point me at some description of how to do this please?\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3625361054, "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22278#issuecomment-3625361054", "createdAt": "2025-12-08T07:21:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I appreciate you may think this is a plugin issue. How can you create a custom dropdown and have that used on every asset type (custom or not) without the additional fields plugin? Could you point me at some description of how to do this please?\n\nYou cannot add a custom field on GLPI native assets types without a plugin.\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3625497282, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22278#issuecomment-3625497282", "createdAt": "2025-12-08T07:58:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22278, "url": "https://github.com/glpi-project/glpi/issues/22278", "author": "andrewc-ui", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-08T06:19:59Z", "updatedAt": "2026-03-19T00:41:17Z", "closedAt": "2025-12-08T07:00:17Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Assets in form dropdown sn search bug", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHi everyone, I’ve run into a minor issue: if I display the group’s devices in a dropdown on the form and try to filter the list by serial number, the device doesn’t show up. However, if I search by UUID or inventory number, it appears correctly in the list.\n[Image omitted]\n\n[Image omitted]\n\nEnvironment details:\nInstallation mode: TARBALL\nCurrent language: hu_HU\nOperating system: Linux 5.15.0-97-generic #​107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 x86_64\n\nPHP: 8.3.26 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem,\nsysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"10000\" max_input_vars=\"1000\" memory_limit=\"512M\" post_max_size=\"512M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"512M\"\n\nWeb server: Apache/2.4.56 (Debian) (Apache/2.4.56 (Debian) Server at Port 80)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 11.2.3-MariaDB-1:11.2.3+maria~ubu2204\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@glpi-mariadb/glpidb\n\nHost info: glpi-mariadb via TCP/IP\n\nRequirements:\nPHP version (8.3.26) is supported.PHP version (8.3.26) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (11.2.3) is supported.Database engine version (11.2.3) is supported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated. Write access to\n/var/www/html/glpi/files/_cron has been validated. Write access to /var/www/html/glpi/files has been validated. Write access to\n/var/www/html/glpi/files/_graphs has been validated. Write access to /var/www/html/glpi/files/_lock has been validated. Write\naccess to /var/www/html/glpi/files/_pictures has been validated. Write access to /var/www/html/glpi/files/_plugins has been\nvalidated. Write access to /var/www/html/glpi/files/_rss has been validated. Write access to /var/www/html/glpi/files/_sessions\nhas been validated. Write access to /var/www/html/glpi/files/_tmp has been validated. Write access to\n/var/www/html/glpi/files/_uploads has been validated.Write access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed:\nctype, iconv, sodium.\nWrite access to /var/www/html/glpi/marketplace has been validated.Write access to\n/var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.Timezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I am not able to reproduce. Could you provide exact steps to reproduce?\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558543869, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21938#issuecomment-3558543869", "createdAt": "2025-11-20T15:05:20Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "I am not able to reproduce. Could you provide exact steps to reproduce?\n\nI made a video of it on the left there is the Form with Assets dropdown, on the right the computer page:\n\nOriginal response date: 2025-11-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3561798372, "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21938#issuecomment-3561798372", "createdAt": "2025-11-21T07:31:55Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "The dropdown search uses a fuzzy match. It means that it proposes results that are similar to the searched term. Are you sure the searched serial number is not present in the list?\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3570093099, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21938#issuecomment-3570093099", "createdAt": "2025-11-24T10:46:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21938, "url": "https://github.com/glpi-project/glpi/issues/21938", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-14T12:07:40Z", "updatedAt": "2026-03-19T00:40:59Z", "closedAt": "2025-12-08T12:50:11Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Plural declaration in CFG_GLPI", "detail": "Issue description:\nThe km_KH lang has been added; plural form declared in the PO file is the following:\n\nSo in the $CFG_GLPI lang declaration array for the plural, value is 0.\nSome other languages (like ja_JP) have the same plural form in their PO file, but plural in the $CFG_GLPI is set to 2, which seems incorrect.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I wonder if it has any effect. As there is only one plural form, whatever the number you pass to the translate functions, it will always result in using the same plural form.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605862657, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22188#issuecomment-3605862657", "createdAt": "2025-12-03T09:21:57Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "It's possible, yes; I did not yet take time to check. If it has no effect, we can just keep as is; no one never complains.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605885125, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22188#issuecomment-3605885125", "createdAt": "2025-12-03T09:27:08Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Seems like that indeed do not change anything :)\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606388550, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22188#issuecomment-3606388550", "createdAt": "2025-12-03T11:22:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22188, "url": "https://github.com/glpi-project/glpi/issues/22188", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-03T09:07:13Z", "updatedAt": "2026-03-14T00:37:13Z", "closedAt": "2025-12-03T11:22:14Z" } }, { "title": "Different language at \"New\" button after update to V11.0.3", "detail": "Affected version:\n11.0.3\n\nIssue description:\nAfter updating to V11.0.3 we saw \"Нэмэх\" instead of \"New\" or \"Create\" (not sure which of the 2 it was).\nThe language of our GLPI is English (US).", "priority": "medium", "type": "support", "createdByEmail": "cameron.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Indeed en_US translates \"Add\" to \"Нэмэх\".... This must be fixed on Transifex; someone made a mistake there.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606700501, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22197#issuecomment-3606700501", "createdAt": "2025-12-03T12:48:27Z" } }, { "userEmail": "cameron.bennett@peppermint.local", "text": "Okay and (maybe a stupid question) will it be fixed?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606769105, "author": "Caseum96", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22197#issuecomment-3606769105", "createdAt": "2025-12-03T13:06:25Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "It is already.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606997339, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22197#issuecomment-3606997339", "createdAt": "2025-12-03T13:57:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22197, "url": "https://github.com/glpi-project/glpi/issues/22197", "author": "Caseum96", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-03T12:39:51Z", "updatedAt": "2026-03-14T00:36:56Z", "closedAt": "2025-12-03T12:48:27Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "MySQL RuntimeException on saved searches list", "detail": "Affected version:\n11.0.2\n\nIssue description:\nOpening the Ticket tab displays a MySQL RuntimeException. A red error block appears with a long SQL query.\n\nObserved behavior:\nThe generated SQL query contains multiple GROUP_CONCAT, several joins on glpi_tickets_users, and dynamic glpi_users_* aliases. MySQL fails to parse the query, and the saved searches list does not load.\n\nExpected behavior:\nThe saved searches list should load normally when pinned.\n\nNote:\nWhen trying to get the logs and switching between super admin and our custom technician profile, the issue only seems to arise when being in the custom technician profile, here redacted :\n[Image omitted]\n[Image omitted]\ndon't hesitate to ask me for more screenshots of our current setup if necessary!\n\nAffected page:\n\nReproduction steps:\n1. Go to Assistance > Tickets.\n2. The SQL error appears immediately.\n3. No ticket is displayed.\n\nEnvironment details:\n[Image omitted]\n\n---\n\nAdditional context:\nMaybe there's too much redacted information?", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "It seems to be related to the search option 119, but I do not find what is search option is for.\nCould you provide the glpi_savedsearches table row corresponding to this saved search?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607218887, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22059#issuecomment-3607218887", "createdAt": "2025-12-03T14:46:37Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "119 seems to be \"Number of documents\" in GLPI 11 according to the debug bar.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607283707, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22059#issuecomment-3607283707", "createdAt": "2025-12-03T15:01:07Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "One of my colleagues was testing saved searches, we had \"test [...]\" ones which I've deleted and now everything seems to be working fine. I have no idea what was the configuration of these saved searches unfortunately, and he don't either :/\n\nI guess we can consider this issue as closed!\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607580052, "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22059#issuecomment-3607580052", "createdAt": "2025-12-03T16:01:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22059, "url": "https://github.com/glpi-project/glpi/issues/22059", "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-25T09:50:34Z", "updatedAt": "2026-03-14T00:36:41Z", "closedAt": "2025-12-03T16:01:52Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Crash when trying to save a knowledge article with no category", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen I try to save a knowledge base article with no category - such that it shows up under the 'without category' section in Self-Service -, I get an unexpected error message. When looking up in the logs I get this error:\n\n[Image omitted]\n\nReproduction steps:\n1. Create a new knowledge article leaving the 'knowledgebase category' empty.\n2. Hit Save.\n3. The unexpected error pops up and the item is not saved.", "priority": "medium", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "remy.bennett@peppermint.local", "text": "Indeed, if you leave the \"Category\" item empty, an error appears in the logs.\nI checked with an account with maximum rights in GLPI and the article in the knowledge base has been saved and is opening. The only difference for me is that if you leave the category empty, you will get an error in the log, and if you fill it in, there will be no error.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3511407527, "author": "rean1mat0r", "anonymizedAuthorEmail": "remy.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21873#issuecomment-3511407527", "createdAt": "2025-11-10T12:42:48Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Actually, I need to edit the case. What I tested is editing an existing KB article having a category and removing this category. Sorry for the confusion. So, the steps to reproduce are:\n\n1. Edit a KB article having a KB category.\n2. Remove the category leave the field empty.\n3. Hit Save.\n4. The unexpected error pops up and the item is not saved with the empty category.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3511588867, "author": "pvasener", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21873#issuecomment-3511588867", "createdAt": "2025-11-10T13:16:32Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm. This function only seems to be used for this specific case, so only this dropdown seems affected.\n\nOriginal response date: 2025-11-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3512786803, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21873#issuecomment-3512786803", "createdAt": "2025-11-10T16:47:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21873, "url": "https://github.com/glpi-project/glpi/issues/21873", "author": "pvasener", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-10T12:11:31Z", "updatedAt": "2026-03-12T00:36:10Z", "closedAt": "2025-12-01T08:24:19Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Expiration on reservaiton doesn't work", "detail": "Affected version:\n11.0.1\n\nIssue description:\nThe new reservation and reservation update notifications are working, but the reservation expiration notification is not. The automatic action is in place and works for the other reservation-related alerts.", "priority": "medium", "type": "support", "createdByEmail": "bailey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Are reservation alerts enabled for the entity?\nAdministration > Entities > Notifications tab.\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3587061199, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22093#issuecomment-3587061199", "createdAt": "2025-11-27T19:07:15Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Also try with latest stable release.\n\nOriginal response date: 2025-11-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3588106770, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22093#issuecomment-3588106770", "createdAt": "2025-11-28T06:44:48Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "Are reservation alerts enabled for the entity? Administration > Entities > Notifications tab.\n\nThis was the solution thanks a lot !\n\nAlso try with latest stable release.\n\nI will soon\n\nOriginal response date: 2025-11-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3588692290, "author": "AziocNEU", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22093#issuecomment-3588692290", "createdAt": "2025-11-28T10:13:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22093, "url": "https://github.com/glpi-project/glpi/issues/22093", "author": "AziocNEU", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-27T14:05:05Z", "updatedAt": "2026-03-09T00:39:18Z", "closedAt": "2025-11-28T10:42:50Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Mailgate cron not running automatically and re-scanning all emails in Docker setup", "detail": "Issue description:\nIn our Docker-based GLPI setup, the mailgate cron job does not execute automatically. Additionally, every time the cron runs, it scans all emails, including those already read, instead of only processing new unread emails. Other cron tasks inside the same Docker containers are working as expected.\n\nSteps to reproduce:\nStep 1: Deploy GLPI 10.0.19 using Docker on Ubuntu 24.\nStep 2: Configure mailgate for a mailbox.\nStep 3: Wait for the scheduled interval inside Docker (without any system-level cron).\n\nExpected behavior:\nStep 1: The mailgate cron job should automatically execute inside Docker.\nStep 2: It should process only new unread emails instead of rescanning all emails.\n\nObserved behavior:\nStep 1: The mailgate cron does not run automatically.\nStep 2: When triggered manually, it scans all emails, even those already processed/read.\nStep 3: Other cron tasks inside the same Docker setup are running correctly.\n\nEnvironment:\n\nGLPI version: 10.0.19\nOS: Ubuntu 24\n\nMail server: office365\n\nAdditional information:\nNo system-level cron is used; all scheduling is expected to run inside Docker.", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "drew.blair@peppermint.local", "text": "This is settings of mailgate .I have run the manually after that i wait but still not run.Everytime this issue. I need to run manually.\n[Image omitted]\n\nAnd this below image is for the logs.I am just set 1 mail to scan but it it scanning more 250 mail.\n\n[Image omitted]\n\nOriginal response date: 2025-11-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3527659485, "author": "Ujebhopshealthcare", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21926#issuecomment-3527659485", "createdAt": "2025-11-13T12:48:23Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nThis kind of issue appears when the mailbox is full, or when any other reason prevent GLPI to delete or move to another folder the collected mails.\n\nCould you check the configuration of your mail collector, the mail collector log and the mailbox status?\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558616917, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21926#issuecomment-3558616917", "createdAt": "2025-11-20T15:17:35Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Hello sir,\n\nThank you for your response.\n\nThe issue is now resolved.\n\nHere is what I did:\n\nI tested with an empty mailbox folder, and the mail collector worked correctly.\n\nI moved all older existing emails to another folder so the inbox only contains new messages.\n\nAfter doing this, GLPI processes only the new emails as expected.\n\nThanks again for your guidance.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3568943664, "author": "Ujebhopshealthcare", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21926#issuecomment-3568943664", "createdAt": "2025-11-24T05:04:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21926, "url": "https://github.com/glpi-project/glpi/issues/21926", "author": "Ujebhopshealthcare", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-13T12:38:27Z", "updatedAt": "2026-03-05T00:39:08Z", "closedAt": "2025-11-24T05:04:27Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Helpdesk : Service Catalog not displayed", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHello,\nIn the Helpdesk tile configuration at the root entity level, I want to configure a tile that redirects to the Service Catalog.\nI have configured it as follows:\n[Image omitted]\n[Image omitted]\n\nHowever, when I access the Helpdesk with a test user (from the root entity), the Service Catalog tile does not appear. The other tiles (ticket list, external links) display correctly.\nI don't have any tile configurations in the profiles that could override this setting.\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. Create a tile in the Helpdesk configuration at the root entity level that redirects to a GLPI page: Service Catalog\n2. Log in with a user in this entity (simplified interface)\n\nAdditional context:\nThansk for help !", "priority": "medium", "type": "support", "createdByEmail": "jordan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.bennett@peppermint.local", "text": "I forgot to mention that my GLPI instance is the result of a migration from GLPI 10, including a migration of FormCreator.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3569777782, "author": "steve-hbt", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22039#issuecomment-3569777782", "createdAt": "2025-11-24T09:38:00Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "My bad,\nSelf-Service profile did not have the \"Create a ticket\" permission, because we had disabled it in V10 to force our users to use the forms.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3570716522, "author": "steve-hbt", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22039#issuecomment-3570716522", "createdAt": "2025-11-24T13:08:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I think we can still consider it an issue because the service catalog can contains others items that forms (for example, knowledge base articles) so blocking the service catalog access if the user can't create ticket might be a bit too harsh.\n\nI'll fix it in the version, thanks for the report.\n\nOriginal response date: 2025-11-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3570732140, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22039#issuecomment-3570732140", "createdAt": "2025-11-24T13:12:30Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22039, "url": "https://github.com/glpi-project/glpi/issues/22039", "author": "steve-hbt", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-24T09:29:03Z", "updatedAt": "2026-03-05T00:38:56Z", "closedAt": "2025-11-24T13:08:33Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Delegates cannot create tickets for themselves", "detail": "Affected version:\n10.0.20\n\nIssue description:\nWith delegation set for a user from a group, it is possible for such user to create a ticket on behalf of someone else of the group.\n\nBut such user cannot create a ticket for himself !\n\nA pop-up message You cannot create a ticket for this user appears and ticket is not created:\n[Image omitted]\n\nThis was not the case in version 9 of GLPI.\n\nIs there a way to allow creation of tickets for one-self and at the same time allow creation of tickets for other group members, keeping simplified view ?\n\nReproduction steps:\n1. Users accounts A and B are part of same group with delegatee set.\n2. User A has post-only profile.\n3. User A creates a ticket and let Yes default value for \"This ticket concerns me\" field.\n4. When user A clics on \"Submit message\", ticket is not created and an error message appears.\n\nEnvironment details:\nBrand new 10.0.20 installation with group and profile configuration as indicated in steps to reproduce.\n\nAdditional context:\nThis behavior changed from version 9.\n\nIf I understand correctly, same behavior/bug has to be expected in version 11 of GLPI.", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "The team is telling me that this may already be fixed by #21110, can you try it?\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3532239624, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21935#issuecomment-3532239624", "createdAt": "2025-11-14T11:11:09Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Skyler Adler I modified src/Ticket.php with this code change and it corrects perfectly the problem in my case !\n\n(Sorry, I missed issue 20973 when I search for a solution.)\n\nI can also test a particular configuration, if needed.\n\nThanks and Regards !\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3532757574, "author": "felag", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21935#issuecomment-3532757574", "createdAt": "2025-11-14T13:23:41Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Sorry to re-open: it appears that ticket is created, but without any requester !\n\nSee below: ticket is created by post-only user, but there is no requester:\n\n[Image omitted]\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3533064038, "author": "felag", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21935#issuecomment-3533064038", "createdAt": "2025-11-14T14:30:45Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21935, "url": "https://github.com/glpi-project/glpi/issues/21935", "author": "felag", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-11-14T08:26:01Z", "updatedAt": "2026-03-01T00:44:04Z", "closedAt": "2025-11-20T15:06:38Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Undefined array key 400 in /var/www/glpi/src/Glpi/Error/ErrorHandler.php on line 278", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHi,\nIl the logs I get : Undefined array key 400 in /var/www/glpi/src/Glpi/Error/ErrorHandler.php on line 278\nevery time I start bin/console (for example)\n\nReproduction steps:\nstart bin/console", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Could you check if #21911 fies this issue?\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3542246827, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21959#issuecomment-3542246827", "createdAt": "2025-11-17T14:47:03Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Thanks,\n\nHi, unfortunately no.\n\nUpdate all files in the patch, then I took the nightly build and it does not solve my issue.\n\nThanks\n\nOriginal response date: 2025-11-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3546162300, "author": "InformatiqueOLLN", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21959#issuecomment-3546162300", "createdAt": "2025-11-18T08:28:21Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "#21968 should fix your issue.\n\nOriginal response date: 2025-11-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3546581019, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21959#issuecomment-3546581019", "createdAt": "2025-11-18T09:57:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21959, "url": "https://github.com/glpi-project/glpi/issues/21959", "author": "InformatiqueOLLN", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-17T13:26:21Z", "updatedAt": "2026-02-27T00:39:08Z", "closedAt": "2025-11-18T11:04:46Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "problem with connecting entries from knowledge base", "detail": "Affected version:\n11.0.2\n\nIssue description:\nIt is not possible to attach a solution from the knowledge base in the ticket, computer, software.... actions shows me\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please include any errors in files/_log/php-errors.log that appear when you try to do this action.\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3532947133, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21941#issuecomment-3532947133", "createdAt": "2025-11-14T14:01:20Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "every time when i try open combo in knowledge base ( doesnt matter in computer, ticket ,software) i get error:\nglpi.CRITICAL: * Uncaught PHP Exception Error: \"Cannot use object of type Glpi\\DBAL\\QueryExpression as array\" at Dropdown.php line 2964\n Backtrace :\n ./src/Dropdown.php:2964\n ./ajax/getDropdownValue.php:48 Dropdown::getDropdownValue()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n[2025-11-14 15:28:14] glpi.CRITICAL: * Uncaught PHP Exception Error: \"Cannot use object of type Glpi\\DBAL\\QueryExpression as array\" at Dropdown.php line 2964\n Backtrace :\n ./src/Dropdown.php:2964\n ./ajax/getDropdownValue.php:48 Dropdown::getDropdownValue()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3533060393, "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21941#issuecomment-3533060393", "createdAt": "2025-11-14T14:29:43Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Should be fixed by #21931\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3533084628, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21941#issuecomment-3533084628", "createdAt": "2025-11-14T14:36:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21941, "url": "https://github.com/glpi-project/glpi/issues/21941", "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-14T13:57:44Z", "updatedAt": "2026-02-26T00:37:22Z", "closedAt": "2025-11-17T06:55:38Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "glpi simplified interface lacks attachments in issues creation", "detail": "Affected version:\n110.0.2\n\nIssue description:\nHello,\n\nWith version 11 of GLPI, you introduced the simplified interface that provides a brand-new UI for end users.\n\nHowever, we have encountered the following problem:\n\nWhen a user chooses to create either a request or an incident, neither creation form allows them to attach a file directly. The user must first create the ticket and then reopen it to add the attachment.\n\nCould you clarify whether this behavior is related to permissions or if it is a bug?\n\nThank you.", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "You are free to add or edit the forms in Administration > Forms. A question type exists for file uploads. The only restriction is that file questions currently will not show for anonymous users (users not logged in).\n\nOriginal response date: 2025-11-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3536547146, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21949#issuecomment-3536547146", "createdAt": "2025-11-15T14:37:25Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "Hi.\n\nThank you for your answer.\n\nI haven't understood what you are saying.\n\nDefault forms for request and incident doesn't have file upload for\nattachments.\n\nHow can I add it?\n\nThanks\n\nIl sab 15 nov 2025, 15:38 Curtis Conard *@*.*> ha\nscritto:\n\nClosed #21949 as not\nplanned.\n—\nReply to this email directly, view it on GitHub\n, or\nunsubscribe\n\n.\nYou are receiving this because you authored the thread.Message ID:\n*@*.*>\n\nOriginal response date: 2025-11-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3536610833, "author": "antoniotvr", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21949#issuecomment-3536610833", "createdAt": "2025-11-15T15:49:05Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "Hi.\n\nI have solved my problem.\n\nThanks\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3540739221, "author": "antoniotvr", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21949#issuecomment-3540739221", "createdAt": "2025-11-17T09:20:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21949, "url": "https://github.com/glpi-project/glpi/issues/21949", "author": "antoniotvr", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-15T10:55:02Z", "updatedAt": "2026-02-26T00:37:07Z", "closedAt": "2025-11-15T14:37:53Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Pending reason warning on homepage confusing users", "detail": "Affected version:\n11.0/bugfixes\n\nIssue description:\nI've been seeing several users say they are confused by the \"You have defined pending reasons without any respective active notification\" warning on their homepage.Some say they aren't even using pending reasons as far as they are aware. Also the auto_reminder notification is disabled by default which can add to the confusion.\n\nI don't know if there is a bug here causing the message to be displayed when it shouldn't be, but there does seem to be a need for a UX improvement.\n\n- Is it important to have this kind of warning specifically for the auto_reminder notification when we don't do anything like this for other notifications?\n- Should this notification be enabled by default?", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Possibly a bug that is causing this:\nIf you click the Pause button when adding a followup or task but don't select a reason, an entry is still added to the glpi_pendingreasons_items table which is enough for the warning on the homepage to show.\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3496973249, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21603#issuecomment-3496973249", "createdAt": "2025-11-06T12:16:27Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Jordan Blair do you have any ideas if this is expected?\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3496977161, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21603#issuecomment-3496977161", "createdAt": "2025-11-06T12:17:19Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Jordan Blair do you have any ideas if this is expected?\n\nI reproduce. In my opinion, if no reason is selected, the ticket should be put on pending, but none of the logic behind the pending reasons should be triggered.\nI will try to push a fix for this.\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3497518959, "author": "ccailly", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21603#issuecomment-3497518959", "createdAt": "2025-11-06T14:29:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21603, "url": "https://github.com/glpi-project/glpi/issues/21603", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "ccailly", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-22T13:11:31Z", "updatedAt": "2026-02-26T00:36:50Z", "closedAt": "2025-11-17T20:03:44Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "GLPI 11 - Forms / Actors : unable to use Item, GLPI Objects, Administration Groups", "detail": "Affected version:\n11.01\n\nIssue description:\nHello. In the Forms, when you're using Actors, you can not use \"Item, GLPI Objects, Administration Groups\"\nSo all our Forms from GLPI 10 can't work and it's less powerfull to use Actors because users have to browse or know the name of the group. Could you add the GLPI object Administration Group and users to have more control ?", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Avery Blair,\n\nWe just released the 11.0.2 version which fixes a lot of form related issues.\n\nCan you update and retry?\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491391959, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21810#issuecomment-3491391959", "createdAt": "2025-11-05T14:03:57Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Hello Skyler Adler , i've updated and the problem is fixed, thanks.\nCould you add multiselection in Item, GLPI Objects, Administration Groups and user like Actors ? It will be more powerfull and more precise :)\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3492033681, "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21810#issuecomment-3492033681", "createdAt": "2025-11-05T15:57:43Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Glad to hear everything is fixed on your side!\n\nCould you add multiselection in Item, GLPI Objects, Administration Groups and user like Actors ?\n\nThere is a lot of demand for this, it very likely that we add it for the 11.1.0 release (but I can't give you a date for this, it is still too early).\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3496238577, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21810#issuecomment-3496238577", "createdAt": "2025-11-06T09:49:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21810, "url": "https://github.com/glpi-project/glpi/issues/21810", "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-05T13:20:50Z", "updatedAt": "2026-02-15T00:42:20Z", "closedAt": "2025-11-06T07:58:21Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Profile - Unable to list 'Assets' from fellow users (of the same entity) even with the 'Read' combo checked, unless the profile has the 'Update' combo checked also.", "detail": "Affected version:\n10.0.20\n\nIssue description:\nWe set up the Supervisor profile so as to have only read access to specific types of assets (e.g. - Computers), but when we try to use this profile to list them, by using the Asset menu to navigate to the specific form, no item at all from any other user (of the same Entity) appear, except for those specifically assigned to oneself.\n\nNote that access to these same items is properly granted when assigning them to a ticket.\nAnd, by the way, when assigned to a ticket, the specific asset can still be accessed through the shortcut in the ticket (as it should be, by the way). [So is still searchable]\n\nThe listing ability only comes if we check the 'Update' combo, but that's not what we want. We need them to have read-only acces to all the assets of the Entity. Specially as to the Administrative Information of each one.\n\nAffected page:\n/front/computer.php\n\nReproduction steps:\n1. Config Profile Supervisor with only 'Read' access to all asset types.\n2. Log in with Supervisor profile\n3. Navigate to the Computer Main Form\n4. Nothing shows up (except own computer)\n5. Config Profile Supervisor with 'Update' access to Computers\n6. Navigate to the Computer Main Form\n7. All Computers from users of the same Entity show in the list\n\nAdditional context:\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue.\n\nPlease test with plugins disabled.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3429683757, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21585#issuecomment-3429683757", "createdAt": "2025-10-21T21:46:48Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "Hello.\n\nWe disabled all the plugins and it works ok.\nWe re-enablied the plugins one by one, and the issue reappeared when Behaviours was enabled.\nPlugins *Formcreator* and *Fields* (two logical suspects) worked ok.\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491110589, "author": "Jacques-Laniado", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21585#issuecomment-3491110589", "createdAt": "2025-11-05T13:07:00Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "OK then please report issue on Behaviours plugin\n\nOriginal response date: 2025-11-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3491274489, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21585#issuecomment-3491274489", "createdAt": "2025-11-05T13:38:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21585, "url": "https://github.com/glpi-project/glpi/issues/21585", "author": "Jacques-Laniado", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-21T21:39:27Z", "updatedAt": "2026-02-14T00:38:35Z", "closedAt": "2025-11-05T13:38:41Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "LDAP sync ver 11.0.1", "detail": "Affected version:\n11.0.1\n\nIssue description:\nLDAP sync on version 11.0.1 keeps bringing back users from \"trash\" even if they are disabled in ActiveDirectory.\n\nThe fist time the command runs, it finds all users and imports them\nIf in the meantime a user gets disabled, it will move it to \"trash\".\n\nNow, the problem:\nafter multiple runs of the cron job, it moves users to trash and brings them back in a loop, one time move to trash, one time resotore and so on.\n\nReproduction steps:\nrun php bin/console ldap:synchronize_users --no-interaction multiple times and disbale test users between runs", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Seems related to\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3484661574, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21774#issuecomment-3484661574", "createdAt": "2025-11-04T08:50:53Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Robin Bennett\n\nCould you confirm that #21462 fixes your issue ?\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3485551791, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21774#issuecomment-3485551791", "createdAt": "2025-11-04T11:39:26Z" } }, { "userEmail": "robin.bennett@peppermint.local", "text": "Yes it does. Thanks you!\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3486187448, "author": "remuseu", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21774#issuecomment-3486187448", "createdAt": "2025-11-04T14:07:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21774, "url": "https://github.com/glpi-project/glpi/issues/21774", "author": "remuseu", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-04T08:11:01Z", "updatedAt": "2026-02-13T00:41:55Z", "closedAt": "2025-11-04T11:39:04Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI11. Mail server stopped working", "detail": "Affected version:\n11.01\n\nIssue description:\nSince updating to glpi11 the connection to my mail server doenst work anymore. It keeps returning with an error saying my email and password combination is incorrect when i try to send a test email to the administrator. I am very sure that I have not misconfigured the smtp settings. They used to work before the migration, I have already tried all combinations of settings with the password, TLS enabled/disabled, port 465 and 587 and nothings seems to work\n\nReproduction steps:\nUpdate to glpi 11\nTry to send a mail via glpi (either via an automatic notification or via a test notification)", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "lane.bennett@peppermint.local", "text": "After doing some testing it seems to be the case that if spaces are part of the password this bugs it out. Changing the password of my mail account has solved the issue\n\nOriginal response date: 2025-11-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3478404910, "author": "QuantumNomad26", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21728#issuecomment-3478404910", "createdAt": "2025-11-02T22:01:21Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "After doing some testing it seems to be the case that if spaces are part of the password this bugs it out. Changing the password of my mail account has solved the issue\n\nThanks for this information, it will help to investigate.\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3479440207, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21728#issuecomment-3479440207", "createdAt": "2025-11-03T08:41:07Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "After doing some testing it seems to be the case that if spaces are part of the password this bugs it out. Changing the password of my mail account has solved the issue\n\n#21764 fixes the encoding of passwords to correctly support passwords with special chars.\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3479746772, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21728#issuecomment-3479746772", "createdAt": "2025-11-03T10:04:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21728, "url": "https://github.com/glpi-project/glpi/issues/21728", "author": "QuantumNomad26", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-31T13:45:19Z", "updatedAt": "2026-02-12T00:39:00Z", "closedAt": "2025-11-03T12:58:44Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "Error while migrating from 10.0.20 to 11.0.5", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHi,\n\nTrying to upgrave from GLPI v10.0.20 to GLPI v11.0.5 , already tried a couple of times.\n\nSuspect Windows Server x OpenSSL is the culprit (and may be my openssl conf & my fault too)\n\n[Image omitted]\n\n[Image omitted]\n\nAny help very much appreciated.\n\nReproduction steps:\n1. Existing install v10.0.20 , working well with some plugins.\n2. Migrate v11.0.5\n3. Migration success, but with an error.\n4. Database clean, but some things are wrong (EG : Error on the page Configuration > General > System)\n\nEnvironment details:\nI can't reach that page as stated above, so i'll do my best and give some info myself\n\n- GLPI v11.0.5\n- Every PHP mandatory PHP extension is enabled and found.\n- PHP : 8.3.26\n- OS : Windows Server 2022\n\nMore details, from a phpinfo() :\n\nPHP Version 8.3.26\nSystem Windows NT SV5537V 10.0 build 17763 (Windows Server 2019) AMD64\nBuild Date Sep 23 2025 18:09:22\nBuild System Microsoft Windows Server 2022 Datacenter [10.0.20348]\nCompiler Visual C++ 2019\nArchitecture x64\n\nApache Version Apache/2.4.62 (Win64) PHP/8.3.26 OpenSSL/3.1.6\nApache API Version 20120211\n\n[Image omitted]\n\nAdditional context:\nNasty little AI suggests this is due to Windows Server missing a proper openssl library / path and tells me to install an external one.\n\nNot convinced by the AI solution, but seems like a good clue regarding OpenSSL.", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "bailey.bennett@peppermint.local", "text": "Note , i did this , and it worked fine. Don't know it the installation is really fine though...\n\nOriginal response date: 2026-02-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3854752809, "author": "NoxWorld2660", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23030#issuecomment-3854752809", "createdAt": "2026-02-05T16:25:08Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "Skyler Adler Hi, i understand the \"support\" tag, but if the issue is related to windows server, and a missing openssl dependency, i think it should be documented. I havn't found anything on this.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3875677130, "author": "NoxWorld2660", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23030#issuecomment-3875677130", "createdAt": "2026-02-10T06:44:03Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This is an environment problem, not a GLPI bug. openssl extension is marked as required; having it working properly on your env is out of the scope.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3875789969, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23030#issuecomment-3875789969", "createdAt": "2026-02-10T07:17:36Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23030, "url": "https://github.com/glpi-project/glpi/issues/23030", "author": "NoxWorld2660", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-05T16:12:14Z", "updatedAt": "2026-02-10T07:17:40Z", "closedAt": "2026-02-09T07:12:33Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "GLPI 11 - Display bug in ticket", "detail": "Affected version:\n11\n\nIssue description:\nHi,\n\nThere’s an issue with the user info popup in the ticket form: it doesn’t disappear when you move the mouse away from it.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "lane.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "Yes, that's right. When you hover over it and move to the right, it keeps the card displayed and doesn't disappear, even if you move the cursor in other directions after that.\n\nVersion: 11.0.1\n[Image omitted]\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3412738998, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21526#issuecomment-3412738998", "createdAt": "2025-10-16T20:32:22Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "You can hover back over the actor field and then away from it and the popover to get rid of it, but I agree it isn't perfect. The popovers were explicitly made to prevent auto-closing if the mouse is hovering over the popover and the auto-hide doesn't get reset for when the mouse leaves.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3412809605, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21526#issuecomment-3412809605", "createdAt": "2025-10-16T20:55:36Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "I tested both in Chrome and Firefox, and this seems really anecdotal : i had to make a really specific micro-move to reproduce, plus this doesn't seems to really block the user. According to Taylor Adler this isn't perfect but i think this doesn't need further investigations. Feel free to reopen the issue if this is really a blocking bug.\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3472562625, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21526#issuecomment-3472562625", "createdAt": "2025-10-31T11:09:24Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21526, "url": "https://github.com/glpi-project/glpi/issues/21526", "author": "sis68", "anonymizedAuthorEmail": "lane.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-16T20:05:31Z", "updatedAt": "2026-02-09T00:40:51Z", "closedAt": "2025-10-31T11:09:24Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Information message when 'utf8mb4...' collation is other than 'utf8mb4_unicode_ci'", "detail": "Affected version:\nGLPI 11.0.0\n\nIssue description:\nWe're using Swedish as the default UI language. Sorting of the swedish characters 'Å', 'Ä' and 'Ö' doesn't work. They're sorted as 'A' and 'O' respectively. To fix this we have changed the collation from utf8mb4_unicode_ci to utf8mb4_swedish_ci.\n\nThe sorting now works. But - now we have an annoying banner telling us to migrate 'utf8mb3' tables to 'utf8mb4'. I have found that this message originates from the getNonUtf8mb4Tables function in DBmysql.php. It seems the use of 'utf8mb4_unicode_ci' is hard coded and expected to be used. It should be possible to use other collations than the utf8mb4_unicode_ci.\n\nReproduction steps:\n1. Change collation of the DB to utf8mb4_swedish_ci\n2. Restart DB and web server.\n3. Login to central.", "priority": "low", "type": "feature", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Skyler Adler Skyler Adler\n\nWhat happens if you have an international GLPI with multiple languages that don't expect the same sorting rules?\n\nYou can't solve it by changing the database collation, it must be done inside each requests instead using the expected collation for the current user language.\n\nFor example: SELECT * FROM sometable ORDER BY somecolumn COLLATE utf8_swedish_ci for a swedish user.\n\nBut this comes at a performance cost as indexes won't be able to be used.\n\nUnrelated, is it on purpose that we are still on utf8mb4_unicode_ci and not something like utf8mb4_0900_ai_ci or uca1400_ai_ci?\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3466677882, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21700#issuecomment-3466677882", "createdAt": "2025-10-30T08:40:39Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Skyler Adler Skyler Adler\n\nWhat happens if you have an international GLPI with multiple languages that don't expect the same sorting rules?\n\nGLPI do not propose to switch collation; but admins can still do if they want, that's not a problem.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3466713049, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21700#issuecomment-3466713049", "createdAt": "2025-10-30T08:51:48Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Unrelated, is it on purpose that we are still on utf8mb4_unicode_ci and not something like utf8mb4_0900_ai_ci or uca1400_ai_ci?\n\nMaybe it was not available on all supported DB server versions when I worked on this migration, but I cannot remember.\n\nAnyway, changing the default collation requires indexes recomputation. We could indeed propose this in the future, with a console command for instance, but it is probably preferable to use dedicated tools to do this.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3466726553, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21700#issuecomment-3466726553", "createdAt": "2025-10-30T08:55:59Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21700, "url": "https://github.com/glpi-project/glpi/issues/21700", "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "enhancement" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-29T15:37:41Z", "updatedAt": "2026-02-08T00:49:10Z", "closedAt": "2025-10-30T08:04:08Z" } }, { "title": "GLPI 11.0.1 - Force unlock button missing?", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHi, I checked all rights in profiles' abilities but we no longer see \"Force unlock\" button on tickets despite having all the possible abilities checked.\nSorry if do something wrong, but it looks like a regression to me\n\nAffected page:\nticket.form.php?id=xxxx\n\nReproduction steps:\n1. Lock an object with user A\n2. Tries to unlock object with user B", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "sage.blair@peppermint.local", "text": "I also have this issue after 11.0.1 I see that it was locked but no force unlock, Manually running the automatic action will clear the locks\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3411418770, "author": "cjdrilling29", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21522#issuecomment-3411418770", "createdAt": "2025-10-16T15:18:10Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "#21667 may fix the issue, please try. You need to clear cache.\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3455769159, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21522#issuecomment-3455769159", "createdAt": "2025-10-28T10:35:16Z" } }, { "userEmail": "jamie.bennett@peppermint.local", "text": "Taylor Adler thanks, it seems to fix the issue\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460227129, "author": "SteadEXE", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21522#issuecomment-3460227129", "createdAt": "2025-10-29T07:48:00Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21522, "url": "https://github.com/glpi-project/glpi/issues/21522", "author": "SteadEXE", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-16T11:25:03Z", "updatedAt": "2026-02-07T00:37:35Z", "closedAt": "2025-10-29T09:32:46Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Issue sync ldap user deleted", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHello, I am using debian with a version of GLPI 11.0.1. I am encountering an issue with LDAP synchronization involving disabled users and deleted AD accounts. The following command runs every 5 minutes via a CRON job on my debian server: bin/console glpi:ldap:synchronize_users.\nThe accounts are successfully moved to the trash in GLPI, but 5 minutes later, when the command runs again, the accounts are restored.\n\nI do not understand the behavior of GLPI. Can you help me?\n\nReproduction steps:\nLaunch the synchronization command with an ad account outside the synchronized OU\n\nThe account is deleted\n\nRelaunch the command, the account is restored", "priority": "medium", "type": "bug", "createdByEmail": "finley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you please indicate what is the exact command that is executed (what options for instance) and the general authentication configuration (from /front/auth.settings.php)?\n\n[Image omitted]\n\nThis can help to investigate.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396311224, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21423#issuecomment-3396311224", "createdAt": "2025-10-13T08:01:55Z" } }, { "userEmail": "finley.bennett@peppermint.local", "text": "Hello\n\nFor the command I use (cron file):\nphp /var/www/glpi/bin/console glpi:ldap:synchronize_users --no-interaction\nit's the same with\nphp /var/www/glpi/bin/console glpi:ldap:synchronize_users --no-interaction -d \"2,0,0\" -r 1\n\n[Image omitted]\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396482916, "author": "pierregager-design", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21423#issuecomment-3396482916", "createdAt": "2025-10-13T08:52:03Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "I was able to reproduce the bug, with importing user once, remove them form my local LDAP, then :\n\n1 new synchronization (with 8 users deleted in LDAP) => is_deleted_ldap = 1\n2 another synchronization => is_deleted_ldap = 0 and then users are restored\n\nSeems to come from this block :\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3397707368, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21423#issuecomment-3397707368", "createdAt": "2025-10-13T14:11:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21423, "url": "https://github.com/glpi-project/glpi/issues/21423", "author": "pierregager-design", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "assignees": [], "labels": [ "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-11T13:56:28Z", "updatedAt": "2026-02-07T00:37:02Z", "closedAt": "2025-10-15T12:20:17Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI 11.0.1 Display bug in page computer.php", "detail": "Affected version:\n11.0.1\n\nIssue description:\nIn page : front/computer.php\n\nIf an computer have locate at \"France > Pouzac\" (is not 2 locations, is one location named \"France > Pouzac\")\n\nYou display : \"France > Pouzac\"\n\nAffected page:\nfront/computer.php\n\nReproduction steps:\nAdd location with \">\" character", "priority": "medium", "type": "bug", "createdByEmail": "devon.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I added a location named A > B as child location of pAris. I do not see the problem:\n\n[Image omitted]\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409266675, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21508#issuecomment-3409266675", "createdAt": "2025-10-16T05:47:32Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "Now assign this location to a computer and go to the view of all computer : front/computer.php\nIn this view display location for computer\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409360688, "author": "TxX8N8LN", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21508#issuecomment-3409360688", "createdAt": "2025-10-16T06:25:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I am able to reproduce with a location created in GLPI 10.0.x having the following completename: Foo > A > B.\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409436264, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21508#issuecomment-3409436264", "createdAt": "2025-10-16T06:52:45Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21508, "url": "https://github.com/glpi-project/glpi/issues/21508", "author": "TxX8N8LN", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [ "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-16T05:35:37Z", "updatedAt": "2026-02-06T00:37:04Z", "closedAt": "2025-10-28T08:08:50Z" } }, { "title": "GLPI 11 : External event template : date mandatory ?", "detail": "Affected version:\n11.0.1\n\nIssue description:\nIt looks like the date on an external event template is mandatory.", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI confirm the issue. The date is not mandatory.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401713647, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21477#issuecomment-3401713647", "createdAt": "2025-10-14T13:07:14Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Indeed missing a date cause en error; it's quite easy to fix.\n\nBut once fixed, a default date is set while opening the form; and that seems more complex to fix.\n\nIt looks like all \"plan\" fields (start date, duration and reminder) are ignored when using the template (or maybe I did not find where it's used, I do no known well this part).\nI have no idea if it is this really useful to define a start date from a template. Maybe duration and reminder makes more sense (so it have to be fixed).\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3402015243, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21477#issuecomment-3402015243", "createdAt": "2025-10-14T13:54:33Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "Yes indeed, I do not see why a set date should be even present on a template, it doesn't make sense to me either. A task should only have a duration and a reminder. Thanks for your time\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3402060527, "author": "agnesmorin-itgouv", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21477#issuecomment-3402060527", "createdAt": "2025-10-14T14:05:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21477, "url": "https://github.com/glpi-project/glpi/issues/21477", "author": "agnesmorin-itgouv", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-14T12:54:15Z", "updatedAt": "2026-02-06T00:36:49Z", "closedAt": "2025-10-28T09:29:30Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI-Agent inventory task with oauth token authentication (400 Bad Request)", "detail": "Affected version:\nGLPI 11.0.2-dev\n\nIssue description:\nWhen the glpi-agent (1.15) does an inventory task, the server.\n\nReproduction steps:\nIn GLPI, set up an oauth client under \"Setup\" with the preferences below. Install the official glpi agent (1.15), pointing it to the GLPI server and use the oauth token and id you received from the server. Force the agent to perform the inventory task: glpi-agent -f.\n\nEnvironment details:\nThe setup uses the glpi [GLPI 11.0.2-dev]\nThe oauth client has the following settings:\nGrants: \"Client credentials\"\nScopes: \"Inventory\"\nAuthorized redirect URIs: \"/api.php/token\" and the default ones (\"/api.php/oauth2/redirection\", \"/api.php/swagger-oauth-redirect\")\nIP Restrictions: none", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I tested just from the GLPI side, with the API disabled, and wasn't able to recreate the issue. I was still able to get a token using client_credentials and the inventory scope.\n\nOriginal response date: 2025-10-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3449024781, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21641#issuecomment-3449024781", "createdAt": "2025-10-26T23:51:05Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "Hello, thank you for your help. Could you tell me the exact URL to use for testing from the a bash script\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3449637907, "author": "Techal62", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21641#issuecomment-3449637907", "createdAt": "2025-10-27T05:57:15Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "I have identified the cause of the problem.\nThe URL to enter in the GLPI Agent for inventory is this one: without adding anything after it.\nAfter testing, everything is now working.\nI think it would be a good idea to add this to the agent documentation to avoid spending hours searching for the cause of the problem.\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3450260224, "author": "Techal62", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21641#issuecomment-3450260224", "createdAt": "2025-10-27T09:23:15Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21641, "url": "https://github.com/glpi-project/glpi/issues/21641", "author": "Techal62", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-26T09:11:38Z", "updatedAt": "2026-02-05T00:40:17Z", "closedAt": "2025-10-27T09:45:13Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GLPI 11.0.1 : Unable to display sub-entity rules", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHello,\n\nWhen I create a new Entity at the \"Root Entity > Sub-Entity\" level and edit it to go to the \"Rules\" tab, I get the following error message:\n\nGlpi\\Exception\\Http\\NotFoundHttpException\nIn ./src/CommonDBTM.php(3062)\n#0 ./src/RuleRight.php(390): CommonDBTM->check()\n#1 ./src/Rule.php(2970): RuleRight->showForm()\n#2 ./src/Rule.php(3293): Rule->showAndAddRuleForm()\n#3 ./src/CommonGLPI.php(694): Rule::displayTabContentForItem()\n#4 ./ajax/common.tabs.php(108): CommonGLPI::displayStandardTab()\n#5 ./src/Glpi/Controller/LegacyFileLoadController.php(64): require('...')\n#6 ./vendor/symfony/http-kernel/HttpKernel.php(181): Glpi\\Controller\\LegacyFileLoadController->invoke()\n#7 ./vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n#8 ./vendor/symfony/http-kernel/Kernel.php(197): Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n#9./public/index.php(70): Symfony\\Component\\HttpKernel\\Kernel->handle()\n#10 {main}\n\nI only encounter this problem on level 2 sub-entities (Root Entity > Entity), not on level 3 (Root Entity > Entity > Entity), nor on the root entity (Root Entity >).\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce on current 11.0/bugfixes branch. Please try if you reproduce on a nightly build.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3424789641, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21560#issuecomment-3424789641", "createdAt": "2025-10-21T05:47:46Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "I'm on the latest stable version on a production server. I can't put the latest nightly build on a production server.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3425332039, "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21560#issuecomment-3425332039", "createdAt": "2025-10-21T08:10:10Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No, but you can on a test server.\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3426241247, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21560#issuecomment-3426241247", "createdAt": "2025-10-21T11:59:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21560, "url": "https://github.com/glpi-project/glpi/issues/21560", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-20T19:01:55Z", "updatedAt": "2026-02-05T00:40:05Z", "closedAt": "2025-10-27T11:13:46Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "When changing the computer name, there are two errors in the GLPI 11 Rc5 inventory.", "detail": "Affected version:\nGLPI 11 Rc5\n\nIssue description:\nWhen I change the computer name in GLPI 11 Rc5, two things happen: first, the log below appears, and second, the next time, instead of keeping the data updated on the same machine, it creates a new PC.\n\nRegarding the second issue, in my opinion, it is a bug, since in version 10, even if I change the computer name, it still keeps the same inventoried item (computer created).\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Provided log is about a Transfer issue, not related to a simple computer update.\n\nInventory issue is probably caused by a wrong rule, please reset rules to defaults.\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3336817776, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21158#issuecomment-3336817776", "createdAt": "2025-09-26T05:20:47Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "[Image omitted]\n\nMessage when updating the name: Item successfully updated: Test new name\nUser or group updated. Connected items have been moved to the same values.\n\nHello, what type of rule are you referring to? In my case, there is no separate rule created. I went to business rules for assets and disabled the three created, which were probably already part of the installation, and tried to import again. When I updated the PC name again, it created a new one in the new inventory.\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3338795118, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21158#issuecomment-3338795118", "createdAt": "2025-09-26T13:43:53Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "You have to reset rules used for inventory \"Rules for import and link equipments\".\n\nOriginal response date: 2025-10-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3360752099, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21158#issuecomment-3360752099", "createdAt": "2025-10-02T11:38:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21158, "url": "https://github.com/glpi-project/glpi/issues/21158", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "beta / rc" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-09-25T23:56:42Z", "updatedAt": "2026-02-05T00:39:57Z", "closedAt": "2025-10-27T13:49:16Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Forms: Checkbox options deleted by Short Answer field", "detail": "Affected version:\n11.0.0\n\nIssue description:\nWhen editing a form, hitting Enter/Return while in a Short Answer field (any type) which a Checkbox question somewhere else in the form, the options on the Checkbox question will vanish. It doesn't prompt you to Save, but saving will delete the option completely, and refreshing the page will return them.\n\nReproduction steps:\n1. Make a form\n2. Add a 'Checkbox' & 'Short Answer' question\n3. Type anything as checkbox options\n4. Click into the 'Short Answer' field, press Enter/Return", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I have no idea if that's been fixed, but please try with latest stable release (11.0.1).\n\nOriginal response date: 2025-10-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3414530232, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21534#issuecomment-3414530232", "createdAt": "2025-10-17T09:02:45Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "My Apologies, I am running 11.0.1\n\nOriginal response date: 2025-10-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3414537712, "author": "FMG-Jay", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21534#issuecomment-3414537712", "createdAt": "2025-10-17T09:05:01Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the bug.\nPressing the enter key in a short answer form is somehow triggering hidden buttons in the checkbox options list and causes the first option in the list to be removed every time.\n\nOriginal response date: 2025-10-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3417579747, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21534#issuecomment-3417579747", "createdAt": "2025-10-18T00:31:26Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21534, "url": "https://github.com/glpi-project/glpi/issues/21534", "author": "FMG-Jay", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-17T08:59:28Z", "updatedAt": "2026-02-01T00:45:18Z", "closedAt": "2025-10-23T05:06:54Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI 11 - Bugs while testing forms", "detail": "Affected version:\n11.0.0 RC 4\n\nIssue description:\nDisply bug while configurating conditions. The whole form crashed. I had to close it all.\n\n[Image omitted]", "priority": "medium", "type": "bug", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "We will need precise steps explaining how to reproduce the issue in order to move forward with it as it does not happen on any form on our side.\n\nOriginal response date: 2025-09-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3291460858, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20963#issuecomment-3291460858", "createdAt": "2025-09-15T10:24:49Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I might be able to reproduce the issue as someone else reported it to me with a migrated form, Iet's keep it open for now.\n\nOriginal response date: 2025-09-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3338585123, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20963#issuecomment-3338585123", "createdAt": "2025-09-26T12:50:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I'll close for now, we have a meeting planned for next week where we'll be able to discuss it directly if needed.\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3437381279, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20963#issuecomment-3437381279", "createdAt": "2025-10-23T14:36:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20963, "url": "https://github.com/glpi-project/glpi/issues/20963", "author": "agnesmorin-itgouv", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [ { "sourceLogin": "ccailly", "anonymizedEmail": "jordan.blair@peppermint.local" }, { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "beta / rc", "bug", "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-10T12:58:14Z", "updatedAt": "2026-02-01T00:44:57Z", "closedAt": "2025-10-23T14:36:35Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "GLPI 10.0.18 and 11.0.1 - Rule doesn't work when 'Status' and 'Validation' are in Criteria for action change 'Status'", "detail": "Affected version:\n10.0.18 and 11.0.1\n\nIssue description:\nWhen creating business rules for tickets or changes in version 11, you may encounter an issue if you use both 'Validation' as a criterion and 'Status' to change the ticket status upon granted validation.\n\nIn such cases, the rule does not function correctly. However, if you remove either the 'Validation' or the 'Status' criterion, the rule works. The combination of 'Status' and 'Validation' criteria, coupled with the action to change status, fails to operate as intended.\n\nInterestingly, the test rule engine indicates that it works.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. Create a new business rules for ticket or change in last version (110.0.1)\n2. On rule tab select value like this : [Image omitted]\n3. On Criteria tab select value like this : [Image omitted]\n4. On, Actions tab select value like this: [Image omitted]\n5. Create a ticket or change\n6. Use validation to ask approval from a specific user\n7. With the specific user grant approval\n8. Rule doesn't play and status don't change\n\nAdditional context:\nthis issue still seems alive since 2023 :", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.bennett@peppermint.local", "text": "Hello, as i read from the mention before, is that a bug or is that how the tool works ? Thanks\n\nOriginal response date: 2025-10-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3420883493, "author": "PowerMike-BZH", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21531#issuecomment-3420883493", "createdAt": "2025-10-20T07:20:20Z" } }, { "userEmail": "jamie.bennett@peppermint.local", "text": "Hello everyone, could i've answer about this problem ?\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3424893781, "author": "PowerMike-BZH", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21531#issuecomment-3424893781", "createdAt": "2025-10-21T06:23:39Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Seems a duplicate of #21538. See\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3424939015, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21531#issuecomment-3424939015", "createdAt": "2025-10-21T06:40:15Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21531, "url": "https://github.com/glpi-project/glpi/issues/21531", "author": "PowerMike-BZH", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-10-17T08:54:30Z", "updatedAt": "2026-01-30T00:37:52Z", "closedAt": "2025-10-21T06:40:15Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI 11- notification issue on ticket requesters", "detail": "Affected version:\n11.0\n\nIssue description:\nHi, I've been having a problem since updating to glpi 11, so I don't know if it's a bug or if it's me who's not good at configuring, but as soon as a user creates a ticket, email notifications are not active for them. But if you add someone to the requesters, this new person will be notified. Observers and technicians are already notified...\nI was able to test with 2 self-service users, for example Albert and Sara) if Albert creates a ticket, he will not be notified but if I manually add Sara to the requesters she will be notified and vice versa\nEmails are correctly configured for each user, as well as the entity. The groups set up for the comment notification are requester, observer, and technician.\nMy mail server is sending emails correctly, since technicians are receiving emails for ticket creation.\n\nEnvironment details:\nOperating system: Linux SRV-GLP-04 6.12.48+deb13-amd64 #​1 SMP PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20) x86_64\n\nPHP: 8.4.11 fpm-fcgi\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\ncgi-fcgi, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv,\nintl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer,\nxmlreader, xmlwriter, xsl, zip, Zend OPcache", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "and I also didn't notice that when the requester doesn't have notifications enabled, and the observers have notifications enabled (all on the same ticket), if we add a follow-up, the observers don't receive the modification made to the ticket by email. whereas if I manually activate notifications on the ticket notifications for the requester, everyone receives the notification email\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401370543, "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21438#issuecomment-3401370543", "createdAt": "2025-10-14T11:39:20Z" } }, { "userEmail": "robin.blair@peppermint.local", "text": "I see the same thing - I noticed that this is standard for a user who creates a ticket via the form (self service) the notification is not selected and the bell is grey. If a user submits a ticket via email then the notifications are enabled.\n\n[Image omitted]\n\nenabling the bell for user notifications presents a popup. Did you find a method of enabling it by default for form-submitted tickets?\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3413219922, "author": "gituser-bit1", "anonymizedAuthorEmail": "robin.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21438#issuecomment-3413219922", "createdAt": "2025-10-16T23:26:31Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Yes, I found the solution. You have to update to GLPI 11.0.1. They fixed the problem with this update (well, normally, at least when I did the update, it fixed the problem).\n\nOriginal response date: 2025-10-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3414137529, "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21438#issuecomment-3414137529", "createdAt": "2025-10-17T06:58:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21438, "url": "https://github.com/glpi-project/glpi/issues/21438", "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-13T08:43:19Z", "updatedAt": "2026-01-26T00:35:17Z", "closedAt": "2025-10-15T14:58:48Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI 11.0.1 | form problem", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWe're trying to create a form with checkboxes. We've set two questions to appear independently. They appear depending on which box is checked.\nOnly when one of the boxes is checked does the question appear. If we select another box to check, the hidden question that appeared last time disappears.\n1. [Image omitted]\n2. [Image omitted]\n3. [Image omitted]\n\nEnvironment details:\nGLPI: 11.0.1 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: fr_FR\n\nOperating system: Linux SRV-GLP-04 6.12.48+deb13-amd64 #​1 SMP PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20) x86_64\n\nPHP: 8.4.11 fpm-fcgi\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\ncgi-fcgi, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv,\nintl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer,\nxmlreader, xmlwriter, xsl, zip, Zend OPcache", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "I add that as soon as I check the 2 boxes causing the hidden questions to be displayed, nothing is displayed either.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3406932076, "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21505#issuecomment-3406932076", "createdAt": "2025-10-15T15:08:05Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "I tested it here on 11.0.1 and had no problems. I think the issue is that you are leaving the condition as “is equal to,” and in your case, it should be ‘contains’ because there is more than one option that can be selected. When you leave it as “is equal to,” it assumes that it will only appear if that option is selected.\n\nIt is not a problem with the form in this case, it is just a matter of logic in the hidden condition.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3407526642, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21505#issuecomment-3407526642", "createdAt": "2025-10-15T17:27:28Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "Thanks, I hadn't thought of that when designing the form\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3409460898, "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21505#issuecomment-3409460898", "createdAt": "2025-10-16T07:02:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21505, "url": "https://github.com/glpi-project/glpi/issues/21505", "author": "Sousou-cloud", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-15T14:57:48Z", "updatedAt": "2026-01-25T00:36:04Z", "closedAt": "2025-10-16T07:02:36Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Translate Arabic language", "detail": "Contribution description:\nhi\nI want to translate the Arabic language file ar_SA.po because it contains words that have not been translated, and the website shows an error 404 Error - We're sorry the page you're looking for is not available. I tried using the website and with the help of Gemini AI, I translated the defect in the file, but when I moved it to the program path and applied permissions to the file and ownership, the translation did not work or remained in its position.", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Translations are done only on transifex:\n\nIt currently works for me, if their website are down, you have to wait or contact them.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396143225, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21429#issuecomment-3396143225", "createdAt": "2025-10-13T07:12:06Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "okay it work now\nyou should change the url in\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396182072, "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21429#issuecomment-3396182072", "createdAt": "2025-10-13T07:21:37Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "okay it work now you should change the url in\n\nIndeed this link is wrong, we'll fix.\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396244491, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21429#issuecomment-3396244491", "createdAt": "2025-10-13T07:38:45Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21429, "url": "https://github.com/glpi-project/glpi/issues/21429", "author": "wastn", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-13T07:07:31Z", "updatedAt": "2026-01-22T00:34:52Z", "closedAt": "2025-10-13T07:12:06Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Generalize binary GUID attribute handling in AuthLDAP::getFieldValue() (start with ms-DS-ConsistencyGuid)", "detail": "Contribution description:\nContext\nAuthLDAP::getFieldValue() applies the binary-to-string GUID conversion only when the attribute name is literally objectguid (src/AuthLDAP.php, around line 4201 in 11.0.7). Any other 16-byte binary GUID attribute used as sync_field is returned as raw bytes, producing unreadable values in the LDAP information tab and in the database.\n\n[Image omitted]\n\nUse case\nms-DS-ConsistencyGuid is the immutable anchor that Microsoft documents for hybrid AD / Entra ID Connect deployments, because it survives inter-forest migrations where objectGUID does not (Microsoft Learn reference). Organizations consolidating AD domains cannot use it today in GLPI without ending up with binary garbage in glpi_users.sync_field.\n\nProposal\nGeneralize the existing logic to match a small explicit list of binary-GUID attributes (case-insensitive), keeping guidToString() as the conversion path. Two attributes to start: objectguid (no change in behavior) and ms-ds-consistencyguid. objectSid has a different binary layout and would need a separate decoder — out of scope for this PR.\nPatch is ready (about 11 inserted / 5 removed lines in a single hunk, plus unit tests). Happy to open the PR once the approach is agreed.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Happy to open the PR once the approach is agreed.\n\nCould you open the pull request so it can be reviewed? The approach makes sense to me and it should be easy to validate if you have unit tests ready. I don't have a hybrid AD/Azure/Entra setup but I should be able to do real tests by manually setting the attribute too.\n\nOriginal response date: 2026-05-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4553714222, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24332#issuecomment-4553714222", "createdAt": "2026-05-27T10:31:27Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Opened the pull request: 24367\n\nThe change generalizes the binary GUID handling to a small list of attribute names, covering both the LDAP search filter (searchUserDn) and the value read back from the directory (getFieldValue). I've verified it on a GLPI 11.0.7 instance against a real Active Directory with ms-DS-ConsistencyGuid populated: the field now renders as a canonical GUID string and user import/synchronization by that sync_field works. Screenshots are included in the PR.\n\nApologies for the earlier PR I opened yesterday — it only covered getFieldValue and missed the filter hex-escaping in searchUserDn, so synchronization wouldn't have actually worked. I've closed it; this one supersedes it.\n\nOriginal response date: 2026-05-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4562115692, "author": "danicouso", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24332#issuecomment-4562115692", "createdAt": "2026-05-28T08:28:25Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "fixed by #24367\n\nOriginal response date: 2026-07-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4849782127, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24332#issuecomment-4849782127", "createdAt": "2026-07-01T02:40:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24332, "url": "https://github.com/glpi-project/glpi/issues/24332", "author": "danicouso", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "danicouso", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-27T10:24:03Z", "updatedAt": "2026-07-01T02:40:52Z", "closedAt": "2026-07-01T02:40:52Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Authentication setup can't saved", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen you try to save the setup aunder authentication you can not save it becouse it redirects to general setup page\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. Go to authentication\n2. Go to Setup\n3. Try to save it\n4.\n\nEnvironment details:\nGLPI: 11.0.7 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_US\nOperating system: Linux glpi.okfo.gov.hu 5.15.0-97-generic #​107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 x86_64\n\nPHP: 8.3.26 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, apache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, igbinary, imagick, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"10000\" max_input_vars=\"10000\" memory_limit=\"512M\" post_max_size=\"512M\" session.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\" upload_max_filesize=\"512M\"\n\nWeb server: Apache/2.4.56 (Debian) (Apache/2.4.56 (Debian) Server at Port 80)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 11.2.3-MariaDB-1:11.2.3+maria~ubu2204\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@glpi-mariadb/glpidb\n\nHost info: glpi-mariadb via TCP/IP\n\nRequirements:\nPHP version (8.3.26) is supported.PHP version (8.3.26) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader, xmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (11.2.3) is supported.Database engine version (11.2.3) is supported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated. Write access to /var/www/html/glpi/files/_cron has been validated. Write access to /var/www/html/glpi/files has been validated. Write access to /var/www/html/glpi/files/_graphs has been validated. Write access to /var/www/html/glpi/files/_lock has been validated. Write access to /var/www/html/glpi/files/_pictures has been validated. Write access to /var/www/html/glpi/files/_plugins has been validated. Write access to /var/www/html/glpi/files/_rss has been validated. Write access to /var/www/html/glpi/files/_sessions has been validated. Write access to /var/www/html/glpi/files/_tmp has been validated. Write access to /var/www/html/glpi/files/_uploads has been validated.Write access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2, Phar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed: ctype, iconv, sodium.\nWrite access to /var/www/html/glpi/marketplace has been validated.Write access to /var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.Timezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce on 11.0/bugfixes branch. Try with a nightly build if you reproduce; and also try without plugins.\n\nOriginal response date: 2026-05-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4517895603, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24281#issuecomment-4517895603", "createdAt": "2026-05-22T10:31:45Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "I use the official 11.0.7 version on 3 instances (without plugins) and i got the same behavior. I will try the nightly build.\n\nOriginal response date: 2026-05-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4518249794, "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24281#issuecomment-4518249794", "createdAt": "2026-05-22T11:28:24Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Fixed by #24251\n\nOriginal response date: 2026-05-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4538395518, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24281#issuecomment-4538395518", "createdAt": "2026-05-26T00:24:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24281, "url": "https://github.com/glpi-project/glpi/issues/24281", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-22T06:05:08Z", "updatedAt": "2026-05-26T00:24:46Z", "closedAt": "2026-05-26T00:24:46Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI 11.0.7 Forms: Auto-Create Destination Change Error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWe are going to establish \"change management\" in our orgaization,\ninstead of using \"Tickets\" for that purpose.\n\nI have createt a new simple Form by hand,\nwith 1 field \"short answer\" for the (to be generated) change-title\nand 1 field \"long answer\" for the description\nForm activated and used\n\nResult is a error in files/_log/php-errors.log\n\n(Generating \"Destination\" Tickets using a Form is working well!)\n\nAffected page:\n\nReproduction steps:\n1. I have createt a new simple Form by hand,\n2. with 1 field \"short answer\" for the (to be generated) change-title\n3. and 1 field \"long answer\" for the description\n4. adding destination \"change\", setting \"#Answer:Kurztext\" fpr the title\n5. deleting destination \"ticket\"\n6. activate\n\nUsing the new Form, Result is a error in files/_log/php-errors.log", "priority": "medium", "type": "support", "createdByEmail": "lane.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "lane.bennett@peppermint.local", "text": "i tried to set a default change template in the Form->Destinations, i get the same error:\n\n[Image omitted]\n\nOriginal response date: 2026-05-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4405980858, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24176#issuecomment-4405980858", "createdAt": "2026-05-08T11:16:40Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "AH!\nThis solved the issue:\n\nAdding a template in the ITIL category\n\n[Image omitted]\n\nSet this category in the forms' destination\n\n[Image omitted]\n\nBut it remains, that there was no expicit warning/error message what exactly went wrong.\n\nOriginal response date: 2026-05-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4406013942, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24176#issuecomment-4406013942", "createdAt": "2026-05-08T11:22:11Z" } }, { "userEmail": "lane.bennett@peppermint.local", "text": "What is exactly happening in the system ?\n\nThe last step to solve, I assigned a specific \"Change template\" to the ITIL category.\n\nThe error mentions field \"changetemplates_id\",\n but the change template in the Form->Destination(type change)->Properties->Change template was set !\n\nSo the systems' search path was\nForm->ITIL-category->change template\ninstead of\nForm->Template ??\n\nOriginal response date: 2026-05-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4406042854, "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24176#issuecomment-4406042854", "createdAt": "2026-05-08T11:27:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24176, "url": "https://github.com/glpi-project/glpi/issues/24176", "author": "AlthausOV", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-05-08T09:41:40Z", "updatedAt": "2026-05-08T18:56:47Z", "closedAt": "2026-05-08T18:56:47Z" } }, { "title": "Migration from generic object to GLPI 11.0.4 - The object types families have not been imported as they are not handled by GLPI.", "detail": "Affected version:\n11.0.4\n\nIssue description:\n$ php bin/console migration:genericobject_plugin_to_core\n[>---------------------------] 0%\nImporting dropdowns definitions...\n16 dropdowns definitions successfully imported.\nThe migration failed.\n The object types families have not been imported as they are not handled by GLPI.\nx Unable to import the \"courier_id\" field.\nx Migration was aborted due to errors, all changes have been reverted.\n\nDiagnostic information:\nAnother fields for custom asset defined in files/_plugins/genericobject/fields/paymentterminal.constant.php\n\nOr files/_plugins/genericobject/fields/scannercharger.constant.php", "priority": "medium", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Seems like a bug with foreign key detection because you have a text field named with the same format GLPI uses for foreign keys *_id. I guess the check should be ignored for text fields.\n\nOriginal response date: 2025-12-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3687154577, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22456#issuecomment-3687154577", "createdAt": "2025-12-23T16:02:39Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Taylor Adler When can we expect a fix (in which version) or a workaround?\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3960862111, "author": "Wolvverine", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22456#issuecomment-3960862111", "createdAt": "2026-02-25T17:37:01Z" } }, { "userEmail": "kai.bennett@peppermint.local", "text": "Taylor Adler check this:\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4313986627, "author": "Wolvverine", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22456#issuecomment-4313986627", "createdAt": "2026-04-24T14:37:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22456, "url": "https://github.com/glpi-project/glpi/issues/22456", "author": "Wolvverine", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-19T23:15:55Z", "updatedAt": "2026-05-05T11:41:03Z", "closedAt": "2026-05-05T11:41:03Z" } }, { "title": "Bulleted Lists start on wrong line in Change body fields", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nBulleted lists - starting on wrong line.\n\nIssue description:\nIf you type a paragraph of text, and then you go to a new line, and you click the 'bulleted list' button, the bulleted list starts with the paragraph, instead of the line that you're on.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I do not understand/see the issue you are describing. Please including a screen capture and include the information that was requested in the bug report template.\n\nOriginal response date: 2026-04-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4328343471, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24029#issuecomment-4328343471", "createdAt": "2026-04-27T15:39:40Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Paragraph of text entered with the insertion point on a new line below the paragraph:\n[Image omitted]\n\nBulleted list button clicked, bulleted list started on wrong line...\n\n[Image omitted]\n\nOriginal response date: 2026-04-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4328409815, "author": "bturnbough81", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24029#issuecomment-4328409815", "createdAt": "2026-04-27T15:49:15Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "This isn't a GLPI issue and may not be considered a TinyMCE issue either. Paragraph elements are not allowed to contain list elements in HTML. It seems like you stayed within the paragraph by using Shift+Enter and this is no different than having your cursor within a line of text and clicking the list button to convert it to a list.\n\nOriginal response date: 2026-04-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4328780654, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24029#issuecomment-4328780654", "createdAt": "2026-04-27T16:43:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24029, "url": "https://github.com/glpi-project/glpi/issues/24029", "author": "bturnbough81", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-04-27T15:36:22Z", "updatedAt": "2026-04-27T18:49:13Z", "closedAt": "2026-04-27T18:49:13Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Type field not displayed on ticket Template", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.5\n\nIssue description:\n[Image omitted]\n\nType field is not displayed from ticket template\n\nDue to TicketTempalteMandatoryField.php\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I'm not sure this makes sense to me. It is impossible for a ticket to not have a type, so therefore it is always mandatory.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3897606092, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23093#issuecomment-3897606092", "createdAt": "2026-02-13T14:46:04Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "ok no problem, but counter on tab says 5 and not 4 - so confusing for users\n\nOriginal response date: 2026-02-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3919314993, "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23093#issuecomment-3919314993", "createdAt": "2026-02-18T08:09:32Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I am not sure how to recreate this issue unless the Type field was added directly in the database or a bug made it show in the UI previously.\n\nOriginal response date: 2026-04-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4188781312, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23093#issuecomment-4188781312", "createdAt": "2026-04-05T12:01:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23093, "url": "https://github.com/glpi-project/glpi/issues/23093", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [ "need feedback", "ui" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-12T09:42:11Z", "updatedAt": "2026-04-24T06:52:45Z", "closedAt": "2026-04-24T06:52:45Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Simplified interface layout breaks when viewing closed tickets after solution validation", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nI retested the original solution approval / refusal behavior in simplified interface and the workflow itself is now working correctly once the profile lifecycle is configured properly.\n\nHowever, I found a different issue related to the UI layout.\n\nIn the simplified interface:\n- open / active tickets are displayed correctly;\n- once the ticket reaches the Closed state after solution validation, the ticket view becomes visually broken / misaligned.\n\nThis appears to be a visual/layout issue only. The approval/refusal workflow itself is working.\n\nSteps to reproduce:\n1. Use a profile with simplified interface.\n2. Configure the ticket lifecycle to allow the transition from Resolved to Closed.\n3. Log in as the ticket requester.\n4. Open a ticket in simplified interface.\n5. Validate the proposed solution so the ticket moves to Closed.\n6. Open the closed ticket again.\n7. Observe that the layout is broken, with large blank areas and misaligned content.\n\nExpected behavior:\nClosed tickets in simplified interface should keep the same correct layout as open tickets.\n\nActual behavior:\nWhen the ticket is in Closed state, the simplified interface layout becomes broken / misaligned. Large blank areas appear and the ticket content is no longer rendered correctly.\n\nInstalled plugins:\n- ActualTime 4.0.0\n- advancedforms 1.0.1\n- Costs 4.0.0\n- Escalation 2.10.1\n- gantt 1.3.2\n- GLPI Inventory 1.6.7\n- OAuth IMAP 1.5.0\n- One-Time Secret 3.0.0\n- PDF 4.1.2\n- Used items export 2.6.1\n\nAdditional notes:\n\n- The visual issue appears specifically when the ticket is viewed in Closed state.\n- No relevant PHP/server-side errors were observed during reproduction.\n- No console errors were observed in Edge DevTools during reproduction.\n- I attached screenshots comparing an open ticket (rendered correctly) and a closed ticket (broken layout).\n- I also attached screenshots from DevTools showing a noticeable difference in the rendered page structure between the working and broken cases.\n\n[Image omitted]\n[Image omitted]\n\nReproduction steps:\nSteps to reproduce:\n1. Use a profile with simplified interface.\n2. Configure the ticket lifecycle to allow the transition from Resolved to Closed.\n3. Log in as the ticket requester.\n4. Open a ticket in simplified interface.\n5. Validate the proposed solution so the ticket moves to Closed.\n6. Open the closed ticket again.\n7. Observe that the layout is broken, with large blank areas and misaligned content.\n\nEnvironment details:\nEnvironment:\n- GLPI: 11.0.6\n- PHP: 8.4.18 fpm-fcgi\n- Web server: Apache/2.4.63 (Rocky Linux)\n- Database: MariaDB Server 11.4.5-MariaDB\n- Browser: Microsoft Edge 145.0.0.0", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I was not able to recreate the issue, although I don't have Edge (but I tested with Chrome and both are based on Chromium). Please verify you have tested this with all plugins disabled. Several of your plugins may be modifying the ticket form page.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4042977844, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23441#issuecomment-4042977844", "createdAt": "2026-03-11T23:57:40Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "Hi,\n\nI retested the issue with all plugins disabled and it is still reproducible.\n\nI checked this in two ways:\n1. by manually disabling the installed plugins;\n2. by using the “Suspend execution of all plugins” option.\n\nI also reproduced it in a private/incognito session, and the problem persists.\n\nAdditionally, I tested it in Brave as well, and the same layout issue is present there too.\n\nSo at least on my side, this does not seem to be caused by a plugin or by a browser-specific issue limited to Edge.\n\nWhat I observe is:\n- in simplified interface, open tickets are rendered correctly;\n- when the ticket is in Closed state, the layout becomes broken / misaligned;\n\nIf useful, I can provide additional screenshots or further browser tests.\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4043229262, "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23441#issuecomment-4043229262", "createdAt": "2026-03-12T01:12:45Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Replaced by #23943\n\nOriginal response date: 2026-04-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4263065424, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23441#issuecomment-4263065424", "createdAt": "2026-04-16T20:07:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23441, "url": "https://github.com/glpi-project/glpi/issues/23441", "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-03-10T15:01:00Z", "updatedAt": "2026-04-16T20:07:53Z", "closedAt": "2026-04-16T20:07:53Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "API: Delete user or assets always force", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen I delete a user or a Computer with the API, even when force is set to false.\n\nTested with a Powershell script that connect to the API, and directly with the web API Endpoint at\n\nReproduction steps:\n1. Go to API Endpoint\n2. Log in with valid credential in \"Authorize\"\n3. Try to Delete a user, or a Computer with force=false\n4. The user is completely deleted, without going to the trash.", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please provide the exact request being used (minus any authorization headers of course).\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4253230480, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23891#issuecomment-4253230480", "createdAt": "2026-04-15T15:11:29Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "If you are using \"?force=false\" then the value is a string of \"false\", not a boolean, and it is evaluated as true in PHP. It was originally intended to use 1 or 0 as the value. If you don't intend to permanently delete something, it is best to omit the parameter entirely to avoid mistakes. I'll open a PR to make it a little smarter in parsing the parameter.\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4253285854, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23891#issuecomment-4253285854", "createdAt": "2026-04-15T15:19:22Z" } }, { "userEmail": "taylor.bennett@peppermint.local", "text": "curl -X 'DELETE' \\\n '' \\\n -H 'accept: */*' \\\n -H 'Accept-Language: en_GB' \\\n -H 'Authorization: Bearer xxxxxxxxx'\n\nI was using the parameter like it's used in the web API Endpoint.\n\n[Image omitted]\n\nOh, I understand ok\nWhen using 0 or 1, it works perfectly !\n\nI have adapted my script to use this instead of true and false.\n\nIt all good for me, thanks !\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4253596467, "author": "Izanagi52", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23891#issuecomment-4253596467", "createdAt": "2026-04-15T16:05:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23891, "url": "https://github.com/glpi-project/glpi/issues/23891", "author": "Izanagi52", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-15T13:57:38Z", "updatedAt": "2026-04-16T11:31:02Z", "closedAt": "2026-04-16T11:31:02Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "MACOS : Component - Hard Drive Size problem", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.24\n\nIssue description:\nHello, using GLPI-AGENT 1.16 and 1.17 on MACOS Sonoma, we can see that the display of the Component - Hard Drive size is not present. In the computer, we can the the partition.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Hard drive size and volume space are not the same thing in GLPI. Please check if there are hard drives under the MACOS computer's Components tab and that they have a size.\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4254368854, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23877#issuecomment-4254368854", "createdAt": "2026-04-15T18:08:16Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "Hello, good point, there is no hard drive in the computer's component !!! I've double checked with ./glpi-inventory --json > inventory.json and nothing in. I've got this from MAC OS 15 to the last 26.4.1.\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4255236868, "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23877#issuecomment-4255236868", "createdAt": "2026-04-15T20:28:20Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "If information is not present in inventory file, it's either an agent issue, or a misconfiguration - this is not a GLPI issue anyway.\n\nOriginal response date: 2026-04-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4257498935, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23877#issuecomment-4257498935", "createdAt": "2026-04-16T05:03:00Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23877, "url": "https://github.com/glpi-project/glpi/issues/23877", "author": "tristangallet", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-04-15T06:55:26Z", "updatedAt": "2026-04-16T05:03:00Z", "closedAt": "2026-04-16T05:03:00Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Problem validating a form with full access", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello, I want to share a link to a form accessible without logging in using GLPI 11.0.5.\nThe link correctly redirects to the page, but when the captcha (not a robot, protected by ALCHA) is clicked, the text \"Verification in progress...\" is displayed continuously. If the \"Submit\" button is clicked anyway, a message appears saying \"Form submission failed, please contact your administrator.\"\nThere are no messages in the logs. The problem is the same in Firefox and Chrome.\nThe problem persists even with all plugins disabled.\nIt was also identified here: without any solutions being found.\n\nAffected page:\nxxx.xxx.xxx.xxx/Form/Render/9?token=e7CmjZdKgj3lqw6qRs2stmLoF0Gf3Vuy1gAom2nWN", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.bennett@peppermint.local", "text": "PS : My GLPI site is ; no\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3968961095, "author": "IP-V15", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23262#issuecomment-3968961095", "createdAt": "2026-02-26T20:11:45Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "I found that :\nbut I don't see the captcha disable button on my stable version.\n\nOriginal response date: 2026-02-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3971999216, "author": "IP-V15", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23262#issuecomment-3971999216", "createdAt": "2026-02-27T10:12:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Skyler Bennett,\n\nI believe there should be an error in your browser's console causing the captcha to fail loading, can you check it out?\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4111081475, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23262#issuecomment-4111081475", "createdAt": "2026-03-23T14:32:59Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23262, "url": "https://github.com/glpi-project/glpi/issues/23262", "author": "IP-V15", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [], "labels": [ "forms", "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-26T20:09:20Z", "updatedAt": "2026-04-15T05:57:47Z", "closedAt": "2026-04-15T05:57:47Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Linked assistance objects search restricted to active entity, ignoring cross-entity visibility", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.1\n\nIssue description:\nGLPI Version: 11.0.1 (all 11.0.2-3-4-5 and 6)\nPHP Version: 8.2.30\nMysql Version: 8.4\n\nDropdown.php\n\nBug description:\nWhen trying to link tickets from different child entities using \"Linked assistance objects\",\nthe search returns no results even for Super-Admin with tree entity visibility.\n\nRoot cause:\nIn templates/components/itilobject/linked_itilobjects.html.twig line 102:\n'entity_restrict': session('glpiactive_entity')\nThis restricts search to the current active entity only.\n\nAdditionally in src/Dropdown.php line ~3767,\nSession::getMatchingActiveEntities() overwrites any -1 value passed.\n\nFix applied:\n1. Change entity_restrict to -1 in linked_itilobjects.html.twig\n2. Add && $post['entity_restrict'] !== -1 condition in Dropdown.php\n\nSteps to reproduce:\n1. Have tickets in different child entities\n2. Try to link them via \"Linked assistance objects\"\n3. Search returns \"No results found\"", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.bennett@peppermint.local", "text": "This directly resolves the issue of linking a ticket to: Linked support objects\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4076901483, "author": "michaelmartinez-sistemasentry", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23517#issuecomment-4076901483", "createdAt": "2026-03-17T17:57:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "11.0.1 is really outdated; you should consider upgrading.\n\nTo propose code changes, please open a pull request.\n\nOriginal response date: 2026-03-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4080457283, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23517#issuecomment-4080457283", "createdAt": "2026-03-18T07:58:44Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "(of course, try first on latest stable if the issue is reproducible)\n\nOriginal response date: 2026-03-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4080458755, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23517#issuecomment-4080458755", "createdAt": "2026-03-18T07:59:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23517, "url": "https://github.com/glpi-project/glpi/issues/23517", "author": "michaelmartinez-sistemasentry", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-03-17T17:54:04Z", "updatedAt": "2026-04-15T05:56:46Z", "closedAt": "2026-04-15T05:56:46Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Problem with linking Tickets in the Helpdesk", "detail": "Affected version:\nGLPI 11.0.4\n\nIssue description:\nHello i has problem to linking tickets when i try these in the Helpdesk Field then i become only these -----.\nWhen i go Helpdesk Element in the Ticket > then to Tickets.\nIts since the upgrade to Version 11 from Version 10 before i has no problem with these.\nI has made me an Admin Profile with all rights for the Main Entity.\n\n[Image omitted]\n\nAdditional context:\nIts mostly when the ticket is transfered to an entity if the tickets has no entity and they are in the default then there i can linke the tickets.", "priority": "medium", "type": "support", "createdByEmail": "devon.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "parker.blair@peppermint.local", "text": "I have the same problem with GLPI 11.0.4\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3811265848, "author": "Pyroteknix25", "anonymizedAuthorEmail": "parker.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22631#issuecomment-3811265848", "createdAt": "2026-01-28T13:18:20Z" } }, { "userEmail": "quinn.bennett@peppermint.local", "text": "I noticed that only the tickets that belongs to the currnetly active entity are available to associate.\nFor example: The ticket belongs to a child entity and the user is logged in the root entity, only the tickets from the root entity are shown. If the user change to the child entity, other tickets from this entity are available.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3868836125, "author": "raultak", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22631#issuecomment-3868836125", "createdAt": "2026-02-09T01:38:20Z" } }, { "userEmail": "quinn.blair@peppermint.local", "text": "I noticed that only the tickets that belongs to the currnetly active entity are available to associate. For example: The ticket belongs to a child entity and the user is logged in the root entity, only the tickets from the root entity are shown. If the user change to the child entity, other tickets from this entity are available.\n\nI have the same bug in GLPI 11.0.5\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3965794058, "author": "TIITANIC1912", "anonymizedAuthorEmail": "quinn.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22631#issuecomment-3965794058", "createdAt": "2026-02-26T10:49:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22631, "url": "https://github.com/glpi-project/glpi/issues/22631", "author": "MKNRTV", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-12T15:14:52Z", "updatedAt": "2026-04-14T09:29:18Z", "closedAt": "2026-04-14T09:29:18Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 11 API v2.2 - ERROR ON DOCUMENTATION PAGE", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello.\n\nI’ve somehow managed to bug the Swagger documentation page for the new API, and it’s stuck on this OAuth token error screen. I’ve been facing this issue for a while now, and I’ve even updated GLPI twice since it started.\n\n[Image omitted]\n\nIt happened when I tried to authenticate a user through the Swagger interface. Since then, it has been stuck on this error. I’ve already cleared the browser cache, the GLPI cache, and tested it in different browsers, but the problem persists.\n\nThe legacy API is working fine, but the new one handles Defined Assets much better. If anyone knows how to resolve this, I would greatly appreciate it.\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Do you have some web server configuration, or something else that always adds an Authorization header to your requests to GLPI?\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4237005950, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23848#issuecomment-4237005950", "createdAt": "2026-04-13T14:08:04Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "Yes, my GLPI is currently behind two Nginx web servers.\n\nThe first is an edge (entry) server that receives requests via the domain and forwards them to the GLPI server for external traffic.\n\nThe second is on the GLPI server itself, which was previously used to deliver GLPI only on the internal network.\n\nBelow are their configuration files:\n\nFirst (External):\n\nSecond (Internal):\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4237380356, "author": "coca-mann", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23848#issuecomment-4237380356", "createdAt": "2026-04-13T14:59:29Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "I managed to solve it.\n\nI commented out the line fastcgi_param HTTP_AUTHORIZATION $http_authorization in the internal Nginx config, and the API documentation loaded.\n\nTaylor Adler I wouldn't have figured it out without your question opening my eyes to this issue.\n\nThank you very much, and sorry for the trouble.\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4237623360, "author": "coca-mann", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23848#issuecomment-4237623360", "createdAt": "2026-04-13T15:30:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23848, "url": "https://github.com/glpi-project/glpi/issues/23848", "author": "coca-mann", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-13T13:50:18Z", "updatedAt": "2026-04-13T15:30:55Z", "closedAt": "2026-04-13T15:30:55Z" } }, { "title": "Creating A Problem from computer leads to error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen opening a problem from a computer element the following error happens\n\n[Image omitted]\n\nGoing back to the previous site and adding the the problem again succeeds but adds two identical problems.\n\nWe already have patch #22903 applied", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirmed the issue.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3897550915, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23111#issuecomment-3897550915", "createdAt": "2026-02-13T14:35:07Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The issue still happens with 11.0.6 looks like the fix was not successful\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4004139266, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23111#issuecomment-4004139266", "createdAt": "2026-03-05T10:43:58Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please open a new issue with all requested details.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4004165772, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23111#issuecomment-4004165772", "createdAt": "2026-03-05T10:48:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23111, "url": "https://github.com/glpi-project/glpi/issues/23111", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-13T13:27:18Z", "updatedAt": "2026-03-05T10:48:52Z", "closedAt": "2026-02-24T13:08:19Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Unable to open new ticket - An unexpected error occurred", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWe are encountering an issue when creating tickets with the Super-Admin profile. The system returns the error:\n\"An unexpected error occurred.\"\n\nThe issue does not occur with the Self-service profile, and ticket creation via the email receiver is functioning correctly.\n\nAffected page:\n\nReproduction steps:\n1. Open new ticket:\nNew ticket\n\n2. Fill forms and add new ticket\nAdd ticket\n\n3. An unexpected error occurred", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Already reported and fixed\n\nOriginal response date: 2026-02-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3906517687, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23116#issuecomment-3906517687", "createdAt": "2026-02-16T05:26:44Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Already reported and fixed\n\nIn which version was it fixed? I'm on 11.0.5\n\nOriginal response date: 2026-02-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3920110467, "author": "dioig0", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23116#issuecomment-3920110467", "createdAt": "2026-02-18T10:53:01Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Will be fixed in 11.0.6.\n\nOriginal response date: 2026-02-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3920552524, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23116#issuecomment-3920552524", "createdAt": "2026-02-18T12:26:37Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23116, "url": "https://github.com/glpi-project/glpi/issues/23116", "author": "dioig0", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-02-13T16:13:49Z", "updatedAt": "2026-02-18T12:26:41Z", "closedAt": "2026-02-16T05:26:44Z" } }, { "title": "Incorrect counter \"Tickets waiting for your approval\" on /front/helpdesk.public.php", "detail": "Affected version:\n10.0.15\n\nIssue description:\nIncorrect display counter \"Tickets waiting for your approval\" on /front/helpdesk.public.php for self-service profile.\n\nThe number of tickets awaiting approval is displayed incorrectly. All tickets are displayed and counted, including those with the status resolved and closed. Only tickets with the not-solved status should be included in the counter.\n\nThe counter should only count tickets with the status Not Solved.\nThe search filter that opens when you click on the counter should also include a filter by status - Not Solved\n\nI also noticed that the counter on /front/helpdesk.public.php and after following the link (by clicking on the counter - /front/ticket.php?....) displays a different number of tickets\n\nAffected page:\n/front/helpdesk.public.php", "priority": "medium", "type": "bug", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "emerson.bennett@peppermint.local", "text": "Is it possible to fix this in GLPI version 10? Maybe some code or changes from version 11 can be ported over?\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3870789308, "author": "ak47d", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/17215#issuecomment-3870789308", "createdAt": "2026-02-09T10:21:27Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "It's not possible to report all changes on v10; consider upgrading. v10 will not be supported at some point anyway.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3870804125, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/17215#issuecomment-3870804125", "createdAt": "2026-02-09T10:24:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 17215, "url": "https://github.com/glpi-project/glpi/issues/17215", "author": "ak47d", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2024-05-31T22:07:18Z", "updatedAt": "2026-02-09T10:24:38Z", "closedAt": "2025-05-25T13:04:10Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "notimportedemail empty itself", "detail": "Issue description:\nDescribe the bug\n\nWhen an email get rejected by mailcollectors, they appears in the front/notimportedemail.php interface. Few minutes later, the list get emptied and all the rejected emails disappears so we can't get to see what was causing the rejection.\n\nIt's like the table in the database get flushed by some function.\n\nNot sure if the problem happened on earlier version because we were missing a column (users_id) in the glpi_notimportedemails table but since fixed, I see them getting added to the list/table but then, get flushed.\n\nPage(s) URL\n\nfront/notimportedemail.php\n\nTo reproduce\n\nSteps to reproduce the behavior:\nGet an email denied for whatever reason (user don't exist, permissions, etc)\nGo quickly to the front/notimportedemail.php page or in the database and see the email with the reason for refusal\nGo back to the same page or database later, the table is empty\n\nExpected behavior\n\nEmails not imported should stay present in the section\n\nLogs\n\ndidn't see any error related to this in the logs\n\nScreenshots\n\nYour GLPI setup (you can find it in Setup > General menu, System tab)\n\n[code]   GLPI 9.5.2 (/glpi => /var/www/html/glpi-9.5.2) Installation mode: TARBALL\n--\n\nOperating system: Linux glpi06 3.10.0-1127.19.1.el7.x86_64 #1 SMP Tue Aug 25 17:23:54 UTC 2020 x86_64 PHP 7.3.24 apache2handler (Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, apcu, bcmath, bz2, calendar, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, imap, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_sqlite, posix, session, shmop, soap, sockets, sodium, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib) Setup: max_execution_time=\"30\" memory_limit=\"256M\" post_max_size=\"8M\" safe_mode=\"\" session.save_handler=\"files\" upload_max_filesize=\"8M\" Software: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.3.24 () Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.193 Safari/537.36 Server Software: Source distribution Server Version: 8.0.21 Server SQL Mode: Parameters: REDACTED/glpi Host info: REDACTED via TCP/IP PHP version is at least 7.2.0 - Perfect! Sessions support is available - Perfect! Allocated memory > 64 Mio - Perfect! mysqli extension is installed ctype extension is installed fileinfo extension is installed json extension is installed mbstring extension is installed iconv extension is installed zlib extension is installed curl extension is installed gd extension is installed simplexml extension is installed intl extension is installed ldap extension is installed apcu extension is installed Zend OPcache extension is installed xmlrpc extension is installed CAS extension is installed exif extension is installed zip extension is installed bz2 extension is installed sodium extension is installed Database version seems correct (8.0.21) - Perfect! Timezones seems loaded in database The log file has been created successfully. Write access to /var/www/glpiData/config/ has been validated. Write access to /var/www/glpiData/files has been validated. Write access to /var/www/glpiData/files/_dumps has been validated. Write access to /var/www/glpiData/files/_sessions has been validated. Write access to /var/www/glpiData/files/_cron has been validated. Write access to /var/www/glpiData/files/_graphs has been validated. Write access to /var/www/glpiData/files/_lock has been validated. Write access to /var/www/glpiData/files/_plugins has been validated. Write access to /var/www/glpiData/files/_tmp has been validated. Write access to /var/www/glpiData/files/_cache has been validated. Write access to /var/www/glpiData/files/_rss has been validated. Write access to /var/www/glpiData/files/_uploads has been validated. Write access to /var/www/glpiData/files/_pictures has been validated. Write access to /var/www/html/glpi-9.5.2/marketplace has been validated. For security reasons, SELinux mode should be Enforcing.\n\nGLPI_ROOT: /var/www/html/glpi-9.5.2 GLPI_CONFIG_DIR: /var/www/glpiData/config/ GLPI_VAR_DIR: /var/www/glpiData/files GLPI_LOG_DIR: /var/log/glpi GLPI_MARKETPLACE_DIR: /var/www/html/glpi-9.5.2/marketplace GLPI_USE_CSRF_CHECK: 1 GLPI_CSRF_EXPIRES: 7200 GLPI_CSRF_MAX_TOKENS: 100 GLPI_TELEMETRY_URI: GLPI_INSTALL_MODE: TARBALL GLPI_NETWORK_MAIL: [email redacted] GLPI_NETWORK_SERVICES: GLPI_MARKETPLACE_PRERELEASES: GLPI_USER_AGENT_EXTRA_COMMENTS: GLPI_AJAX_DASHBOARD: 1 GLPI_CALDAV_IMPORT_STATE: 0 GLPI_DEMO_MODE: 0 GLPI_FORCE_EMPTY_SQL_MODE: 1 GLPI_DOC_DIR: /var/www/glpiData/files GLPI_CACHE_DIR: /var/www/glpiData/files/_cache GLPI_CRON_DIR: /var/www/glpiData/files/_cron GLPI_DUMP_DIR: /var/www/glpiData/files/_dumps GLPI_GRAPH_DIR: /var/www/glpiData/files/_graphs GLPI_LOCAL_I18N_DIR: /var/www/glpiData/files/_locales GLPI_LOCK_DIR: /var/www/glpiData/files/_lock\n\n[Content truncated.]", "priority": "low", "type": "feature", "createdByEmail": "remy.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "harper.bennett@peppermint.local", "text": "### Still relevant in recent versions – automatic cleanup makes the feature unusable\n\nWe are still observing this behavior today (GLPI 10.x):\n\n* A rejected email does appear briefly in *Not imported emails* (front/notimportedemail.php).\n* Seconds or minutes later it disappears, and the corresponding record is removed from glpi_notimportedemails.\n\nThis confirms what was already described in this issue: entries are automatically deleted by design, not by user configuration.\n\n---\n\n### Why this is a real problem\n\nWhile this was previously classified as *not a bug*, the current behavior effectively defeats the purpose of having a UI and a database table for rejected emails:\n\n* Administrators cannot reliably inspect why emails are rejected.\n* With mailgate running frequently (every 1–2 minutes is common), the list is almost always empty.\n* The feature exists in the interface, but is unusable in practice.\n\nIn real-world operations, this causes loss of traceability and makes troubleshooting mail issues unnecessarily difficult.\n\n---\n\n### Proposal (already suggested in this issue, still valid)\n\nAs already mentioned by Skyler Adler back in 2020, a time-based cleanup would make much more sense than an immediate purge.\n\nSuggested approaches:\n\n* Do not delete entries immediately.\n* Integrate the cleanup into automatic purge tasks, like other GLPI data.\n* Keep rejected emails for a configurable retention period, for example:\n\n * 30 days (preferred)\n * or at least 15 or 10 days\n\nThis would:\n\n* preserve useful diagnostic information\n* avoid database overload\n* align this feature with other GLPI purge mechanisms\n\n---\n\n### Why this should be reconsidered now\n\n* Mailgate usage has increased significantly.\n* Email rejection debugging is critical in modern deployments (shared mailboxes, external senders, security rules).\n* GLPI 10.x and later versions expose this UI, which creates an expectation that the data is actually usable.\n\nAt the moment, the near-instant cleanup removes most of the practical value of this feature.\n\n---\n\n### Summary\n\n* The behavior described in this issue is still reproducible today.\n* Immediate deletion of glpi_notimportedemails records makes the interface ineffective.\n* A retention-based cleanup (10–30 days) would be a reasonable and low-risk improvement.\n\nWe believe it is worth reconsidering this enhancement, even if implemented incrementally.\n\nThanks for taking another look at this.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3876812949, "author": "SruiSan", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/8297#issuecomment-3876812949", "createdAt": "2026-02-10T10:41:28Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please use suggestions website for RFEs.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3876838622, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/8297#issuecomment-3876838622", "createdAt": "2026-02-10T10:46:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 8297, "url": "https://github.com/glpi-project/glpi/issues/8297", "author": "fralla2", "anonymizedAuthorEmail": "remy.adler@peppermint.local", "assignees": [], "labels": [ "enhancement", "stale" ], "state": "closed", "stateReason": "completed", "createdAt": "2020-11-18T20:49:02Z", "updatedAt": "2026-02-10T10:46:50Z", "closedAt": "2021-11-26T08:07:49Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Review our CSRF policy for better UX", "detail": "Issue description:\nThere are two ways to handle CSRF tokens:\n- Generate single token per session (a bit less secure but better for UX).\n- Generate a new token for each POST action (more secure, but worse for UX as user that press the \"back\" button on their browser won't be able to submit a form).\n\nCSRF tokens should be generated on the server-side and they should be generated only once per user session or each request. Because the time range for an attacker to exploit the stolen tokens is minimal for per-request tokens, they are more secure than per-session tokens. However, using per-request tokens may result in usability concerns.\n\nFor example, the \"Back\" button browser capability can be hindered by a per-request token as the previous page may contain a token that is no longer valid. In this case, interaction with a previous page will result in a CSRF false positive security event on the server-side. If per-session token implementations occur after the initial generation of a token, the value is stored in the session and is used for each subsequent request until the session expires.\n\nThe problem with GLPI is that we implement both of these solutions, meaning we get both drawbacks (less secure and worse UX) and none of the benefits.\n\nIndeed, we have a specific per token form that will result in the \"bad UX\" downside of a broken \"back\" action (I think we've all experienced it) but it doesn't come with the benefits of extra protection because we also have reusable tokens for AJAX requests that are easily retrieved and could be used without limits on any forms by a malicious user.\n\nSince we have no extra security benefits, maybe we could switch to a single per session token to improve our UX at no security cost?\n\nI'm opening this discussion because I've noticed that this behavior make the new \"Import form\" feature less convenient to use.\nIndeed, this action is based on multiple chained POST actions and as a user it is very tempting to press the browser's back button to go back to the previous step (which mean you lose all progress and have to start your import again as you will fail CSRF check).\nObviously this applies everywhere on GLPI, the benefits would not be limited to this feature as this is a very common issue.\n\nThis could be done quite easily on the 11.0 branch, as the change to make this effective would be very minimal and completely safe:\n\nThis would bring a UX improvement right away.\n\nThen on the main branch the code could be reworked more efficiently to remove the useless preserve_token parameter and make sure only a single token is generated (i.e. delay riskier changes to the next major to avoid any bugs).", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I may start working on this while waiting for my others PRs to be reviewed/merged.\n\nThus, I am researching the subject again and it seems CRSF token could potentially be totally removed in favor of fetch metadata.\n\nThere was recently a discussion on OWASP's github repository about whether or not fetch metadata was a good enough standalone solutions to protect against CSRF attacks and it concluded that it does.\n\nDon't take my word for it and read it here:\n\nDo you agree?\n\nOriginal response date: 2026-01-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3719324563, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20803#issuecomment-3719324563", "createdAt": "2026-01-07T15:10:58Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I do not have time to read the full documentation right now. If it permit to have the same level of protection with simplier code, then it is OK for me.\n\nOriginal response date: 2026-01-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3719525668, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20803#issuecomment-3719525668", "createdAt": "2026-01-07T15:48:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20803, "url": "https://github.com/glpi-project/glpi/issues/20803", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-08-27T11:12:50Z", "updatedAt": "2026-04-16T07:22:01Z", "closedAt": "2026-04-16T07:22:01Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Drag and Drop of some documenttypes fails in editor window", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen writing an answer to a change, ticket or problem and dragging in a filetype other than an image into the editor window it blocks the upload\n[Image omitted]\nUploading the file directly via the button works or dragging it into the lower area. In my case I tested it with a pdf.\n\nI think the behavior should be consistent with images: When dragging a file into the editor the upload should be triggered and the file should be replaced with a link to the uploaded document. If I remember correctly this is how it worked in glpi 10.\n\nI tested in chrome and firefox", "priority": "low", "type": "feature", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I checked and this behavior has not changed between GLPI 10 and 11.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4139181266, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23493#issuecomment-4139181266", "createdAt": "2026-03-27T00:21:49Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Really ? Than I'm sorry for suggesting the behavior changed and wondering how I missed that before. Thank you for investigating.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4140583715, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23493#issuecomment-4140583715", "createdAt": "2026-03-27T06:52:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23493, "url": "https://github.com/glpi-project/glpi/issues/23493", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-16T09:47:30Z", "updatedAt": "2026-07-06T00:53:35Z", "closedAt": "2026-03-27T00:21:31Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Database schema not compliant after upgrading GLPI from 10.0.7 to 11.0.6", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAfter upgrading GLPI from version 10.0.7 to 11.0.6, the migration process completes but GLPI displays the following error message:\n\n\"Le schéma de base de données n'est pas conforme à celui de la version actuelle de GLPI.\" /\n\"The database schema is not compliant with the current GLPI version.\"\n\nBecause of this, the instance does not appear to be fully migrated.\n\nReproduction steps:\n1. Upgrade GLPI to 11.0.6 following the official upgrade procedure.\n2. Run the database migration process.\n3. After the migration completes, GLPI reports that the database schema is not compliant.", "priority": "medium", "type": "support", "createdByEmail": "parker.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "If I may make a suggestion, you could try updating first to the latest version of version 10: 10.0.24, and then update to the latest version of 11.\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4012183552, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23398#issuecomment-4012183552", "createdAt": "2026-03-06T14:48:06Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "You need to make the corrections to your database manually, after making a backup of course. Apparently one or more updates did not fully apply.\n\nFor example:\n\nIndicates the freesize and totalsize columns of glpi_items_disks needs to be bigint type now instead of int.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4139211814, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23398#issuecomment-4139211814", "createdAt": "2026-03-27T00:31:16Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23398, "url": "https://github.com/glpi-project/glpi/issues/23398", "author": "jeremypgn", "anonymizedAuthorEmail": "parker.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-06T14:16:11Z", "updatedAt": "2026-07-05T00:53:30Z", "closedAt": "2026-03-27T00:31:33Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "missing criteria SLAs TTO and SLA TTR on service levels", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.23 and 10.0.24\n\nIssue description:\nWhen i want to add a new criterion in the escalation levels, the criteria SLAs TTO and SLAs TTR are missing.\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. Setup\n2. Service levels\n3. SLA\n4. Escalation levels\n5. Add new criterion", "priority": "low", "type": "feature", "createdByEmail": "jordan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This is not a bug but a feature request.\nThese criteria are intentionally unset.\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4075339145, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23449#issuecomment-4075339145", "createdAt": "2026-03-17T14:20:13Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "Hello,\nThank for you response. But, I would like to point out that this\nfeature already exists in previous versions up to 10.0.20(See attached\nfile)\n\nLe mar. 17 mars 2026 à 14:18, github-actions[bot]\n*@*.*> a écrit :\nClosed #23449 as completed.\n—\nReply to this email directly, view it on GitHub, or unsubscribe.\nYou are receiving this because you authored the thread.Message ID: *@*.*>\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4075491428, "author": "glpi123", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23449#issuecomment-4075491428", "createdAt": "2026-03-17T14:41:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23449, "url": "https://github.com/glpi-project/glpi/issues/23449", "author": "glpi123", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-11T15:01:16Z", "updatedAt": "2026-06-26T01:05:40Z", "closedAt": "2026-03-17T14:18:00Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Glpi 11.0.2 - Helpdesk home page custom ?", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHi\n\nIs there a way ton simply custom the Helpdesk homepage ?\n\nFor our usage, the huge blue gap with Title is too height for us.\n+ the use of 2 separate picture is a but weird and displayed.\nfor example : i put on the left a 700x400Px picture, and a 400x400px on the right.\nDisplay is broken, as the right picture go out of frame.\n\nWhat i want to do\nreduce height of this zone, and the ability to put a sigle wide image in the back.\n\nCan i do this without having to edit the php code ?\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "bailey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I think we need to add the recommended size in a tooltip, and improve our support for others sizes.\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3674515910, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21887#issuecomment-3674515910", "createdAt": "2025-12-19T10:30:00Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Fixed here\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3778789911, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21887#issuecomment-3778789911", "createdAt": "2026-01-21T15:22:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21887, "url": "https://github.com/glpi-project/glpi/issues/21887", "author": "Chico0008", "anonymizedAuthorEmail": "bailey.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-12T08:15:56Z", "updatedAt": "2026-05-02T00:52:38Z", "closedAt": "2026-01-21T15:22:50Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Type mismatch between glpi_itils_validationsteps items_id and glpi_tickets id", "detail": "Affected version:\n10.0.22 / 11.0.4\n\nIssue description:\nMigrating with a ticket id above the signed int limit leads to the errors in the log, when the mysql default is to use signed primary keys", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Adding public $allow_signed_keys = false; to config_db.php fixes this. Maybe the default can be changed ? Or a note can be added to the migration documentation\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3616410943, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22257#issuecomment-3616410943", "createdAt": "2025-12-05T11:06:46Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "If you have item IDs outside the signed integer range, you should run the unsigned keys migration first to make all ID/foreign key columns unsigned.\nRunning as the same user as your web server:\nbin/console migration:unsigned_keys\n\nManually changing properties in the config_db.php is not recommended.\n\nWas the ID column for tickets manually altered to make it unsigned or a larger integer type?\n\nOriginal response date: 2025-12-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3694843441, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22257#issuecomment-3694843441", "createdAt": "2025-12-28T15:51:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22257, "url": "https://github.com/glpi-project/glpi/issues/22257", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-05T09:45:18Z", "updatedAt": "2026-04-16T00:50:44Z", "closedAt": "2026-01-05T13:43:28Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "No impersonate", "detail": "Affected version:\n11.04\n\nIssue description:\nAfter upgrade froma 11.02 to 11.04 I see missing impersonate button on users", "priority": "medium", "type": "support", "createdByEmail": "reese.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "reese.bennett@peppermint.local", "text": "[Image omitted]\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3625385741, "author": "dcrst7575", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22279#issuecomment-3625385741", "createdAt": "2025-12-08T07:30:20Z" } }, { "userEmail": "casey.blair@peppermint.local", "text": "This is a right now\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3625408700, "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22279#issuecomment-3625408700", "createdAt": "2025-12-08T07:36:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22279, "url": "https://github.com/glpi-project/glpi/issues/22279", "author": "dcrst7575", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-08T07:07:46Z", "updatedAt": "2026-03-19T00:41:20Z", "closedAt": "2025-12-08T07:42:54Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "No agent connectivity when behind proxy", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWe're behind a proxy in our business and if I add the proxy to GLPI Settings, the agent connectivity does not work anymore. It seems like GLPI wants to send everything through the proxy in the general settings, but our endpoints are not behind the proxy. Thus, GLPI cannot talk to the agents anymore.\n\nGLPI Version: 11.0.2\nGLPI Agent Version: 1.15\n\nReproduction steps:\n1. User GLPI Agents\n2. Enter proxy information in General > System > Proxy", "priority": "low", "type": "feature", "createdByEmail": "kendall.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Seems like this is what's currently expected. Once a proxy is configured; GLPI will use it for all external calls.\n\nWhat you'd want to achieve would require a proxy setup for each external requests; that's not currently planned.\n\nOriginal response date: 2025-11-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3561657443, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22020#issuecomment-3561657443", "createdAt": "2025-11-21T06:46:34Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I just made a quick PoC #22027. Not sure yet it will be included.\n\nOriginal response date: 2025-11-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3563102417, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22020#issuecomment-3563102417", "createdAt": "2025-11-21T13:48:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22020, "url": "https://github.com/glpi-project/glpi/issues/22020", "author": "dk381", "anonymizedAuthorEmail": "kendall.adler@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-21T06:38:14Z", "updatedAt": "2026-03-02T00:38:31Z", "closedAt": "2025-11-21T06:46:51Z" } }, { "title": "GLPI 11.0.1 : Function Sysdescr not available when I want to create an custom asset", "detail": "Affected version:\n11.0.1\n\nIssue description:\nIs it possible to add the Sysdescr function? when I want to create a custom asset\nFor example, if I want to differentiate two network devices with different assets\ni dont see Sysdescr\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\n/front/asset/assetdefinition.php", "priority": "low", "type": "feature", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jesse.bennett@peppermint.local", "text": "example Printer and network\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3552627310, "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21993#issuecomment-3552627310", "createdAt": "2025-11-19T13:11:27Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nThis is not possible for the moment.\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558200627, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21993#issuecomment-3558200627", "createdAt": "2025-11-20T13:56:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21993, "url": "https://github.com/glpi-project/glpi/issues/21993", "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-19T12:55:29Z", "updatedAt": "2026-03-01T00:44:10Z", "closedAt": "2025-11-20T13:56:54Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Answers by mail, notifications for replies and settings (followups for anonymous)", "detail": "Issue description:\nPlease create a feature that will allow limiting follow-ups from users to other users.\n\nWhat I mean is that we need a mechanism similar to the function in the general settings Setup -> General -> Notifications for my changes, which, incidentally, does not always work.\nSpecifically, when correspondence is conducted by email, other participants who are copied on the email but are not direct observers in the system should not receive notifications from the GLPI system about new replies from other users.\nThis is because they can already see these replies in the correspondence.\nHowever, they should be able to receive replies from the system (when a technical engineer responds within the request)\n\nI am interested in responses (Followup) so that the system accepts responses from users, but does not send them notifications with their own response or from other users who are in this correspondence. But it could send a follow-up in case of a response from a technician in the system itself.\nIdeally, this would be for users who are not registered in the system or simply do not have an account, but it could also be for users who are in the system but have never logged in, and correspond and create requests via email.\n\nPerhaps there are already some ready-made solutions for this, such as plugins or settings in the system itself?\n\nThank you in advance!", "priority": "low", "type": "feature", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.bennett@peppermint.local", "text": "It's bug!\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501366947, "author": "Code-Near", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21843#issuecomment-3501366947", "createdAt": "2025-11-07T08:56:49Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "\"Please create a feature\" does not sounds like a bug.\n\nIf it's a bug, please use bug report template and provide all requested information.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501411124, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21843#issuecomment-3501411124", "createdAt": "2025-11-07T09:10:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21843, "url": "https://github.com/glpi-project/glpi/issues/21843", "author": "Code-Near", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-06T18:34:47Z", "updatedAt": "2026-02-16T00:40:09Z", "closedAt": "2025-11-07T06:40:24Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Business rules with “Validation” criteria still not working when combined with other criteria", "detail": "Affected version:\n10.0.19\n\nIssue description:\nHello,\n\nI’ve noticed that the issue with business rules not executing actions when the “Validation” criterion is combined with other criteria is still present in version 10.0.19.\n\nWhen I create a business rule with only the “Validation” criterion, the configured action works correctly.\nHowever, if I add one or more additional criteria (e.g., Category), the rule no longer executes any action.\n\nFor example: the criteria is Validation and Category\n\n[Image omitted]\n\nAction: Change ticket status\nResult: No action is performed when both criteria are used. The action only works when the “Validation” criterion is used alone.\n\nThis issue is very similar to previously reported issues: #17795, #15773 and #20155.\n\nReproduction steps:\n1. Create a business rule for tickets\n- Use rule for: Add/Update\n- Logical operator: AND\n2. Add criteria:\n- Validation is “Refused” (or similar)\n- Category is [some category]\n3. Add an action (e.g., change status to Pending).\n4. Trigger the rule by creating or updating a ticket.\n5. Observe that no action is executed.\n\nExpected behavior:\nThe action should be executed when all criteria (including Validation) are met.\n\nActual behavior:\nThe action is only executed if “Validation” is the single criterion.", "priority": "medium", "type": "support", "createdByEmail": "elliot.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Not a bug. This isn't how the rules system works. Generally, rules only work on the fields that are sent as part of the update. There are some things that are forced to be included, but they are only a few exceptions. Global validations are supposed to always be included, but category is not. If the update includes the category, then both criteria should be available.\n\nOriginal response date: 2025-10-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3416917729, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21538#issuecomment-3416917729", "createdAt": "2025-10-17T19:58:59Z" } }, { "userEmail": "elliot.blair@peppermint.local", "text": "Thanks for the explanation, Taylor Adler.\n\nBut, I didn’t fully understand how this works. Could you give a simple, practical example of how rules behave in this case and what the exact limitations are?\n\nFor example, if I change only the validation status and have a category criterion in the rule, why exactly is it ignored?\n\nAlso, another issue was created recently about this: #21531 it seems very similar, but is about the status.\n\nOriginal response date: 2025-10-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3416991877, "author": "Berlinst", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21538#issuecomment-3416991877", "createdAt": "2025-10-17T20:23:56Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21538, "url": "https://github.com/glpi-project/glpi/issues/21538", "author": "Berlinst", "anonymizedAuthorEmail": "elliot.blair@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-17T18:25:30Z", "updatedAt": "2026-01-30T00:37:55Z", "closedAt": "2025-10-21T06:00:45Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "PHP error in install.php on Windows 11/10 with Xampp", "detail": "Affected version:\n11.0.1\n\nIssue description:\nThis error occurs when I go to the install.php file\n\nAffected page:\n\nReproduction steps:\n1. Go to /install/install.php", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "devon.bennett@peppermint.local", "text": "My PHP version is 8.2\n\nPHP 8.2.12 (cli) (built: Oct 24 2023 21:15:15) (ZTS Visual C++ 2019 x64)\nCopyright (c) The PHP Group\nZend Engine v4.2.12, Copyright (c) Zend Technologies\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3386152755, "author": "OxydeBots", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21391#issuecomment-3386152755", "createdAt": "2025-10-09T14:29:13Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nThis is due to a misconfiguration of your webserver. You can find some configuration examples on this page:\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396359955, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21391#issuecomment-3396359955", "createdAt": "2025-10-13T08:15:39Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21391, "url": "https://github.com/glpi-project/glpi/issues/21391", "author": "OxydeBots", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-09T14:21:00Z", "updatedAt": "2026-01-22T00:34:50Z", "closedAt": "2025-10-13T08:31:29Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Components list: \"Child entities\" not available in dialog \"Select default items to show\"", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAll components (at least in my setup) are anchored in an entity and allow to be set visible in child entities.\nBut in contrast to other items, the components list view doesn't allow the column \"Child entities\" to be added to the displayed columns via the \"Select default items to show\" dialog.\nAdditionally, this field is missing from the Actions->Update dialog too, so it's impossible to change the value of this field in a single operation for multiple selected items. This makes it quite tedious to find or change this setting for wrongly configured items.\n\nI could get both things to work by adding\n\nto rawSearchOptions() of src/CommonDevice.php with a temporary quick&dirty patch.\nIt would be great if this feature could be officially supported, whether it really is a bug or not.\n\nReproduction steps:\n1. Go to Setup -> Components\n2. select an item class with \"Entity management\"\n3. open the dialog \"Select default items to show\" (top right) to configure the visible columns\n4. (the field \"Child entities\" is not available for selection and cannot be added)", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "to rawSearchOptions() of src/CommonDevice.php with a temporary quick&dirty patch.\n\nAs far as I know just from quickly looking at it, this seems like the correct fix. It is present on some itemtypes but not others. For consistency, I guess it should be present for all itemtypes that have the is_recursive column in the database.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3992123977, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23336#issuecomment-3992123977", "createdAt": "2026-03-03T16:20:26Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Fixed by #23632 for GLPI 12.\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4210909615, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23336#issuecomment-4210909615", "createdAt": "2026-04-09T01:51:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23336, "url": "https://github.com/glpi-project/glpi/issues/23336", "author": "sl077", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-03T16:12:19Z", "updatedAt": "2026-07-19T00:44:46Z", "closedAt": "2026-04-09T01:51:31Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "File ajax/ldap.php apparently missing from the repository", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAfter installing GLPI 11 in a test environment (pre-upgrade validation), testing an LDAP replica fails due to a call to a non-existent endpoint.\nWith debug enabled, I observed that the application attempts to send a POST request to the following endpoint:\n\n/ajax/ldap.php\n\nHowever, this file does not exist in the current installation. I also verified the official repository and could not find this file there either.\n\nThis suggests one of the following:\n\nan incorrect or outdated endpoint is being called, or\nthe corresponding file has been removed without updating the related logic.\n\nAffected page:\n/front/authldap.form.php?id=1\n\nReproduction steps:\nInstall GLPI 11\nGo to Setup > Authentication > LDAP directories\nConfigure a new LDAP directory\nNavigate to the Replicates tab\nAdd a new replica\nClick Test on the newly added replica (debug enabled will give you the missing endpoint information)", "priority": "medium", "type": "bug", "createdByEmail": "emerson.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Emerson Blair Could you test the changes in #23749?\n\nOriginal response date: 2026-04-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4176692398, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23734#issuecomment-4176692398", "createdAt": "2026-04-02T11:17:37Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "It works now, with the suggested changes applied.\n\nThank you!\n\nOriginal response date: 2026-04-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4196983755, "author": "valentindragan", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23734#issuecomment-4196983755", "createdAt": "2026-04-07T06:28:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23734, "url": "https://github.com/glpi-project/glpi/issues/23734", "author": "valentindragan", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-01T11:14:43Z", "updatedAt": "2026-07-19T00:44:43Z", "closedAt": "2026-04-07T06:28:36Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Error when accessing Forms → Created tickets → Show all", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen accessing the page:\n\nForms > Created tickets > Show all\n\nthe page fails to load and shows a SQL error.\n\nEnvironment details:\n1 Administration > Forms > Any form > Created tickets > Show all\n\nThe error is displayed", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirmed the issue.\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967344156, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23259#issuecomment-3967344156", "createdAt": "2026-02-26T15:26:49Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Drew Bennett,\n\nThis should fix your issue: #23580.\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4111632145, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23259#issuecomment-4111632145", "createdAt": "2026-03-23T15:45:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23259, "url": "https://github.com/glpi-project/glpi/issues/23259", "author": "pedroalves5770", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-26T15:22:42Z", "updatedAt": "2026-07-09T00:48:35Z", "closedAt": "2026-03-30T09:02:15Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Regression: Knowledgebase comparison overflows", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nThe bug fixed in #17773 is back. Exact same symptoms.\n\nReproduction steps:\n- Create a long KB entry\n- change something\n- compare revisions", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Long lines seemed to wrap properly. The only thing I noticed was the modal was very small for the kind of content being displayed.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3897577183, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23104#issuecomment-3897577183", "createdAt": "2026-02-13T14:39:56Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Hmm just to make sure we looking at identical things I will write a more detailed guide to reproduce:\n\ncreate a new kb article with the html content\n\nsave and change to\n\ncompare both revisions\n\n[Image omitted]\n\nit also makes sense logically. The table generated by Knowbase.js is missing the class='text-wrap text-break' from the referenced issue.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3898802280, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23104#issuecomment-3898802280", "createdAt": "2026-02-13T18:50:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23104, "url": "https://github.com/glpi-project/glpi/issues/23104", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-13T07:05:08Z", "updatedAt": "2026-07-09T00:48:26Z", "closedAt": "2026-03-30T12:35:56Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Clone ITIL objects but changes creation date, requester and object status", "detail": "Contribution description:\nHello,\nwhen cloning tickets, changes and other objects, the creation date and other attributes of the object remain the sames.\n\nWhen users clone their own objects created recently it isn't an issue because the stats remains the same. But when an user 'A' clone a ticket from one year ago from an user 'B', the ticket will keep the old creation date. So when taking a look at the statistics of our GLPI, it seems like the cloned ticket was opened a year ago by user 'B' while it's not the case at all.\n\nIn my opinion, it would be interesting to change this behavior so that cloning an object change at least the creation date, for other attributes that can be changed manually it may not be interesting.\n\nBest regards, Nathanaël.", "priority": "medium", "type": "support", "createdByEmail": "bailey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "We may need to know what the need to clone a year old ticket was to make any change here without breaking expected behavior for other cases where someone wants to clone a ticket.\n\nIs this something that could have been done with ticket templates?\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3961286910, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23244#issuecomment-3961286910", "createdAt": "2026-02-25T18:48:20Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No feedback, closing\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4140791677, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23244#issuecomment-4140791677", "createdAt": "2026-03-27T07:46:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23244, "url": "https://github.com/glpi-project/glpi/issues/23244", "author": "0xNath", "anonymizedAuthorEmail": "bailey.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-25T14:30:19Z", "updatedAt": "2026-07-06T00:53:31Z", "closedAt": "2026-03-27T07:46:23Z" } }, { "title": "Broken form field RegEx validation", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.4\n\nIssue description:\nI have a form with a text field. I'm using RegEx to check that the string entered is a valid swedish PID.\n\nThe RegEx is: ^(?:\\d{2})?\\d{6}[-+]?(\\d{4})$\n\n[Image omitted]\n\nBut, when the form validates it determines the field value 19121212-1212 to be invalid. The RegEx as well as the submitted PID are both indeed correct, so it must be the validation feature that is broken.\n\n[Image omitted]\n\nAffected page:\n/Form/Render/21\n\nReproduction steps:\n1. In a form, add a text field (Short answer - Text).\n2. Configure validation as \"Valid if\" and configure a criteria \"Match regular expression\" with a value of ^(?:\\d{2})?\\d{6}[-+]?(\\d{4})$\n3. Preview the form and enter the PID 19121212-1212", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "I found the issue. It's the same as in #20611. Maybe you could make it clearer in the validation configuration dialog, like in #20647?\n\nOriginal response date: 2026-02-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3972121573, "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23267#issuecomment-3972121573", "createdAt": "2026-02-27T10:37:07Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "A small hint was added in #23655.\n\nI'll probably try to go a bit further in the future and report invalid regex to the users, this should help them find potential issues quicker.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4141669632, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23267#issuecomment-4141669632", "createdAt": "2026-03-27T10:33:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23267, "url": "https://github.com/glpi-project/glpi/issues/23267", "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "forms", "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-27T10:23:06Z", "updatedAt": "2026-07-06T00:53:28Z", "closedAt": "2026-03-27T10:33:34Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Display issue with monitors and peripherals in a computer’s connections tab", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello\nI’m not sure whether I should report this issue here or on the GitHub of the GLPI Inventory plugin, but since we upgraded to GLPI v11.0.6 + GLPI Inventory v1.6.7, when we check the monitors or peripherals connected to a computer, GLPI displays all the monitors and peripherals from my entire database.\nHowever, when I open a specific monitor or peripheral, it correctly shows only a single associated computer.\n\nYet the number shown next to ‘Connections’ is correct; it displays the proper number of monitors/peripherals associated with the computer.\n(See attached image)\n\nIs this a known bug in GLPI v11.0.6?\n\nI didnt have that bug in precious versions\n\nThanks for your reply\n\nAffected page:\n/front/computer\n\nReproduction steps:\n1. Go to Assets / Computers\n2. Select a computer that has connections with a monitor/peripherals\n3. Go to the Connections tab\n4. All monitors/peripherals are displayed\n\nAdditional context:\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "As far as I remember; this issue already has been reported and is fixed for next release. You can try a nightly build.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4142794890, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23661#issuecomment-4142794890", "createdAt": "2026-03-27T13:55:49Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Thanks a lot !\nHave a great day\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4142822688, "author": "ReskPP", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23661#issuecomment-4142822688", "createdAt": "2026-03-27T13:59:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23661, "url": "https://github.com/glpi-project/glpi/issues/23661", "author": "ReskPP", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-03-27T13:51:54Z", "updatedAt": "2026-07-06T00:53:23Z", "closedAt": "2026-03-27T13:55:49Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "External Event Templates do not pre-fill Title and Category in Planning Calendar", "detail": "Affected version:\n11.0.4\n\nIssue description:\nBug description\nWhen creating a new \"External Event\" directly from the Planning Calendar, selecting an External Event Template (Externe Ereignis-Vorlage) does not pre-fill the Title and Category fields, even if they are defined in the template.\n\nIn GLPI 10, the \"Name\" of the template was automatically used as the \"Title\" of the event. In GLPI 11, the fields remain empty after selecting the template, requiring manual input for every event.\n\nSteps to reproduce\nGo to Setup > Dropdowns > External Event Templates.\n\nCreate a template (e.g., \"Annual Leave\") and assign a category (e.g., \"Vacation\").\n\nGo to Helpdesk > Planning.\n\nClick on a time slot to add a new event.\n\nIn the \"New Element - External Event\" modal, select the previously created template.\n\nObservation: The \"Title\" and \"Category\" fields remain empty or at default values.\n\nExpected behavior\nSelecting a template should automatically:\n\nFill the Title field with the Template's Name (or a predefined string).\n\nSet the Category dropdown to the value defined in the template.\n\nActual behavior\nThe modal does not react to the template selection for these specific fields.", "priority": "medium", "type": "support", "createdByEmail": "casey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I'm not able to recreate the issue on the latest GLPI 11, but I also didn't find a specific PR that addressed the issue. Would you be able to confirm if the issue remains on 11.0.6 for you?\n\nOriginal response date: 2026-03-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4062868198, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22590#issuecomment-4062868198", "createdAt": "2026-03-15T12:10:27Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "No feedback for a while. Closing this but feel free to re-open if you can recreate the issue on the latest GLPI 11.\n\nOriginal response date: 2026-03-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4138676703, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22590#issuecomment-4138676703", "createdAt": "2026-03-26T22:14:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22590, "url": "https://github.com/glpi-project/glpi/issues/22590", "author": "GerryCrooked", "anonymizedAuthorEmail": "casey.adler@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-08T08:11:04Z", "updatedAt": "2026-07-05T00:53:33Z", "closedAt": "2026-03-26T22:14:57Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "strings not translated data view dashboards", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nTe string in close button is not translated.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I don't know where this data view dashboard widget comes from. Do you have plugins installed?\n\nPlease provide the GLPI Setup information that was requested in the bug report template.\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4113235027, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23569#issuecomment-4113235027", "createdAt": "2026-03-23T19:40:32Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "it comes from the native dashboard and witgets, option \"View Data\"\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4114736915, "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23569#issuecomment-4114736915", "createdAt": "2026-03-24T01:15:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23569, "url": "https://github.com/glpi-project/glpi/issues/23569", "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-21T17:35:43Z", "updatedAt": "2026-07-04T00:48:41Z", "closedAt": "2026-03-25T13:15:18Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Custom dropdown add button missing", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen creating a new item of a custom dropdown, the + icon is missing on front/dropdown/dropdown.php?class=nameofclass\n\n[Image omitted]\n\nIf I change the URL to front/dropdown/dropdown.form.php?class=nameofclass I can add the dropdowns.\n\nSimilar to #19939\n\nAffected page:\n\nReproduction steps:\n1. Create a custom dropdown\n2. Try to create a new item for this new dropdown", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Did you try logging out and back in to force the menu data to be regenerated?\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4113180929, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23581#issuecomment-4113180929", "createdAt": "2026-03-23T19:31:04Z" } }, { "userEmail": "robin.bennett@peppermint.local", "text": "I have tried it, and the result was the same.\nAfter reading your message, I also made sure to clear the cache using console, and it worked well. Thanks\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4119089332, "author": "arthurrschaefer", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23581#issuecomment-4119089332", "createdAt": "2026-03-24T15:13:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23581, "url": "https://github.com/glpi-project/glpi/issues/23581", "author": "arthurrschaefer", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-23T19:25:54Z", "updatedAt": "2026-07-03T00:49:54Z", "closedAt": "2026-03-24T15:13:43Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "API wrong SQL", "detail": "Issue description:\nLooks like those assertions are incorrect. Should not that be AND (_.name IS NOT NULL)))\"?", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Probably. I think it was a mistake since there is no \"IS NOT\" operator supported by DBmysqlIterator and I was avoiding nesting conditions in \"NOT\" arrays.\n\nOriginal response date: 2026-03-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4089136139, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23538#issuecomment-4089136139", "createdAt": "2026-03-19T10:25:13Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Tested on my mariadb instance, <> NULL just does not work\n\nOriginal response date: 2026-03-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4089145216, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23538#issuecomment-4089145216", "createdAt": "2026-03-19T10:27:00Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23538, "url": "https://github.com/glpi-project/glpi/issues/23538", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-19T10:15:32Z", "updatedAt": "2026-06-28T01:06:08Z", "closedAt": "2026-03-19T12:26:50Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "GLPI 11: “Select” questions do not wrap to the next line with longer text lists", "detail": "Contribution description:\nGuys, I came across an issue here in the GLPI 11 forms that I’m not sure is a bug or just a feature that, unlike in GLPI 10, didn’t make it into the GLPI 11 forms version. Here’s what it is:\n\nVersion 10: When creating a dropdown question, if I have a vertical list of items, pasting them automatically places them one below the other in the “values” field:\n\n[Image omitted]\n\n[Image omitted]\n\nVersion 11: In version 11, the same field—which in this case was named “drop-down list”—does not allow you to enter the same text; instead, it places all items in the list under item 1 rather than wrapping to the next line:\n\n[Image omitted]\n\nP.S.: The same applies to multiple-select questions: in GLPI 10, you can enter the entire text in the “values” field, with each entry on a separate line, but in GLPI 11, it pastes everything into the first field instead of wrapping to the next line.\n\nPotential issue: Users who work with this type of question involving large lists will have difficulty creating long lists or even maintaining them, since in GLPI 10 it’s easy to copy the current content, make changes, and then simply paste it.\n\nIt would be good if GLPI 11 behaved the same way as GLPI 10.\n\nVersion: GLPI 11.0.6", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Is this what you are looking for?\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4076208576, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23515#issuecomment-4076208576", "createdAt": "2026-03-17T16:15:37Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Great, I didn't know there was already a PR for that. In that case, I'll close this issue for now. Thanks.\n\nOriginal response date: 2026-03-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4076314907, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23515#issuecomment-4076314907", "createdAt": "2026-03-17T16:31:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23515, "url": "https://github.com/glpi-project/glpi/issues/23515", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-17T15:39:44Z", "updatedAt": "2026-06-26T01:05:37Z", "closedAt": "2026-03-17T16:31:04Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Issue with pasted images in GLPI 11.0.6 causing Twig RuntimeError", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen creating a ticket in GLPI 11.0.6, the application throws a filesize(): stat failed warning followed by a critical Twig\\Error\\RuntimeError during template rendering.\nThe issue occurs specifically when GLPI attempts to process pasted images (files named image_pasteXXXX.png) in the ticket timeline editor.\n\nAll system permissions and PHP/NGINX upload settings have been verified as correct. The problem appears to be linked to GLPI’s internal handling of temporary pasted images in /var/lib/glpi/_tmp, suggesting a GLPI-side bug in version 11.0.6.\n\nGLPI 11.0.6 encounters a fatal error when rendering the ticket timeline (simple_form.html.twig). The error is triggered when GLPI tries to load a temporary image file generated by the \"paste image\" feature in the rich‑text editor.\n\nThe application attempts to run filesize() on a file named image_pasteXXXXX.png inside /var/lib/glpi/_tmp/, but the file does not exist anymore, resulting in:\nfilesize(): stat failed for /var/lib/glpi/_tmp/xxxximage_pastexxxx.png\n\nThis warning escalates into a critical exception:\nTwig\\Error\\RuntimeError: An exception has been thrown during the rendering of a template\n(“An error occurred”) in simple_form.html.twig at line 83.\n\nAffected page:\n\nReproduction steps:\n1. In Outlook, open any email that contains multiple inline images (minimum 2–4 images).\n2. Copy the entire email content (CTRL+C).\n3. In GLPI, create a new ticket as a technician and not as a user, via :\n4. Paste the email content into the Description field (CTRL+V).\n GLPI automatically converts pasted inline images into temporary files named image_pasteXXXX.png in /var/lib/glpi/_tmp.\n5. Change any field in the ticket (for example, change Type from Incident to Request).\n6. The ticket form fails to render and GLPI generates a warning followed by a fatal Twig error.\n\nEnvironment details:\nGLPI version: 11.0.6\nWeb server: NGINX\nPHP: 8.4\nPermissions:\n /var/www/glpi: root:root (644/755)\n /var/lib/glpi, /etc/glpi, /var/log/glpi, marketplace: www-data:www-data\n\nUpload size settings:\n upload_max_filesize: OK\n post_max_size: OK\n NGINX client_max_body_size: OK", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "filesize(): stat failed warning is certainly due to an issue with filesystems rights. It should be fixed with the correct chmod/chown commands.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4038210199, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23446#issuecomment-4038210199", "createdAt": "2026-03-11T10:35:01Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "Hi,\n\nMy /etc/glpi/local_define.php file is configured as indicated in the documentation :\n\n/var/www/glpi/inc/downstream.php\n\nAnd for chmod/chown, I use this after all updates :\n\nSo I don't think it's a rights issue, because otherwise the images work fine. It only happens when they come from the clipboard (from Outlook in my case). Have you tried to reproduce the problem as described in my description?\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4038283089, "author": "OteJlo", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23446#issuecomment-4038283089", "createdAt": "2026-03-11T10:46:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23446, "url": "https://github.com/glpi-project/glpi/issues/23446", "author": "OteJlo", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-11T10:19:33Z", "updatedAt": "2026-06-25T01:02:32Z", "closedAt": "2026-03-16T13:19:29Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Display all items on Change throws NotFoundHttpException", "detail": "Issue description:\nWhen opening a Change and clicking \"Display all items\" GLPI throws:\n\nSteps to reproduce:\n- Create a Change\n- Link multiple assets (minimum 6 items because \"Display all items\" button displayed only on 6 and more items)\n- Click save\n- Click Display all items", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide all requested information - there is a template to fill.\n You did not ever mention which GLPI version you use...\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3870080494, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23023#issuecomment-3870080494", "createdAt": "2026-02-09T08:26:57Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Sorry for that.\nBug description\n\nWhen opening a Change and clicking \"Display all items\" GLPI throws NotFoundHttpException.\n\nRelevant log output\n\nPage URL\n\nSteps To reproduce\n\n1. Create a Change\n2. Link multiple assets (minimum 6 items because \"Display all items\" button displayed only on 6 and more items)\n3. Click save\n4. Click Display all items\n\nYour GLPI setup information\nGLPI: 11.0.4 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: 2 files changed\n A: inc/downstream.php\n D: install/install.php\nPHP: 8.2.29 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, redis, shmop, SimpleXML, soap, sockets,\nsysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"60\" max_input_vars=\"5000\" memory_limit=\"256M\" post_max_size=\"20M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"20M\"\n\nWeb server: Apache/2.4.66 (Debian) (Apache/2.4.66 (Debian) Server at glpi_url Port 443)\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36\nEdg/144.0.0.0\n\nDatabase:\n\nServer Software: Debian 12\n\nServer Version: 10.11.14-MariaDB-0+deb12u2\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@localhost/glpi\n\nHost info: Localhost via UNIX socket\n\nRequirements:\nPHP version (8.2.29) is supported.\nOS and PHP are relying on 64 bits integers.\nSessions configuration is OK.\nAllocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installed\ncurl extension is installed\ngd extension is installed\nintl extension is installed\nmbstring extension is installed\nzlib extension is installed\nbcmath extension is installed\nThe constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installed\nDatabase engine version (10.11.14) is\nsu\n\n[Content truncated.]\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3870691065, "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23023#issuecomment-3870691065", "createdAt": "2026-02-09T10:01:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23023, "url": "https://github.com/glpi-project/glpi/issues/23023", "author": "vi-lgtm", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-05T06:44:03Z", "updatedAt": "2026-06-21T01:13:26Z", "closedAt": "2026-03-12T08:09:19Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Html::DateField broken layout and translate GLPI 11.0.4", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHtml::showDateField breaks layout and ignores translation, while Html::showDateTimeField works correctly\n\nWhen using Html::showDateTimeField, the field is rendered correctly, with proper layout and translations applied as expected.\n[Image omitted]\n\nHowever, when switching to Html::showDateField, the layout becomes broken and the translation is not applied.\n\n[Image omitted]\n\nExpected behavior\n\nHtml::showDateField should follow the same layout structure as Html::showDateTimeField\n\nTranslations (locale/date format) should be applied consistently\n\nActual behavior\n\nBroken/misaligned layout\n\nMissing or incorrect translation\n\nThis suggests an inconsistency between showDateField and showDateTimeField in terms of rendering or localization handling.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This issue isn't reproducible on Project > Costs ( which also uses Html::showDateField. It seems something is wrong in the plugin you're using (if any). Please provide the native GLPI URL page that triggers the issue. If it's a plugin page, I'd recommend contacting the plugin author for support. The only relevant difference is that the input field of Html::showDateTimeField has a \"value\" attribute while Html::showDateField does not, but I do not believe it's related to the issue you're facing here.\nGLPI is a bit tricky about translations; it could also be related to the translation cache (you can clean it in Setup > General > Performance page with Debug mode enabled). Some plugins, like GLPI Inventory, reproduce similar behavior with translations. There are similar issues regarding translation problems, but the GLPI team always recommends contacting the plugin author instead. However, I do believe the translation issue is a GLPI core issue, maybe related to the translation cache or Twig engine. Some plugins use the language selected during installation (GLPI Inventory) and translation does not work well for other languages. If you're using GLPI on Docker or other third-party providers, I'd also recommend you set up GLPI selecting your native language, as some UI elements use the default GLPI language selected during installation (e.g. Self-Service panels).\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3756938623, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22695#issuecomment-3756938623", "createdAt": "2026-01-15T21:25:05Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Este problema não é reproduzível em Projeto > Custos (\n\nglpi/src/ProjectCost.php\n\nLinha 266 em 19f08e3\n\nHtml:: showDateField ( \" begin_date \" , [ ' value ' => $ this -> fields [ ' begin_date ' ]]);\n), que também usa Html::showDateField. Parece que há algo errado com o plugin que você está usando (se houver). Por favor, forneça a URL nativa da página do GLPI que desencadeia o problema. Se for uma página de plugin, recomendo entrar em contato com o autor do plugin para obter suporte. A única diferença relevante é que o inputcampo de Html::showDateTimeFieldpossui um atributo \"value\", enquanto Html::showDateFieldnão possui, mas não acredito que esteja relacionado ao problema que você está enfrentando.\nO GLPI é um pouco complicado com traduções; também pode estar relacionado ao cache de traduções (você pode limpá-lo em Configuração > Geral > Desempenho com o modo de depuração ativado). Alguns plugins, como o GLPI Inventory, reproduzem comportamento semelhante com traduções. Existem problemas semelhantes relacionados a traduções, mas a equipe do GLPI sempre recomenda entrar em contato com o autor do plugin. No entanto, acredito que o problema de tradução seja um problema do núcleo do GLPI, talvez relacionado ao cache de traduções ou ao mecanismo Twig. Alguns plugins usam o idioma selecionado durante a instalação (GLPI Inventory) e a tradução não funciona bem para outros idiomas. Se você estiver usando o GLPI no Docker ou em outros provedores de terceiros, também recomendo que configure o GLPI selecionando seu idioma nativo, pois alguns elementos da interface do usuário usam o idioma padrão do GLPI selecionado durante a instalação (por exemplo, painéis de autoatendimento).\n\nIn Plugin More Reports has this issues too, layout and translate\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3813733483, "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22695#issuecomment-3813733483", "createdAt": "2026-01-28T20:19:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22695, "url": "https://github.com/glpi-project/glpi/issues/22695", "author": "jobercavalcante", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-15T18:25:11Z", "updatedAt": "2026-06-20T01:05:33Z", "closedAt": "2026-03-11T16:41:06Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "The \"Insert/Edit link\" modal window opened multiple times.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nI can see this bug at the \"Notes\" tab in my task page.\n\nEvery time I click on any point of my page, a strange \"Insert/Edit link\" modal opens multiple times.\n\nAffected page:\nfront/projecttask.form.php?id=N\n\nReproduction steps:\n1. Add a note with a link; this can be an image with a link or text with a link, and then click \"Add.\"\n\n[Image omitted]\n\n[Image omitted]\n\n2. After, try to click in any point in GLPI UI, and the \"Insert/Edit link\" modal will open, forcing you to click in \"Cancel\" multiple times to use the GLPI again, or refreshing the page.\n\nIn this example, I click in my profile pic in user header menu, and the modal are opened.\n\n[Image omitted]\n\n[Image omitted]\n\nThat's the same UI, to prove this I will put the screen shot of the last modal after click multiple times in \"Cancel\"\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jamie.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the bug, although I don't know how it is possible. I am also not sure yet if it is a TinyMCE bug or something in GLPI.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024215075, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23417#issuecomment-4024215075", "createdAt": "2026-03-09T14:32:23Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I tried on firefox on linux and no issue.\n\nIndeed using chrome if I go the project then Notes tab then (click anywhere) instantly the modal is open\n\nChrome on the left, firefox on the right. Modal looks like a modal from TinyMCE\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024378822, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23417#issuecomment-4024378822", "createdAt": "2026-03-09T14:57:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23417, "url": "https://github.com/glpi-project/glpi/issues/23417", "author": "GSGustavo", "anonymizedAuthorEmail": "jamie.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-09T14:17:02Z", "updatedAt": "2026-06-19T01:16:18Z", "closedAt": "2026-03-10T08:15:16Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GET /Rule/Collection/ImportEntity/Rule/{id}/Action returns an error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello, today while working with the API and trying to automate rule creation, I encountered the following issue.\n\nGET /Rule/Collection/ImportEntity/Rule returns the created rules.\n\nAs we can see, there are two \"actions\" present there.\nNext, we can access each rule individually:\nGET /Rule/Collection/ImportEntity/Rule/{rule_id}/Action/{id}\n\nAs we can see, the values are returned correctly. (Yep, one wrong action ID for test)\nHowever, the problem occurs when I try to retrieve all \"actions\" at once using:\nGET /Rule/Collection/ImportEntity/Rule/{id}/Action\n_400. Error: Bad Request_\nI receive an error.\n\nMoreover, this happens both in my Docker test environment and on the test server — both return the same error.\n\nAffected page:\n[GET] /Rule/Collection/ImportEntity/Rule/{id}/Action\n\nReproduction steps:\n1. Create rule in Administration -> Rules -> Rules for assigning an item to an entity\n2. Create Action in this rule\n3. Try to get \"actions\" by api link /Rule/Collection/ImportEntity/Rule/{id}/Action", "priority": "medium", "type": "support", "createdByEmail": "devon.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the bug. There is a mismatch between the endpoint attribute and the value it tries using for the implicit filtering.\nEndpoint: '/Collection/{collection}/Rule/{id}/Action'\nFilter being built:\n\nOriginal response date: 2026-02-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3947305966, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23215#issuecomment-3947305966", "createdAt": "2026-02-23T20:59:37Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "(writing missing regression tests)\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4024067398, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23215#issuecomment-4024067398", "createdAt": "2026-03-09T14:10:36Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23215, "url": "https://github.com/glpi-project/glpi/issues/23215", "author": "Kentrier", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "api", "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-23T20:54:54Z", "updatedAt": "2026-06-19T01:16:12Z", "closedAt": "2026-03-10T08:24:12Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Token not valid/expired", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen a new user created and \"Send an email to the user to set their own new password.\" is enabled the get the mail but when they click on the link the system said the token is not valid or expired.\n\nToken lifetime is 1 day but i tried it with 7 days as well. Server time is ok. And it works with 11.0.2.\nThanks for the help\n\nReproduction steps:\nCreate a user\nEnable \"Send an email to the user to set their own new password.\"\nOpen the link that you got\n\nEnvironment details:\nGLPI: 11.0.4 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: OK\n\nPHP: 8.3.25 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem,\nsysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"1000\" max_input_vars=\"1000\" memory_limit=\"512M\" post_max_size=\"512M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"512M\"\n\nWeb server: Apache/2.4.56 (Debian) (Apache/2.4.56 (Debian) Server at *)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 11.2.3-MariaDB-1:11.2.3+maria~ubu2204\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@glpi-mariadb/glpidb\n\nHost info: glpi-mariadb via TCP/IP\n\nRequirements:\nPHP version (8.3.25) is supported.\nOS and PHP are relying on 64 bits integers.\nSessions configuration is OK.\nAllocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installed\ncurl extension is installed\ngd extension is installed\nintl extension is installed\nmbstring extension is installed\nzlib extension is installed\nbcmath extension is installed\nThe constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installed\nDatabase engine version (11.2.3) is supported.\nThe log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.\nexif extension is installed\nldap extension is installed\nFollowing extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installed\nFollowing extensions are installed:\nctype, iconv, sodium.\nWrite access to\n/var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "reese.blair@peppermint.local", "text": "When a new user is created via mail collector, GLPI sends a password initialization email containing a ##user.passwordiniturl## link. Clicking the link results in the following error:\n\"Your password reset request has expired or is invalid. Please renew it.\"\nRoot Cause:\nIn src/NotificationTargetUser.php, the passwordinit case builds the URL using the encrypted token stored in the database:\n\ncase 'passwordinit':\n $this->data['##user.token##'] = $this->obj->getField(\"password_forget_token\");\n $this->data['##user.passwordiniturl##'] = urldecode($CFG_GLPI[\"url_base\"]\n . \"/front/initpassword.php?password_forget_token=\"\n . $this->obj->getField(\"password_forget_token\"));\n break;\n\nHowever, getUserByForgottenPasswordToken() in src/User.php compares the incoming token against the decrypted value:\nif ($token === $glpi_key->decrypt($user_data['password_forget_token'])) {\n\nThis means the tokens will never match, causing the validation to always fail.\nAdditionally, urldecode() is used instead of urlencode(), which corrupts special characters like + in the token (converted to spaces %20).\nSteps to reproduce:\n\nConfigure a mail collector\nSend an email from an unknown address to create a new user\nReceive the password initialization email\nClick the link → error appears\n\nExpected behavior:\nPassword initialization page loads successfully and allows the user to set their password.\n\nProposed fix:\nphp\n\ncase 'passwordinit':\n $glpi_key = new GLPIKey();\n $decrypted_token = $glpi_key->decrypt($this->obj->getField(\"password_forget_token\"));\n $this->data['##user.token##'] = $decrypted_token;\n $this->data['##user.passwordiniturl##'] = $CFG_GLPI[\"url_base\"]\n . \"/front/initpassword.php?password_forget_token=\"\n . urlencode($decrypted_token);\n break;\n\nTried this solution and it worked for me .\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4029544921, "author": "boraergul", "anonymizedAuthorEmail": "reese.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22554#issuecomment-4029544921", "createdAt": "2026-03-10T08:22:56Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "This was fixed in 11.0.5 by #22811.\n\nPlease try to test issues on the latest bugfix releases to ensure the issues haven't already been fixed before opening a bug report.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4030147001, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22554#issuecomment-4030147001", "createdAt": "2026-03-10T10:01:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22554, "url": "https://github.com/glpi-project/glpi/issues/22554", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-05T07:06:47Z", "updatedAt": "2026-06-19T01:16:09Z", "closedAt": "2026-03-10T10:01:04Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Missing “Approve / Refuse solution” option on tickets in GLPI 11.0.5 (regression vs previous version)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.5\n\nIssue description:\nIn GLPI 11.0.5, the ticket interface no longer shows the option to approve or refuse a ticket solution (“Approve solution / Refuse solution”), which traditionally appeared when a technician added a solution and the requester needed to validate it.\n\nThis worked correctly in the previous version, but after upgrading to 11.0.5 the approval/refusal action is not displayed, so the requester cannot validate the solution from the ticket.\n\nSteps to reproduce\n\nUpgrade an instance from a previous GLPI version (where solution approval worked) to GLPI 11.0.5.\n\nOpen a ticket and add a Solution as a technician.\n\nOpen the same ticket as the requester (or a profile that previously could approve/refuse solutions).\n\nLook for the “Approve solution / Refuse solution” option in the ticket UI.\n\nExpected behavior\n\nThe requester should have an option to:\n\nApprove the solution, or\n\nRefuse the solution (to reopen/request changes),\n\nas in previous versions.\n\nActual behavior\n\nIn GLPI 11.0.5, the approve/refuse solution option is missing from the ticket UI, preventing solution validation.", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Does the user's profile allow moving a ticket from Solved to Closed in the \"Life cycles\" tab of the profile?\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4027819731, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23020#issuecomment-4027819731", "createdAt": "2026-03-10T00:37:29Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "Hi,\n\nI tested this again and I can confirm that the original behavior I reported is no longer reproducible on my side.\n\nThe solution validation / refusal flow is now working correctly in the simplified interface once the profile lifecycle is configured properly, so this part can be considered resolved and the issue may be closed.\n\nHowever, during retesting I noticed a different problem: when the ticket is validated and moves to the closed state in the simplified interface, the layout becomes visually broken / misaligned.\nIn open tickets, the page is displayed correctly, but in closed tickets the interface becomes distorted.\n\nSo, to avoid mixing two different topics in the same report:\n\n* this original issue can be closed as resolved;\n* I will report the layout problem separately as a new issue, since it appears to be a different UI bug.\n\nThank you for your follow-up.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4031887722, "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23020#issuecomment-4031887722", "createdAt": "2026-03-10T14:34:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23020, "url": "https://github.com/glpi-project/glpi/issues/23020", "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-04T17:50:13Z", "updatedAt": "2026-06-19T01:16:03Z", "closedAt": "2026-03-10T15:14:20Z" } }, { "title": "\"System retrieving the category from the knowledge base instead of the knowledge base itself when associating it with the ITIL category.\"", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nSystem retrieving the category from the knowledge base instead of the knowledge base itself when associating it with the ITIL category.\n\n[Image omitted]\n\n[Image omitted]\n\nAffected page:\n/front/knowbaseitem.php", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The behavior is correct while the label is confusing. ITIL categories can be linked to KB categories, not individual articles.\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4013105728, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23402#issuecomment-4013105728", "createdAt": "2026-03-06T17:43:53Z" } }, { "userEmail": "avery.bennett@peppermint.local", "text": "Is there somewhere I can associate the knowledge base with a form?\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4013121652, "author": "nobrupinto", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23402#issuecomment-4013121652", "createdAt": "2026-03-06T17:47:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23402, "url": "https://github.com/glpi-project/glpi/issues/23402", "author": "nobrupinto", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-06T17:38:49Z", "updatedAt": "2026-06-18T01:10:50Z", "closedAt": "2026-03-09T07:16:00Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "[11.0.6][Notifications] Disabling \"Allow response\" seems ineffective", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nDisabling the \"Allow response\" option for an email notification does not prevent a user to create a followup by responding to this email.\n\nAccording to the FAQ, this should not be the case :\n\n-\n-\n\nReproduction steps:\n1. Start from a fresh install (I used the docker image for 11.0.6)\n2. Enable & configure email notifications\n3. For notification \"New ticket\", set \"Allow response\" to \"No\"\n4. Configure a receiver. Collection options can be left as default\n5. Create a self-service user with an email\n6. Create a ticket with this user\n7. Respond to the new ticket email notification & collect emails\n8. A followup has been created", "priority": "medium", "type": "support", "createdByEmail": "cameron.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Did you configure the no-reply email address?\n\nThis setting just changes the Reply-To address to the No-Reply address when responses are not allowed, and removed the text in the emails indicating when the user should add their response.\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4011915777, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23394#issuecomment-4011915777", "createdAt": "2026-03-06T14:01:03Z" } }, { "userEmail": "cameron.blair@peppermint.local", "text": "Oh, right. I hadn't understood it that way.\nThank you very much, my problem is solved ! Closing this issue now.\n\nOriginal response date: 2026-03-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4021842243, "author": "b1llyshears", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23394#issuecomment-4021842243", "createdAt": "2026-03-09T07:55:00Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23394, "url": "https://github.com/glpi-project/glpi/issues/23394", "author": "b1llyshears", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-06T11:49:30Z", "updatedAt": "2026-06-18T01:10:43Z", "closedAt": "2026-03-09T07:55:00Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Bug in Dashboard", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWe use de version 10 and in dashboard show the name of the groups when i select \"TOP tickes for sign group\". In version 11.0.5, this option only show the ID of groups.\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. click in Assistence\n2. click in Dashboard\n3. Edit the page\n4. chice \"TOP tickes for sign group\"", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue exactly, but only because some other errors occur and breaks card rendering.\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3966763247, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23251#issuecomment-3966763247", "createdAt": "2026-02-26T13:49:08Z" } }, { "userEmail": "harper.bennett@peppermint.local", "text": "Hi, have one position?\n\nOriginal response date: 2026-03-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4000342030, "author": "wesleipedroza", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23251#issuecomment-4000342030", "createdAt": "2026-03-04T21:15:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23251, "url": "https://github.com/glpi-project/glpi/issues/23251", "author": "wesleipedroza", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "dashboard" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-26T12:35:46Z", "updatedAt": "2026-06-18T01:10:34Z", "closedAt": "2026-03-09T11:32:53Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "CSV export in GLPI 11 is not adding BOM", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nGLPI 10.x created CSV export output with BOM which provided better Excel compatibility to detect encoding.\nGLPI 11.x is not adding BOM in CSV which is causing issues with Excel.\n\nGLPI 10 code (always adds BOM):\n\nI suggest to add line to CSV exporters:\n$csv->setUseBOM(true);\n\nand:\n\n$this->setUseBOM(true)\n\nPlease let me know whether this is fine and I will submit PR.\n\nReproduction steps:\n1. In any search list click Export to CSV\n2. Check output using some HEX viewer (xxd) and watch whether it contains BOM", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "On a related note, I am curious why GLPI is using two separate libraries to write CSV files.\n\nI guess the BOM should be restored if it was working properly in GLPI 10 with it.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993338149, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23291#issuecomment-3993338149", "createdAt": "2026-03-03T20:24:17Z" } }, { "userEmail": "devon.bennett@peppermint.local", "text": "Yeah, you are right, it looks Search Engine is now using the PhpSpreadsheet\nand some other parts are using CsvResponse eg League\\Csv and there is different method for BOM setup eg: $csv->setOutputBOM(BOM::Utf8);\n\nI suggest to change for now just Search engine which previously used that simple echo in GLPI setUseBOM(true)\n.\nI've created PR#23389\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4010054570, "author": "VladoTTX", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23291#issuecomment-4010054570", "createdAt": "2026-03-06T07:24:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23291, "url": "https://github.com/glpi-project/glpi/issues/23291", "author": "VladoTTX", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-02T09:46:40Z", "updatedAt": "2026-06-18T01:10:26Z", "closedAt": "2026-03-09T13:00:21Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI update from 10.0.25 to 11.07 display problems", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nI've just upgraded from GLPI 10.0.25 to 11.07\nMany display problems like :\n\n[Image omitted]\n\nor in ticket listing where requester or technician vcard is display without clicking on \"i\"\n\n[Image omitted]\n\nReproduction steps:\nJust open plugin or ticket menu", "priority": "medium", "type": "support", "createdByEmail": "riley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "You should try clearing your browser cache/trying another browser first. If issues persist, you may ask on the forum for more help. We keep GitHub issues for only bugs and I am not sure there is a bug here but it is hard to say without you providing the requested GLPI Setup Information.\n\nIf you are hosting on Windows, see\n\nOriginal response date: 2026-06-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4724018880, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24582#issuecomment-4724018880", "createdAt": "2026-06-16T22:03:20Z" } }, { "userEmail": "riley.bennett@peppermint.local", "text": "Hi,\n\nIssue solved by modify src/html.php #24098\n.\n\nI'm running GLPI on Windows but not in IIS. I've installed Apache server\nbut it seems that same issue appears in aApache for Windows too.\n\nThanks for the solution.\n\nBR\n\nMath\n\nLe mer. 17 juin 2026 à 00:03, Curtis Conard *@*.*> a\nécrit :\n\n*cconard96* left a comment (glpi-project/glpi#24582)\n\nYou should try clearing your browser cache/trying another browser first.\nIf issues persist, you may ask on the forum for more help We keep GitHub\nissues for only bugs and I am not sure there is a bug here but it is hard\nto say without you providing the requested GLPI Setup Information.\nIf you are hosting on Windows, see #24098\n.\n—\nReply to this email directly, view it on GitHub\n,\nor unsubscribe\n\n.\nTriage notifications, keep track of coding agent tasks and review pull\nrequests on the go with GitHub Mobile for iOS\n\nand Android\n.\nDownload it today!\nYou are receiving this because you authored the thread.Message ID:\n*@*.*>\n\nOriginal response date: 2026-06-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4726722935, "author": "Math6768", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24582#issuecomment-4726722935", "createdAt": "2026-06-17T06:30:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24582, "url": "https://github.com/glpi-project/glpi/issues/24582", "author": "Math6768", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-16T16:00:10Z", "updatedAt": "2026-06-17T06:30:11Z", "closedAt": "2026-06-16T22:00:59Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Bug on the top ticket entities widget", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello,\n\nI am encountering a bug on the top ticket entities widget. Following the update from V10 to V11, you must manually define a palette on the widget in order to access it.\n\n[Image omitted]\n\nAfter defining the palette, everything works.\n\nSincerely,\n\nAffected page:\nfront/dashboard_helpdesk.php", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Could you test the fix in #23338?\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993463940, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23268#issuecomment-3993463940", "createdAt": "2026-03-03T20:50:24Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "Could you test the fix in #23338?\n\nHello, thank you, it works perfectly.\n\nOriginal response date: 2026-03-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3998607691, "author": "anthonymontebrun", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23268#issuecomment-3998607691", "createdAt": "2026-03-04T16:20:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23268, "url": "https://github.com/glpi-project/glpi/issues/23268", "author": "anthonymontebrun", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "dashboard" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-27T10:31:10Z", "updatedAt": "2026-06-14T01:11:24Z", "closedAt": "2026-03-05T07:05:57Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Error saving form when adding question type “Item” selecting – GLPI Objects Documents – GLPI Forms", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4 - 11.0.5\n\nIssue description:\nHello,\n\nI am experiencing an error in the GLPI Forms module while creating a form. When I add a new question and select the type “Item”, and then choose “GLPI Objects” followed by “Management – Documents” (in order to list and allow selection of existing documents in the system), the form cannot be saved and an “Unexpected error” message appears.", "priority": "medium", "type": "support", "createdByEmail": "avery.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue on the latest GLPI 11.0/bugfixes branch. Maybe it was already fixed, or there is something I am missing in order to recreate it.\n\nOriginal response date: 2026-02-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3911170729, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23117#issuecomment-3911170729", "createdAt": "2026-02-17T00:29:20Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No feedback, closing.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4005677807, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23117#issuecomment-4005677807", "createdAt": "2026-03-05T14:59:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23117, "url": "https://github.com/glpi-project/glpi/issues/23117", "author": "Jose-Pachongo", "anonymizedAuthorEmail": "avery.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-13T16:30:58Z", "updatedAt": "2026-06-14T01:11:15Z", "closedAt": "2026-03-05T14:59:04Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "PHP Warning: Undefined array key \"items_id\" in src/Webhook.php when creating ITIL validation (GLPI 11.0.5)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nAfter upgrading to GLPI 11.0.5, I’m consistently getting a PHP warning in the logs when creating an ITIL validation (ticket approval / validation) having a webhook activated to notify it.\n\nReproduction steps:\n1. Activate a webhook. itemType: \"Assistance - Ticket approval\"\n2. Create or process an ITIL validation (ticket approval/validation)\n3. Check PHP logs\n\nNotes\nThis does not seem to break functionality, but it pollutes the PHP logs.\nFinally the Parentitem infoi is sent in webhook payload\n\nAdditional context:\nIn src/Webhook.php (around line ~635), addParentItemData() assumes $data['item']['items_id'] exists for CommonDBChild subclasses:\n\nprivate function addParentItemData(array &$data, string $itemtype, int $items_id): void\n{\n if (is_subclass_of($itemtype, CommonDBChild::class)) {\n $parent_itemtype = $data['item']['itemtype'];\n $parent_id = $data['item']['items_id']; // triggers warning when missing\n } elseif (is_subclass_of($itemtype, CommonITILTask::class)) {\n ...\n } else {\n return;\n }\n ...\n}\n\nIt seems that during the ITIL validation creation, $data['item'] contains itemtype but does not contain items_id, resulting in Undefined array key \"items_id\".", "priority": "medium", "type": "support", "createdByEmail": "cameron.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Cannot reproduce. Please check if any plugin or custom settings may interfere.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3897096653, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23069#issuecomment-3897096653", "createdAt": "2026-02-13T12:55:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No feedback, closing.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4005680271, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23069#issuecomment-4005680271", "createdAt": "2026-03-05T14:59:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23069, "url": "https://github.com/glpi-project/glpi/issues/23069", "author": "mepuerto", "anonymizedAuthorEmail": "cameron.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-10T12:39:12Z", "updatedAt": "2026-06-14T01:11:12Z", "closedAt": "2026-03-05T14:59:21Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Password requirements not checked when using expired password link", "detail": "Affected version:\n11.0.5\n\nIssue description:\nHi, there's a bug (and we have the same one on our GLPI server) : I received an email telling me I need to change my password.\n\nI get to the interface, enter a new password, and it doesn't work when I try to log in again. It works if I use LostPassword, but not with the email.\n\nIt doesn't seem to check the password requirements (I entered a 14-character password and it didn't say anything) – whereas LostPassword checks correctly.", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello Casey Blair i cannot reproduce.\n\nHere is what I just tested:\n\n- Configured password expiration delay and backdated password_last_update to trigger the expired password flow\n- Logged in and was correctly redirected to the password update form\n- The password security policy requirements are displayed on the form (when use_password_security is enabled)\n- Client-side validation prevents submitting a password that doesn't meet the requirements\n- Server-side validation (User::validatePassword()) is also called before saving\n- After changing the password with a valid one, login works correctly with the new password\n\nThe code path is identical between version 11.0.5 and the current branch — no changes were made to the relevant files.\n\nCould you provide more details to help us reproduce?\n1. What are your password security policy settings? (Configuration > General > Security)\n2. When you say \"it didn't say anything\", did you see the password requirements checklist on the form (minimum length, digit, uppercase, etc.)?\n3. After submitting the new password, did you see a success message (\"Your password has been successfully updated\") or an error?\n4. Do you have any plugins that might interfere with the authentication or user update process?\n\nThank you!\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3870389773, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22730#issuecomment-3870389773", "createdAt": "2026-02-09T09:16:31Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No feedback, closing.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4005683398, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22730#issuecomment-4005683398", "createdAt": "2026-03-05T14:59:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22730, "url": "https://github.com/glpi-project/glpi/issues/22730", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-19T08:46:20Z", "updatedAt": "2026-06-14T01:11:09Z", "closedAt": "2026-03-05T14:59:43Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "user:reset_password console command gets an error", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nThe user:reset_password console command won't succeed in resetting an user's password.\n\nI keep getting the following error:\n\nDiagnostic information:\nphp-errors.log contains:\n\nEach call to bin/console user:reset_password generates a new glpi.WARNING: * Test logger line of log.\n\nCalling bin/console user:disable normal works (it disables the user, without any error) and also generates a new line of log.\n\nReproduction steps:\nYou'll get:\n\nAdditional context:\nI am using the Dockerized version from but I doubt it has an impact on the behavior.\n\nI've tested tags 11.0.0 (sha256:d4cea82338b14c761e6707a71241bb85a3f22fc47befeeb518039a251be742c2), 11.0.5 (sha256:f727df6b56b2a0b464dae6111af6da3e215c639ca81e0bfc921219a3cd5574ef) and 11.0-nightly (sha256:3e266a2ad110c475cdc99477f4ca8a826ea5eada9e6b6cf6e949ba0b72f7b187): got the same error for all of them.\n\nI've looked at the code and the error seems to be in User::prepareInputForUpdate() (called by CommonDBTM::update()).\n\nThere is a big if there:\n\nI get bool(true) for:\n\n* isset($input['id'])\n* $this->validatePassword($input[\"password\"] ?? '', $password_errors)\n* $input['password_forget_token'] == $glpi_key->decrypt($this->fields['password_forget_token'])\n\nBut bool(false) for:\n\n* (($input['id'] == Session::getLoginUserID())\n* $this->currentUserHaveMoreRightThan($input['id'])\n* isset($this->fields['password_forget_token'])", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "avery.bennett@peppermint.local", "text": "Checking for CLI execution with isCommandLine() in User::currentUserHaveMoreRightThan() fixes the issue:\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3826118622, "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22931#issuecomment-3826118622", "createdAt": "2026-01-30T22:33:12Z" } }, { "userEmail": "logan.blair@peppermint.local", "text": "Hello!\n\nHow can I reset a password for a user without this console command in 11.0.5?\n\nThe \"Change password\" menu in the Web UI neither works as the submit button is not visible. May I open a new issue for this?\n\nThanks!\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3877963965, "author": "alesnav", "anonymizedAuthorEmail": "logan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22931#issuecomment-3877963965", "createdAt": "2026-02-10T14:25:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22931, "url": "https://github.com/glpi-project/glpi/issues/22931", "author": "C-Duv", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-30T22:15:37Z", "updatedAt": "2026-06-14T01:11:04Z", "closedAt": "2026-03-05T15:18:48Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "[11.0.5 - Regression] Impossible to create ticket with \"Assigned To\" field mandatory", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen creating a ticket with \"assigned to\" field mandatory and selecting a group of technicians or single technicians, i got the following error :\nglpi.CRITICAL: * Uncaught PHP Exception TypeError: \"Safe\\preg_match(): Argument # 2 ($subject) must be of type string, array given, called in ./src/CommonITILObject.php on line 3029\" at pcre.php line 613\n Backtrace :\n ...hecodingmachine/safe/generated/8.3/pcre.php:613\n ./src/CommonITILObject.php:3029 Safe\\preg_match()\n ./src/Ticket.php:1527 CommonITILObject->prepareInputForAdd()\n ./src/CommonDBTM.php:1339 Ticket->prepareInputForAdd()\n ./front/ticket.form.php:79 CommonDBTM->add()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:71 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\nNo forms plugin in use.\nIf disabling \"Assign to\" is mandatory, the ticket creates correctly and with appropriate access we can add a technician or group.\nIn 11.0.4 and before, no problem with this.\n\nAffected page:\n/front/ticket.form.php\n\nReproduction steps:\n1. Go to Create ticket with \"Assign to\" template mandatory\n2. Fill all mandatory fields\n3. Click Add\n4. Got error\n\nEnvironment details:\nServer\n\nOperating system: Linux XXXX 6.8.0-90-generic #​91-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 18 14:14:30 UTC 2025 x86_64\n\nPHP: 8.3.6 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv,\nintl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer,\nxmlreader, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"512M\" post_max_size=\"40M\"\nsession.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"40M\"\n\nWeb server: Apache ()\n\nDatabase:\n\nServer Software: Ubuntu 24.04\n\nServer Version: 10.11.13-MariaDB-0ubuntu0.24.04.1\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nRequirements:\nPHP version (8.3.6) is supported.\nOS and PHP are relying on 64 bits integers.\nSessions configuration is OK.\nAllocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installed\ncurl extension is installed\ngd extension is installed\nintl extension is installed\nmbstring extension is installed\nzlib extension is installed\nbcmath extension is installed\nThe constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installed\nDatabase engine version (10.11.13) is\nsupported.\nThe log file has been created successfully.", "priority": "medium", "type": "support", "createdByEmail": "emerson.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.blair@peppermint.local", "text": "I have exactly the same problem. If template have mandatory fields, then error appears durig ticket creation. And seams that problem is related only to \"assigned to\" field\n\nOriginal response date: 2026-03-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3984736677, "author": "Kuba-Pawlak", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23223#issuecomment-3984736677", "createdAt": "2026-03-02T14:27:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This issue has laready been reported and a fix is available. Try with a recent nightly build, or wait for 11.0.6 release.\n\nOriginal response date: 2026-03-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3985077793, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23223#issuecomment-3985077793", "createdAt": "2026-03-02T15:27:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23223, "url": "https://github.com/glpi-project/glpi/issues/23223", "author": "Bigthibo", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-24T11:28:07Z", "updatedAt": "2026-06-11T01:08:14Z", "closedAt": "2026-03-02T15:27:03Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Unable to access the assistance tab in general config menu", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nError when accessing to assistance tab in general settings.\n\nAffected page:\nfront/config.form.php\n\nReproduction steps:\n1. Go to Configuration > General\n2. Click on \"Assistance\" tab", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. What are the current values of the \"time_step\", \"planning_begin\" and \"planning_end\" config values?\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967216990, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23256#issuecomment-3967216990", "createdAt": "2026-02-26T15:06:44Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "It's OK !\nI don't know why but the planning_begin value was an URL...\n\nThanks\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967273071, "author": "RandomFrenchAdmin", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23256#issuecomment-3967273071", "createdAt": "2026-02-26T15:14:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23256, "url": "https://github.com/glpi-project/glpi/issues/23256", "author": "RandomFrenchAdmin", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-26T14:53:29Z", "updatedAt": "2026-06-07T01:08:58Z", "closedAt": "2026-02-26T15:18:11Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Differentiate between start date of current period and start date of contract", "detail": "Contribution description:\nCurrently glpi offers to track how a contract is prolonged (never,tactil,express) but does not track when the current period started.\nI suggest adding a field current period start date. For tactil it will be updated via cron, for express it must be updated manually. I think this could make the code easier during calculation if a notification is needed and hopefully allow to sort and filter contracts by expiration.\nOne ambiguity that would need specification is what should happen with the current period start date when the user retroactively changes the contract start date.\nDo you thing this would be a good addition to glpi or better done in a custom plugin?", "priority": "low", "type": "feature", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "cameron.blair@peppermint.local", "text": "While this does not add a current period start date, this PR #23516 does change the period end calculation method and should be closer to reality and send notifications at the appropriate time (I would really appreciate your feedback, as this fix lacks end users validation).\n\nRegarding the sorting on expiration dates, from my understanding it is not possible to sort on this field as is because the sorting on GLPI is done via SQL on the table fields, and the expiration field is a virtual field calculated on runtime after the query has been run, and not a field in the database.\n\nOriginal response date: 2026-06-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4600059351, "author": "troncoli", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24422#issuecomment-4600059351", "createdAt": "2026-06-02T08:07:58Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Its a contribution offer I would like to discuss if the maintainers agree it makes sense.\n\nOriginal response date: 2026-06-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4610288021, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24422#issuecomment-4610288021", "createdAt": "2026-06-03T08:03:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24422, "url": "https://github.com/glpi-project/glpi/issues/24422", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-01T12:03:45Z", "updatedAt": "2026-06-03T08:03:31Z", "closedAt": "2026-06-03T07:51:47Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Data centers /Server rooms", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nThe plan displays only one color for all racks. After changing the rack color in the properties, the plan continues to display a single common color. The color change occurs when a new rack is added to the plan. All racks are then changed to the same color as the new one.", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jesse.bennett@peppermint.local", "text": "clean installation without plugins\n\nOriginal response date: 2026-02-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3908009275, "author": "cofig", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23131#issuecomment-3908009275", "createdAt": "2026-02-16T11:40:14Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm\n\nOriginal response date: 2026-02-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3911065854, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23131#issuecomment-3911065854", "createdAt": "2026-02-17T00:00:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23131, "url": "https://github.com/glpi-project/glpi/issues/23131", "author": "cofig", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-16T11:33:41Z", "updatedAt": "2026-05-30T01:00:37Z", "closedAt": "2026-02-18T13:38:09Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "filter rule dropdown in rule group not showing right criteria items", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nIn the search filters when creating a group of rules and choosing \"is\" for the filter in the group it's showing the wrong values in the dropdown (items name) unless you use global rules. It's only happening inside the group.\n\nHere is a screenshot of what's happening :\n1. the rule outside of the group is showing Yes and No for child entities which is correct :\n[Image omitted]\n\n2. the rule inside the group isn't showing the same values (it's the name of items in this category) :\n[Image omitted]\n\nReproduction steps:\n1. Open one of the assets category\n2. Add a group of rules\n3. Add a search criteria using \"is\" or \"is not\"\n4. Try to choose a value", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please check with latest nightly if you reproduce; I guess this already have been reported and it could be fixed already.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3869843699, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23048#issuecomment-3869843699", "createdAt": "2026-02-09T07:31:28Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "Yes, it's fixed in the latest nightly, closing this issue and waiting for next release.\n\nOriginal response date: 2026-02-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3916525392, "author": "emitlinks", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23048#issuecomment-3916525392", "createdAt": "2026-02-17T18:50:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23048, "url": "https://github.com/glpi-project/glpi/issues/23048", "author": "emitlinks", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-08T20:27:12Z", "updatedAt": "2026-05-29T01:05:42Z", "closedAt": "2026-02-17T18:50:18Z" } }, { "title": "bad template display", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWith respect to version 10.x.x, this was how a ticket was displayed when a user with a limited template created the ticket:\n\n[Image omitted]\n\nIn version 11.x.x, the technician observes the creator's template:\n\n[Image omitted]\n\nNote: In version 10, it makes no difference whether the originating user has a standard or simplified profile interface.\n\nReproduction steps:\n1. assign a user a self-service profile with a standard interface and a template with minimal information.\n2. create the ticket with this user.\n3. With a user with a technical profile and a template without information restrictions, view the ticket.", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It isn't a bug, but I have noted the confusion/inconsistency.\n\nEssentially, one of the early additions for GLPI 11 was the ability to restrict the available statuses for tickets/changes/problems and it was tied into the template system. In order for it to work, templates suddenly became a property on the ticket/change/problem rather than just a custom form when creating them.\n\nIf the template changes via a category change or something else, then that ticket/change/problem will use that template for everyone.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3899201274, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23118#issuecomment-3899201274", "createdAt": "2026-02-13T20:06:23Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "It would be good if, in the \"Read-only fields\" tab within the template, it was possible to add which profiles will not be able to see what is added there.\n\nOriginal response date: 2026-02-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3916806944, "author": "german-giraldom", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23118#issuecomment-3916806944", "createdAt": "2026-02-17T20:00:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23118, "url": "https://github.com/glpi-project/glpi/issues/23118", "author": "german-giraldom", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-13T18:42:41Z", "updatedAt": "2026-05-29T01:05:39Z", "closedAt": "2026-02-16T06:09:42Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "TypeError in CommonITILObject::prepareInputForAdd() when creating ticket with Technician profile", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen creating a ticket using a Technician profile in GLPI 11.0.5 (PHP 8.2), ticket creation fails with a fatal error:\n\nUncaught PHP Exception TypeError:\nSafe\\preg_match(): Argument #2 ($subject) must be of type string, array given\n\nThe issue occurs in:\n\nsrc/CommonITILObject.php (around line 3029)\n\nReproduction steps:\nLogin with a profile that can modify the requester (e.g. Technician)\n\nCreate a new ticket\n\nFill required fields\n\nSubmit\n\nResult:\n\nSafe\\preg_match(): Argument #2 ($subject) must be of type string, array given\n\nEnvironment details:\nGLPI version: 11.0.5\n\nPHP version: 8.2\n\nWeb server: Apache\n\nDatabase: MySQL\n\nNo plugin involved\n\nOccurs only with Technician profile\n\nAdditional context:\n✅ Proposed fix\n\nProtect preg_match() by ensuring the value is not an array.\n\nSuggested patch\nif (\n empty($input[$key])\n || (!is_array($input[$key])\n && preg_match('/([\\s| ]+)?/', $input[$key]) !== 0)\n || ($input[$key] == 'NULL')\n || (is_array($input[$key])\n && ($input[$key] === [0 => \"0\"]))\n) {\n $mandatory_missing[$key] = $fieldsname[$val];\n}", "priority": "medium", "type": "support", "createdByEmail": "devon.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This issues already has been reported and fixed. Try with nightly build.\n\nOriginal response date: 2026-02-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3883186486, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23079#issuecomment-3883186486", "createdAt": "2026-02-11T09:13:39Z" } }, { "userEmail": "devon.blair@peppermint.local", "text": "Oh thank you. I hadn't seen it\n\nOriginal response date: 2026-02-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3884516526, "author": "ElanOD78", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23079#issuecomment-3884516526", "createdAt": "2026-02-11T13:41:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23079, "url": "https://github.com/glpi-project/glpi/issues/23079", "author": "ElanOD78", "anonymizedAuthorEmail": "devon.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-02-11T08:55:05Z", "updatedAt": "2026-05-24T01:03:00Z", "closedAt": "2026-02-11T09:13:39Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Ticket/Approvals State Error when no request is available", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.18\n\nIssue description:\nError in GLPI Version 10.0.18:\nWhile there is no approval request sent the Site will go all white, by changing the approval state \"Minimum validation required\" to 50 or 100%.\nTrying the same with 0% the site will just reload.\n\nI haven´t made any tests on other Versions.\n\nReproduction steps:\n1. create new Ticket with no approvals\n2. move to the approval of the ticket\n3. change the \"Minimum validation required\" to 50 or 100%\n4. save your changes\n5. Error will accur", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please try with 10.0.23. There were 5 bug-fix releases since 10.0.18 and this may have already been resolved.\n\nOriginal response date: 2026-02-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3891054582, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23100#issuecomment-3891054582", "createdAt": "2026-02-12T13:44:39Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Feel free to reopen if your reproduce after updade.\n\nOriginal response date: 2026-02-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3891134628, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23100#issuecomment-3891134628", "createdAt": "2026-02-12T14:01:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23100, "url": "https://github.com/glpi-project/glpi/issues/23100", "author": "leon9neun", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-12T13:40:24Z", "updatedAt": "2026-05-24T01:02:51Z", "closedAt": "2026-02-12T14:01:17Z" } }, { "title": "Virtualization on Computer issue", "detail": "Affected version:\n11.0.4\n\nIssue description:\nDuring usage 11.0.4 I notice 2 issue with Virtualization section on Computer asset.\n\n1. Machine column currently show Virtualization system. In previouse version, that column show linked by UUID other Computer\n2. After created entry in Virtualization and enter to it, Computer and Machine are the same. When I save any changes on existed item, virtual machine \"move\" to other computer. Reproduce step provided.\n\nReproduction steps:\n1. Create 1st Computer: server00\n2. Create 2nd Computer: vm00 with any UUID (for linkin)\n3. Navigate to server00 and on Virtualization, create entry vm00 with the same UUID\n4. Return to server00 and to go Virtualization again,\n5. Open created entry for vm00\n6. Look on \"Computer\" and \"Machine\". Both are equal and set to vm00\n7. Made changes (i.e. add comment) and save.\n8. Back to server00 and to go Virtualization again.\n9. At that point vm00 gone from server00 and can be found on vm00", "priority": "medium", "type": "support", "createdByEmail": "lane.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I confirm the issue\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3766877510, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22726#issuecomment-3766877510", "createdAt": "2026-01-19T07:33:16Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "* After created entry in Virtualization and enter to it, Computer and Machine are the same. When I save any changes on existed item, virtual machine \"move\" to other computer. Reproduce step provided.\n\nWill be fixed by #22728\n\n* Machine column currently show Virtualization system. In previouse version, that column show linked by UUID other Computer\n\nI do not get the point. We're listing a computer's VMs, there is no need for a link to this computer. UUID itself is still show.\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3766960093, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22726#issuecomment-3766960093", "createdAt": "2026-01-19T07:57:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22726, "url": "https://github.com/glpi-project/glpi/issues/22726", "author": "dkurzelewski", "anonymizedAuthorEmail": "lane.adler@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-18T17:36:33Z", "updatedAt": "2026-05-24T01:02:48Z", "closedAt": "2026-01-19T08:49:01Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "[11.0.5] Error on displaying System tab", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nAfter upgrading from version 11.0.2 to version 11.0.5, I get the following error when trying to visit the System tab in the Setup>General menu:\n\n[Image omitted]\n\nAffected page:\najax/common.tabs.php?_glpi_tab=Config%245&formoptions=data-track-changes%3Dtrue&_target=%2Ffront%2Fconfig.form.php&_itemtype=Config&id=1", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This should not be possible. This particular config entry is done in a file that is automatically included with each request and should cause other issues if it wasn't.\n\nWhen you updated did you copy the new files over the old ones (this is not recommended), or was the \"src/autoload/CFG_GLPI.php\" file otherwise modified? At the end of the file should be this line:\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3874162801, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23061#issuecomment-3874162801", "createdAt": "2026-02-09T22:17:28Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "You're right about it, the src/autoload/CFG_GLPI.php was in its former version and needed to be updated. After doing that, the error went away.\n\nThanks for the quick reply, and sorry for bothering you with this unnecessary issue.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3877933826, "author": "rafaelse", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23061#issuecomment-3877933826", "createdAt": "2026-02-10T14:19:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23061, "url": "https://github.com/glpi-project/glpi/issues/23061", "author": "rafaelse", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-09T20:47:52Z", "updatedAt": "2026-05-22T01:01:38Z", "closedAt": "2026-02-10T14:19:58Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Impersonation is missing", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\n[Image omitted]\n\nImpersonation user function is missing?", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "lane.blair@peppermint.local", "text": "Check permission in profile\n\n[Image omitted]\n\nOriginal response date: 2026-05-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4449073563, "author": "igwtsw", "anonymizedAuthorEmail": "lane.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24223#issuecomment-4449073563", "createdAt": "2026-05-14T08:37:30Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "Got it.\nThanks.\n\nOriginal response date: 2026-05-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4484000611, "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24223#issuecomment-4484000611", "createdAt": "2026-05-19T02:52:37Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24223, "url": "https://github.com/glpi-project/glpi/issues/24223", "author": "wjqwh", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-14T06:54:32Z", "updatedAt": "2026-05-19T02:52:37Z", "closedAt": "2026-05-17T00:29:04Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI API v2.1 ERROR_RIGHT_MISSING On any Administration path endpoints", "detail": "Issue description:\nHi, I try to implement GLPI API to my software, and I have this problem that if I want to get Entity on /Administration/Entity Endpoint, I got this response:\n\n{\n \"status\": \"ERROR_RIGHT_MISSING\",\n \"title\": \"You don't have permission to perform this action.\",\n \"detail\": null\n}\n\nMy GET request is like this:\n\nHeaders:\n{\n 'Accept': 'application/json',\n 'Authorization': 'Bearer {Access_Token}\n 'Accept-Language': 'en_GB'\n}\n\nI also get my Access_Token from\n\nI am authorizing using Client_ID, Client_Secret, Username, Password and scope\n{\n'scope': 'api inventory user email graphql'\n}\n\nWhen I try to get something else like from /status/all everything goes smoothly, but not on the Administration path\n\nI have given all scopes to OAUTH and API\nAnd I am using user with Super-Admin role", "priority": "medium", "type": "support", "createdByEmail": "morgan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. If your user has access to multiple profiles/entities, be sure to specify the desired ones using the \"GLPI-Profile\" (ID of the profile), \"GLPI-Entity\" (ID of the entity) and \"GLPI-Entity-Recursive\" (1/true to include child entities) request headers.\n\nOriginal response date: 2026-02-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3853477295, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23025#issuecomment-3853477295", "createdAt": "2026-02-05T12:57:28Z" } }, { "userEmail": "morgan.bennett@peppermint.local", "text": "Thanks for help! It finally worked\n\nOriginal response date: 2026-02-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3853556731, "author": "Czaraoth", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23025#issuecomment-3853556731", "createdAt": "2026-02-05T13:10:16Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23025, "url": "https://github.com/glpi-project/glpi/issues/23025", "author": "Czaraoth", "anonymizedAuthorEmail": "morgan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-05T12:52:52Z", "updatedAt": "2026-05-17T01:00:12Z", "closedAt": "2026-02-05T13:10:16Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "MySQL Query error computer.php", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nTrying to access to computer, blank page with \"an error occured, go back\"\nSQL query contain 2 \",\" and throw an SQL error\n\nAffected page:\n\nReproduction steps:\n11.0.4\ngo to computer\n\nEnvironment details:\nGLPI: 11.0.4 ( => /var/www/html/glpi-info.cauxseine.fr)\nInstallation mode: TARBALL\nCurrent language: fr_FR\nSource Integrity: 2 files changed\n A: inc/downstream.php\n A: public/statistiques.php\n\nOperating system: Linux CSA-WEB 6.12.57+deb13-amd64 #​1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) x86_64\n\nPHP: 8.3.28 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv,\nimap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm,\ntokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"60\" max_input_vars=\"1000\" memory_limit=\"256M\" post_max_size=\"100M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"100M\"\n\nWeb server: Apache/2.4.65 (Debian) (Apache/2.4.65 (Debian) Server at glpi-info.cauxseine.fr Port 80)\n\nUser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36\nEdg/144.0.0.0\n\nDatabase:\n\nServer Software: MySQL Community Server - GPL\n\nServer Version: 8.4.7\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi-info@172.16.30.50/glpi-info\n\nHost info: 172.16.30.50 via TCP/IP\n\nRequirements:\nPHP version (8.3.28) is supported.PHP version (8.3.28) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (8.4.7) is supported.Database engine version (8.4.7) is supported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/lib/glpi/info/files/_cache has been validated. Write access to\n/var/lib/glpi/info/files/_cron has been validated. Write access to /var/lib/glpi/info/files has been validated. Write access to\n/var/lib/glpi/info/files/_graphs has been validated. Write access to /var/lib/glpi/info/files/_lock has been validated. Write\naccess to /var/lib/glpi/info/files/_pictures has been validated. Write access to /var/lib/glpi/info/files/_plugins has been\nvalidated. Write access to /var/lib/glpi/info/files/_rss has been validated. Write access to /var/lib/glpi/info/files/_sessions\nhas been validated. Write access to /var/lib/glpi/info/files/_tmp has been validated. Write access to\n/var/lib/glpi/info/files/_uploads has been validated.Write access to /var/lib/glpi/info/files/_cache has been validated.\nWrite access to /var/lib/glpi/info/files/_cron has been validated.\nWrite access to /var/lib/glpi/info/files has been validated.\nWrite access to /var/lib/glpi/info/files/_graphs has been validated.\nWrite access to /var/lib/glpi/info/files/_lock has been validated.\nWrite access to /var/lib/glpi/info/files/_pictures has been validated.\nWrite access to /var/lib/glpi/info/files/_plugins has been validated.\nWrite access to /var/lib/glpi/info/files/_rss has been validated.\nWrite access to /var/lib/glpi/info/files/_sessions has been validated.\nWrite access to /var/lib/glpi/info/files/_tmp has been validated.\nWrite access to /var/lib/glpi/info/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed:\nctype, iconv, sodium.\nWrite access to /var/www/html/glpi-info.cauxseine.fr/marketplace has been validated.Write\naccess to /var/www/html/glpi-info.cauxseine.fr/marketplace has been validated.\nTimezones seems loaded in d\n\n[Content truncated.]", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "That's probably due to a column you added in your view. You should first try without plugins.\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798772698, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22825#issuecomment-3798772698", "createdAt": "2026-01-26T10:03:52Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Thank you very much, tried disabling GLPI Inventory plugin and it worked. I removed the agent version column and all is fine.\n\nThanks !\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798819290, "author": "H4rDBuG", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22825#issuecomment-3798819290", "createdAt": "2026-01-26T10:14:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22825, "url": "https://github.com/glpi-project/glpi/issues/22825", "author": "H4rDBuG", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-26T09:14:30Z", "updatedAt": "2026-05-15T00:57:22Z", "closedAt": "2026-01-26T10:14:05Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Cannot place Two 'Half Rack' assets together", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen adding/moving assets within a Rack, you cannot have two 'Half Rack' assets on the same row, despite one being on the left, & the other on the right - an error appears stating \"Not enough space available to place item\"\n\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce:\n\n[Image omitted]\n\nI'm using a up-to-date 11.0/bugfixes branch; maybe try with a recent nightly build (or wait for next release).\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798164547, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22814#issuecomment-3798164547", "createdAt": "2026-01-26T07:07:31Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "I have updated to 11.0.5 today, and the issue appeared to still be present initially.\n\nI then tried moving the items around (So left now on right and vice versa) and it worked?\nI now cannot reproduce the issue.\n\nOriginal response date: 2026-02-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3841451221, "author": "FMG-Jay", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22814#issuecomment-3841451221", "createdAt": "2026-02-03T13:50:26Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22814, "url": "https://github.com/glpi-project/glpi/issues/22814", "author": "FMG-Jay", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-23T15:43:22Z", "updatedAt": "2026-05-15T00:57:08Z", "closedAt": "2026-02-03T13:53:23Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Accessing /front/networkport.php shows warnings on Debug Mode", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen accessing /front/networkport.php page to list all Network Ports, it shows two PHP warnings for each Network Port added to GLPI:\n\nThis page does not seems to be publicly accessible to the end user, I had to access it manually because I wanted to list all Network Ports from all devices.\n\nAffected page:\n/front/networkport.php\n\nReproduction steps:\n1. Goes to /front/networkport.php page with at least one Network Port added to GLPI.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "drew.blair@peppermint.local", "text": "Same problem\n\n[Image omitted]\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3821684386, "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22911#issuecomment-3821684386", "createdAt": "2026-01-30T04:02:17Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "This page is not meant to be accessed; this is a virtual page that exists only because of our new v11 Legacy controller is not enough restrictive.\nThis issue already have been reported; this kind of page won't be fixed, it should disappear.\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3822158207, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22911#issuecomment-3822158207", "createdAt": "2026-01-30T06:51:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22911, "url": "https://github.com/glpi-project/glpi/issues/22911", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-29T22:57:26Z", "updatedAt": "2026-05-11T00:58:59Z", "closedAt": "2026-01-30T06:51:06Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "[Forms] User selection in native Forms displays Login instead of Full Name (GLPI 11)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHello,\n\nIn the new native Forms module of GLPI 11, there is a display issue when selecting User objects.\n\nEnvironment:\n\nGLPI version: 11.0.4\n\nPHP version: 8.4\n\nSteps to reproduce:\n\n[Image omitted]\n\nUse the native Forms feature (not the old plugin).\n\nAdd a question of type GLPI Object.\n\nSelect Administration > Users as the target object.\n\nFill out the form and select a user.\n\nView the submitted response/answer.\n\nExpected behavior: The answer should display the user's Full Name.\n\nActual behavior: The answer displays only the Login/Logon name (the name field in the database).\n\nAdditional information: This issue seems to be related to how the new native Forms module handles the getFriendlyName or the display parameters for the User class in the transition to GLPI 11. Given that I am using PHP 8.4, there might also be a compatibility nuance in how object strings are rendered.\n\nThank you for looking into this!", "priority": "medium", "type": "support", "createdByEmail": "riley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "riley.bennett@peppermint.local", "text": "Fix for this:\n\nfix_username.txt\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3822082022, "author": "husisusi", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22856#issuecomment-3822082022", "createdAt": "2026-01-30T06:24:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Please open a pull request with your change proposal\n\nOriginal response date: 2026-01-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3822227227, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22856#issuecomment-3822227227", "createdAt": "2026-01-30T07:13:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22856, "url": "https://github.com/glpi-project/glpi/issues/22856", "author": "husisusi", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-27T21:35:58Z", "updatedAt": "2026-05-11T00:58:53Z", "closedAt": "2026-01-30T13:08:02Z" } }, { "title": "GLPI dont ask for 2FA code everyday", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHello,\n\nI enabled two-factor authentication (2FA) on January 12, 2026, on version 11.0.4. The 2FA activation worked; I was able to enter the 2FA code on my favorite application. However, I have NEVER been asked for the 2FA code. After restarting my computer, either the following morning (Tuesday the 13th) or even today, I have never been prompted for the two-factor authentication code.\n\nMy account uses three profiles, and I forced 2FA on one of them.", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "What type of GLPI authentication are you using (Local DB, LDAP, etc)?\nDoes the prompt show if you log out of GLPI, clear the cookies for GLPI, and then try logging in again?\n\nOriginal response date: 2026-01-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3758456769, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22654#issuecomment-3758456769", "createdAt": "2026-01-16T06:54:48Z" } }, { "userEmail": "robin.bennett@peppermint.local", "text": "Hello,\n\nWe are using LDAP. If im using the button log out, when i reconnect GLPI ask me for 2FA code. Some people said to me that after 7 days, they need to put the 2FA code again when log in.\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3784167556, "author": "MathisLXE", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22654#issuecomment-3784167556", "createdAt": "2026-01-22T12:36:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22654, "url": "https://github.com/glpi-project/glpi/issues/22654", "author": "MathisLXE", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-14T07:35:09Z", "updatedAt": "2026-05-10T00:58:55Z", "closedAt": "2026-01-29T08:42:43Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI 11 - Error with some Tickets Datetime Null?", "detail": "Affected version:\n11.0.2\n\nIssue description:\nThis error appears when i click some tickets, not all.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "harper.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "harper.bennett@peppermint.local", "text": "Solved, in the migration some columns in glpi_documents_items in tickets with a linked file, the column date_creation was null\n\nOriginal response date: 2025-12-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3596626983, "author": "akuv-20", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22134#issuecomment-3596626983", "createdAt": "2025-12-01T13:44:34Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Solved, in the migration some columns in glpi_documents_items in tickets with a linked file, the column date_creation was null\n\nWe should still try to handle this case in our code, to prevent this kind of failure.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606508042, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22134#issuecomment-3606508042", "createdAt": "2025-12-03T11:56:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22134, "url": "https://github.com/glpi-project/glpi/issues/22134", "author": "akuv-20", "anonymizedAuthorEmail": "harper.bennett@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-01T12:49:48Z", "updatedAt": "2026-05-10T00:58:50Z", "closedAt": "2026-01-29T10:50:08Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Email notifications do not include attachments added after ticket creation", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.22\n\nIssue description:\nSince upgrading to GLPI 10.0.22, email notifications no longer include documents attached to ticket tasks, follow-ups, or solutions.\n\nOnly attachments added at ticket creation are included in email notifications.\nAny file added later is ignored and not transmitted by email.\n\nReproduction steps:\n1. Create a new ticket and attach a document at creation time\n2. Verify that the attachment is correctly included in the email notification\n3. Add a new attachment to the ticket afterward (via a task, follow-up, or solution)\n4. Trigger an email notification (update, follow-up, or solution notification)\n5. You'll still get the very first(s) file(s) attached but none of those added afterward", "priority": "medium", "type": "support", "createdByEmail": "logan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "kai.blair@peppermint.local", "text": "I confirm this problem on a Teclib GLPI instance, version 10.0.22.\n\nOriginal response date: 2026-01-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3804085263, "author": "DamienGombaultRecia", "anonymizedAuthorEmail": "kai.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22801#issuecomment-3804085263", "createdAt": "2026-01-27T09:28:03Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "This is the same as this:\n\nOriginal response date: 2026-01-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3810070382, "author": "oneill2john", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22801#issuecomment-3810070382", "createdAt": "2026-01-28T09:29:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22801, "url": "https://github.com/glpi-project/glpi/issues/22801", "author": "Loiseau2nuit", "anonymizedAuthorEmail": "logan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-22T15:13:26Z", "updatedAt": "2026-05-09T00:54:38Z", "closedAt": "2026-01-28T09:42:35Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "GLPI 11.0.4 - Attachments missing in Simplified (Post-only) ticket interface", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nHi,\nAfter migration from GLPI 10 to 11.0.4, file attachments are no longer available in simplified (post-only) interface.\n\nReproduction steps:\n1. Configure post-only to simplified view in the profile\n2. Change Superadmin to Post-Only\n3. Add new ticket\n4. File attachments not available", "priority": "medium", "type": "support", "createdByEmail": "finley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.bennett@peppermint.local", "text": "Hi Finley Bennett\nI created yesterday a ticket about same subject I think :\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3789108638, "author": "labiloute", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22803#issuecomment-3789108638", "createdAt": "2026-01-23T08:48:07Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Looks like a duplicate, yes\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3789163963, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22803#issuecomment-3789163963", "createdAt": "2026-01-23T09:04:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22803, "url": "https://github.com/glpi-project/glpi/issues/22803", "author": "werewolf004", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-23T07:54:14Z", "updatedAt": "2026-05-04T00:55:37Z", "closedAt": "2026-01-23T09:04:06Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "REST API: Missing operating system information in /assets/computer endpoint", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen querying the REST API endpoint:\n\n/assets/computer\n\nthe response does not include the operating system information (OS type and OS version).\n\nIn the GLPI web interface, OS details are visible in the computer’s information page, but I cannot find any documented way to retrieve these values through the API.\n\nI would like to know whether the OS information is accessible through another endpoint or relation, or if it is not currently exposed by the API.\n\nReproduction steps:\n1. Open a computer item in the GLPI web interface and note that OS information is displayed.\n\n2. Query the REST API endpoint /assets/computer.\n\n3. Observe that no OS-related fields are returned.", "priority": "medium", "type": "support", "createdByEmail": "avery.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.blair@peppermint.local", "text": "yep exactly,\nIt's possible to add this feature ?\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3790236479, "author": "greglg45", "anonymizedAuthorEmail": "skyler.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22220#issuecomment-3790236479", "createdAt": "2026-01-23T13:27:06Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "It will not be added to the \"/Assets/Computer\" or \"/Assets/Computer/{id}\" endpoints as it adds a lot of info that may not be important.\nIt will be coming in v2.2 as separate endpoints.\n\nIf you want to get more information, even requesting information from related schemas, in a single request, consider using the GraphQL API instead.\n\nOriginal response date: 2026-01-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3790295892, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22220#issuecomment-3790295892", "createdAt": "2026-01-23T13:43:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22220, "url": "https://github.com/glpi-project/glpi/issues/22220", "author": "Gbrl-BC", "anonymizedAuthorEmail": "avery.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-04T08:56:06Z", "updatedAt": "2026-05-04T00:55:34Z", "closedAt": "2026-01-23T13:43:10Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Follow-up templates created or migrated from GLPI 10 show empty content in GLPI 11", "detail": "Affected version:\n11.0.4\n\nIssue description:\nAfter upgrading GLPI from version 10.0.17 to 11.0.4, follow-up templates no longer work as expected.\n\nFollow-up templates are correctly displayed in the follow-up editor dropdown when adding a follow-up to a ticket.\nHowever, when a template is selected, no content is inserted into the follow-up field: the editor remains empty.\n\nThe template content is correctly saved and visible in Configuration → Templates → Follow-up templates, and the HTML content (generated by GLPI, e.g. , , ') looks valid.\nDespite this, the content is not injected into the ticket timeline when the template is applied.\n\n- This happens with:\n\n- templates migrated from GLPI 10.x\n\n- newly created templates in GLPI 11.0.4\n\nCreating a follow-up directly in a ticket and then saving it as a template works correctly, which suggests an issue with the follow-up template creation or injection logic in GLPI 11.\n\nAffected page:\n/front/itilfollowuptemplate.php\n\nReproduction steps:\n1. Go to Configuration → Templates → Follow-up templates.\n\n2. Create a new follow-up template and add some text content (plain text, no custom HTML).\n\n3. Save the follow-up template.\n\n4. Open any existing ticket (or create a new one).\n\n5. Click Add a follow-up.\n\n6. In the follow-up editor, select the previously created follow-up template from the template dropdown.\n\n7. Observe the follow-up editor content.", "priority": "medium", "type": "support", "createdByEmail": "finley.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce on current 11.0/bugfixes. Created 2 followup templates, and I can use both of them or switch with expected changes done.\nCheck if you reproduce without plugins, and also check for javascript errors in your browser console.\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3771417688, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22739#issuecomment-3771417688", "createdAt": "2026-01-20T07:27:50Z" } }, { "userEmail": "finley.blair@peppermint.local", "text": "I disabled and re-enabled the plugins, and it’s now working correctly. That’s very strange.\n\nThank you for your help — I’ll open other issues, as we’re encountering additional problems\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3774011749, "author": "blainvillem", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22739#issuecomment-3774011749", "createdAt": "2026-01-20T17:09:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22739, "url": "https://github.com/glpi-project/glpi/issues/22739", "author": "blainvillem", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-19T15:30:07Z", "updatedAt": "2026-05-02T00:52:56Z", "closedAt": "2026-01-21T06:39:01Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Software in global rule for search filter of computer missing", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen I try to realize the multi criteria example from I'm not able to choose \"Software\" in a added global rule in the Assets > Computers tab.\n\n[Image omitted]\n\nReproduction steps:\n1. Go to Assets > Computer\n2. Open the search filter menu\n3. Add a global rule\n4. Try to select Software", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I guess this is an autoloader issue. Composer's autoloader is case-sensitive so when it checks \"software_types\", is_a('software', CommonDBTM::class, true) resolves as false because the class is \"Software\" not \"software\". A manual check of class_exists('software') also resolves false.\n\nOriginal response date: 2026-01-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3715428842, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22581#issuecomment-3715428842", "createdAt": "2026-01-06T16:42:10Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I guess this is an autoloader issue. Composer's autoloader is case-sensitive so when it checks \"software_types\", is_a('software', CommonDBTM::class, true) resolves as false because the class is \"Software\" not \"software\". A manual check of class_exists('software') also resolves false.\n\nI confirm the issue on GLPI v11. This does not happen on v10, maybe because of the changes made on autoloading.\n\nOriginal response date: 2026-01-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3717680330, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22581#issuecomment-3717680330", "createdAt": "2026-01-07T07:40:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22581, "url": "https://github.com/glpi-project/glpi/issues/22581", "author": "AndiMb", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-06T16:10:20Z", "updatedAt": "2026-05-02T00:52:47Z", "closedAt": "2026-01-21T14:32:36Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Adding a user to a group without selecting a group throws an exception", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen going to Groups tab of an User and clicking on [Add] without selecting a group, it shows the friendly toast on the right bottom of the screen but also throws an exception on the main UI (even with Debug mode disabled), as can be seen below:\n\nAffected page:\n\nReproduction steps:\n1. Go to Administration > Users.\n2. Click on a user.\n3. Go to \"Groups\" tab.\n4. Click on [Add] without selecting a group.\n5. See error.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "lane.bennett@peppermint.local", "text": "In my site work perfect with group selected.\n\n[Image omitted]\n\nMaybe the detail is the not reload with empty fields, but it shows the alert, it´s a cosmetic bug.\n\n[Image omitted]\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3745603029, "author": "CYAsistemas", "anonymizedAuthorEmail": "lane.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22652#issuecomment-3745603029", "createdAt": "2026-01-13T17:42:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Yes, the issue is only when not selecting a group. Only the toast (the error message on the bottom right of the screen) should be shown to the end user.\n\nOriginal response date: 2026-01-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3745627158, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22652#issuecomment-3745627158", "createdAt": "2026-01-13T17:49:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22652, "url": "https://github.com/glpi-project/glpi/issues/22652", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-13T16:19:03Z", "updatedAt": "2026-05-02T00:52:44Z", "closedAt": "2026-01-21T14:42:53Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "Unable to assign Profile on \"Authorizations assignment rules\"", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen attempting to assign a Profile to a user through \"Authorizations assignment rules\", it silently fails. No error message is shown in the UI, and no SQL/PHP error and no historical information of the rule is updated, as can be seen below:\n\nAffected page:\n\nReproduction steps:\n1. Go to Administration > Rules > Authorizations assignment rules\n2. Select an existing rule (built-in or created by the user) or create a new one\n3. Select a Profile ('Active' dropdown with 'Yes' or 'No', it doesn't work)", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I confirm the issue\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3753195366, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22672#issuecomment-3753195366", "createdAt": "2026-01-15T07:12:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Seems to be fixed with\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3772740995, "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22672#issuecomment-3772740995", "createdAt": "2026-01-20T12:52:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22672, "url": "https://github.com/glpi-project/glpi/issues/22672", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-15T00:10:16Z", "updatedAt": "2026-05-01T00:58:58Z", "closedAt": "2026-01-20T12:52:03Z" } }, { "title": "\"Project Tasks\" missing from Problems", "detail": "Affected version:\n11.0.4\n\nIssue description:\nThe GLPI User Docs states on \"Problems\" that the \"Project Tasks\" tab is available for \"Problems\", but it seems missing:\n\n[Image omitted]\n\nAnalyzing the source code, I've found that only Tickets contains a direct link with Project Tasks.\n\nOther official pages with screenshots that do not show \"Project Tasks\" for problems:\n\nAffected page:\n\nReproduction steps:\n1. Go to Assistance > Problems\n2. Create a new problem\n3. Try to assign a project task into it (missing tab)", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It sounds like the documentation is wrong. There is nothing in GLPI for linking project tasks to changes or problems.\n\nOriginal response date: 2026-01-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3762010801, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22712#issuecomment-3762010801", "createdAt": "2026-01-16T22:14:47Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Reported on doc\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3766863673, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22712#issuecomment-3766863673", "createdAt": "2026-01-19T07:28:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22712, "url": "https://github.com/glpi-project/glpi/issues/22712", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "need user doc" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-16T21:55:41Z", "updatedAt": "2026-04-30T00:55:20Z", "closedAt": "2026-01-19T07:28:32Z" } }, { "title": "[Issue] 'Incorrect use of ' on NetworkPort", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHello,\nThe 'Name' field of an existing NetworkPort throws an issue in the Chrome console:\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. Go to Asset > Network Devices > Network Ports.\n2. Select a device.\n3. Go to 'Network ports' tab.\n4. Manually add a new port, assign a Name and save.\n5. Open browser console (F12) on 'Console' tab.\n6. Open the created port in your browser.\n7. See error.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I guess this is not really useful to open an issue for each problem of this kind; there will be hundreds.\nNote also those issues won't be fixed on legacy code (ie. all code not migrated yet to Twig templates).\n\nOriginal response date: 2026-01-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3760286421, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22707#issuecomment-3760286421", "createdAt": "2026-01-16T14:32:30Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "BTW, this is not that important because it does not cause any *real bug*. I close, there are chances this kind of issues will be fixed when we can work on global accessibility.\n\nOriginal response date: 2026-01-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3760297886, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22707#issuecomment-3760297886", "createdAt": "2026-01-16T14:35:22Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22707, "url": "https://github.com/glpi-project/glpi/issues/22707", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-16T14:26:42Z", "updatedAt": "2026-04-27T00:52:15Z", "closedAt": "2026-01-16T14:35:22Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "\"Enabled\" (Plugin list) is being translated on Setup > General page", "detail": "Affected version:\n11.0.4\n\nIssue description:\nSimilar to inside the \"Plugin list\" section, the \"State\" is being translated to the language that the user selected in GLPI:\n\n[Image omitted]\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Can i work on this Taylor Adler ?\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737530354, "author": "felipee-monteiro", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22608#issuecomment-3737530354", "createdAt": "2026-01-12T09:08:48Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Can i work on this Taylor Adler ?\n\nOK with me 👍\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3737532870, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22608#issuecomment-3737532870", "createdAt": "2026-01-12T09:09:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22608, "url": "https://github.com/glpi-project/glpi/issues/22608", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "felipee-monteiro", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-09T22:29:48Z", "updatedAt": "2026-04-25T00:46:28Z", "closedAt": "2026-01-14T08:24:28Z" }, "assignedTo": "jordan.blair@peppermint.local" }, { "title": "inventory_frequency config not loaded into $CFG_GLPI - always defaults to 24 hours", "detail": "Affected version:\n11.0.4\n\nIssue description:\nThe inventory_frequency configuration setting is ignored. Agents always receive the default value of 24 hours regardless of the configured value.\n\nRoot cause:\nIn src/Glpi/Inventory/Request.php, the code uses:\n\nHowever, the inventory_frequency config is stored in glpi_configs table with context='inventory'. GLPI only auto-loads configs with context='core' into $CFG_GLPI. Therefore $CFG_GLPI['inventory_frequency'] is always NULL and falls back to DEFAULT_FREQUENCY (24 hours).\n\nExpected behavior:\nThe agent should receive the configured inventory frequency value (e.g., 1 hour if set to 1).\n\nObserved behavior:\nThe agent always receives 24 hours (or multiples) regardless of the configuration set in the web interface.\n\nReproduction steps:\n1. Go to Administration > Inventory\n2. Set \"Inventory frequency (in hours)\" to 1\n3. Click Save\n4. Verify in database:\n\n Result shows value=1 (correctly saved)\n5. On a Windows client with GLPI Agent installed, force an inventory:\n\n6. Check agent next run time via or in agent logs\n7. Bug: Next run shows ~24 hours instead of ~1 hour\n\nProposed fix:\nReplace in src/Glpi/Inventory/Request.php all occurrences of:\n\nWith:\n\nThis affects the following methods:\n- getParams() (line 168)\n- prolog() (lines 200, 205)\n- contact() (line 313)\n- inventory() (line 403)\n\nRelated issues:\nA similar issue was fixed in 2022 for the GLPI Inventory Plugin:\n-\n-\n\nHowever, the core GLPI Request.php code was not updated to use the correct method to retrieve the configuration value from the 'inventory' context.", "priority": "medium", "type": "maintenance", "createdByEmail": "cameron.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This issue already exists for GLPI v10\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3673714955, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22438#issuecomment-3673714955", "createdAt": "2025-12-19T06:20:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "PR has been merged for 10.0/bf; will be merged into the 11.0/bf branch probably in January.\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3674206739, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22438#issuecomment-3674206739", "createdAt": "2025-12-19T09:09:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22438, "url": "https://github.com/glpi-project/glpi/issues/22438", "author": "vincenzopirozzideveloper", "anonymizedAuthorEmail": "cameron.adler@peppermint.local", "assignees": [], "labels": [ "inventory" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-18T20:27:44Z", "updatedAt": "2026-04-16T00:52:02Z", "closedAt": "2026-01-05T08:35:52Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Improve navigation on GLPI Rules", "detail": "Affected version:\n11.0.3\n\nIssue description:\nIn GLPI 10, when I checked my rules, I was able to move forward and backward between them without any issues.\n\n[Image omitted]\n\nHowever, in GLPI 11, this navigation feature between rules is no longer present.\n\n[Image omitted]\n\nIs it possible to bring this feature back?\n\nAffected page:\n/front/ruleticket.form.php\n\nReproduction steps:\n1 . Create two rules\n2 . Try go forward rule", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "bailey.bennett@peppermint.local", "text": "Hi team.\n\nAny feedback?\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3632106482, "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22213#issuecomment-3632106482", "createdAt": "2025-12-09T12:50:06Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi, no.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3632166122, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22213#issuecomment-3632166122", "createdAt": "2025-12-09T13:04:16Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22213, "url": "https://github.com/glpi-project/glpi/issues/22213", "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "good first issue", "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-03T18:41:53Z", "updatedAt": "2026-04-16T00:51:20Z", "closedAt": "2026-01-05T10:14:28Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 11.0.4 – Contract “Ticket” tab displays wrong ID (shows contract ID instead of ticket ID)", "detail": "Issue description:\n[Image omitted]\n[Image omitted]\n\nAffected version:\n11.04\n\nIssue description:\nWhen viewing a contract in GLPI 11.0.4, the “Cases” tab shows a list of related tickets.\nHowever, the ID column displays the wrong value:\n\nInstead of showing the ticket ID (tickets.id),\n\nIt shows the contract ID (or the ID of the relation table glpi_tickets_contracts).\n\nDespite this incorrect display, the relation is correctly stored in the database.\n\nThis results in misleading information on the contract view, making it appear as if the contract ID were the ticket ID.\n\nReproduction steps:\nCreate or open an existing contract (example: Contract ID = 11).\n\nOpen any ticket (example: Ticket ID = 142).\n\nIn the ticket, go to the Contracts section and link the ticket to the contract.\n\nNow return to the contract and open the Cases tab.\n\nExpected Result\n\nThe table in Contract → Cases should list:\n\nID = the real ticket ID (e.g. 142)\n\nThe correct title, date, entity, etc.\n\nActual Result\n\nThe table shows:\n\nID = 11 (the contract ID),\n\nInstead of ID = 142 (the ticket ID).\n\nTitle, dates, and other fields are correct, but the ID column is wrong.\n\nThis happens for every ticket associated with a contract.\n\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I confirm the issue.\n\nThere is also a Twig error when in debug mode:\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3616895338, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22248#issuecomment-3616895338", "createdAt": "2025-12-05T13:16:13Z" } }, { "userEmail": "casey.bennett@peppermint.local", "text": "Thanks for confirming the issue and adding it to the 11.0.5 milestone.\n\nWhile reviewing the behavior from the browser side (Inspect → DOM), I noticed one additional detail that may help with the fix:\n\nThe backend is correctly loading the related tickets_id (verified through the database).\nHowever, in the Contracts → Tickets tab, the rendered ID in the datatable corresponds to the contracts_id (or the row index), not the tickets_id.\nThe wrong value is already present in the element before any JavaScript processing, which suggests that the mismatch happens during Twig rendering or datatable column mapping.\n\nJust sharing this in case it's useful while working on the correction.\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3617246303, "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22248#issuecomment-3617246303", "createdAt": "2025-12-05T14:53:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22248, "url": "https://github.com/glpi-project/glpi/issues/22248", "author": "cdbaq", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-04T22:38:03Z", "updatedAt": "2026-04-16T00:51:17Z", "closedAt": "2026-01-05T10:16:12Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Problem migrating form from GLPI 10.0.18 to GLPI 11", "detail": "Affected version:\n10.0.18\n\nIssue description:\nbug for migration form in glpi 11\nsudo -u www-data php bin/console migration:formcreator_plugin_to_core\nPHP Warning: Module \"snmp\" is already loaded in Unknown on line 0\n[==>-------------------------] 10%\nImport des sections...\nLa migration à échouée\nx Une erreur est survenue\nx Des erreurs sont survenues, la migration est annulée, aucun changement.\n\nmy log php [2025-11-06 11:06:21] glpi.ERROR: * Syntax error\n Backtrace :\n ...machine/safe/lib/Exceptions/JsonException.php:9\n .../thecodingmachine/safe/lib/special_cases.php:39 Safe\\Exceptions\\JsonException::createFromPhpError()\n ...QuestionType/AbstractQuestionTypeActors.php:190 Safe\\json_decode()\n ./src/Glpi/Form/Migration/FormMigration.php:668 Glpi\\Form\\QuestionType\\AbstractQuestionTypeActors->convertDefaultValue()\n ./src/Glpi/Form/Migration/FormMigration.php:409 Glpi\\Form\\Migration\\FormMigration->processMigrationOfQuestions()\n .../Glpi/Migration/AbstractPluginMigration.php:139 Glpi\\Form\\Migration\\FormMigration->processMigration()\n ...Migration/AbstractPluginMigrationCommand.php:88 Glpi\\Migration\\AbstractPluginMigration->execute()\n ./vendor/symfony/console/Command/Command.php:326 Glpi\\Console\\Migration\\AbstractPluginMigrationCommand->execute()\n ./vendor/symfony/console/Application.php:1088 Symfony\\Component\\Console\\Command\\Command->run()\n ./src/Glpi/Console/Application.php:330 Symfony\\Component\\Console\\Application->doRunCommand()\n ./vendor/symfony/console/Application.php:324 Glpi\\Console\\Application->doRunCommand()\n ./vendor/symfony/console/Application.php:175 Symfony\\Component\\Console\\Application->doRun()\n ./bin/console:144 Symfony\\Component\\Console\\Application->run()", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Avery Blair\n\nThis likely mean there is some unexpected data that we can't parse properly.\n\nCould you run the following SQL query?\n\nOriginal response date: 2025-12-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3627074557, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21832#issuecomment-3627074557", "createdAt": "2025-12-08T13:58:50Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I'll close as the issue seems stale, feel free to re-open if needed.\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3674175301, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21832#issuecomment-3674175301", "createdAt": "2025-12-19T08:58:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21832, "url": "https://github.com/glpi-project/glpi/issues/21832", "author": "Izzaya0212", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-06T11:09:01Z", "updatedAt": "2026-03-30T00:45:29Z", "closedAt": "2025-12-19T08:58:46Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "MySQL query error", "detail": "Affected version:\n11.0.1 (from pkg on FreeBSD)\n\nIssue description:\nOnce in a while (I have no info on frequency) the cron job spits out this error message:\n\nReproduction steps:\nNo info", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with latest version, and no plugins.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3610676400, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22217#issuecomment-3610676400", "createdAt": "2025-12-04T07:29:43Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "No feedback, I close\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3668792640, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22217#issuecomment-3668792640", "createdAt": "2025-12-18T07:31:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22217, "url": "https://github.com/glpi-project/glpi/issues/22217", "author": "pboosten", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-04T07:28:23Z", "updatedAt": "2026-03-29T00:46:05Z", "closedAt": "2025-12-18T07:31:31Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Associated item missing for tickets created by users with a self-service profile.", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHi\n\nIn GLPI 11.0.2 Associated Item (computer, printer and software) are unavailable for user member of Self-Service Profile.\n\nThe associated dropdown list stay blanc\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "avery.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you check if #21983 fixes your issue?\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607696948, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22040#issuecomment-3607696948", "createdAt": "2025-12-03T16:23:33Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "11.0.1 and 11.0.2 are outdated. No feedback, I close.\n\nOriginal response date: 2025-12-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3668797570, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22040#issuecomment-3668797570", "createdAt": "2025-12-18T07:33:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22040, "url": "https://github.com/glpi-project/glpi/issues/22040", "author": "tvanparys", "anonymizedAuthorEmail": "avery.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-24T10:17:58Z", "updatedAt": "2026-03-29T00:46:03Z", "closedAt": "2025-12-18T07:33:12Z" } }, { "title": "It is not possible to create an Entity.", "detail": "Affected version:\n11.0.4\n\nIssue description:\nIt is not possible to create an Entity; the option is not appearing.\n\n[Image omitted]\n\nAffected page:\nfront/entity.php", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nPlease provide requested information.\n\nOriginal response date: 2025-12-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3630884733, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22289#issuecomment-3630884733", "createdAt": "2025-12-09T08:01:14Z" } }, { "userEmail": "kendall.blair@peppermint.local", "text": "Reslove:\nGive full permissions to folder \"core\" in /var/www/glpi/files/_cache/11.0.4-1d4fbe9a-production/\n\nOriginal response date: 2025-12-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3646829808, "author": "Alabaster12", "anonymizedAuthorEmail": "kendall.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22289#issuecomment-3646829808", "createdAt": "2025-12-12T14:57:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22289, "url": "https://github.com/glpi-project/glpi/issues/22289", "author": "ghost", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-08T19:18:54Z", "updatedAt": "2026-03-26T00:43:16Z", "closedAt": "2025-12-15T06:03:56Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "v11.0.4 Automatic inventory is not working due to a dictionary rule about manufacturers", "detail": "Affected version:\n11.0.4\n\nIssue description:\nAutomatic inventory is not working due to a dictionary rule about manufacturers with the follow rule\n\n[Image omitted]\n\nAttache\n\n[Image omitted]\n\nd is a screenshot of the glpi-agent.log file.\n\nReproduction steps:\nCreate a rule in the dictionary for manufacturers as the screenshoot with the regular expression.\nChange an information for example the manufacturer of the computer , delete the lock\nthen\nrun force an inventory on then agent glpi.\nlast contact is good, verify the manufacter of the computer .\ntthe manufacurer doesn't change.", "priority": "medium", "type": "maintenance", "createdByEmail": "parker.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I'm able to reproduce, but only when the regular expression ha nos result. For example, if the manufacturer is -Any and the regular expression is /(.*)-/.\nA simple workaround is to fix the regular expression to prevent empty results; /(.+)-/ here fix the issue.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3635640628, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22305#issuecomment-3635640628", "createdAt": "2025-12-10T06:47:32Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed by #22314.\n\nOriginal response date: 2025-12-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3635857145, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22305#issuecomment-3635857145", "createdAt": "2025-12-10T08:04:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22305, "url": "https://github.com/glpi-project/glpi/issues/22305", "author": "bcnan", "anonymizedAuthorEmail": "parker.adler@peppermint.local", "assignees": [ { "sourceLogin": "trasher", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "inventory" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-09T12:10:42Z", "updatedAt": "2026-03-21T00:37:16Z", "closedAt": "2025-12-10T08:04:32Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Allow over-quota \"No\" can be bypassed", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHello\nIf the setting for \"Allow over-quota\" for a licence is set to \"No\", we can't assign new items to it from the licence.\n\n[Image omitted]\n\n[Image omitted]\n\nBut we can assign a new item from the item directly, exemple with a user :\n\n[Image omitted]\n\n[Image omitted]\n\nAnd the licence is over assigned\n\n[Image omitted]\n\nReproduction steps:\n1. Create a licence with with over quota disable\n2. Assign items to the licence with the maximum quota allowed\n3. Assign this licence from the items directly\n4. Quota is bypassed", "priority": "medium", "type": "support", "createdByEmail": "taylor.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with latest release.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611944005, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22231#issuecomment-3611944005", "createdAt": "2025-12-04T12:13:04Z" } }, { "userEmail": "taylor.bennett@peppermint.local", "text": "I just updated to 11.0.4 (i use the docker version), and nothing changed.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612021681, "author": "Izanagi52", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22231#issuecomment-3612021681", "createdAt": "2025-12-04T12:31:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22231, "url": "https://github.com/glpi-project/glpi/issues/22231", "author": "Izanagi52", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-04T11:25:06Z", "updatedAt": "2026-03-21T00:37:13Z", "closedAt": "2025-12-09T15:57:56Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "RTL dashoboards alignment", "detail": "Issue description:\ngood now.\nCan you force the numbers to stay aligned to the left regardless of RTL or LTR, or make the icons flip to the left when using RTL\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n[Image omitted]\n[Image omitted]\n[Image omitted]\n\n _Originally posted by Drew Bennett in #21559_", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Drew Bennett there is an incoming PR (#21573) that fixes this case and a few other ones I saw on the dashboard pages.\n\nIf you see RTL specific issues, please report them in a new ticket so we can try to fix. It's hard for me to use GLPI with a RTL language :)\n\nOriginal response date: 2025-10-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3426515821, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21567#issuecomment-3426515821", "createdAt": "2025-10-21T13:01:43Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Fix is not the correct one, it will be reverted\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3450171642, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21567#issuecomment-3450171642", "createdAt": "2025-10-27T09:02:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21567, "url": "https://github.com/glpi-project/glpi/issues/21567", "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-21T08:41:35Z", "updatedAt": "2026-03-21T00:37:04Z", "closedAt": "2025-12-10T12:51:13Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "[API/UI] Discrepancy: fields exposed in Model Asset Definition API response but missing in UI", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen querying a Model object via the API, the JSON response includes several fields related to physical properties and Datacenter management (weight, required_units, depth, power_connections, power_consumption, is_half_rack). However, when editing the same Model object in the GLPI Web UI, these fields are nowhere to be found (neither in the Main tab nor in a specific Physical/Datacenter tab).\nI don't know if it's a bug or not, but it would be interesting to see (optionally or not) at least the power consumption section for CSR topics.\n\nEnvironment details:\nGo to Setup > Dropdowns (or the specific plugin menu).\nOpen a Model form for the concerned ItemType (e.g., a specific Generic Object Model).\nObserve that fields like \"Weight\", \"Depth\", \"Power consumption\" are not visible in the form.\nPerform a GET request on the API for this specific ID.\nGET /apirest.php/[ItemType]Model/[ID]\n\n{\n \"id\": 4,\n \"name\": \"VMware vSphere / ESXi\",\n \"weight\": 0,\n \"required_units\": 1,\n \"depth\": 1,\n \"power_connections\": 0,\n \"power_consumption\": 0,\n \"is_half_rack\": false\n ...\n}", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It only shows in the UI when the \"Racks\" capacity is enabled, but the fields still exist in the DB so it shows in the legacy API. The legacy API is not designed to be more abstract/user friendly and I don't think it is valid to change anything in it.\n\nThe new API doesn't hide the fields either, but it is at least valid to adapt the new API to work like that.\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3617186425, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22269#issuecomment-3617186425", "createdAt": "2025-12-05T14:37:28Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "I wasn't aware of that trick regarding the rack. Thanks for the tip, and I understand the logic now. It does create a lot of fields, but it could address a CSR need.\n\nOriginal response date: 2025-12-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3617389099, "author": "Yann843", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22269#issuecomment-3617389099", "createdAt": "2025-12-05T15:30:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22269, "url": "https://github.com/glpi-project/glpi/issues/22269", "author": "Yann843", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [], "labels": [ "api" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-05T14:30:34Z", "updatedAt": "2026-03-19T00:41:23Z", "closedAt": "2025-12-08T05:54:29Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Problem selecting knowledge base items in tickets.", "detail": "Affected version:\n11.02\n\nIssue description:\nProblem selecting knowledge base items in tickets. We have items in the knowledge base but we can't assign them to tickets.\nIn previous versions of the application this option works fine.\n\nReproduction steps:\n1. Go to any ticket.\n2. In the lateral panel go to option \"Knowledge Base\"\n3. No options appear to choose from in the drop-down menu. (In old versions works fine with many options)", "priority": "medium", "type": "support", "createdByEmail": "dakota.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue.\n\nPlease provide the requested log output information (and check the browser console for errors)\n\nOriginal response date: 2025-11-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3587056245, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22098#issuecomment-3587056245", "createdAt": "2025-11-27T19:04:22Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Double check users rights, and try without plugins.\n\nOriginal response date: 2025-11-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3588105560, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22098#issuecomment-3588105560", "createdAt": "2025-11-28T06:44:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22098, "url": "https://github.com/glpi-project/glpi/issues/22098", "author": "keguapo-cell", "anonymizedAuthorEmail": "dakota.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-27T18:25:53Z", "updatedAt": "2026-03-19T00:40:56Z", "closedAt": "2025-12-08T12:50:52Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Glpi 11.0.3 shows 'This version is UNSTABLE' in SuperAdmin -> About", "detail": "Issue description:\nHello,\n\nI was in the process of manual installation of GLPI on Alma Linux 8.10 with PHP 8.2, MYSQL 8.0, Apache 2.4 using latest 11.0.3 tgz package from Github\n\nHowever, post successful installation following is shown under SuperAdmin->About tab i.e :\n\n This version is UNSTABLE and some SECURITY FIXES may not be included.\n\nFollowing is the screenshot for the same :\n\n[Image omitted]\n\nIs 11.0.3 stable or is it some bug with 11.0.3?.\n\nCould you please replicate?.\n\nRegards.", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nWe are right now publishing a new release to fix this.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611048652, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22225#issuecomment-3611048652", "createdAt": "2025-12-04T09:20:04Z" } }, { "userEmail": "jesse.bennett@peppermint.local", "text": "Hello Skyler Adler ,\n\nThanks for the quick reply. Shall wait for the release.\n\nRegards.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3611053272, "author": "prbt2016", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22225#issuecomment-3611053272", "createdAt": "2025-12-04T09:21:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22225, "url": "https://github.com/glpi-project/glpi/issues/22225", "author": "prbt2016", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-12-04T09:19:30Z", "updatedAt": "2026-03-15T00:44:51Z", "closedAt": "2025-12-04T09:19:56Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Page refreshing", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWhen I select certain options on the ticket creation screen, the screen keeps refreshing.\n\nReproduction steps:\n1 go to ticket creation screen\n2 make changes on fields\n\nAdditional context:", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nThis is not the best we can do from the UX point of view, but this is how GLPI has always worked. It permits to refresh the form according to the tickets template configuration.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612172494, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22234#issuecomment-3612172494", "createdAt": "2025-12-04T13:07:48Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Not a bug. This has been how GLPI has handled templates and some other things which can change the form options for as long as I remember.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3612172910, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22234#issuecomment-3612172910", "createdAt": "2025-12-04T13:07:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22234, "url": "https://github.com/glpi-project/glpi/issues/22234", "author": "RuanBojarski", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-12-04T13:05:59Z", "updatedAt": "2026-03-15T00:44:48Z", "closedAt": "2025-12-04T13:07:48Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI 11 - Can't select default ticket template for simplified interface profiles", "detail": "Affected version:\n11.0\n\nIssue description:\nHi,\n\nWhen you want to select the default ticket template for a profile with simplified interface, the dropdown can't load the list (/ajax/getDropdownValue.php give error 500, tied to a SQL request to an inexisting field \"SELECT DISTINCT glpi_tickettemplates.* FROM glpi_tickettemplates WHERE glpi_tickettemplates.entity = '0' AND (true) ORDER BY glpi_tickettemplates.entities_id, glpi_tickettemplates.name LIMIT 100\")\n\nLooking at other issues, I can understand that this setting doesn't apply anymore in GLPI 11 as simplified interface users don't have access to the regular ticket creation interface.\n\nSo I guess that this setting has to be removed from the interface ?\n\n[Image omitted]\n\nAffected page:\n/front/profile.form.php?id=1", "priority": "medium", "type": "support", "createdByEmail": "jordan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "quinn.bennett@peppermint.local", "text": "The same here.\nIn a installation upgraded from 10.0.20 to 11.0, where there was already a template selected, it is working after the upgrade.\nBut for a new installation, where the profile didn't have a default template, it is not possible to select one.\n\nOriginal response date: 2025-10-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3393717089, "author": "raultak", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21378#issuecomment-3393717089", "createdAt": "2025-10-11T22:54:39Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "To be clear, this dropdown must be removed as Simplified Interface users don't have access to regular ticket creation form. The template must be chosen in the form logic.\n\nI reported this issue so the team can remove this choice and investigate the incorrect sql query that should never have been processed\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396414492, "author": "CoRpO", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21378#issuecomment-3396414492", "createdAt": "2025-10-13T08:32:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21378, "url": "https://github.com/glpi-project/glpi/issues/21378", "author": "CoRpO", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-09T08:31:34Z", "updatedAt": "2026-03-15T00:44:45Z", "closedAt": "2025-12-04T14:40:18Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "GLPI 11 - Can't update ticket", "detail": "Affected version:\n11.0.2\n\nIssue description:\nHello,\n\nI can't update new ticket which are created from new dashboard post-only.\nI have theses errors :\n\n[2025-12-02 10:37:17] glpi.WARNING: * Warning: Undefined array key \"entities_id\" at CommonITILObject.php line 8290\n Backtrace :\n ./src/CommonITILObject.php:8290\n ./src/CommonITILObject.php:2346 CommonITILObject->getITILTemplateFromInput()\n ./front/ticket.form.php:89 CommonITILObject->enforceReadonlyFields()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\n[2025-12-02 10:37:17] glpi.WARNING: * Warning: Array to string conversion at DBmysql.php line 1268\n Backtrace :\n ./src/DBmysql.php:1268\n ./src/DBmysql.php:1410 DBmysql::quoteValue()\n ./src/DBmysql.php:1445 DBmysql->buildUpdate()\n ./src/CommonDBTM.php:735 DBmysql->update()\n ./src/CommonDBTM.php:1762 CommonDBTM->updateInDB()\n ./front/ticket.form.php:90 CommonDBTM->update()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()\n\n[2025-12-02 10:37:17] glpi.CRITICAL: * Uncaught PHP Exception RuntimeException: \"MySQL query error: Incorrect integer value: 'Array' for column dbbglpi.glpi_tickets.items_id at row 1 (1366) in SQL query \"UPDATE glpi_tickets SET itemtype = '0', items_id = 'Array', users_id_lastupdater = '636', date_mod = '2025-12-02 10:37:17' WHERE id = '15221'\".\" at DBmysql.php line 371\n Backtrace :\n ./src/DBmysql.php:371\n ./src/DBmysql.php:1446 DBmysql->doQuery()\n ./src/CommonDBTM.php:735 DBmysql->update()\n ./src/CommonDBTM.php:1762 CommonDBTM->updateInDB()\n ./front/ticket.form.php:90 CommonDBTM->update()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "dakota.bennett@peppermint.local", "text": "If i remove this item form from ticket, i can update\n\n[Image omitted]\n\nStrange ?\n\nOriginal response date: 2025-12-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3601268990, "author": "kevin-m87", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22168#issuecomment-3601268990", "createdAt": "2025-12-02T10:16:31Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "Fixed by :\n\nALTER TABLE glpi_tickets\n -> DROP COLUMN items_id;\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3605675641, "author": "kevin-m87", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22168#issuecomment-3605675641", "createdAt": "2025-12-03T08:37:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22168, "url": "https://github.com/glpi-project/glpi/issues/22168", "author": "kevin-m87", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-02T09:41:41Z", "updatedAt": "2026-03-14T00:37:23Z", "closedAt": "2025-12-03T08:37:57Z" } }, { "title": "GLPI 11.0.3: About screen", "detail": "Affected version:\n11.0.3\n\nIssue description:\nWe have upgraded to GLPI version 11.0.3 and now seem to have this in our About screen?\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "kendall.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Indeed, this should not appear :/\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606692515, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22196#issuecomment-3606692515", "createdAt": "2025-12-03T12:46:05Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed in #22199\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3606987886, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22196#issuecomment-3606987886", "createdAt": "2025-12-03T13:56:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22196, "url": "https://github.com/glpi-project/glpi/issues/22196", "author": "perplexityjeff", "anonymizedAuthorEmail": "kendall.adler@peppermint.local", "assignees": [ { "sourceLogin": "cedric-anne", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-03T12:39:10Z", "updatedAt": "2026-03-14T00:37:02Z", "closedAt": "2025-12-03T13:56:36Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "GLPI 11 : tinyMCE /richtext editor not enable", "detail": "Affected version:\n11.0.3\n\nIssue description:\nrich text editor is not available but enable in configuration\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide browser javascript logs, there is certainly something that failed.\n\nDisabling WYSIWYG editor is no longer possible since v10 (as far as I remember).\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607378555, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22206#issuecomment-3607378555", "createdAt": "2025-12-03T15:21:17Z" } }, { "userEmail": "rowan.bennett@peppermint.local", "text": "Rigth is Single Sign-on plugin issue\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607422433, "author": "tomamplius", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22206#issuecomment-3607422433", "createdAt": "2025-12-03T15:30:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22206, "url": "https://github.com/glpi-project/glpi/issues/22206", "author": "tomamplius", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-03T15:17:05Z", "updatedAt": "2026-03-14T00:36:47Z", "closedAt": "2025-12-03T15:30:53Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Image not show", "detail": "Affected version:\n11.0.3\n\nIssue description:\nSince migration from 10.0.20 to 11.0.2 image are not show in tickets\n\n[Image omitted]\n\nAlternative text is display with link to the image but link not work (see bellow)\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "rowan.bennett@peppermint.local", "text": "duplicate with?\nIt's not a duplicate of the ticket\nAll plugin disable issue is always present\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607818945, "author": "tomamplius", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22205#issuecomment-3607818945", "createdAt": "2025-12-03T16:52:05Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Search in issues, it's been reported several times. I do not have time to search for you.\n\nOriginal response date: 2025-12-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3607975298, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22205#issuecomment-3607975298", "createdAt": "2025-12-03T17:27:23Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22205, "url": "https://github.com/glpi-project/glpi/issues/22205", "author": "tomamplius", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-12-03T15:09:24Z", "updatedAt": "2026-03-14T00:36:35Z", "closedAt": "2025-12-03T15:21:46Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Editing a response with hold status does not change the ticket status.", "detail": "Affected version:\n11.0.2\n\nIssue description:\nIf I try to edit a response to a ticket and check the “pending” box, the ticket status does not change.\n\nReproduction steps:\nAdd a response to a ticket.\nEdit the ticket.\nCheck the pending button.\nSave.\nNo error and status unchanged.", "priority": "medium", "type": "support", "createdByEmail": "quinn.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI cannot reproduce on the current nightly build. Could you try to reproduce (on a test server) with and provided detailed steps to reproduce if the issue persist?\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558601239, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21927#issuecomment-3558601239", "createdAt": "2025-11-20T15:14:52Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Also, please try first to reproduce with no active plugins. You can suspend their execution from the plugins/marketplace page:\n\n[Image omitted]\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558607536, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21927#issuecomment-3558607536", "createdAt": "2025-11-20T15:15:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21927, "url": "https://github.com/glpi-project/glpi/issues/21927", "author": "tguichard25", "anonymizedAuthorEmail": "quinn.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-13T13:17:05Z", "updatedAt": "2026-03-13T00:38:28Z", "closedAt": "2025-12-02T08:34:52Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Change Impact don't change priority ticket", "detail": "Affected version:\n10.0.2\n\nIssue description:\nWhen i change the Impact on a ticket it doesn't change the priority. Only Urgency trigger the priority change\n\nReproduction steps:\n1. Change impact to have another urgency x impact value\n2. Save\n3. No change in priority", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.bennett@peppermint.local", "text": "I've added the proposed fix (src/ticket.php) and it's work but we have the same problem when a ticket is created, the priority don't change, do you want opening a new ticket or add this behavior to the actual ticket ?\n\nOriginal response date: 2025-11-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3575583554, "author": "PowerMike-BZH", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21946#issuecomment-3575583554", "createdAt": "2025-11-25T13:12:48Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Hello Jamie Bennett this a work in progress, the complete fix will handle both frontend and backend priority calculation / update original issue. Stay tuned ;)\n\nOriginal response date: 2025-11-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3575966691, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21946#issuecomment-3575966691", "createdAt": "2025-11-25T14:38:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21946, "url": "https://github.com/glpi-project/glpi/issues/21946", "author": "PowerMike-BZH", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-14T15:45:37Z", "updatedAt": "2026-03-08T00:39:35Z", "closedAt": "2025-11-27T11:15:03Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "SMTP+OAUTH Email Notifications stopped working (Authorization failed with error: Cannot access offset of type string on string)", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWe have been building out a GLPI instance since last month(October 1st) and we are currently on v11.0.2. Last week on\nNovember 6th our email notifications suddenly stopped working (this had been working properly since first install). The day\nbefore we were testing the recipients for certain notifications for tickets. Everything was working great when we wrapped up\nfor the day. The next morning we noticed that we were no longer getting email notifications.\n\nEdit: This issue originally occurred on v11.0.1\n\n[Image omitted]\n_--successful email notification_\n\nThis is the php-error log entry that we were getting:\n\nThinking that I needed to re-establish the login to our M365 environment, I did the following:\n- I cleared out the Email Notification Configuration settings and disabled the email notification setting\n- I ran the clear:cache console command\n- I ran restart apache2\n- I logged out and logged back in\n- I enabled email notifications\n- I re-entered all the settings and the values for the client ID, Tenant ID, and Client Secret. This did not work.\n-- (am unsure if I received an error here or not, probably did and as the php-error logs are nearly the same)\n\nNext I trashed the M365 app and made a new one. Then ran through all of the above steps again hit save and instead of being redirected to the Microsoft login page I get an error.\n\n[Image omitted]\n\n\"Error Authorization failed with error: Cannot access offset of type string on string\"\n\nThis is the current php-error log entry that we are getting(slightly different, but still failing on the Azure.php file):\n\nAffected page:\nfront/notificationmailingsetting.form.php", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "avery.blair@peppermint.local", "text": "I was able to run a test on my home lab instance and successfully connected the email notifications to the m365 app, therefore ruling out it being a MS issue (surprising, I know).\n\nWhile inspecting and comparing the html between the 2 instances I noticed that the main instance is missing the \"Force OAuth Authentication Refresh\" option as well as missing the dropdown for SMTP+TLS.\n\n[Image omitted]\n\nDoes this alter what the backend does with the page/authentication request when saved?\nHow can I fix this issue?\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3534143315, "author": "romvek", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21884#issuecomment-3534143315", "createdAt": "2025-11-14T18:56:47Z" } }, { "userEmail": "avery.blair@peppermint.local", "text": "The html code portion for the \"Force OAuth Authentication Refresh\" option was missing. What I think to be the page responsible for the html code, \"mailing_setting.html.twig\" was not any different from the source code.\n\nWas not able to fix this issue.\n\nWe exported our forms and ITIL categories and built a new image with a fresh install. Everything works as expected now.\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3559052214, "author": "romvek", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21884#issuecomment-3559052214", "createdAt": "2025-11-20T16:47:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21884, "url": "https://github.com/glpi-project/glpi/issues/21884", "author": "romvek", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-11-11T20:27:13Z", "updatedAt": "2026-03-02T00:38:46Z", "closedAt": "2025-11-21T05:34:36Z" } }, { "title": "npm audit failed (10.0/bugfixes)", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Requires to be solved.\n\nOriginal response date: 2025-11-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3540968327, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21951#issuecomment-3540968327", "createdAt": "2025-11-17T10:17:04Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed in #22016.\n\nOriginal response date: 2025-11-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3558445425, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21951#issuecomment-3558445425", "createdAt": "2025-11-20T14:47:24Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21951, "url": "https://github.com/glpi-project/glpi/issues/21951", "author": "github-actions[bot]", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-17T10:02:33Z", "updatedAt": "2026-03-01T00:44:07Z", "closedAt": "2025-11-20T14:47:24Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Licence TAB shows software not licence", "detail": "Affected version:\n11.0.2\n\nIssue description:\nAfter updating, I'm having trouble with the license list. When I go to the Licenses tab, it shows a list of software as a group to which licenses are attached, and only then can I access the licenses assigned to the software. I should be able to see the license names. Previously, it showed a list of all licenses, and I could sort by software.Now I see a list, for example, of Microsoft Office 40x, instead of license names.\n\n[Image omitted]\n\nClicking on the license (program name) takes me to the Assets>software, and then I see the Licenses subtab. Then, when I click Licenses, I see all the licenses assigned to the program.\n\n[Image omitted]\nbut in Management> licence i should see all subtabs licence from all software Assets>software (name) >licence.\n\nJust list of licences in firm", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Make sure you have the \"Name\" field in your displayed columns list. You may also reset the global columns display for this itemtype to the defaults under Setup > General > Search result display tab.\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3532860820, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21939#issuecomment-3532860820", "createdAt": "2025-11-14T13:39:14Z" } }, { "userEmail": "dakota.bennett@peppermint.local", "text": "of course u right ...\n\nOriginal response date: 2025-11-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3532922357, "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21939#issuecomment-3532922357", "createdAt": "2025-11-14T13:55:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21939, "url": "https://github.com/glpi-project/glpi/issues/21939", "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-14T13:32:02Z", "updatedAt": "2026-02-23T00:39:52Z", "closedAt": "2025-11-14T13:55:32Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Tickets that have been solved are shown in the \"Your Planning\" section", "detail": "Affected version:\n11\n\nIssue description:\nSince version 11 of GLPI, my dashboard shows solved and closed tickets. These tickets have a planned date:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Related to #21867\n\nI don't know if it was intentional, but the planning widget on the homepage uses the same active filters as Assistance > Planning. If you have \"Done\" events showing here, they will also show on the homepage.\n\nOriginal response date: 2025-11-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3516423615, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21879#issuecomment-3516423615", "createdAt": "2025-11-11T11:29:16Z" } }, { "userEmail": "jamie.bennett@peppermint.local", "text": "Thank you! As you described, it was just the wrong setting.\n\nOriginal response date: 2025-11-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3516517023, "author": "wgondzik", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21879#issuecomment-3516517023", "createdAt": "2025-11-11T11:53:39Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21879, "url": "https://github.com/glpi-project/glpi/issues/21879", "author": "wgondzik", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [ "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-11T10:39:06Z", "updatedAt": "2026-02-20T00:37:10Z", "closedAt": "2025-11-11T11:53:39Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Update User Photo - Error", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWhen I Update the user profile photo:\n\n[Image omitted]\n\nLogs:\n\nUser ID: 171 tried to execute an invalid request on /front/document.send.php?file=_pictures%2Fc3%2F171_682f5acf044c3_min.png.\n\n Backtrace :\n ./front/document.send.php:117\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:197 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:70 Symfony\\Component\\HttpKernel\\Kernel->handle()", "priority": "medium", "type": "support", "createdByEmail": "kendall.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue.\nDoes the picture exist in files/_pictures/c3 and are the file permissions on it correct for the web server to read it?\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3499941666, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21841#issuecomment-3499941666", "createdAt": "2025-11-07T00:22:20Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "I do update to 11.0.2 and resolve...\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3499985375, "author": "alfredudu", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21841#issuecomment-3499985375", "createdAt": "2025-11-07T00:42:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21841, "url": "https://github.com/glpi-project/glpi/issues/21841", "author": "alfredudu", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-06T16:58:02Z", "updatedAt": "2026-02-19T00:40:42Z", "closedAt": "2025-11-07T00:42:47Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "When recursion is disabled for the same entity, users can still see all assets belonging to that entity under My Assets → All on their personal page.", "detail": "Affected version:\n11.0.1\n\nIssue description:\nn the same entity, an LDAP user has asset permissions configured through the configuration file to view only their own assets — no other permissions or administrative rights are granted.\n\nOn the user's personal web page under the Assets menu, individual assets are correctly shown as those belonging to the user.\nHowever, when clicking All, the user can see all assets of the entity (they are visible but not clickable).\n\nCould you please tell me where to disable the display of all entity assets?\nI have searched through a large number of documents but haven’t found a solution.\nThank you.\n\nEnvironment details:\nGLPI deployed via Docker, with users imported through LDAP and assets automatically added via the client agent.", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello Bailey Bennett,\n\n should fix it.\n\nOriginal response date: 2025-10-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3468489420, "author": "Rom1-B", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21640#issuecomment-3468489420", "createdAt": "2025-10-30T15:04:54Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "您好,\n\n#21713 应该修复它。\n\nI will wait to verify it in the next version, TKS.\n\nOriginal response date: 2025-11-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3506642116, "author": "A-Loong", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21640#issuecomment-3506642116", "createdAt": "2025-11-08T15:30:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21640, "url": "https://github.com/glpi-project/glpi/issues/21640", "author": "A-Loong", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [ { "sourceLogin": "Rom1-B", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-26T08:34:52Z", "updatedAt": "2026-02-17T00:39:21Z", "closedAt": "2025-10-30T14:51:30Z" }, "assignedTo": "jordan.blair@peppermint.local" }, { "title": "Dialog behind Show list of available tags does not contains all tags", "detail": "Affected version:\ndocker 11.0.2\n\nIssue description:\nHi.\nstand-alone v 10.0.16, docker v11.0.1 and also docker v11.0.2 does not contains tags problem.causes and problem.symptoms under notification template-tickets-default translation yellow button: list of available tags. But theses tags exists.\n\nMaybe exists more missing tags then these two in this dialog-table.", "priority": "medium", "type": "support", "createdByEmail": "emerson.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue and as far as I can tell, these tags are always available for notification templates for every Problem event.\n\nDo you have any plugins enabled?\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3500021459, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21823#issuecomment-3500021459", "createdAt": "2025-11-07T01:03:31Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "Do you have any plugins enabled?\n\nNo, it is plain docker compose up without plugins. V11.0.2, official image.\n\nI cannot recreate the issue\n\nI am apologize. I search it under:\nSetup -> Notifications -> Notifications -> New Ticket\nTemplates: Tickets : Default translation\nAnd there is probably no \"problem.causes\" and \"problem.symptoms\", because in this time problem is not exists yet.\n\nWhen I go instead of New Ticket to New Problem, these mentioned tags are here.\n\nSry, this is not a bug.\n\nOriginal response date: 2025-11-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3501800733, "author": "jerry-ne", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21823#issuecomment-3501800733", "createdAt": "2025-11-07T10:41:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21823, "url": "https://github.com/glpi-project/glpi/issues/21823", "author": "jerry-ne", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-05T20:09:02Z", "updatedAt": "2026-02-16T00:40:03Z", "closedAt": "2025-11-07T10:41:03Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "[11.0.2] Group list view - group names not clickable (missing href attribute)", "detail": "Affected version:\nGLPI 11.0.2\n\nIssue description:\nIn GLPI 11.0.2, the group list page displays all existing groups correctly, but the group name column (\"Name\") is not clickable — it appears as plain text, not as a link to the group form.\n\nEven when logged in as a super-admin (with full rights), and when the entity context matches the group’s entity, the group name remains inactive.\nGroups can still be opened directly by URL, which proves that permissions are correct — it’s only a UI rendering issue.\n\nReproduction steps:\nLog in as administrator (super-admin profile).\nGo to Administration → Groups.\nObserve that all groups are listed, but the Name field is not clickable (no link / href).\nTry to open one directly via\n\n→ it opens successfully.\n\nEnvironment details:\nGLPI constantsGLPI_ROOT: \"C:\\\\inetpub\\\\www\\\\glpi11_stable\"\nGLPI_VERSION: \"11.0.2\"\nGLPI_SCHEMA_VERSION: \"11.0.2\"\nGLPI_FILES_VERSION: \"11.0.2-52505ef9\"\nGLPI_MIN_PHP: \"8.2\"\nGLPI_MAX_PHP: \"8.5\"\nGLPI_YEAR: \"2025\"\nGLPI_I18N_DIR: \"C:\\\\inetpub\\\\www\\\\glpi11_stable/locales\"\nGLPI_ENVIRONMENT_TYPE: \"production\"\nGLPI_CONFIG_DIR: \"C:\\\\inetpub\\\\www\\\\glpi11_stable/config\"\nGLPI_VAR_DIR: \"C:\\\\inetpub\\\\www\\\\glpi11_stable/files\"\nGLPI_MARKETPLACE_DIR: \"C:\\\\inetpub\\\\www\\\\glpi11_stable/marketplace\"\nGLPI_ALLOW_IFRAME_IN_RICH_TEXT: false", "priority": "medium", "type": "support", "createdByEmail": "jordan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Precision: this is the \"complete name\" column which do not contain link, not name:\n\n[Image omitted]\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3495406691, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21825#issuecomment-3495406691", "createdAt": "2025-11-06T07:03:46Z" } }, { "userEmail": "jordan.bennett@peppermint.local", "text": "Thank you very much, I didn’t even notice. I’ll close this issue\n\nOriginal response date: 2025-11-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3495440083, "author": "Laurynas871", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21825#issuecomment-3495440083", "createdAt": "2025-11-06T07:14:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21825, "url": "https://github.com/glpi-project/glpi/issues/21825", "author": "Laurynas871", "anonymizedAuthorEmail": "jordan.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-11-06T06:50:43Z", "updatedAt": "2026-02-15T00:42:29Z", "closedAt": "2025-11-06T07:15:00Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "GLPI 11 - Issue with mass update of user-created custom fields", "detail": "Affected version:\nMass action with custom field\n\nIssue description:\nWhen performing a mass update of a custom field (created by a user via the Custom Fields ), the operation reports \"Operation successful\", but the field values are not actually updated — they remain unchanged.\n\nReproduction steps:\nI create a new asset type (e.g. Customer Device).\nI create a new dropdown (e.g. Customer Name).\nI add a new custom field to the new asset type (field name: Customer Name, type: dropdown).\nI add some devices under the Customer Device asset type.\nI select several devices → Actions → Update → select the field I want to update (Custom field – Customer Name).\nThe operation shows as successful, but nothing actually changes.\n\nEnvironment details:\nGLPI: 11.0.1 ( => /var/www/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: OK", "priority": "medium", "type": "support", "createdByEmail": "reese.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please include details about the custom field including the field type as we can try to reproduce the issue\n\nOriginal response date: 2025-10-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3394294887, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21424#issuecomment-3394294887", "createdAt": "2025-10-12T12:21:41Z" } }, { "userEmail": "reese.bennett@peppermint.local", "text": "I create a new asset type (e.g. Customer Device).\nI create a new dropdown (e.g. Customer Name).\nI add a new custom field to the new asset type (field name: Customer Name, type: dropdown).\nI add some devices under the Customer Device asset type.\nI select several devices → Actions → Update → select the field I want to update (Custom field – Customer Name).\nThe operation shows as successful, but nothing actually changes.\n\nOriginal response date: 2025-10-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3394554015, "author": "this-is-boris", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21424#issuecomment-3394554015", "createdAt": "2025-10-12T14:30:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21424, "url": "https://github.com/glpi-project/glpi/issues/21424", "author": "this-is-boris", "anonymizedAuthorEmail": "reese.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-11T17:48:47Z", "updatedAt": "2026-02-14T00:38:43Z", "closedAt": "2025-11-05T08:25:40Z" } }, { "title": "Line breaking Text in Brazilian Portuguese", "detail": "Affected version:\nGLPI 11.0.0\n\nIssue description:\nOn the ticket screen, the texts are breaking the line, this did not happen in glpi 10\nGLPI 11:\n[Image omitted]\n\nGLPI 10:\n[Image omitted]\n\nReproduction steps:\n1. Change the GLPI language to Brazilian Portuguese\n2. Access any ticket screen\n\nAdditional context:\nI apologize if this is classified as an improvement.\n\nWhen we select \"plan this task,\" we receive text that is misaligned with the rest of the task section of the ticket. It would be great if the three fields were also icons, consistent with the rest of the task screen.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "This is an effect of the .glpi-full-width use :\n\nOnce removed, no linebreak.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401077745, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21307#issuecomment-3401077745", "createdAt": "2025-10-14T10:09:31Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Since i remove the associated scss rules from on the DOM defined here : the the .field-container and .col-form-label elements seems to have the correct behavior.\n\n[Image omitted]\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401542695, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21307#issuecomment-3401542695", "createdAt": "2025-10-14T12:26:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21307, "url": "https://github.com/glpi-project/glpi/issues/21307", "author": "pedroalves5770", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [ { "sourceLogin": "f2cmb", "anonymizedEmail": "jordan.blair@peppermint.local" } ], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-06T14:04:04Z", "updatedAt": "2026-02-13T00:42:07Z", "closedAt": "2025-11-04T09:02:28Z" }, "assignedTo": "jordan.blair@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI 11 : impossible to get token API in user page", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHello,\n\nI can't copy or see the API token in the user page.\nThe buttons are not functional.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "As far as I rmember, this issue is already solved; try with nightly build.\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3487376547, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21784#issuecomment-3487376547", "createdAt": "2025-11-04T17:58:39Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "Yes, with the nightly version. Thanks a lot !\n\nOriginal response date: 2025-11-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3487433442, "author": "VF404", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21784#issuecomment-3487433442", "createdAt": "2025-11-04T18:13:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21784, "url": "https://github.com/glpi-project/glpi/issues/21784", "author": "VF404", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-04T17:57:32Z", "updatedAt": "2026-02-13T00:41:49Z", "closedAt": "2025-11-04T18:13:35Z" } }, { "title": "Cannot listSearchOptions for AllAssets, making /search/AllAssets useless", "detail": "Affected version:\nglpi/glpi:10\n\nIssue description:\nThe /search/AllAssets API endpoint sounds usefull but is actually useless because it is impossible to know which fields can be searched on or returned, because there is no corresponding /listSearchOptions/AllAssets endpoint", "priority": "medium", "type": "support", "createdByEmail": "finley.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "finley.blair@peppermint.local", "text": "I looked in the code to find which fields can be searched on. But I still don't understand why listSearchOptions gives a 400 error for AllAssets. Feel free to close this.\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3473743723, "author": "jfoucher", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21730#issuecomment-3473743723", "createdAt": "2025-10-31T15:56:34Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The endpoint expects the itemtype to be based on CommonDBTM which are itemtypes with a database table. AllAssets has no database table and doesn't extend CommonDBTM.\n\nOriginal response date: 2025-10-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3473750938, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21730#issuecomment-3473750938", "createdAt": "2025-10-31T15:58:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21730, "url": "https://github.com/glpi-project/glpi/issues/21730", "author": "jfoucher", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-31T14:32:01Z", "updatedAt": "2026-02-09T00:40:45Z", "closedAt": "2025-10-31T15:56:34Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "If we change the status from pending to any other status that isn't resolved or closed, the call remains with the pending reason.", "detail": "Affected version:\n10.0.20\n\nIssue description:\nIf we have a call with pending status and a pending reason assigned, if the call status is changed via a rule, the pending reason is not removed.\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "harper.blair@peppermint.local", "text": "I added this code snippet to the CommonITILObject class in the prepareInputForUpdate method. The problem was solved, as it only changed when the status was entered in $this>input, and if it was entered in the $input variable, it didn't work.\n // If status changed from pending to anything else, remove pending reason\n if (\n isset($this->input[\"status\"])\n && $this->input[\"status\"] != self::WAITING || isset($input[\"status\"])\n && $input[\"status\"] != self::WAITING\n ) {\n PendingReason_Item::deleteForItem($this);\n }\n\nOriginal response date: 2025-10-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3378435589, "author": "verdanatech-marcio", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21331#issuecomment-3378435589", "createdAt": "2025-10-07T19:33:40Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Jesse Blair\n\ncan you take a look ?\n\nOriginal response date: 2025-10-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3380085296, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21331#issuecomment-3380085296", "createdAt": "2025-10-08T07:18:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21331, "url": "https://github.com/glpi-project/glpi/issues/21331", "author": "verdanatech-marcio", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [ { "sourceLogin": "stonebuzz", "anonymizedEmail": "skyler.adler@peppermint.local" }, { "sourceLogin": "Rom1-B", "anonymizedEmail": "jordan.blair@peppermint.local" }, { "sourceLogin": "Lainow", "anonymizedEmail": "jesse.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-07T14:41:55Z", "updatedAt": "2026-02-08T00:49:04Z", "closedAt": "2025-10-30T13:17:54Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Page counter inside printers not working", "detail": "Affected version:\n11.0.1\n\nIssue description:\nI ran network discovery to inventory the printers on my network. I also used the SNMP protocol to capture other information, such as supplies, sheets, and more. However, the page counter specifically isn't working. The icons indicate that the field contains data (2), but it can't be returned.\n\n[Image omitted]\n\nReproduction steps:\n1. After inventorying with the Glpiinventory plugin.\n2. Access Printers in the Assets category.\n3. Page Counters.\n\nEnvironment details:\nsysinfo.txt", "priority": "medium", "type": "support", "createdByEmail": "rowan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please check the GLPI logs (files/_logs folder).\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3458174432, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21674#issuecomment-3458174432", "createdAt": "2025-10-28T19:35:08Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Probably a duplicate of #21519\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3459684853, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21674#issuecomment-3459684853", "createdAt": "2025-10-29T05:08:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21674, "url": "https://github.com/glpi-project/glpi/issues/21674", "author": "raulFeitosa", "anonymizedAuthorEmail": "rowan.adler@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-10-28T18:58:47Z", "updatedAt": "2026-02-07T00:37:50Z", "closedAt": "2025-10-29T05:08:39Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Error during form migration", "detail": "Affected version:\n11.0.1\n\nIssue description:\nI have an error during form migration that occurs at 10%.\n\nHere are my php logs below:\n\n[2025-10-22 10:10:37] glpi.WARNING: * Test logger\n[2025-10-22 10:10:38] glpi.ERROR: * Syntax error\n Backtrace :\n ...machine/safe/lib/Exceptions/JsonException.php:9\n .../thecodingmachine/safe/lib/special_cases.php:39 Safe\\Exceptions\\JsonException::createFromPhpError()\n ...QuestionType/AbstractQuestionTypeActors.php:190 Safe\\json_decode()\n ./src/Glpi/Form/Migration/FormMigration.php:610 Glpi\\Form\\QuestionType\\AbstractQuestionTypeActors->convertDefaultValue()\n ./src/Glpi/Form/Migration/FormMigration.php:353 Glpi\\Form\\Migration\\FormMigration->processMigrationOfQuestions()\n .../Glpi/Migration/AbstractPluginMigration.php:137 Glpi\\Form\\Migration\\FormMigration->processMigration()\n ...Migration/AbstractPluginMigrationCommand.php:88 Glpi\\Migration\\AbstractPluginMigration->execute()\n ./vendor/symfony/console/Command/Command.php:326 Glpi\\Console\\Migration\\AbstractPluginMigrationCommand->execute()\n ./vendor/symfony/console/Application.php:1096 Symfony\\Component\\Console\\Command\\Command->run()\n ./src/Glpi/Console/Application.php:323 Symfony\\Component\\Console\\Application->doRunCommand()\n ./vendor/symfony/console/Application.php:324 Glpi\\Console\\Application->doRunCommand()\n ./vendor/symfony/console/Application.php:175 Symfony\\Component\\Console\\Application->doRun()\n ./bin/console:144 Symfony\\Component\\Console\\Application->run()\n\nReproduction steps:\n1 Migrate form Glpi 10.0.6 to 11.0.1\n2 Update FormCreator plugin\n3 Apply the migration command line : php bin/console migration:formcreator_plugin_to_core\n\nEnvironment details:\nDocker compose", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "This error most likely mean there is an invalid row in your database.\n\nIt seems to be happening when reading the default value of an actor question.\n\nCould you please send us the result of this SQL query to see if we can find the invalid row?\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3437421043, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21597#issuecomment-3437421043", "createdAt": "2025-10-23T14:44:35Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "Thanks for answer, for this table we only had:\nid : 2\nname : \"Demande effectué par:\"\ndefault_values : \"\"\n\nwe tried to change this row with :\nid : 2\nname : \"Test\"\ndefault_values : \"test\"\n\nBut it didn't work.\n\nThen we tried to delete this row and formcreator migration was successful.\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3462612707, "author": "tc-jfoucault", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21597#issuecomment-3462612707", "createdAt": "2025-10-29T16:34:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21597, "url": "https://github.com/glpi-project/glpi/issues/21597", "author": "tc-jfoucault", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-22T10:17:24Z", "updatedAt": "2026-02-07T00:36:50Z", "closedAt": "2025-10-29T16:34:40Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "GLPI 11.0.1 : Impossible to update a ticket in simplified mode, the Save button does not appear.", "detail": "Affected version:\nglpi 11.0.1\n\nIssue description:\nWith the simplified view, the checkbox is not accessible — see my screenshot. If a user chose the wrong category or wants to modify their ticket, they won’t be able to. Also, the Save button no longer exists.\nHowever, if I select the standard view, the Save button appears correctly, and the checkbox is visible in the profile.\n\nProfil Simplfied view\n[Image omitted]\n\nProfil Standard view\n[Image omitted]\n\nTicket mode standard\nI can to modif if the user correctly the ticket\n[Image omitted]\n\nTicket mode simplified\nI cant to modif with button save\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jesse.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jesse.bennett@peppermint.local", "text": "Profil Simplfied view\n[Image omitted]\n\nOriginal response date: 2025-10-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3396516578, "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21439#issuecomment-3396516578", "createdAt": "2025-10-13T09:00:31Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Jesse Bennett,\n\nThis is done on purpose as we don't want requesters to be able to modify the ticket's details once it is opened.\nIn case of a mistake, they can always add a followup to explain their issue.\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400818921, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21439#issuecomment-3400818921", "createdAt": "2025-10-14T09:01:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21439, "url": "https://github.com/glpi-project/glpi/issues/21439", "author": "steph461", "anonymizedAuthorEmail": "jesse.bennett@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-13T08:47:49Z", "updatedAt": "2026-02-06T00:37:02Z", "closedAt": "2025-10-28T08:40:51Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "cannot save form with plugin fields Dropdown", "detail": "Affected version:\nGLPI 11 Main\n\nIssue description:\nExample : [Image omitted]\n\nError validateExtraDataInput\n\nArray\n (\n [name] => Abonnement SIM\n [visibility_strategy] => visible_if\n [description] =>\n [default_value] => {\"items_id\":-1}\n [extra_data] => Array\n (\n [categories_filter] => Array\n (\n [0] => request\n [1] => incident\n [2] => change\n [3] => problem\n )\n\n [root_items_id] => 0\n [subtree_depth] => 0\n [sub_type] => PluginFieldsTypedabonnementfieldDropdown\n )\n\n [_type_category] => Glpi\\Form\\QuestionType\\QuestionTypeCategory->item\n [type] => Glpi\\Form\\QuestionType\\QuestionTypeItemDropdown\n [is_mandatory] => 0\n [uuid] => 63f9bcd634c6ec\n [forms_sections_uuid] => f998fd56-ae42-4cc7-bdf1-a00fe254eb1c\n [vertical_rank] => 4\n [horizontal_rank] => NULL\n [category] => Glpi\\Form\\QuestionType\\QuestionTypeCategory->item\n [forms_sections_id] => 332\n [_no_history] =>\n [conditions] => [{\"item\":\"question-9349b264-e66c-457c-afe4-f8840530130c\",\"item_uuid\":\"9349b264-e66c-457c-afe4-f8840530130c\",\"item_type\":\"question\",\"value_operator\":\"equals\",\"value\":\"1868892213\"}]\n [validation_conditions] => []\n )\n\nif i add into QuestionTypeItem.php :\n\npublic function validateExtraDataInput(array $input): bool\n {\n\n if (isset($input['sub_type'])) {\n $input['itemtype'] = $input['sub_type'];\n }\n\nI can save the form.", "priority": "medium", "type": "bug", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi Casey Blair, is this still an ongoing issue?\n\nI was able to create this very simple form without issues:\n\n[Image omitted]\n\nOriginal response date: 2025-10-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3370682802, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21144#issuecomment-3370682802", "createdAt": "2025-10-06T09:24:45Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "I'll close as there is no activity on this issue, feel free to reopen if needed.\n\nOriginal response date: 2025-10-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3455217577, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21144#issuecomment-3455217577", "createdAt": "2025-10-28T08:42:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21144, "url": "https://github.com/glpi-project/glpi/issues/21144", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [ "beta / rc", "bug", "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-25T09:57:33Z", "updatedAt": "2026-02-06T00:36:58Z", "closedAt": "2025-10-28T08:42:28Z" }, "assignedTo": "skyler.adler@peppermint.local" }, { "title": "GLPI 11 - [CLI][Bug] SessionException prevents running migrations with GLPI_SESSION_DIR defined", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWhen attempting to run any migration command via CLI (migration:utf8mb4, migration:unsigned_keys, migration:formcreator_plugin_to_core), a fatal error occurs related to session handling:\n\nSafe\\Exceptions\\SessionException: An error occurred\nat vendor/thecodingmachine/safe/generated/8.2/session.php:452\nin src/Session.php:255 -> Session::setPath()\n\nReproduction steps:\nInstall GLPI on a Linux server.\n\nDefine GLPI_SESSION_DIR in /etc/glpi/local_define.php.\n\nAttempt to execute any migration command via CLI\n\nThe error occurs immediately.\n\nExpected result:\nMigrations should run normally without depending on session management, as they are executed in CLI mode.\n\nActual result:\nThe script fails with Safe\\Exceptions\\SessionException due to attempting to set session_save_path() when the session is already active or in a CLI environment\n\nEnvironment details:\nPHP 8.2\n\nGLPI 11.0.1\n\nOS: Debian\n\nGLPI_SESSION_DIR defined in /etc/glpi/local_define.php\n\nAdditional context:\nTemporary workaround:\nModify the Session::setPath() function to skip session handling when in CLI:\n\npublic static function setPath()\n{\n if (php_sapi_name() === 'cli') {\n return;\n }\n\n if (\n ini_get(\"session.save_handler\") == \"files\"\n && session_status() !== PHP_SESSION_ACTIVE\n ) {\n session_save_path(GLPI_SESSION_DIR);\n }\n}\n\nImpact:\nCannot run any migrations via CLI, affecting database updates and plugin migrations.\n\nSuggestion:\nAdd CLI environment detection in the Session::setPath() function or make migrations independent of session management.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "It should be already fixed by #21383, that has been merged after the 11.0.1 version release.\n\nWhat is the content of your /etc/glpi/local_define.php file?\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3400503010, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21456#issuecomment-3400503010", "createdAt": "2025-10-14T07:39:50Z" } }, { "userEmail": "emerson.bennett@peppermint.local", "text": "Sorry, I didn't realize they already had it. I took a bit longer to add this issue\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3401411501, "author": "Gabo700", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21456#issuecomment-3401411501", "createdAt": "2025-10-14T11:52:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21456, "url": "https://github.com/glpi-project/glpi/issues/21456", "author": "Gabo700", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-10-13T17:27:45Z", "updatedAt": "2026-02-06T00:36:52Z", "closedAt": "2025-10-28T09:27:25Z" } }, { "title": "Port history is empty all the time", "detail": "Affected version:\n11.0.1\n\nIssue description:\nHi! We are currently testing glpi agent to inventory our network, mainly switches. And history of port on switches are crucial for us. Now GLPI agent is scanning switches itself properly, updating information every hour for at least 3 days, and still there isn't port history on any port on any switch.\n\nGLPI agent version is 1.15\n\n[Image omitted]\n\nEnvironment details:\nGLPI: 11.0.1 ( => /var/www/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: OK", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Did that work as you expect in any previous version? If yes, in which one was that OK?\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3405172906, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21488#issuecomment-3405172906", "createdAt": "2025-10-15T08:26:32Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "Did that work as you expect in any previous version? If yes, in which one was that OK?\n\nWe wasn't using it in previous versions. Started to scan network with snmp only after upgrade from 10.0.16 to 11.0.0.\n\nOriginal response date: 2025-10-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3405183966, "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21488#issuecomment-3405183966", "createdAt": "2025-10-15T08:28:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21488, "url": "https://github.com/glpi-project/glpi/issues/21488", "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-15T06:22:31Z", "updatedAt": "2026-02-05T00:39:51Z", "closedAt": "2025-10-27T14:36:02Z" } }, { "title": "Self-service user cant see GLPI-objects at form", "detail": "Affected version:\n11.0.1\n\nIssue description:\nSelf-service users cant see glpi-objects (Assets) in form item list.\n\nI managed problem by disabling simplified interface for self-service profile, after this Assets tab was enabled in Self-service profile settings, and i can enable Printer asset to be viewed. But why we cant have Simplified interface with asset management in form?\n\nAlso with Simplified interface enabled or not, i got errors in php-error log. I wounder if this errors relevant to this problem. Form work well with Standart self-service interface, and Task was created normally.\n\n[Image omitted]\n\nhere my form exported.\nzaavka-na-obsluzivanie-printera-mfu-skanera-2025-10-21.json\n\nReproduction steps:\nenable simplified iterface\nnow you cant use assets in forms for self-service users.\n\nEnvironment details:\nglpi docker container migrated from 10 to 11", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Thank you for reporting the warning, I have fixed it but this warning don't have any impact on your main error.\n\nFor your main error this issue is a duplicate of #21509 where you'll find more information about the current discussion on it's resolution\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3432726773, "author": "froozeify", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21566#issuecomment-3432726773", "createdAt": "2025-10-22T14:41:31Z" } }, { "userEmail": "harper.blair@peppermint.local", "text": "[Image omitted]\n[Image omitted]\n\nlook like problem in this #21509 slightly different, because we are using list of Assets differently. They want self-service users see their own computers(or any assets)/ In our system we let Self-service user choose over all Printers(Assets) in our organisation. So how i see in #21509 you reffer to READ_OWNED rights, but only with this right users will not see other assets (if i understand right)\nso maybe just let asset tab enabled while in simplified mode? because look like users LOSE all rights for assets in this mode.\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3435137849, "author": "n0womann0cry", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21566#issuecomment-3435137849", "createdAt": "2025-10-23T05:21:06Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21566, "url": "https://github.com/glpi-project/glpi/issues/21566", "author": "n0womann0cry", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [ { "sourceLogin": "froozeify", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-21T08:18:27Z", "updatedAt": "2026-02-01T00:45:09Z", "closedAt": "2025-10-23T07:32:23Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Input type number and step any in forms not allowed by Microsoft Edge (at least)", "detail": "Affected version:\n10.0.20\n\nIssue description:\nHello,\n\nThe issue was discovered when I tried to update an infocom form for a computer device. It leaded to:\n\n[2025-10-22 15:55:46] glpisqllog.ERROR: DBmysql::doQuery() in glpi/src/DBmysql.php line 395\n * MySQL query error:\n SQL: UPDATE glpi_infocoms SET value = '', warranty_value = '', date_mod = '2025-10-22 15:55:46' WHERE id = '2526'\n\nsql-errors.log said:\nError: Incorrect decimal value: '' for column glpi.glpi_infocoms.value at row 1\n Backtrace :\n src/DBmysql.php:1499 DBmysql->doQuery()\n src/CommonDBTM.php:686 DBmysql->update()\n src/CommonDBTM.php:1703 CommonDBTM->updateInDB()\n front/infocom.form.php:69 CommonDBTM->update()\n public/index.php:82 require()\n\nChecking GLPI database, for this entry showed that value (and warranty_value) was set to 0.0000\n\nLooking closer allowed me to detect that Microsoft Edge does not display the values in the corresponding fields:\n\n[Image omitted]\n\nInstead with Firefox the result is correct:\n\n[Image omitted]\n\nI'm not sure if other forms are concerned (probably).", "priority": "medium", "type": "support", "createdByEmail": "bailey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Already fixed for 10.0.21; you can try with nightly build.\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3435048094, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21606#issuecomment-3435048094", "createdAt": "2025-10-23T04:42:14Z" } }, { "userEmail": "bailey.bennett@peppermint.local", "text": "Just a pointer to the duplicated issue...\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3435660987, "author": "kabassanov", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21606#issuecomment-3435660987", "createdAt": "2025-10-23T08:10:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21606, "url": "https://github.com/glpi-project/glpi/issues/21606", "author": "kabassanov", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2025-10-22T14:27:33Z", "updatedAt": "2026-02-01T00:45:03Z", "closedAt": "2025-10-23T04:42:14Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI-11.0.1 - Unable to delete netw device from trashbin", "detail": "Affected version:\nGlpi 11.0.1\n\nIssue description:\nGoodmorning,\n\nI try to do \"delete permanently and remove devices\" from trashbin my old network devices, but \"An unexpected error occurred \"\n\nAffected page:\n\nReproduction steps:\n1. Assets --> Network Devices\n2. Put in trashbin a specific devices\n3. show trashbin\n4. Delete permanently and remove devices", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Hello,\n\nI cannot reproduce, without any associations, with associated Location, Network & Group.\n\nCan you please :\n- retry with original templates/components/form/fields_macros.html.twig (yours is modified).\n- retry with plugins disabled\n- provided a screenshot of network device details\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3437269710, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21600#issuecomment-3437269710", "createdAt": "2025-10-23T14:15:20Z" } }, { "userEmail": "dakota.blair@peppermint.local", "text": "Hi,\n\nI try to restore the fields_macros.html.twig but the error is still present\nI try to disable plugin \"Additional Fileds\" and this solve the problem, so I think is a problem about this plugin\nNow I open a case about this plugin\n\nThanks for your support\n\nOriginal response date: 2025-10-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3437460848, "author": "barte91", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21600#issuecomment-3437460848", "createdAt": "2025-10-23T14:52:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21600, "url": "https://github.com/glpi-project/glpi/issues/21600", "author": "barte91", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-22T12:34:55Z", "updatedAt": "2026-02-01T00:44:51Z", "closedAt": "2025-10-23T14:52:40Z" } }, { "title": "GLPI 11.0.1 Tickets Notification: Please note that there are no more contracts with days available for this customer.", "detail": "Issue description:\n[Image omitted]\nThere is a prompt on the work order interface: \"Please note that there are no more contracts with days available for this customer.\" I cannot confirm which type of contract has expired. How can I remove this prompt? Where should I configure it?", "priority": "medium", "type": "support", "createdByEmail": "finley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Seems like this string is not coming from GLPI; try without plugins.\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3430644220, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21590#issuecomment-3430644220", "createdAt": "2025-10-22T06:13:26Z" } }, { "userEmail": "finley.bennett@peppermint.local", "text": "Seems like this string is not coming from GLPI; try without plugins.\n\nYou are right. The issue is with the plugin Entities Portal. When I enable this plugin, the contract expiration notification appears, even though I have updated the plugin to the latest version.\n\nThank you!\n\nOriginal response date: 2025-10-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3430732772, "author": "KissWam", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21590#issuecomment-3430732772", "createdAt": "2025-10-22T06:51:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21590, "url": "https://github.com/glpi-project/glpi/issues/21590", "author": "KissWam", "anonymizedAuthorEmail": "finley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2025-10-22T06:08:20Z", "updatedAt": "2026-01-31T00:35:49Z", "closedAt": "2025-10-22T06:13:26Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Network port metrics not showing properly", "detail": "Affected version:\n11.0.1\n\nIssue description:\nAny network port on any network device do not show anything in \"Network port metrics\" tab. Even if it saying that there is \"5\" data of something, still blank screen.\n\n[Image omitted]\n\nIn \"Network ports\" tab of the network device I can see that there are some statistics\n\n[Image omitted]\n\nAffected page:\n/front/networkport.form.php\n\nEnvironment details:\nGLPI: 11.0.1 ( => /var/www/glpi)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: OK", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "noel.bennett@peppermint.local", "text": "We started using it only from GLPI 11.0.1 so don't know if it was working in previous versions\n\nOriginal response date: 2025-10-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3410092522, "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21518#issuecomment-3410092522", "createdAt": "2025-10-16T09:54:29Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Problem does not exist on v10. It looks like there is something wrong when initializing the JS lib.\n\nOriginal response date: 2025-10-17", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3414540095, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21518#issuecomment-3414540095", "createdAt": "2025-10-17T09:05:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21518, "url": "https://github.com/glpi-project/glpi/issues/21518", "author": "hamx01", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [], "labels": [ "javascript" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-16T09:50:37Z", "updatedAt": "2026-01-30T00:37:40Z", "closedAt": "2025-10-21T06:19:08Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Error when response to a ticket with more than 1 technician", "detail": "Affected version:\n11.0.1\n\nIssue description:\nWe have an error when we add a follow to a ticket with more than one technician\n\nAffected page:\n\nReproduction steps:\n1. add a second technician on attribued to on a ticket and save\n2. add a follow up to the ticket", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "cameron.bennett@peppermint.local", "text": "This issue seems to come from the \"behaviors\" plugin, please open the issue on the plugin repository.\n\nOriginal response date: 2025-10-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3421308135, "author": "flegastelois", "anonymizedAuthorEmail": "cameron.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21546#issuecomment-3421308135", "createdAt": "2025-10-20T09:50:21Z" } }, { "userEmail": "dakota.blair@peppermint.local", "text": "ok sorry & thankyou !\n\nOriginal response date: 2025-10-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3421508397, "author": "efpbe", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21546#issuecomment-3421508397", "createdAt": "2025-10-20T10:33:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21546, "url": "https://github.com/glpi-project/glpi/issues/21546", "author": "efpbe", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-20T09:06:52Z", "updatedAt": "2026-01-29T00:37:01Z", "closedAt": "2025-10-20T09:50:21Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Approval template doesn't add all users when using on a ticket", "detail": "Affected version:\n11.0.0\n\nIssue description:\nUsing Group user(s) in an approval template, even though there are several users, when using it on a ticket, just one user is added to the approval request.\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. Create an approval template with group of users\n2. Add every user you want to be added to the template\n3. Try to use the approval template on a ticket\n4. Just the first user will be added as approver", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "The same thing happened here.\n\nOriginal response date: 2025-10-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3356799547, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21230#issuecomment-3356799547", "createdAt": "2025-10-01T14:49:19Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm. The call of the custom JS event setValue is not sending the event data properly. An array of data can be passed so it doesn't see the list of users as a single parameter.\n\nOriginal response date: 2025-10-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3358504311, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21230#issuecomment-3358504311", "createdAt": "2025-10-01T23:28:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21230, "url": "https://github.com/glpi-project/glpi/issues/21230", "author": "arthurrschaefer", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-01T14:25:34Z", "updatedAt": "2026-01-26T00:35:20Z", "closedAt": "2025-10-17T05:22:08Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "GLPI11 - Forms with many destinations", "detail": "Affected version:\n11.0.0\n\nIssue description:\nHello,\n\nI have a form with 89 destinations that does not load (in the ‘Destinations’ submenu of the form). When I go to the form's destinations, the page remains loading and then displays an error. I do not have any errors on the GLPI side or in the browser tools.\n\nIf you wish, I can email you an export of the form in JSON format.", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi Anthony, yes it would help a lot if you could send us the form.\n\nInstead of an email, could you please open a ticket on our support with the form attached? It might be simpler for us to track.\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3384604556, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21310#issuecomment-3384604556", "createdAt": "2025-10-09T07:56:37Z" } }, { "userEmail": "noel.bennett@peppermint.local", "text": "Hello,\n\nIt's done (ticket number 39674).\n\nSincerely,\n\nOriginal response date: 2025-10-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3384820608, "author": "anthonymontebrun", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21310#issuecomment-3384820608", "createdAt": "2025-10-09T08:51:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21310, "url": "https://github.com/glpi-project/glpi/issues/21310", "author": "anthonymontebrun", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [ { "sourceLogin": "froozeify", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-06T15:37:04Z", "updatedAt": "2026-01-24T00:31:38Z", "closedAt": "2025-10-15T14:00:09Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "MariaDB 10.5 not supported", "detail": "Affected version:\n11\n\nIssue description:\nUpgrading to GLPI 11 in our test instance and docs state that it supports MariaDB 10.5 but upon installation and checking requirements, I get an error stating it requires 10.6. We will upgrade our DB server, as should be, but the docs should be corrected as well.\n\n[Image omitted]\n\nAffected page:", "priority": "medium", "type": "support", "createdByEmail": "jamie.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "You should have reported this on the documentation repo. It's fixed anyway.\n\nOriginal response date: 2025-10-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3388365572, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21393#issuecomment-3388365572", "createdAt": "2025-10-10T05:41:16Z" } }, { "userEmail": "jamie.blair@peppermint.local", "text": "Thanks! I didn't know there was a documentation repo available, it isn't fully apparent to look for one. One doesn't know what one doesn't know...until they know 😊\n\nOriginal response date: 2025-10-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3403539624, "author": "bwutsa", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21393#issuecomment-3403539624", "createdAt": "2025-10-14T20:38:18Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21393, "url": "https://github.com/glpi-project/glpi/issues/21393", "author": "bwutsa", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-09T17:51:14Z", "updatedAt": "2026-01-23T00:33:00Z", "closedAt": "2025-10-10T05:41:16Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "mailcollector fails with PREG_BACKTRACK_LIMIT_ERROR", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nA mail is stuck in our inbox and during import glpi produces the attached error.\nI can not share the full eml, but I attached a cleaned version which produces the same error on\nWhat sticks out is that the mail contains a 600KB base64 encoded image.\nOtherwise the used html is valid.\n\nThe culprit is the following regex:\n\nMy first idea was to include the white spaces in the capture group and later remove with trim. However, this still leads to the same error.\n\nOne idea could be to use stripos instead of regex for the same effect. Should I put together a pull request with that or do you have an other idea?\n\nsave.eml\n\nReproduction steps:\n1. Write a html mail with a large base64 encoded image to glpi\n2. Import Mail\n3. Observe error", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nCould you check if the problem persist on GLPI 11.0.7. I think we fixed something related to this recently.\n\nOriginal response date: 2026-05-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4380017488, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23863#issuecomment-4380017488", "createdAt": "2026-05-05T14:04:32Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I cherry-picked the commit adding the test case from my pull request on top of the current 11.0/bugfix branch and it still reproduces the error.\nSee also:\nglpi_imap.log\n\nOriginal response date: 2026-05-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4385590811, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23863#issuecomment-4385590811", "createdAt": "2026-05-06T06:19:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23863, "url": "https://github.com/glpi-project/glpi/issues/23863", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-14T11:34:37Z", "updatedAt": "2026-07-20T08:32:54Z", "closedAt": "2026-07-20T08:32:54Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "v11.0.8: Debug mode breaks image uploads with FileNotFoundException on PHP temporary upload file", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nv11.0.8\n\nSummary:\nWhen GLPI debug mode is enabled for the current user/session, uploading or dropping an image as an attachment fails with a server-side exception.\n\nThe upload itself reaches PHP, but during shutdown the GLPI debug profiler tries to save the request profile and recreates the Symfony request from globals. At that point, the PHP temporary uploaded file no longer exists, causing Symfony\\Component\\HttpFoundation\\File\\Exception\\FileNotFoundException.\n\nDisabling debug mode fixes the image upload immediately.\n\nEnvironment:\n- GLPI version: 11.0.8\n- PHP version: 8.5.7\n- Web server: Apache\n- Deployment: Docker/Kubernetes pod\n- Document root: /var/www/glpi/public\n- GLPI var dir: /var/glpi/files\n- GLPI log dir: /var/glpi/logs\n\nAffected page:\n\nReproduction steps:\n1. Log in to GLPI with a user that has debug mode enabled.\n2. Open a ticket or another object that supports file attachments.\n3. Drag and drop an image, or paste/drop an image as an attachment.\n4. The upload fails.\n5. Disable debug mode.\n6. Log out and log back in, or refresh the session.\n7. Retry the same image upload.\n8. The upload works.\n\nEnvironment details:\n- GLPI version: 11.0.8\n- PHP version: 8.5.7\n- Web server: Apache\n- Deployment: Docker/Kubernetes pod\n- Document root: /var/www/glpi/public\n- GLPI var dir: /var/glpi/files\n- GLPI log dir: /var/glpi/logs", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "#24714 should fix the issue. It has been done in the main branch, since we had no issue reported yet, but it can probably be backported to GLPI 11.\n\nOriginal response date: 2026-07-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4923492719, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24820#issuecomment-4923492719", "createdAt": "2026-07-09T09:14:04Z" } }, { "userEmail": "drew.blair@peppermint.local", "text": "#24714 should fix the issue. It has been done in the main branch, since we had no issue reported yet, but it can probably be backported to GLPI 11.\n\nDoes that mean it's going to be fixed in a future release?\n\nOriginal response date: 2026-07-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4926728192, "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24820#issuecomment-4926728192", "createdAt": "2026-07-09T15:21:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24820, "url": "https://github.com/glpi-project/glpi/issues/24820", "author": "BENZOOgataga", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-07-09T08:53:13Z", "updatedAt": "2026-07-16T07:36:06Z", "closedAt": "2026-07-16T07:36:06Z" } }, { "title": "Projects Description Bug", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nIn GLPI version 11.0.7, the Description field in the Projects module (and possibly other ITIL objects) is failing to load. The field shows a continuous loading state, making it impossible to type or view any content.\n\nHowever, the Comments field under the Planning section works fine. This issue started occurring immediately after the upgrade to version 11.0.7. I have tried clearing the browser cache and using different browsers, but the issue persists.\n\nReproduction steps:\nGo to Tools > Projects.\n\nOpen an existing project or create a new one.\n\nObserve the Description field—it stays in a loading state and is non-interactive.", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Please try clearing your browser cache.\n\nOriginal response date: 2026-05-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4409059852, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24177#issuecomment-4409059852", "createdAt": "2026-05-08T18:55:56Z" } }, { "userEmail": "parker.bennett@peppermint.local", "text": "Dear Curtis and Johan,\n\nThank you for looking into this issue.\n\nI would like to update you that after performing a clean reinstall of the\nsystem, the issue has been successfully resolved and everything is running\nfine now.\n\nThank you again for your support.\n\nOn Thu, May 21, 2026 at 9:12 PM Johan Cwiklinski *@*.*>\nwrote:\n\nClosed #24177 as not\nplanned.\n—\nReply to this email directly, view it on GitHub\n, or\nunsubscribe\n\n.\nTriage notifications on the go with GitHub Mobile for iOS\n\nor Android\n.\nYou are receiving this because you authored the thread.Message ID:\n*@*.*>\n\nOriginal response date: 2026-07-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4931802061, "author": "helpdesklypogroup", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24177#issuecomment-4931802061", "createdAt": "2026-07-10T03:49:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24177, "url": "https://github.com/glpi-project/glpi/issues/24177", "author": "helpdesklypogroup", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-05-08T10:20:16Z", "updatedAt": "2026-07-10T03:49:41Z", "closedAt": "2026-05-21T13:12:01Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "It is not possible to add or modify ANS", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nHello Team\n\nAfter updating from version 10.0.16 and testing all features before going live, we found that the ANS values cannot be adjusted; neither TTR nor TTO can be deleted or rescheduled.\n\nObviously, I have some rules in place to control this for certain entities, but there are other entities that don’t have rules, and I can’t use the ticket templates to set these fields as read-only either.\n\n[Image omitted]\n\n[Image omitted]\n\nThanks", "priority": "medium", "type": "support", "createdByEmail": "emerson.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "Add SLM rights to your profile\n\n[Image omitted]\n\n[Image omitted]\n\nOriginal response date: 2026-07-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4902058027, "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24773#issuecomment-4902058027", "createdAt": "2026-07-07T09:02:56Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "Hey, thanks so much—I didn't know about that new feature.\n\nI tried it out, and it works perfectly.\n\nOriginal response date: 2026-07-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4904909408, "author": "sard1091", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24773#issuecomment-4904909408", "createdAt": "2026-07-07T14:28:30Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24773, "url": "https://github.com/glpi-project/glpi/issues/24773", "author": "sard1091", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-07-03T20:46:20Z", "updatedAt": "2026-07-07T15:48:41Z", "closedAt": "2026-07-07T15:48:41Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Regression in regex evaluation for hierarchical fields (Formcreator vs Native Forms - GLPI 11)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.7\n\nIssue description:\nHi,\n\nAfter our migration tests from GLPI 10 (with Formcreator) to GLPI 11 using native forms, I’ve encountered a change in behavior when applying regex conditions on hierarchical fields (such as categories or locations).\n\nIn GLPI 10 with Formcreator, the value evaluated by regex conditions corresponded to the full hierarchical path (i.e., completename). For example:\n\nADMIN / DOCENTE > RECTORIA GENERAL > DIRECCIÓN ADMINISTRATIVA\n\nThis allowed regex expressions like:\n\n/.*\\b(RECTORIA GENERAL)\\b.*/iu\n\nto match correctly, even when selecting child nodes, because the parent string was part of the evaluated value.\n\nWhen using the same type of field in native forms, the system appears to evaluate only the selected node (i.e., the leaf), not the full path.\n\nFor example, selecting:\n\nADMIN / DOCENTE > RECTORIA GENERAL > DIRECCIÓN ADMINISTRATIVA\n\nThe regex is evaluated only against:\n\nDIRECCIÓN ADMINISTRATIVA\n\nAs a result:\n\n* Matching RECTORIA GENERAL works only if that exact node is selected\n* Matching fails when selecting any child node, since the parent is no longer part of the evaluated string\n\nThis is a blocking issue for our upgrade.\n\nWe currently have more than 30 forms using regex conditions based on hierarchical paths.\nAll of them worked correctly in GLPI 10 (Formcreator), but in GLPI 11 these conditions no longer work, leaving key parts of our forms unusable during upgrade testing.\n\nMaintaining this logic by explicitly listing all child nodes is not feasible due to the size and complexity of our hierarchy.\n\nWhat is the recommended way in GLPI 11 native forms to apply conditions that take into account parent or ancestor elements in hierarchical fields?\n\nThanks in advance for your help.", "priority": "medium", "type": "bug", "createdByEmail": "emerson.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello, thank you for your feedback.\n\nA fix has recently been added to resolve your issue ( and will be included in the next release.\nCan you confirm that the fix resolves your issue by testing it on the 11.0/bugfixes branch or the latest nightly build?\n\nOriginal response date: 2026-05-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4561672849, "author": "ccailly", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24142#issuecomment-4561672849", "createdAt": "2026-05-28T07:22:44Z" } }, { "userEmail": "emerson.blair@peppermint.local", "text": "Sorry for the late reply. After updating my Docker image to the latest version, 11.0.8, this error was resolved.\n\nThank you\n\nOriginal response date: 2026-07-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4870885878, "author": "sard1091", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24142#issuecomment-4870885878", "createdAt": "2026-07-02T22:13:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24142, "url": "https://github.com/glpi-project/glpi/issues/24142", "author": "sard1091", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [], "labels": [ "bug", "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-05T20:15:13Z", "updatedAt": "2026-07-03T05:15:22Z", "closedAt": "2026-07-03T05:15:22Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "No LDAP group import", "detail": "Issue description:\nUnder Administration > Groups, the \"LDAP directory link\" button—which appears in the Users section—is missing.\nMy LDAP is correctly configured, and user import is working fine.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I am not able to recreate the issue. The code for this doesn't seem to have changed between GLPI 11 and 12. Maybe a cache issue?\n\nAs long as the following are met, it should appear:\n1. Have at least 1 active LDAP\n2. Have \"Add users from an external source\" right on users\n3. Have Update right for Groups\n\nOriginal response date: 2026-07-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4865181682, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24761#issuecomment-4865181682", "createdAt": "2026-07-02T11:27:09Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Actually, it was simpler than that... I hadn't indicated that LDAP was...enabled... sorry 😑\nI close the issue...\n\nOriginal response date: 2026-07-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4865852760, "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24761#issuecomment-4865852760", "createdAt": "2026-07-02T12:49:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24761, "url": "https://github.com/glpi-project/glpi/issues/24761", "author": "Otijom", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-07-02T11:18:47Z", "updatedAt": "2026-07-02T12:49:10Z", "closedAt": "2026-07-02T12:49:10Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Export ticket list", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.8\n\nIssue description:\nWhen trying to export anithing from ticket list i got an error\n\nReproduction steps:\nGo to tickets\nTry to export\n\nEnvironment details:\nOperating system: Linux * 5.15.0-125-generic #​135-Ubuntu SMP Fri Sep 27 13:53:58 UTC 2024 x86_64\n\nPHP: 8.3.23 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, apache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"8M\" session.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\" upload_max_filesize=\"100M\"\n\nWeb server: Apache/2.4.56 (Debian) (Apache/2.4.56 (Debian) Server at 10.90.5.14 Port 8015)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 11.2.6-MariaDB-ubu2204\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@glpi8014-mariadb/glpidb\n\nHost info: glpi8014-mariadb via TCP/IP\n\nRequirements:\nPHP version (8.3.23) is supported.\nOS and PHP are relying on 64 bits integers.\nSessions configuration is OK.\nAllocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader, xmlwriter.\nmysqli extension is installed\ncurl extension is installed\ngd extension is installed\nintl extension is installed\nmbstring extension is installed\nzlib extension is installed\nbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installed\nDatabase engine version (11.2.6) is supported.\nThe log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.\nexif extension is installed\nldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.\nZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.\nWrite access to /var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "I do not reproduce. The method do exist in the class:\n\nDouble check you've properly extracted/uploaded/whatever your vendor directory.\n\nOriginal response date: 2026-06-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4840634082, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24707#issuecomment-4840634082", "createdAt": "2026-06-30T06:45:08Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "i uploaded again, clear the cache and it fixed\nMagick :D\n\nOriginal response date: 2026-06-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4840863242, "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24707#issuecomment-4840863242", "createdAt": "2026-06-30T07:18:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24707, "url": "https://github.com/glpi-project/glpi/issues/24707", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-30T06:31:50Z", "updatedAt": "2026-06-30T07:53:03Z", "closedAt": "2026-06-30T07:53:03Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Automatic Actions history status show \"???\"", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nThe history log from automatic actions... show \"???\" as status changed:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi Drew Bennett\ncan you try this -> #24628\n\nOriginal response date: 2026-06-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4766814858, "author": "stonebuzz", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24619#issuecomment-4766814858", "createdAt": "2026-06-22T09:25:37Z" } }, { "userEmail": "drew.bennett@peppermint.local", "text": "hi Skyler Adler fixed with this PR thanks!\n\n[Image omitted]\n\nOriginal response date: 2026-06-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4789722847, "author": "ftoledo", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24619#issuecomment-4789722847", "createdAt": "2026-06-24T13:20:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24619, "url": "https://github.com/glpi-project/glpi/issues/24619", "author": "ftoledo", "anonymizedAuthorEmail": "drew.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-19T21:31:23Z", "updatedAt": "2026-06-24T13:20:53Z", "closedAt": "2026-06-22T10:25:19Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Simplified interface does allow to assigne SLA", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.25\n\nIssue description:\nHello.\nA week ago I have discovered that user which use as a profiles interface: Simplified interface, create tickets without assigned SLA (TTR or TTO). Using Standard interface there is no problem with that.\nSLA depends on category (ITIL category), so in every category template there is set a template for SLA. In ticket, when using Standard interface, when user assignees a category then SLA is being assigned. I see it also i GLPIs DB in glpi_tickets table, where an ID of TTR or TTO is being set. However when user is using Simplified interface SLA is somehow not being set - user sets a category and creates ticket, but when a user opens that ticket TTR and TTO fields are blank. I have also checked that in GLPIs DB and there is nothing - slas_id_ttr and slas_id_tto are equal zero, so no SLA ID.\nI have checked PHP (8.2.26) and apache2 www server logs and there is nothing.\nWhat can I do with this?\n\n[Image omitted]\n[Image omitted]\n[Image omitted]\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This is intentional. Regular users cannot dictate the SLA that applies. It is intended that you use the SLA criteria to automatically apply them as needed.\n\nOriginal response date: 2026-06-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4780892443, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24650#issuecomment-4780892443", "createdAt": "2026-06-23T15:42:56Z" } }, { "userEmail": "hayden.blair@peppermint.local", "text": "\"It is intended that you use the SLA criteria to automatically apply them as needed.\"\nI did not quite understand what you meant - could you describe it in more detail?\nI have configure profile with Simplified interface by adding a ticket template of ITIL category with SLA, so it would automatically assign such SLA as set in Default ticket template or ITIL category, but this however does not work.\n\nOriginal response date: 2026-06-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4781228611, "author": "namtarkur", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24650#issuecomment-4781228611", "createdAt": "2026-06-23T16:20:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24650, "url": "https://github.com/glpi-project/glpi/issues/24650", "author": "namtarkur", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-06-23T15:29:06Z", "updatedAt": "2026-06-23T16:20:17Z", "closedAt": "2026-06-23T15:43:01Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "MySQL syntax error IN () in Certificate::cronCertificate", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWhen the automatic action certificate (Certificate::cronCertificate) runs via cron (CLI), it triggers a MySQL syntax error (1064). The search engine generates an empty IN () condition for recursive entities, which breaks the query execution.\n\nTo reproduce (Como reproduzir):\nHave a certificate associated with an entity or in a specific context where entity resolution returns empty for recursive checks.\n\nRun the cron task for certificates via CLI (front/cron.php or bin/console glpi:cron:execute).\n\nCheck the files/_log/sql-error.log or php-errors.log.\n\nReproduction steps:\n1. Have a certificate associated with an entity or in a specific context where entity resolution returns empty for recursive checks.\n2. Run the cron task for certificates via CLI (front/cron.php or bin/console glpi:cron:execute).\n3. Check the files/_log/sql-error.log.\n\nAdditional context:\nThe issue happens because the SQL construction in SQLProvider.php generates an empty IN () list for recursive entities, causing a MySQL 1064 syntax error when checking certificates via cron.\n\nExample snippet from the query:\nOR (glpi_certificates.is_recursive='1' AND glpi_certificates.entities_id IN ())", "priority": "medium", "type": "support", "createdByEmail": "harper.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "harper.blair@peppermint.local", "text": "## Root Cause Identified\n\nAfter extensive debugging, I found the root cause of the IN () SQL syntax error.\n\nThe issue occurs in FilterableTrait::itemMatchFilter() which is called by NotificationEvent::raiseEvent() during cron execution. When running in cron context, the following session variables are not initialized:\n\n- $_SESSION['glpiparententities'] — not set (this is the key missing variable)\n- $_SESSION['glpiactiveentities_string'] — empty\n\nThis causes getEntitiesRestrictRequest() in DbUtils.php to fall into the recursive branch and call getAncestorsOf('glpi_entities', '') with an empty string, generating the invalid AND entities_id IN () SQL.\n\n## Workaround Patch\n\nFix 1 — src/Glpi/Search/FilterableTrait.php\n\nAdd session initialization before SearchEngine::getData() call:\n\nFix 2 — src/DbUtils.php\n\nAdd fallback when glpiactiveentities_string is empty:\n\n## Environment\n\n- GLPI 11.0.4 (Docker container)\n- The bug affects all automatic execution of the certificate cron task\n- Manual execution via the web interface works correctly because the session is properly initialized for authenticated users\n- The --allow-superuser CLI flag does not fix the issue\n\n## Verification\n\nAfter applying both patches, the cron task executes successfully:\nAction completed, fully processed with Number: 1\n\nOriginal response date: 2026-06-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4588659193, "author": "ewertonmuller", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24357#issuecomment-4588659193", "createdAt": "2026-06-01T00:13:26Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hi, maybe try if that fix:\n\nOriginal response date: 2026-06-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4610234103, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24357#issuecomment-4610234103", "createdAt": "2026-06-03T07:55:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24357, "url": "https://github.com/glpi-project/glpi/issues/24357", "author": "ewertonmuller", "anonymizedAuthorEmail": "harper.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-05-28T02:06:00Z", "updatedAt": "2026-06-15T06:58:12Z", "closedAt": "2026-06-15T06:58:12Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Content-type header with parameters is not working.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7 (latest)\n\nIssue description:\nI am using the latest version of GLPI which is 11.0.7 and facing issue related to Content-Type=\"application/json; charset=utf8\" is not being supported for the API request. It seems like in below PR which target 11.0.8, and this issue is fixed. Can I get an idea when 11.0.8 is going to publish as latest version.", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "fixed by #24387\n\nOriginal response date: 2026-06-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4669024391, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24525#issuecomment-4669024391", "createdAt": "2026-06-10T10:15:18Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "The Issues section is for bug reports only, not questions. In the future, you may ask on the Forum.\nFor public release date goals, you can look at\n\nAdditionally, the fix is not very complex and can be applied manually if needed before the official release.\n\nOriginal response date: 2026-06-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4669041434, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24525#issuecomment-4669041434", "createdAt": "2026-06-10T10:17:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24525, "url": "https://github.com/glpi-project/glpi/issues/24525", "author": "shivamtestc2-sudo", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-10T10:07:47Z", "updatedAt": "2026-06-10T10:17:28Z", "closedAt": "2026-06-10T10:15:17Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Search on contracts times out", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nWe track contracts with glpi, when using the search glpi becomes unresponsive. Finally the php session times out.\nI think this was introduced by\nThis then leads to lasting side effects:\n- Other glpi pages are unreachable, during and even after the search timed out\n- Opening /front/contract.php triggers the search again\n\nOnly after ending the session by logging out and in again glpi gets into a working state again.\n\nAdditional context:\nDuring the error the apache process spikes to 100% cpu usage", "priority": "high", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "cameron.blair@peppermint.local", "text": "Seems linked to this PR #24274, there likely is a contract in your base with a 0 duration and/or periodicity marked as tacit renewal\n\nOriginal response date: 2026-06-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4590417324, "author": "troncoli", "anonymizedAuthorEmail": "cameron.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24386#issuecomment-4590417324", "createdAt": "2026-06-01T07:26:47Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "Cameron Blair applying PR #24274 in my test enviroment fixes the issue\n\nOriginal response date: 2026-06-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4591956010, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24386#issuecomment-4591956010", "createdAt": "2026-06-01T11:02:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24386, "url": "https://github.com/glpi-project/glpi/issues/24386", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "performance" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-29T10:09:25Z", "updatedAt": "2026-06-03T08:01:02Z", "closedAt": "2026-06-03T08:01:02Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Form can be submitted without required request type", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nA form can be submitted without selecting a request type.\nWhen a request type is selected, the ITIL category is correctly enforced as mandatory.\nHowever, when you do not select any type, the form can still be submitted.\n\n[Image omitted]\n\n[Image omitted]\n\nIn this case, the ticket has neither a category nor a request type.\nTo confirm the issue, I recreated the form from scratch, but the issue persists.\n\nReproduction steps:\n1. Create a new form from scratch\n2. Add a Request Type dropdown field\n3. Add an ITIL Category dropdown field\n4. Set both fields as required\n5. Configure the category field to be displayed only when the type is not empty\n6. Then save the form and submit it without selecting any value in the type field\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "kendall.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please test with the latest release.\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4583746000, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24360#issuecomment-4583746000", "createdAt": "2026-05-30T18:32:17Z" } }, { "userEmail": "kendall.bennett@peppermint.local", "text": "After updating GLPI, the problem no longer exists. Thank you !\n\nOriginal response date: 2026-06-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4602458379, "author": "LeoDef", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24360#issuecomment-4602458379", "createdAt": "2026-06-02T12:39:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24360, "url": "https://github.com/glpi-project/glpi/issues/24360", "author": "LeoDef", "anonymizedAuthorEmail": "kendall.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-28T07:12:57Z", "updatedAt": "2026-06-03T07:52:18Z", "closedAt": "2026-06-03T07:52:17Z" } }, { "title": "Mail collector fails to process attachments with malformed Content-Type header", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.7\n\nIssue description:\nHello,\n\nWe encountered an issue with the GLPI mail collector while processing emails modified by antivirus/security gateways.\n\nIn some cases, the MIME header becomes:\n\nContent-Type: =application/pdf;\n\ninstead of:\n\nContent-Type: application/pdf;\n\nWhen this happens, the attachment is not detected/imported correctly.\n\nFrom what we understood, this behavior seems related to the internal mail parsing library used by the collector, which does not fully tolerate malformed MIME headers.\n\nWe understand that the header itself is technically invalid. However, some mail systems or security appliances appear to generate such messages in real production environments.\n\nSo this may not be a bug strictly speaking, but we would appreciate your insight to better understand whether improving tolerance for this kind of malformed header could be considered or if there is a recommended workaround on our side.\n\nRegards\n\nReproduction procedure:\n1. Create an email containing a PDF attachment.\n\n2. Export the email as raw .eml source.\n\n3. Edit the MIME headers of the attachment section.\n\n4. Replace:\n\nContent-Type: application/pdf;\n\nwith:\n\nContent-Type: =application/pdf;\n\n5. Save the modified .eml file.\n\n6. Send/import the email through the GLPI mail collector.\n\n7. Observe that the attachment is no longer correctly detected/imported.\n\nEnvironment details:\nGLPI 10.0.7 standard, no plugin\n\nAdditional context:\nMany thanks!", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "We encountered an issue with the GLPI mail collector while processing emails modified by antivirus/security gateways.\n\nHave you identified which system is breaking emails? This seems more like an issue with those services as there is only so much GLPI or Laminas Mail can be expected to do with bad email data.\n\nWithout an actual example email source, I don't think there is any more we can do. Randomly adding characters to a working email is not a perfect recreation of the issue you are experiencing as there may be other factors in a real, broken email that gives more clues *how* it broke.\n\nOriginal response date: 2026-05-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4585171480, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24201#issuecomment-4585171480", "createdAt": "2026-05-30T23:43:33Z" } }, { "userEmail": "skyler.bennett@peppermint.local", "text": "Hi Connard,\n\n Yes, is in Laminas Mail, can you replace Laminas Library : ?\n\n it's Not random, I describe the probleme, you can reproduce the error :\n\nReproduction procedure\n\n Create an email containing a PDF attachment.\n\n Export the email as raw .eml source.\n\n Edit the MIME headers of the attachment section.\n\n Replace:\n\nContent-Type: application/pdf;\n\nwith:\n\nContent-Type: =application/pdf;\n\n Save the modified .eml file.\n\n Send/import the email through the GLPI mail collector.\n\n Observe that the attachment is no longer correctly detected/imported.\n\nOriginal response date: 2026-05-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4586212418, "author": "mentaloverflow", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24201#issuecomment-4586212418", "createdAt": "2026-05-31T08:46:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24201, "url": "https://github.com/glpi-project/glpi/issues/24201", "author": "mentaloverflow", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-05-11T16:55:34Z", "updatedAt": "2026-06-03T07:30:38Z", "closedAt": "2026-06-03T07:30:38Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "The tables on the home page (self-service) are not translated", "detail": "Contribution description:\nGood afternoon, everyone!\n\nI've identified an issue here, and I don't think it's a bug, but I'm suggesting it for future consideration if necessary:\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nI noticed that the shortcut cards that can be created for self-service users on the Home tab do not translate if the user is using a different language. I looked in the settings tab but couldn’t find an option to translate the card’s title and description.\n\nIf this feature wasn’t included in the current version, I’d like to suggest it. In multilingual environments, following the same logic of translating the form name itself as in GLPI 10, this could be useful.\n\nVersion: 11.0.7", "priority": "medium", "type": "support", "createdByEmail": "micah.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Non-form translations are under Setup > General > Helpdesk translations tab.\n\nOriginal response date: 2026-05-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4538388553, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24286#issuecomment-4538388553", "createdAt": "2026-05-26T00:23:36Z" } }, { "userEmail": "micah.bennett@peppermint.local", "text": "Oh, okay. I hadn't noticed that screen yet. Since it's in a different place and there's no notice about it, I didn't know there was this separate new setting.\n\nThanks.\n\nOriginal response date: 2026-05-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4544991573, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24286#issuecomment-4544991573", "createdAt": "2026-05-26T14:22:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24286, "url": "https://github.com/glpi-project/glpi/issues/24286", "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-05-22T20:50:38Z", "updatedAt": "2026-05-26T14:22:44Z", "closedAt": "2026-05-26T00:23:36Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Laminas mail receiver does not always import the attachments", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nTicket is created but attachments are missing if the e-mail header is not perfect. When i check the mail directly attachments are present. What can i do? Is there a way to change the praser?\n\nEnvironment details:\nGLPI: 11.0.5 ( => /var/www/html/glpi)\nInstallation mode: TARBALL\nCurrent language: hu_HU\n\nOperating system: Linux 5.15.0-125-generic #​135-Ubuntu SMP Fri Sep 27 13:53:58 UTC 2024 x86_64\n\nPHP: 8.3.23 apache2handler\n\nPHP extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium,\napache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext,\niconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem,\nsysvshm, tokenizer, xmlreader, xmlrpc, xmlwriter, xsl, zip, redis, Zend OPcache\n\nSetup: disable_functions=\"\" max_execution_time=\"30\" max_input_vars=\"1000\" memory_limit=\"128M\" post_max_size=\"8M\"\nsession.cookie_secure=\"0\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\"\nupload_max_filesize=\"100M\"\n\nWeb server: Apache/2.4.56 (Debian) (Apache/2.4.56 (Debian) Server at 10.90.5.14 Port 8015)\n\nUser agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36\n\nDatabase:\n\nServer Software: mariadb.org binary distribution\n\nServer Version: 11.2.6-MariaDB-ubu2204\n\nServer SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION\n\nParameters: glpi@glpi8014-mariadb/glpidb\n\nHost info: glpi8014-mariadb via TCP/IP\n\nRequirements:\nPHP version (8.3.23) is supported.PHP version (8.3.23) is supported.\nOS and PHP are relying on 64 bits integers.OS and PHP are relying on 64 bits integers.\nSessions configuration is OK.Sessions configuration is OK.\nAllocated memory is sufficient.Allocated memory is sufficient.\nFollowing extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer,\nxmlreader, xmlwriter.Following extensions are installed: dom, fileinfo, filter, libxml, simplexml, tokenizer, xmlreader,\nxmlwriter.\nmysqli extension is installedmysqli extension is installed\ncurl extension is installedcurl extension is installed\ngd extension is installedgd extension is installed\nintl extension is installedintl extension is installed\nmbstring extension is installedmbstring extension is installed\nzlib extension is installedzlib extension is installed\nbcmath extension is installedbcmath extension is installed\nThe constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.The constant\nSODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present.\nopenssl extension is installedopenssl extension is installed\nDatabase engine version (11.2.6) is supported.Database engine version (11.2.6) is supported.\nThe log file has been created successfully.The log file has been created successfully.\nWrite access to /var/www/html/glpi/files/_cache has been validated. Write access to\n/var/www/html/glpi/files/_cron has been validated. Write access to /var/www/html/glpi/files has been validated. Write access to\n/var/www/html/glpi/files/_graphs has been validated. Write access to /var/www/html/glpi/files/_lock has been validated. Write\naccess to /var/www/html/glpi/files/_pictures has been validated. Write access to /var/www/html/glpi/files/_plugins has been\nvalidated. Write access to /var/www/html/glpi/files/_rss has been validated. Write access to /var/www/html/glpi/files/_sessions\nhas been validated. Write access to /var/www/html/glpi/files/_tmp has been validated. Write access to\n/var/www/html/glpi/files/_uploads has been validated.Write access to /var/www/html/glpi/files/_cache has been validated.\nWrite access to /var/www/html/glpi/files/_cron has been validated.\nWrite access to /var/www/html/glpi/files has been validated.\nWrite access to /var/www/html/glpi/files/_graphs has been validated.\nWrite access to /var/www/html/glpi/files/_lock has been validated.\nWrite access to /var/www/html/glpi/files/_pictures has been validated.\nWrite access to /var/www/html/glpi/files/_plugins has been validated.\nWrite access to /var/www/html/glpi/files/_rss has been validated.\nWrite access to /var/www/html/glpi/files/_sessions has been validated.\nWrite access to /var/www/html/glpi/files/_tmp has been validated.\nWrite access to /var/www/html/glpi/files/_uploads has been validated.\n\nSessions configuration is secured.Sessions configuration is secured.\nexif extension is installedexif extension is installed\nldap extension is installedldap extension is installed\nFollowing extensions are installed: bz2, Phar, zip.Following extensions are installed: bz2,\nPhar, zip.\nZend OPcache extension is installedZend OPcache extension is installed\nFollowing extensions are installed: ctype, iconv, sodium.Following extensions are installed:\nctype, iconv, sodium.\nWrite access to /var/www/html/glpi/marketplace has been validated.Write access to\n/var/www/html/glpi/marketplace has been validated.\nTimezones seems loaded in database.Timezones seems loaded in database.", "priority": "medium", "type": "support", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please provide an EML file that can be used to reproduce and added to test suite.\n\nOriginal response date: 2026-02-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3907725623, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23127#issuecomment-3907725623", "createdAt": "2026-02-16T10:40:23Z" } }, { "userEmail": "elliot.bennett@peppermint.local", "text": "I try to ask one of our clients who send us that kind of e-mail-s with warnings to send another with no personal information.\n\nI can't reproduce it with my own e-mail client because it ads the relevant header. My production server got mails 600+ in day and about 10% of it has the mentioned warning. I can paste a mail details here with 3 attachments:\n\"\n*\n*\n*\n\nMIME-Version: 1.0\nFrom: User\nDate: Sat, 14 Feb 2026 10:35:37 +0100\nX-Gm-Features: AZwV_Qi-lBS40wT1H93x8A9f4dqz-jsXPAHVPyF7QmVGb6mYHFIhUh30eDMdCsE\nMessage-ID:\nSubject: =?UTF-8?B?RcO8Lm3FsWvDtmTDqXNpIGVuZ2Vkw6lseSBtZWfDumrDrXTDoXNhIGlyw6FudGkga8Opcg==?=\n =?UTF-8?B?ZWxlbQ==?=\nTo: [email redacted]\nContent-Type: multipart/mixed; boundary=\"0000000000003cb206064ac57232\"\nX-FE-Attachment-Name: =?UTF-8?B?QmVsZsO2bGRpIHV0YWzDoXMgXyBPVFAgSW50ZXJuZXRCYW5rIFRNxbFrw7Zkw6lzaSBrw6FydHlhIG1lZ8O6asOtdMOhcy5odG1s?=,\n =?UTF-8?B?S8OpcC5qcGc=?=, =?UTF-8?B?S8OpcCAoMikuanBn?=\nX-FEAS-SPF: spf-result=pass, ip=209.85.218.42, helo=mail-ej1-f42.google.com, mailFrom=s*@gmail.com\nX-FEAS-DKIM: Valid\nX-FEAS-Client-IP: 209.85.218.42\nX-FE-Last-Public-Client-IP: 209.85.218.42\nX-FE-Envelope-From: s*@gmail.com\nX-FEAS-Content-Modification: html remove active content\nX-FE-Policy-ID: 1:1:1:*.*.*\nReturn-Path: s*@gmail.com\nX-MS-Exchange-Organization-Network-Message-Id: 8e471a96-e56f-4c1e-6cc7-08de6bac70ee\nX-MS-Exchange-Organization-AVStamp-Enterprise: 1.0\nX-MS-Exchange-Organization-AuthSource: Domain\nX-MS-Exchange-Organization-AuthAs: Anonymous\nX-MS-Exchange-Transport-EndToEndLatency: 00:00:03.3783519\nX-MS-Exchange-Processed-By-BccFoldering: 15.02.2562.028\n\nOriginal response date: 2026-02-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3907812952, "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23127#issuecomment-3907812952", "createdAt": "2026-02-16T10:59:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23127, "url": "https://github.com/glpi-project/glpi/issues/23127", "author": "chiwbicka1", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-16T10:07:52Z", "updatedAt": "2026-05-21T13:11:12Z", "closedAt": "2026-05-21T13:11:08Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Problem with the (native) form migrated from FormCreator", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11\n\nIssue description:\nHello,\nI just migrated from GLPI 10.0.18 to GLPI 11.0.6. I downloaded the latest version of FormCreator compatible with GLPI 11. Then I migrated all my forms to the native form functionality. However, on one form, when I want to change the title, the changes are applied correctly, but when I preview it, it still has the settings from before my changes. The same thing happens on the user interface; the changes aren't applied. Yet my changes are saved. I also uninstalled FormCreator after migrating to make sure the problem wasn't caused by that plugin.\n\nI have the impression it's getting the information from somewhere else, but where?\n\nEnvironment details:\nOS: ubuntu 2404 LTS\nweb server: Apache\nphp version 8.3\nmariabd 10.11.14", "priority": "medium", "type": "support", "createdByEmail": "avery.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "avery.blair@peppermint.local", "text": "Hello,\nIt seems likely this is related to the translation into different languages ​​in the form. Is this behavior normal?\n\nOriginal response date: 2026-04-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4352523887, "author": "Azgar1998", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24079#issuecomment-4352523887", "createdAt": "2026-04-30T12:40:39Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Yes, If a translated title exist in the target language of the user viewing the form then he will see it instead of the title.\n\nCan you delete the translations if you don't need them.\n\nOriginal response date: 2026-05-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4385903153, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24079#issuecomment-4385903153", "createdAt": "2026-05-06T07:20:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24079, "url": "https://github.com/glpi-project/glpi/issues/24079", "author": "Azgar1998", "anonymizedAuthorEmail": "avery.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-30T10:31:40Z", "updatedAt": "2026-05-06T07:20:15Z", "closedAt": "2026-05-06T07:20:15Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "\"Direct access\" links to forms do not redirect unauthenticated users to the original URL once they log in", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen setting a Form to \"Allow direct access\", the URL provided does not redirect the user to the login page if they are not authenticated.\n\nFor example, if a user is given a generated URL (in our example upon visiting that address they are greeted with a \"You don't have permissions to perform this action\" message with a link to \"Return to previous page\". Clicking that link does send them to the login page, however it is the base URL of the site ( with no redirection facility.\n\nExpected behaviour\nIf an unauthenticated user goes to any other page in GLPI (for example they are presented with an \"Error Your session has expired. Please log in again.\" message with a \"Log in again\" button (at URL Clicking the button takes them to the login page at address . Once they login they are then redirected to the page they initially tried to access.\n\nWorkaround\nA URL to mimic this functionality can manually be created by crafting an address such as (in this example):\n\nHowever this introduces a manual step and can easily lead to errors.\n\nAffected page:\n\nReproduction steps:\nTo reproduce the error\n1. In GLPI as admin go to Administration / Forms and choose any form (or create one).\n2. In the Access Controls tab enable \"Allow Direct Access\". Do not set \"Allow unauthenticated users\". Click Save changes.\n3. Copy the URL and open an In Cognito window. Visit the copied URL and you will get a \"You don't have permission to perform this action\" message. 4. Click the \"Return to previous page\" link.\n5. Enter your login details at the login page and authenticate.\n6. You will be presented with your default landing page, not the initial page you were trying to access.\n\nTo reproduce desired functionality\n1. While logged in to GLPI, copy any other internal URL (such as My Settings, ie\n2. In an In Cognito window, go to the copied URL.\n3. You will be presented with a \"Your session has expired\" message. Click the \"Log in again\" button.\n4. Enter your login details at the login page and authenticate.\n5. You will be redirected to the page you initially requested.", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "11.0.4 is outdated. Please try if you reproduce with latest stable release and no plugins.\n\nOriginal response date: 2026-04-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4311250920, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24001#issuecomment-4311250920", "createdAt": "2026-04-24T06:51:48Z" } }, { "userEmail": "hayden.bennett@peppermint.local", "text": "Hi there, I can confirm that updating to 11.0.7 has resolved the issue.\n\nMany thanks!\n\nOriginal response date: 2026-04-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4344447115, "author": "stcithelpdesk", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24001#issuecomment-4344447115", "createdAt": "2026-04-29T14:02:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24001, "url": "https://github.com/glpi-project/glpi/issues/24001", "author": "stcithelpdesk", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-24T06:49:26Z", "updatedAt": "2026-04-29T14:02:21Z", "closedAt": "2026-04-29T14:02:21Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Text Editor for Change Body Not Working Properly", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nCreate a change.\nSet some text in the body to a color.\nsave the change.\ngo back into the change.\nChange the text color to something else.\nre-save teh change.\ngo out of the change and then back in.\nThe color of the text isnt saved.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "hayden.blair@peppermint.local", "text": "The same applies to bolding of text.\n\nOriginal response date: 2026-04-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4328302764, "author": "bturnbough81", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24028#issuecomment-4328302764", "createdAt": "2026-04-27T15:33:46Z" } }, { "userEmail": "taylor.adler@peppermint.local", "text": "I cannot recreate the issue. Please include the information requested in the bug report template including the relevant log output and GLPI setup information. For this issue, there may be relevant messages in the browser console too (F12 key > Console tab) when performing these actions.\n\nOriginal response date: 2026-04-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4328334357, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24028#issuecomment-4328334357", "createdAt": "2026-04-27T15:38:19Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24028, "url": "https://github.com/glpi-project/glpi/issues/24028", "author": "bturnbough81", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-27T15:31:13Z", "updatedAt": "2026-04-28T07:27:35Z", "closedAt": "2026-04-27T16:01:11Z" } }, { "title": "GraphQL RSQL Filter Errors", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nnightly 11.0-6f44052\n\nIssue description:\nWe had problems with GraphQL in the stable version 11.0.6 so we are testing the nightly build of 11.0.7 right now an found a problem with the RSQL filters. We get \"internal server error\" whenever we filter for location.completename in any way\n\nThis query below works without any problems:\n\nBut when we filter for location.completename we get an error in return. This query:\n\nReturns with HTTP 200 OK and this content:\n\nUnfortunately there were no helpful messages in the logs.", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Please try with #23852 or wait for the next nightly release 😉\n\nAlso when your RSQL filter values have spaces or any characters with special meaning in RSQL like ;, make sure you quote them to be safe:\nComputer(filter: \"location.completename=='DC01 > Rack 2.05'\") {\n\nOriginal response date: 2026-04-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4251191001, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23882#issuecomment-4251191001", "createdAt": "2026-04-15T10:18:32Z" } }, { "userEmail": "dakota.blair@peppermint.local", "text": "Yes, it works with the newest nightly version (11.0-1355f4e), thx :)\n\nOriginal response date: 2026-04-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4258530434, "author": "tst-plutex", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23882#issuecomment-4258530434", "createdAt": "2026-04-16T08:32:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23882, "url": "https://github.com/glpi-project/glpi/issues/23882", "author": "tst-plutex", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api", "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-15T09:49:51Z", "updatedAt": "2026-04-16T08:32:20Z", "closedAt": "2026-04-16T08:32:20Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "SNMP v3 credentials edit", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWhen I create an SNMP v3 credentials, all is good.\nWhen I want to edit (and make no change, but click \"Save\") the credentials, the first time, I get no error but the authentication stops working. The second time, I get\n[Image omitted]\n\nIt looks like the pass field are replaced by a placeholder to display all the dots but the place holder is written in the DB.", "priority": "medium", "type": "support", "createdByEmail": "bailey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "elliot.bennett@peppermint.local", "text": "Hi,\n\nI was testing another issue and I can confirm that bug.\n\nMore accurately, I checked what was stored in database before and after the edit and what was sent to glpi-agent.\n\nIf I only update one of the authentication password or protocol password, this one is updated, and I see it correctly sent to agent. But the one not updated in the form during the edit seems now different, for example, in a test it was 1234567890 and became dH1xFGXT+gskJo2zOOTLplDzsXjSG4LiGYqj0liNLHN2FPOqnqMJhyrZrO2RrS9XgtI=.\n\nIf I update the 2 passwords, the right data is sent to the agent for the 2 passwords.\n\nOriginal response date: 2026-04-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4243581080, "author": "g-bougard", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23843#issuecomment-4243581080", "createdAt": "2026-04-14T11:40:24Z" } }, { "userEmail": "bailey.blair@peppermint.local", "text": "Thank you guys !! :-)\n\nOriginal response date: 2026-04-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4257839609, "author": "J-C-P", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23843#issuecomment-4257839609", "createdAt": "2026-04-16T06:35:13Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23843, "url": "https://github.com/glpi-project/glpi/issues/23843", "author": "J-C-P", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-13T10:42:57Z", "updatedAt": "2026-04-16T06:35:13Z", "closedAt": "2026-04-16T06:28:14Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Error upload image (screenshot) on richtext zone", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.6\n\nIssue description:\nError in php :\n\n[2026-04-14 10:17:42] glpi.CRITICAL: * Uncaught PHP Exception TypeError: \"Safe\\preg_replace_callback(): Argument #2 ($callback) must be of type callable, array given, called in ./src/UploadHandler.php on line 693\" at pcre.php line 716\n Backtrace :\n ...hecodingmachine/safe/generated/8.3/pcre.php:716\n ./src/UploadHandler.php:693 Safe\\preg_replace_callback()\n ./src/UploadHandler.php:734 UploadHandler->upcount_name()\n ./src/UploadHandler.php:869 UploadHandler->get_unique_filename()\n ./src/UploadHandler.php:1335 UploadHandler->get_file_name()\n ./src/UploadHandler.php:1793 UploadHandler->handle_file_upload()\n ./src/GLPIUploadHandler.php:63 UploadHandler->post()\n ./ajax/fileupload.php:40 GLPIUploadHandler::uploadFiles()\n ...Glpi/Controller/LegacyFileLoadController.php:64 require()\n ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\\Controller\\LegacyFileLoadController->invoke()\n ./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n ./vendor/symfony/http-kernel/Kernel.php:208 Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n ./public/index.php:71 Symfony\\Component\\HttpKernel\\Kernel->handle()", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "casey.blair@peppermint.local", "text": "Temporarily\n\ni modify UploadHandler.php on line 693\n\nand unactivate unlink because i have this error too\n\nOriginal response date: 2026-04-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4242585277, "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23856#issuecomment-4242585277", "createdAt": "2026-04-14T08:54:58Z" } }, { "userEmail": "jordan.blair@peppermint.local", "text": "Hi Casey Blair thanks for the report. Can you please provide me an exact scenario for reproducing in GLPI ?\n\n- Page / URL - field\n- Action\n\nOriginal response date: 2026-04-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4245215817, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23856#issuecomment-4245215817", "createdAt": "2026-04-14T15:40:30Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23856, "url": "https://github.com/glpi-project/glpi/issues/23856", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-14T08:50:04Z", "updatedAt": "2026-04-15T07:53:12Z", "closedAt": "2026-04-15T07:53:12Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Service catalog forms are not sorted alphabetically", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nIn the Service Catalog, the forms are not sorted in alphabetical order.\n\nExpected behavior:\nForms should be displayed in alphabetical order to make them easier to find.\n\nActual behavior:\nForms appear in a non-alphabetical order.\n\nReproduction steps:\n1. Go to the Service Catalog in GLPI.\n2. Open the list of available forms.\n3. Check the displayed order of the forms.\n4. Notice that the forms are not sorted alphabetically.\n\nEnvironment details:\nGLPI version: 11.0.6", "priority": "medium", "type": "support", "createdByEmail": "devon.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "devon.bennett@peppermint.local", "text": "[Image omitted]\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4140817469, "author": "Killian-Aidalinfo", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23653#issuecomment-4140817469", "createdAt": "2026-03-27T07:52:59Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Devon Bennett,\n\nI've tried to reproduce your issue using the same form names as you but the order appear to be correct on my side:\n\n[Image omitted]\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4141057542, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23653#issuecomment-4141057542", "createdAt": "2026-03-27T08:45:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23653, "url": "https://github.com/glpi-project/glpi/issues/23653", "author": "Killian-Aidalinfo", "anonymizedAuthorEmail": "devon.bennett@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-27T07:50:36Z", "updatedAt": "2026-04-15T07:29:02Z", "closedAt": "2026-04-15T07:29:02Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Can't delete a ticket", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWe can't delete a ticket from the button present at bottom of a ticket:\n[Image omitted]\n\nOtherwise if we select ticket on the list of tickets we can do that.\n\nAffected page:\n\nReproduction steps:\n1. Open a ticket\n2. Delete a ticket", "priority": "medium", "type": "support", "createdByEmail": "dakota.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Hello, cannot reproduce with no more details. Please check if any plugins or other parameters may interfere.\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4235147896, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23841#issuecomment-4235147896", "createdAt": "2026-04-13T09:01:24Z" } }, { "userEmail": "dakota.blair@peppermint.local", "text": "For an unknown reason, and after disabling/re-enabling the plugins again, completely clearing cookies, and even changing the language for the demo, the problem has not reappeared.\nI am closing this bug issue; sorry for the inconvenience.\n\nOriginal response date: 2026-04-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4235287938, "author": "efpbe", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23841#issuecomment-4235287938", "createdAt": "2026-04-13T09:22:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23841, "url": "https://github.com/glpi-project/glpi/issues/23841", "author": "efpbe", "anonymizedAuthorEmail": "dakota.blair@peppermint.local", "assignees": [], "labels": [ "need feedback" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-13T07:13:09Z", "updatedAt": "2026-04-13T09:22:58Z", "closedAt": "2026-04-13T09:22:58Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Knowledgebase revison comparison overflows", "detail": "Affected version:\n10.0.16\n\nIssue description:\nWhen comparing two revisions the resulting change can overflow the modal-body resulting in the following view:\n\nReproduction steps:\n1. Go to knwoledgebase\n2. create a new article and save\n3. enter a long text line\n4. compare the revisions", "priority": "medium", "type": "bug", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The bug is back in 11.0.5\n\nOriginal response date: 2026-02-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3887607190, "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/17773#issuecomment-3887607190", "createdAt": "2026-02-11T22:35:54Z" } }, { "userEmail": "skyler.adler@peppermint.local", "text": "Open a new ticket with all requested info.\n\nOriginal response date: 2026-02-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3888945828, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/17773#issuecomment-3888945828", "createdAt": "2026-02-12T06:35:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 17773, "url": "https://github.com/glpi-project/glpi/issues/17773", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [ "bug", "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2024-09-02T13:13:14Z", "updatedAt": "2026-02-12T06:35:31Z", "closedAt": "2024-10-04T07:13:50Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Email is not sent (using gmail)", "detail": "Issue description:\nDears,\nI'm going crazy, because i configured in many ways the gmails SMTP in GLPI. but no email is sent when create a incident or request. All emails stays in queue, but not sent automatically.\nI'm able to send them manually, but is not the right way.\n\nin the queuedmail, I've tried all ways, but nothing. So far I let it as it:\n\nIn Adminitration-->email Queue, i see that all messages are there:\n\nmanually, works fine, and I see in my inbox, the emails. But the idea is that the user, will be able to create an incindent or request, and after pressing the SUBMIT button, receive a notification.\n\nI had open my IMAP in my gmail account.\ni've tried with the last version and also with version 0.8.5.5, but the email sending is not working.\n\nCan somebody help me with this to make it work and send automatically a notification email ?\nIs there some rule i'm forgetting? I'm using GLPI as it, just 1 user to create test ticktes, and the glpi users, to manage configuration.\n\nI didn't create any new element.\n\nThanks", "priority": "medium", "type": "support", "createdByEmail": "jordan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "morgan.blair@peppermint.local", "text": "Thanks You , It work times zone error and fix it\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3776025635, "author": "AungShwe2002", "anonymizedAuthorEmail": "morgan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/774#issuecomment-3776025635", "createdAt": "2026-01-21T03:59:59Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 774, "url": "https://github.com/glpi-project/glpi/issues/774", "author": "lcoria", "anonymizedAuthorEmail": "jordan.adler@peppermint.local", "assignees": [], "labels": [ "help wanted" ], "state": "closed", "stateReason": "completed", "createdAt": "2016-06-30T19:23:50Z", "updatedAt": "2026-01-21T06:54:07Z", "closedAt": "2017-08-23T02:55:06Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Requester gets emailed once per mentioned person in a followup", "detail": "Affected version:\n10.0.12\n\nIssue description:\nWhen a requester creates a ticket and the followup / answer mentions people, requester gets 1 e-mail per mentioned people. E-mail contents are the same for every e-mail. In addition there's going to be one extra e-mail, because the ticket has received an update.\n\nAffected page:\nfront/ticket.form.php\n\nReproduction steps:\n1. Create a ticket\n2. Add a followup and in the followup mention people.\n3. Observe that ticket requestor now receives a number of e-mails: 1 e-mail because the ticket has received a followup, and 1 e-mail per person mentioned in the followup. For example if there were 3 people mentioned in the followup, requester receives now 4 e-mails.\n\nEnvironment details:\nGLPI 10.0.12 ( => /var/www)\nInstallation mode: TARBALL\nCurrent language:en_GB\nPlugins list\nfields Name: Additional fields Version: 1.21.6 State: Enabled\nglpiinventory Name: GLPI Inventory Version: 1.3.4 State: Enabled\ngenericobject Name: Objects management Version: 2.14.8 State: Enabled\n\nAdditional context:\nPerhaps related to #16767 , #12773 ?", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.bennett@peppermint.local", "text": "Adding a followup here, as the problem does persist. I'd add to the original problem though. The same problem exists when I'm technician too.\nCurrently on latest 10.0.25 version.\n\nOriginal response date: 2026-06-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4723676378, "author": "AldarisPale", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/16781#issuecomment-4723676378", "createdAt": "2026-06-16T21:09:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 16781, "url": "https://github.com/glpi-project/glpi/issues/16781", "author": "AldarisPale", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [ "stale" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2024-03-14T16:19:14Z", "updatedAt": "2026-06-16T21:09:56Z", "closedAt": "2025-03-03T08:26:39Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Satisfaction surveys don't close after due date", "detail": "Issue description:\n* Steps to reproduce (which actions have you made) :\n\nI have configured the satisfaction surveys by the following:\n- Configuring the satisfaction survey - External Survey\n- Create survey after - As soon as possible\n- Rate to Trigger Survey - 70%\n- Duration of survey - 4 days\n- For tickets closed after - 21-05-2018 12:00\n- URL - A Google Forms URL\n\n* Expected result :\n- As I don't use internal surveys, the system can't get to know when the user has answered the survey.\n- As a result, the satisfaction surveys keeps being shown on the home page of every user which has surveys opened.\n- It should disappear after 4 days\n\n* Actual result :\n- The surveys seem not close anytime.\n\n* URL of the page :\n\n* Screenshot of the problem (if pertinent) :\n\n* Your GLPI setup (you can find it in Setup > General menu, System tab) :\n\nInformation about system installation & configuration\n--\n[code]   GLPI 9.2.3 ( => /var/www/html/producao) Installation mode: TARBALL\n\nOperating system: Linux ip-172-31-2-143 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 PHP 7.0.27-0+deb9u1 apache2handler (Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, apc, apcu, bz2, calendar, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, imap, json, ldap, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_mysql, posix, readline, session, shmop, snmp, soap, sockets, standard, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib) Setup: max_execution_time=\"30\" memory_limit=\"128M\" post_max_size=\"8M\" safe_mode=\"\" session.save_handler=\"files\" upload_max_filesize=\"2M\" Software: Apache/2.4.25 (Debian) Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 Server Software: Debian 9.1 Server Version: 10.1.26-MariaDB-0+deb9u1 via UNIX socket mysqli extension is installed ctype extension is installed fileinfo extension is installed json extension is installed mbstring extension is installed zlib extension is installed curl extension is installed gd extension is installed simplexml extension is installed xml extension is installed ldap extension is installed imap extension is installed Zend OPcache extension is installed APCu extension is installed xmlrpc extension is installed /var/www/html/producao/config : OK /var/www/html/producao/files : OK /var/www/html/producao/files/_dumps : OK /var/www/html/producao/files/_sessions : OK /var/www/html/producao/files/_cron : OK /var/www/html/producao/files/_graphs : OK /var/www/html/producao/files/_lock : OK /var/www/html/producao/files/_plugins : OK /var/www/html/producao/files/_tmp : OK /var/www/html/producao/files/_cache : OK /var/www/html/producao/files/_rss : OK /var/www/html/producao/files/_uploads : OK /var/www/html/producao/files/_pictures : OK /var/www/html/producao/files/_log : OK Web access to files directory is protected : OK\n\nhtmLawed version 1.2.4 in (/var/www/html/producao/lib/htmlawed) phpCas version 1.3.5 in (/var/www/html/producao/vendor/jasig/phpcas/source) PHPMailer version 5.2.26 in (/var/www/html/producao/vendor/phpmailer/phpmailer) SimplePie version 1.5.1 in (/var/www/html/producao/vendor/simplepie/simplepie/library) TCPDF version 6.2.16 in (/var/www/html/producao/vendor/tecnickcom/tcpdf) michelf/php-markdown in (/var/www/html/producao/vendor/michelf/php-markdown/Michelf) true/punycode in (/var/www/html/producao/vendor/true/punycode/src) iacaml/autolink in (/var/www/html/producao/vendor/iamcal/lib_autolink) sabre/vobject in (/var/www/html/producao/vendor/sabre/vobject/lib)\n\nNot active\n\nfields Name: Campos adicionais Version: 1.6.0 State: Not activated behaviors Name: Comportamental Version: 2.0.0 State: Enabled fusioninventory Name: FusionInventory Version: 9.2+1.0 State: Enabled pdf Name: Imprimir em PDF Version: 1.3.0 State: Enabled showloading Name: Mostrar Carregamento Version: 1.0.0 State: Enabled os Name: OS Version: 0.0.8 State: Not activated dashboard Name: Painel Version: 0.9.0 State: Enabled reports Name: Relatórios Version: 1.11.0 State: Enabled renamer Name: Renamer Version: 0.90-1.0 State: Enabled telegrambot Name: TelegramBot Version: 2.0.0 State: Enabled\n[/code]", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jamie.blair@peppermint.local", "text": "Hello, Skyler Adler\n\nIs there a definitive (official) solution planned for this issue, or is the only way to resolve it still through direct database changes as mentioned by Arthur?\n\nThank you.\n\nOriginal response date: 2026-03-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3984334280, "author": "serviceticst", "anonymizedAuthorEmail": "jamie.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/4192#issuecomment-3984334280", "createdAt": "2026-03-02T13:16:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 4192, "url": "https://github.com/glpi-project/glpi/issues/4192", "author": "arthurrschaefer", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2018-06-19T12:14:47Z", "updatedAt": "2026-03-02T13:22:25Z", "closedAt": "2018-09-17T12:54:27Z" } }, { "title": "GLPI 11 password reset", "detail": "Affected version:\nGLPI 11\n\nIssue description:\nAfter creating a new user if you change the password a password 'pupup' is shown. The popup does not have a ' submit' button. If the alter password is confirmed by pressing enter various depr errors are shown and a type error (passing null instead of string).\n\nI expect the error is caused only after initial creation of the user (when there is no history)\n\nAffected page:\n\nReproduction steps:\nJust change the password. also test known errors like password not the same, to short, etc.", "priority": "medium", "type": "bug", "createdByEmail": "taylor.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.bennett@peppermint.local", "text": "Think this one is fixed as well ill close it\n\nOriginal response date: 2025-11-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3479897874, "author": "DonutsNL", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19373#issuecomment-3479897874", "createdAt": "2025-11-03T10:44:15Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 19373, "url": "https://github.com/glpi-project/glpi/issues/19373", "author": "DonutsNL", "anonymizedAuthorEmail": "taylor.bennett@peppermint.local", "assignees": [], "labels": [ "beta / rc", "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-04-07T09:11:08Z", "updatedAt": "2026-02-12T00:39:04Z", "closedAt": "2025-11-03T10:44:26Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "receiver to specific entity", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.5\n\nIssue description:\nHello,\n\nI also created a rule for tickets generated by the mail receiver to assign the ticket to a specific entity based on the requester's email address domain.\n\nIn addition, I created a mail receiver and enabled the option to automatically create users from the email address. However, the user is created in the root entity and does not have permissions on the sub-entity.\n\nTo address this, I configured a user assignment (habilitation) rule to grant permissions to the user, but it does not work as expected.\n\nCould you please advise how to automatically assign the correct entity and permissions to users created from incoming emails?\n\nThank you.\n\nEnvironment details:\nConfigure a mail receiver in GLPI.\n\nEnable the option \"Automatically create users from email addresses\".\n\nCreate a rule for tickets generated by the mail receiver to assign the ticket to a specific entity based on the requester's email domain.\n\nCreate a user assignment (habilitation) rule intended to grant permissions to users based on their email domain.\n\nSend an email from a new external email address (for example: [[email redacted]](mailto:[email redacted])) to the configured support mailbox.", "priority": "low", "type": "feature", "createdByEmail": "kendall.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Mail receiver creates user in the root entity, no option is possible.\nRules to assign a user to an entity is restricted to user using external authentication.\n\nI did not find a way to achieve this.\n\nThis is not a bug. You have to request the implementation of a feature.\n\nOriginal response date: 2026-04-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4169878501, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23344#issuecomment-4169878501", "createdAt": "2026-04-01T12:50:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23344, "url": "https://github.com/glpi-project/glpi/issues/23344", "author": "Lmaquaire92", "anonymizedAuthorEmail": "kendall.adler@peppermint.local", "assignees": [], "labels": [ "feature suggestion", "mail collector", "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-04T08:29:15Z", "updatedAt": "2026-07-11T00:41:57Z", "closedAt": "2026-04-01T12:55:59Z" } }, { "title": "HLAPI Missing dropdown endpoints (ComputerType, Manufacturer etc.)", "detail": "Affected version:\n11\n\nLegacy API (Working):\n- ✅ GET /apirest.php/ComputerType - Returns computer types\n- ✅ GET /apirest.php/Manufacturer - Returns manufacturers\n\nHLAPI v2 (Not Working):\n- ❌ GET /api.php/v2/Dropdowns/ComputerType - Returns 404 Not Found\n- ❌ GET /api.php/v2/Dropdowns/Manufacturer - Returns 404 Not Found\n- ❌ GET /api.php/v2/Assets/ComputerType - Returns 404 Not Found\n- ❌ GET /api.php/v2/Assets/Manufacturer - Returns 404 Not Found\n\nExpected behavior:\nThe HLAPI should provide equivalent endpoints for accessing dropdown resources that were available in the Legacy API, particularly:\n- Computer types should be accessible via /api.php/v2/Dropdowns/ComputerType\n- Manufacturers should be accessible via /api.php/v2/Dropdowns/Manufacturer\n\nAnalysis:\nLooking at the DropdownController source code (src/Glpi/Api/HL/Controller/DropdownController.php), the getRawKnownSchemas() method currently only defines schemas for:\n- Location\n- State\n- Manufacturer (schema exists but endpoint not working)\n- Calendar\n\nHowever, ComputerType is completely missing from the schemas, and despite Manufacturer having a schema definition, the endpoint returns 404.\n\nAdditional Issues:\n1. Swagger Documentation: The /Dropdowns endpoints are not appearing in the OpenAPI/Swagger documentation, making it difficult for developers to discover available dropdown endpoints.\n\n2. Inconsistent Implementation: While Manufacturer has a schema defined in DropdownController, the endpoint is not functional, suggesting a routing or implementation issue.", "priority": "medium", "type": "support", "createdByEmail": "sage.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I'm going to close this issue. It is a little too close to \"finish the HLAPI\" and there have been hundreds of new schemas and endpoints added since the issue was created. Although it isn't feature complete, I believe the vast majority of the dropdown schemas/endpoints and the majority of use cases have been addressed. For everything else, I have a script I run to see which GLPI tables currently don't have schemas and can infer from that which are missing endpoints.\n\nIf there are needed endpoints that are missing where a schema exists or other related endpoints exist, and it isn't already done in a pending PR or a temporary staging branch like feature/hlapi-v2.3, feel free to open an issue for those specifically.\n\nFor reference, there are a few things which I don't see making progress any time soon because of various levels of issues with the feature code:\n- Forms\n- Dashboards (only partially implemented right now)\n- Impact Analysis\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4047244721, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20827#issuecomment-4047244721", "createdAt": "2026-03-12T14:33:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20827, "url": "https://github.com/glpi-project/glpi/issues/20827", "author": "RomainLvr", "anonymizedAuthorEmail": "sage.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-08-28T14:58:46Z", "updatedAt": "2026-06-21T01:13:14Z", "closedAt": "2026-03-12T14:33:34Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI Mobile App", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11\n\nIssue description:\nI’m trying to use the GAPP third-party application with GLPI Self-Service, but it doesn’t seem to be working.\n\nI’m currently running GLPI 11, and I’ve installed GappEssentials 3.0, which appears to be the latest version available on both GitHub releases and the plugin marketplace. I’ve already tried reinstalling it multiple times, clearing the cache, and restarting the server, but no luck so far.\n\nI keep getting the error message: “GappEssentials is outdated. Please upgrade to the latest version,” even though I’m already using the latest version.", "priority": "medium", "type": "support", "createdByEmail": "cameron.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I am not sure any of this could be related to GLPI itself. You should try directing your report to TICGAL on the gappessentials GitHub or somewhere else.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4144532395, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23662#issuecomment-4144532395", "createdAt": "2026-03-27T18:41:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23662, "url": "https://github.com/glpi-project/glpi/issues/23662", "author": "aayush1108", "anonymizedAuthorEmail": "cameron.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-27T17:38:59Z", "updatedAt": "2026-07-09T00:48:42Z", "closedAt": "2026-03-30T08:23:29Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Odd behavior on Notifications table sort", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen sorting the Notifications table by \"Type\" column in Portuguese-Brazil, it creates an odd behavior: the letter \"C\" [Chamados] (Tickets) appears on the 4th page when sorting.\n\nI do believe it happens because the sort is made by the English name (Tickets) instead of the name of the column in the GLPI user language.\n\nAffected page:\n\nReproduction steps:\n1. Change GLPI language to Portuguese-Brazil\n2. Go to Setup > Notifications > Notifications\n3. Go to 4th page\n4. Sort by \"Type\" column", "priority": "low", "type": "feature", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Sorting always happens on raw data in the database. Translations are done once the data is fetched. Changing this would probably involve a significant change on the search code. The same behavior could be seen on other columns. The sort functionality should remain though as it is useful to group the results.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4139360804, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22711#issuecomment-4139360804", "createdAt": "2026-03-27T01:13:15Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22711, "url": "https://github.com/glpi-project/glpi/issues/22711", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-16T20:56:49Z", "updatedAt": "2026-07-06T00:53:37Z", "closedAt": "2026-03-27T01:13:36Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "The loading of templates does not work through the simplified interface.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0..6\n\nIssue description:\nHi,\nThe loading of templates does not work through the simplified interface. Two user cases:\n-if i create a new ticket with the simplied interface (self service profil) . The ticket template don't loading (the page isn't not refresh )\n-if i choose an itil categorie same behavior no loading no refresh of the page\n\nWith the same user ,profil but with the standard interface is working.\n\nI use the version 11.0.6 and php 8.2 (if it does matter) with GLPI 10.0.24 i don't have this issue.\n\nThanks", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Simplified interface users don't create tickets directly anymore. In GLPI 11, the Form Creator plugin features were integrated with two default forms being created for you, and Forms do not use templates directly. You can customize Forms under Administration > Forms and control when questions are visible, add/change/remove questions, and control how the ticket is created from the submission of the form.\n\nOriginal response date: 2026-03-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4078950418, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23511#issuecomment-4078950418", "createdAt": "2026-03-18T01:00:52Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23511, "url": "https://github.com/glpi-project/glpi/issues/23511", "author": "gpiera", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-17T14:33:25Z", "updatedAt": "2026-06-27T01:01:19Z", "closedAt": "2026-03-18T08:02:16Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Problem with adding assets and modyfing datacenter, server room and racks", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI cannot organize my device in GLPI, especially switches, servers, and other infrastructure components mounted in rack cabinets.\n\nI created rack cabinets in GLPI and add to them equipment such as switches, servers, UPS devices, and patch panels, cables and pasive deive. The goal was to organize the infrastructure in such a way that, from the device view, it is immediately possible to see where the device is physically installed. Like on screenshot\n\n[Image omitted]\n\nso i want manage it such like this\nData center as the infrastructure location within a given company / entity,\nServer room as technical rooms or points where servers or local rack cabinets are located,\nRacks as the actual cabinets in which the devices are installed.\n\nThe purpose is to make the exact placement of a device automatically visible once it is mounted in a rack, for example in the Data center position field on the device form, as shown in the attached screenshot.\n\nProblem\n\nIn practice, there is a problem with building this structure. After creating a Data center, it is not possible to assign an already existing Server room to it. A new server room can only be created directly from the Data center, but an existing one cannot be attached.\n\nSimilarly, if I already have existing rack cabinets configured and described, with switches, servers, UPS devices, or patch panels already assigned to them, I cannot later integrate them into the structure:\n\nDatacenter > Server room > Rack ( cant add existing servers room to datacenter or rack to server rooms)\n\ni have 10 Racks descibed and dont want to delete them. its possiblo modyfy data center, server rooms to add existing racks or other staff? another solution is to show in palce Data Center position just another info such Position ( server room > rack ) or just Position > RACK ( in place in red reactangle on screenshots )", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Server rooms can be moved from their forms or search results page.\n1. Go to Management > Data centers\n2. Click the Server rooms button at the top of the page\n3. Search the rooms you want to move and open them or select them directly from the results and click Actions > Update, and update the data center\n\nSame for racks, they can be moved from the rack side.\n\nOriginal response date: 2026-03-11", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4042689553, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23448#issuecomment-4042689553", "createdAt": "2026-03-11T22:39:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23448, "url": "https://github.com/glpi-project/glpi/issues/23448", "author": "adamcios", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-11T11:50:03Z", "updatedAt": "2026-06-20T01:05:30Z", "closedAt": "2026-03-11T22:39:52Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Is there any API 2.2.0 endpoint for creating Link Assistance Objects ?", "detail": "Issue description:\nDear all,\n\nI managed to create ticket using the OpenAPI of GLPI 2.2.0, but unfortunately i don't find anything in the Swagger documentation of the api 2.2.0.\n\nI can create Links from the UI, but not from the API.\n\nDid i miss something ?\n\nGLPI Version : 11.0.5\n\nThanks for the help,\n\nBest Regards, Edouard Fazenda", "priority": "medium", "type": "support", "createdByEmail": "noel.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "If it doesn't show in the Swagger UI, it doesn't exist yet. Schemas for the links exist and are therefore able to be read using GraphQL. The GraphQL implementation does not support mutators. currently. REST endpoints are not implemented for them yet.\n\nOriginal response date: 2026-02-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3961258483, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23241#issuecomment-3961258483", "createdAt": "2026-02-25T18:43:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23241, "url": "https://github.com/glpi-project/glpi/issues/23241", "author": "efazenda", "anonymizedAuthorEmail": "noel.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-25T13:26:51Z", "updatedAt": "2026-06-06T01:02:01Z", "closedAt": "2026-02-25T18:43:49Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "GSSAPI SSO Impersonating issue", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.23\n\nIssue description:\nHello,\n\nAfter implementing GSSAPI SSO authentication, the user impersonation feature no longer works.\n\nWhen attempting to impersonate another user, the system immediately redirects to front/central.php instead of switching the session to the selected user.\n\nAt the moment, I’m not sure what is causing this behavior. The only assumption I have is that the impersonation logic may not be fully compatible with the GSSAPI SSO authentication flow (possibly due to how sessions or authentication tokens are handled).\n\nI have checked the logs, but there are no errors or warnings related to this issue.\n\nCould you please advise what might be causing this redirection or what should be reviewed in the configuration/code to make impersonation work correctly with GSSAPI SSO?\nThanks,\nDomagoj\n\nEnvironment details:\nGLPI 10.0.23 ( => /var/www/html/glpi) Installation mode: TARBALL Current language:en_US\n--\nOperating system: Linux hostname 5.14.0-570.33.2.0.1.el9_6.x86_64 #​1 SMP PREEMPT_DYNAMIC Mon Aug 11 16:38:02 PDT 2025 x86_64 PHP 8.4.17 fpm-fcgi (Core, PDO, PDO_ODBC, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, odbc, openssl, pcre, pdo_dblib, pdo_mysql, pdo_sqlite, posix, random, session, shmop, sockets, sodium, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib) Setup: disable_functions=\"\" max_execution_time=\"300\" max_input_vars=\"1000\" memory_limit=\"1024M\" post_max_size=\"20M\" session.cookie_secure=\"1\" session.cookie_httponly=\"1\" session.cookie_samesite=\"\" session.save_handler=\"files\" upload_max_filesize=\"20M\" Software: Apache/2.4.62 (Oracle Linux Server) OpenSSL/3.5.1 mod_auth_gssapi/1.6.3 mod_fcgid/2.3.9 () Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0 Server Software: MariaDB Server Server Version: 10.5.27-MariaDB-log Server SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION", "priority": "medium", "type": "support", "createdByEmail": "kai.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nI never used GSSAPI SSO, so I cannot tell what is wrong here.\n\nThere is a simple rule to follow in your configuration : all front pages must be provide the remote user identity. If this identity is not present anymore, GLPI will consider that the remote authentication is no longuer valid. See\n\nOriginal response date: 2026-02-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3921202742, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23165#issuecomment-3921202742", "createdAt": "2026-02-18T14:38:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23165, "url": "https://github.com/glpi-project/glpi/issues/23165", "author": "dhrzic", "anonymizedAuthorEmail": "kai.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-18T13:48:42Z", "updatedAt": "2026-05-30T01:00:34Z", "closedAt": "2026-02-18T13:50:36Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "A few questions for assistance", "detail": "Issue description:\n1.The previously deployed version of glpi 1.0.18 installed the glpi inventory plugin, which can be set up to retrieve network devices. Now my GLPI has been continuously upgraded to version 11.0.4, but there is no information about interface configuration anymore. Is version 11.0.4 no longer supported? Or maybe it's just that I couldn't find the corresponding directory.\n2.I am currently using an old version of the API, and I am now using the API to connect to Zebbix through GLPI. How can I change to using the new version of the API? I tested changing to the new version before, but the test failed. Please let me know which areas need to be adjusted, the more detailed the better. Thank you!\n3.I used glpi-behaviors-3.0.1 on version 10.0.18 of GLPI, but now after upgrading to version 11.0.4 of GLPI and installing the glpi-behaviors-3.0.1 plugin, it seems that I cannot use it. The work order still shows the number 202511 * * *. How can I solve this problem?\nI plan to upgrade to version 11.0.5. Can the above issues be resolved? Thank you again for your support", "priority": "medium", "type": "support", "createdByEmail": "emerson.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "We only track bug reports here but if you make a post on the forum, a member of the community (or myself) may be able to assist you with these questions/issues.\n\nOriginal response date: 2026-02-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3850593762, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23022#issuecomment-3850593762", "createdAt": "2026-02-05T01:34:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23022, "url": "https://github.com/glpi-project/glpi/issues/23022", "author": "AlvinChenC", "anonymizedAuthorEmail": "emerson.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-05T01:28:31Z", "updatedAt": "2026-05-17T01:00:18Z", "closedAt": "2026-02-05T01:33:49Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Bug: Manual Asset Number populates Serial Number and breaks inventory matching", "detail": "Affected version:\nGLPI version: 10.0.x\n\nIssue description:\nSummary\n\nWhen a computer does not provide a hardware serial number via inventory, manually entering an Asset Number in GLPI can result in the value being reused or copied into the Serial Number field.\nThis causes import rules based on Serial number + UUID to fail and leads to duplicate computer creation.\n\nEnvironment\n\nGLPI version: 10.0.x\n\nGLPI Agent: Windows (latest stable)\n\nOS: Windows 10 / Windows 11\n\nInventory source: GLPI Agent\n\nImport rule: Serial number + UUID\n\nSteps to reproduce\n\nInventory a computer that reports:\n\nUUID ✅\n\nSerial number ❌ (empty / null)\n\nGLPI creates the computer correctly.\n\nManually enter an Asset Number in the computer form.\n\nThe Serial Number field becomes populated with the manually entered asset value (not coming from inventory).\n\nRun inventory again from the agent.\n\nGLPI fails to match the existing computer and creates a duplicate record.\n\nExpected behavior\n\nIf a serial number is missing from inventory:\n\nManual Asset Number input should not populate or affect the Serial Number field.\n\nManually entered values should not break inventory matching rules.\n\nInventory rules should clearly distinguish inventory data vs manual data.\n\nActual behavior\n\nManual Asset Number is reused as Serial Number.\n\nImport rule (Serial + UUID) no longer matches.\n\nA new computer record is created.\n\nGLPI does not merge or reconcile the duplicated records afterward.\n\nImpact\n\nDuplicate computer entries (typically x2)\n\nIncorrect inventory statistics and dashboard counts\n\nManual cleanup required\n\nHigh risk in environments relying on manual asset tracking\n\n[Image omitted]", "priority": "low", "type": "feature", "createdByEmail": "harper.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Inventory rules should clearly distinguish inventory data vs manual data.\n\nNot a bug, that's not the way rules work in GLPI - and I'm pretty sure this won't be OK for everyone.\nYou can consider opening a feature request via suggestion website.\n\nOriginal response date: 2026-01-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3727481544, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22597#issuecomment-3727481544", "createdAt": "2026-01-09T07:02:07Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22597, "url": "https://github.com/glpi-project/glpi/issues/22597", "author": "wisatan", "anonymizedAuthorEmail": "harper.adler@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-09T04:33:19Z", "updatedAt": "2026-04-20T00:49:08Z", "closedAt": "2026-01-09T07:02:24Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Still having issue with task duration despite applying fix #22238", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHi,\n\nDespite applying this fix I'm still having an issue with the task duration. It keeps displaying tasks in seconds even if I choose a longer period.\nDo I need to do something else? I've restarted Apache but no result, may be I'm missing something.\n\nAny help would be appreciated.", "priority": "medium", "type": "support", "createdByEmail": "bailey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "GLPI cache must be removed, also, see\n\nOriginal response date: 2026-01-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3709776352, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22563#issuecomment-3709776352", "createdAt": "2026-01-05T10:09:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22563, "url": "https://github.com/glpi-project/glpi/issues/22563", "author": "meijin4", "anonymizedAuthorEmail": "bailey.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-05T10:07:23Z", "updatedAt": "2026-04-16T00:50:50Z", "closedAt": "2026-01-05T10:55:34Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Fixed assets/Non fixed assets", "detail": "Contribution description:\nI would like to add an option in the computer interface for me to choose whether this asset is a fixed asset or a non fixed asset. Can you provide a detailed guide? My GLPI version is 11.0.4", "priority": "medium", "type": "support", "createdByEmail": "emerson.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "If you would like to add new fields on built-in asset types like Computers, consider using the Fields plugin.\n\nOriginal response date: 2026-01-01", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3703786806, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22513#issuecomment-3703786806", "createdAt": "2026-01-01T14:43:21Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22513, "url": "https://github.com/glpi-project/glpi/issues/22513", "author": "AlvinChenC", "anonymizedAuthorEmail": "emerson.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-31T06:00:07Z", "updatedAt": "2026-04-12T00:48:13Z", "closedAt": "2026-01-01T14:43:21Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "No Sync full with AD (GLPI 11.0.4)", "detail": "Affected version:\n11.0.4\n\nIssue description:\nI don't know if it was faulty in version 10, because I hadn't activated it; I did so after upgrading to version 11.0.4\n\nI have GLPI 11.0.4 and this configuration is set up to synchronize with Active Directory.\n\nWhere is it synchronizing from? (BASEDN= OU=Users,DC=domain,DC=es)\n\nThe options are set in Configuration -> Authentication -> Settings\n\nAuthentication Configuration\n\nAdd users from external source: Yes\nAdd users without authentication from LDAP: Yes\nAction when a user is restored in LDAP: Restore (remove from trash)\n\nActions when a user is deleted from LDAP\nUser: Move to Trash\nGroups: Delete all groups\nAuthorizations: Delete all authorizations.\n\nBy the way, it's properly connected and says the last update was 2024-02-20 (why doesn't it update to that date if it's synchronized manually?), so apparently, it's not doing anything automatically.\n\nI have this script to automatically synchronize, for example, user password changes, ensuring they are properly synchronized between GLPI and Active Directory.\n\necho Starting GLPI-AD synchronization...\necho Date/Time: %date% %time%\necho\n\nREM --- Editable Configuration ---\nREM Change these paths according to your installation\nset PHP_PATH=\"C:\\PHP\\8.2\\php.exe\"\nset GLPI_PATH=\"C:\\www\\glpi\"\nset SERVER_ID=1\nREM --------------------------------\n\nREM Check for PHP installation\nif not exist %PHP_PATH% (\necho ERROR: php.exe was not found in the path: %PHP_PATH%\necho Please verify your PHP installation.\nexit /b 1\n)\n\nREM Check for GLPI installation\nif not exist %GLPI_PATH%\\bin\\console (\necho ERROR: GLPI was not found in the path: %GLPI_PATH%\necho Please verify your GLPI installation path.\nexit /b 1\n)\n\necho Configuration detected:\necho - PHP: %PHP_PATH%\necho - GLPI: %GLPI_PATH%\necho - Server ID: %SERVER_ID%\necho.\n\nREM Run full synchronization\necho Running synchronization...\n%PHP_PATH% %GLPI_PATH%\\bin\\console glpi:ldap:synchronize_users --ldap-server-id=%SERVER_ID%\n\nif %errorlevel% equ 0 (\necho.\necho Synchronization completed successfully.\n) else (\necho.\necho ERROR: Synchronization failed with error code: %errorlevel%\n)\n\necho.\necho Script finished: %date% %time%\npause\n\nBut with this I realize that:\n\nNo user that has been deleted from AD is deleted in GLPI.\n\nNo user who has moved to another OU (that is not under the Users OU, which is the one that should synchronize) is removed from GLPI.\n\nHaving deleted users in Active Directory, if they are in GLPI and I delete them from GLPI, it recreates them (from where? That user isn't in Active Directory, but they were present at the time of the last update).\n\nI'd like to help by providing a log, but I don't know where it's stored or in which file, so if you tell me, I'll add it.\n\nThank you so much for your help.", "priority": "medium", "type": "support", "createdByEmail": "hayden.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I am not seeing a bug here but some questions about how GLPI works. If you would like to post this on the community forum, myself or a member of the community may be able to help. If a bug is discovered after the questions are cleared up, then we can have a bug report opened on GitHub.\n\nOriginal response date: 2025-12-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3690170419, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22479#issuecomment-3690170419", "createdAt": "2025-12-24T16:08:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22479, "url": "https://github.com/glpi-project/glpi/issues/22479", "author": "Senninha1974", "anonymizedAuthorEmail": "hayden.blair@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-24T15:37:09Z", "updatedAt": "2026-04-04T00:40:41Z", "closedAt": "2025-12-24T16:07:10Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Can not acces to user list", "detail": "Affected version:\n11.0.4\n\nIssue description:\nWhen i try to access to user list, i have this error\n\n[Image omitted]\n\nI also have this error\n\n[Image omitted]\n\nI check and the directory ContainerEgsh3Gf doesn't exist", "priority": "medium", "type": "support", "createdByEmail": "parker.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Seems like a cache issue, try removing ./files/_cache/*.\n\nOriginal response date: 2025-12-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3674128839, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22443#issuecomment-3674128839", "createdAt": "2025-12-19T08:43:29Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22443, "url": "https://github.com/glpi-project/glpi/issues/22443", "author": "zekuraz", "anonymizedAuthorEmail": "parker.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-19T08:31:33Z", "updatedAt": "2026-03-30T00:45:26Z", "closedAt": "2025-12-19T09:14:16Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Base URL setting doesn't work", "detail": "Affected version:\n11.0.4\n\nIssue description:\nI have GLPI installed in via official docker-image.\nSetting \"Setup - General - General Setup - Base URL\" doesn't affect anything.\nRight now my glpi instance accesible via . I can change domain name on nginx-proxy and GLPI will work absolutely fine. But I need to move the site to and there where problem rise up.\n\nReproduction steps:\n1. Install fresh glpi from docker image\n2. Change path in \"Setup - General - General Setup - Base URL\" from \"\" to \"\"\n3. Save and restart the container - nothing will change\n\nAdditional context:\nProblem appeared after 11.0 update, I think it worked fine before", "priority": "medium", "type": "support", "createdByEmail": "jamie.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi,\n\nThe base URL setting is used to generate absolute URLS, for instance in email notifications. Currently, the docker image does not support the usage of a prefix path. You can mount a volume with your own apache configuration to do this.\n\nOriginal response date: 2025-12-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3660478486, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22270#issuecomment-3660478486", "createdAt": "2025-12-16T13:16:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22270, "url": "https://github.com/glpi-project/glpi/issues/22270", "author": "OldmanTrenton", "anonymizedAuthorEmail": "jamie.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-05T15:02:41Z", "updatedAt": "2026-03-27T00:43:32Z", "closedAt": "2025-12-16T13:28:44Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Wrong number format", "detail": "Affected version:\nGLPI 11.0.0-rc4\n\nIssue description:\nSome floating point number fields in the \"Management\" tab of an asset seem to have the wrong formatting. The bug pertains to the fields \"Value\" and \"Warranty extension value\".\n\nThe other decimal value fields are correrctly formatted.\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\n1. Enter \"200\" in the Value field\n2. Click \"Save\"\n3. The number in the Value field changes to \"200,0000\". (4 decimals and ',' decimal character)\n4. Expected value: \"200.00\" (2 decimals and the '.' decimal character)", "priority": "medium", "type": "bug", "createdByEmail": "elliot.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed in GLPI 11.0.3.\n\nOriginal response date: 2025-12-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3610642724, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/20918#issuecomment-3610642724", "createdAt": "2025-12-04T07:17:36Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 20918, "url": "https://github.com/glpi-project/glpi/issues/20918", "author": "pete1854", "anonymizedAuthorEmail": "elliot.bennett@peppermint.local", "assignees": [], "labels": [ "bug" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-09-05T14:24:59Z", "updatedAt": "2026-03-15T00:45:00Z", "closedAt": "2025-12-04T07:17:36Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "HL API (2.1) ERROR_UNAUTHENTICATED client_credentials", "detail": "Affected version:\n11.0.3\n\nIssue description:\nHi,\n\nI need to use the HL API because I need to access custom assets.\n\nI managed to get a token calling api.php/token.\n\n{\"grant_type\", \"client_credentials\"},\n{\"client_id\", clientId},\n{\"client_secret\", clientSecret},\n{\"scope\", \"api inventory user email status graphql\"},\n{\"username\", \"bertrandc\"}\n\nclientId and clientSecret comes from from Client Oauth And everything is accorded to the client (scopes, auth methods, ...)\n\nI get a token like Bearer eyJ0eXA..UzI1NiJ9.eyJhdWQi.....\n\nWhen I use this token to querry /Assets/Computer/1200 I Get :\n{\"title\":\"Vous n'\\u00eates pas authentif\\u00e9\",\"detail\":\"L\\u2019en-t\\u00eate d\\u2019authentification est manquante ou invalide\",\"status\":\"ERROR_UNAUTHENTICATED\"}\n\nIf Y connect myself on api.php/doc and I make a test, everything works. If I take the token generated by api.php/doc, everything also works.\n\nMy problem becomes : client_credentials doesn't work like it should (O I miss a config step, but I can't find it)\n\nThanks\n\nSame problem reported here :", "priority": "medium", "type": "support", "createdByEmail": "rowan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This is explained in the API Getting Started documentation (api.php/getting-started). The client_credentials grant may only be used alongside the inventory scope which is only used to allow GLPI Agent (or other agents) to submit inventories. All other endpoints require an actual user to be authenticated and must therefore use a different grant type.\n\nOriginal response date: 2025-11-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3552587975, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21991#issuecomment-3552587975", "createdAt": "2025-11-19T13:03:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21991, "url": "https://github.com/glpi-project/glpi/issues/21991", "author": "InformatiqueOLLN", "anonymizedAuthorEmail": "rowan.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-19T12:53:46Z", "updatedAt": "2026-02-28T00:34:17Z", "closedAt": "2025-11-19T13:03:40Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Subcatégorie to the ticket", "detail": "Contribution description:\nHello, I would like to have the option to add a subcategory selection field for tickets. Because when there are many categories and several subcategories linked to them, the interface becomes somewhat cluttered and difficult for users to navigate.", "priority": "low", "type": "feature", "createdByEmail": "bailey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Isn't this covered by the Split Categories plugin?\n\nOriginal response date: 2025-10-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3460618993, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21684#issuecomment-3460618993", "createdAt": "2025-10-29T09:43:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21684, "url": "https://github.com/glpi-project/glpi/issues/21684", "author": "AziocNEU", "anonymizedAuthorEmail": "bailey.blair@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-29T09:35:37Z", "updatedAt": "2026-02-07T00:37:32Z", "closedAt": "2025-10-29T09:45:31Z" } }, { "title": "GLPI 11 Forms - Annotation field", "detail": "Contribution description:\nAs GLPI 11 has a native forms, there's something missing from the old one (a customized formcreator) that has some relevance in the form worflow: Annotations (Only visible inside the form creation/editing). This is important for questions who will have the same question name, but for different options when selected. That helps to maintain and easily locate a question for a specific target.\n\nExample of Anottation in forms (the location of the annotation is just for example purposes):\n\n[Image omitted]", "priority": "low", "type": "feature", "createdByEmail": "reese.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "micah.bennett@peppermint.local", "text": "The standard form in version 10 does not have this feature. Perhaps you are confusing it with a form plugin that has been customized for this purpose. It's a good idea, and it would be nice if they added it with form management in mind, but I don't think they will add it for now.\n\nHowever, it's a good suggestion!\n\nOriginal response date: 2025-10-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3452570933, "author": "lucaslevi-consultor-glpi", "anonymizedAuthorEmail": "micah.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21661#issuecomment-3452570933", "createdAt": "2025-10-27T17:45:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21661, "url": "https://github.com/glpi-project/glpi/issues/21661", "author": "stevanborges", "anonymizedAuthorEmail": "reese.adler@peppermint.local", "assignees": [], "labels": [ "feature suggestion" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-27T16:25:47Z", "updatedAt": "2026-02-06T00:37:13Z", "closedAt": "2025-10-28T06:20:47Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "update tcpdf to last version in next release glpi 10/11", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nThe last version fixes some deprecation in php 8.5\n\n6.11.2 (2026-03-03)\n - Refactor setCompression().\n\n6.11.1 (2026-03-03)\n - Remove debug line preventing compression.\n\n6.11.0 (2026-03-01)\n - Updated copyright year.\n - Updated linked http urls to https.\n - Fix PHP 8.5 deprecation on curl_close() - PR #838\n - Fix PHP 8.5 deprecation on null array offset - PR #839\n - Fixed: Font subsetting - incorrect placement of head checksum - PR #849\n - Fix imagedestroy() deprecation in PHP 8.5 - PR #851\n - Fix Rendering of SVG -> PDF issue - PR #855\n\nIn special \"Fix imagedestroy() deprecation in PHP 8.5 - PR #851\" it can affect some community plugins.", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Is there an identifiable need to update this dependency on existing bugfix versions, ie an exception/error being thrown in GLPI?\n\nOriginal response date: 2026-03-28", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4148200732, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23570#issuecomment-4148200732", "createdAt": "2026-03-28T14:48:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23570, "url": "https://github.com/glpi-project/glpi/issues/23570", "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-21T18:16:18Z", "updatedAt": "2026-07-20T00:46:37Z", "closedAt": "2026-04-10T07:33:41Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Bug displaying custom resources in Management > Databases", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI created a custom asset – server and used the GLPI agent to perform a servers inventory. In the tab, I can't display the name of the server associated with the database. There's no such option. I have all possible options enabled in capacity for the custom asset definition.\n\n[Image omitted]\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "quinn.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Fixed by #23769 for GLPI 12. Search option changes can be considered a breaking change so it was not done for GLPI 11.\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4210903546, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22949#issuecomment-4210903546", "createdAt": "2026-04-09T01:49:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22949, "url": "https://github.com/glpi-project/glpi/issues/22949", "author": "Bellegund", "anonymizedAuthorEmail": "quinn.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-02T11:29:52Z", "updatedAt": "2026-07-19T00:44:49Z", "closedAt": "2026-04-09T01:49:55Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Discover tab in marketplace colletions php errors", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nIt shows when open Discover tab in the Marketplace ()\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\nGo to Setup - > Plugins\nOpen Discover tab", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "fixed by #23530 for GLPI 11.0.7\n\nOriginal response date: 2026-04-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4218179524, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23826#issuecomment-4218179524", "createdAt": "2026-04-09T22:43:01Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23826, "url": "https://github.com/glpi-project/glpi/issues/23826", "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-09T17:11:13Z", "updatedAt": "2026-07-19T00:44:41Z", "closedAt": "2026-04-09T22:43:01Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Custom asset Yes/No values are all Yes in the asset view", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nI have created a new custom asset (asset definition).\nI have created a bunch of custom fields in there, which have functioned properly, mainly string and dropdown types, but when I created the Yes/No type custom fields, although opening the item, I see the Yes/No values as No, when I go back to the asset view, all values are Yes.\n\nAffected page:\n\nNew Custom Asset Definition:\n1. Go to Setup - Asset definitions.\n2. Click on Add to create a new asset definition.\n3. Name the new custom asset, make it active, and add it.\n4. Open the new custom asset.\n\nNew Custom Field:\n1. Go to Fields.\n2. At the bottom right, click on the + New field link under Custom fields.\n3. Name the new field.\n4. Select the Yes/No type and add it.\n\nCreate new asset:\n1. Under Assets, open the new custom asset you just created.\n2. Click on Add to create a new asset.\n3. Fill whatever built-in fields you have and set the custom Yes/No field to No.\n4. Save the asset.\n\nModify the default items to show view:\n1. At the header of the asset table, on the right, find an icon that has an alt text Select default items to show. Click on it.\n2. In the search box left of the Add button, type custom, select the custom field you created earlier, and add it.\n3. Close the modal window.\n\nAlthough you set the custom field value to No in the Create new asset, point 3, it will show the value in the asset view as Yes.\nOpen the asset again to ensure that the value there is still No.\n\nAdditional context:\nI started using that custom field type with the 11.0.6 version, so I don't know if it has worked correctly before.", "priority": "medium", "type": "support", "createdByEmail": "elliot.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirmed the issue. Yes/No fields are stored as JSON true/false values in the custom_fields column in the database. When the values are extracted using JSON_UNQUOTE(JSON_EXTRACT(...)), they get converted to \"true\" or \"false\" strings. Then, since Dropdown::getYesNo only checks the truthiness of a value to determine if it outputs \"Yes\" or \"No\", it would output \"Yes\" because \"false\" as a string evaluates to true. Normally in GLPI boolean values are stored in the database as a 0 or 1.\n\nThere are two potential solutions:\n1. Change the computation for boolean custom fields so it becomes COALESCE(JSON_UNQUOTE(JSON_EXTRACT(glpi_assets_assets.custom_fields, '$.\\\"21\\\"')), '0') = \"true\" instead of COALESCE(JSON_UNQUOTE(JSON_EXTRACT(glpi_assets_assets.custom_fields, '$.\\\"21\\\"')), '0'). This would probably be the solution with the least amount of side-effects.\n2. Change Dropdown::getYesNo to evaluate the value through filter_var($value, FILTER_VALIDATE_BOOLEAN) so that some strings like \"false\" get treated as false. This could have unintended side-effects since it is used in many places but could be considered the more correct implementation of the function.\n\nOriginal response date: 2026-03-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4064194669, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23490#issuecomment-4064194669", "createdAt": "2026-03-15T23:44:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23490, "url": "https://github.com/glpi-project/glpi/issues/23490", "author": "RRohi", "anonymizedAuthorEmail": "elliot.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-15T22:16:24Z", "updatedAt": "2026-07-17T00:43:37Z", "closedAt": "2026-04-07T09:11:18Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Monitor with \"serial\": \"00000001\" not added to Assets (Monitors) on fresh GLPI install", "detail": "Issue description:\nEnvironment:\n\nGLPI version: 11.0.8\nGLPI-Inventory: v1.18\nDatabase: initial, empty, fresh install\nSteps to reproduce:\n\nLoad inventory.json\n\nAttempt to add monitor “AQ32H1UE” with serial 00000001 to Assets → Monitors.\nObserve that the monitor is not added.\nNo errors or warnings are displayed.\nExpected behavior:\nThe monitor should be successfully added to the Assets (Monitors) list.\n\nActual behavior:\nThe monitor is not added, with no errors or warnings shown.\n\nAdditional observations:\n\nChanging the serial number to another value allows the monitor to be added.\nMonitor “MSI G24C4” can be added without any issues.\n\npart of inventory.json:", "priority": "medium", "type": "support", "createdByEmail": "harper.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "As far as I remember, this kind of serial is part of the blacklist you can configure.\n\nOriginal response date: 2026-07-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4991890737, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24870#issuecomment-4991890737", "createdAt": "2026-07-16T12:37:10Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24870, "url": "https://github.com/glpi-project/glpi/issues/24870", "author": "kotkrsk", "anonymizedAuthorEmail": "harper.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-07-16T12:32:11Z", "updatedAt": "2026-07-16T12:37:28Z", "closedAt": "2026-07-16T12:37:28Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "GLPI 11 Docker – Cannot connect to MariaDB with TLS (external DB, connection works manually)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello,\n\nWe are facing an issue with GLPI 11 deployed via Docker, using an external MariaDB server with TLS enabled.\n\nEnvironment:\nGLPI: 11 (official Docker image)\nMariaDB: 10.11 (external server)\nDocker: running on Linux\nDatabase is NOT in Docker\n\nDatabase configuration:\nMariaDB is configured with TLS and requires secure transport:\n\nrequire_secure_transport = ON\nssl_cert = ...\nssl_key = ...\nssl_ca = ...\n\nGLPI configuration (config_db.php):\nclass DB extends DBmysql {\n public $dbhost = '1.2.3.4:3306';\n public $dbuser = 'glpi_user';\n public $dbpassword = '';\n public $dbdefault = 'glpi';\n\n public $dbssl = true;\n public $dbsslca = '/var/glpi/config/certs/ca.pem';\n\n public $use_timezones = true;\n public $use_utf8mb4 = true;\n}\n\nThe CA certificate is correctly mounted inside the container:\n\n/var/glpi/config/certs/ca.pem\n\nWhat works:\nFrom inside the GLPI container, we can connect successfully using:\n\nmysql -h 1.2.3.4 -u glpi_user -p --ssl-ca=/var/glpi/config/certs/ca.pem\n\nProblem:\nGLPI container keeps looping with:\n\n[entrypoint] Waiting for database to be ready...\n\nAnd never starts.\n\nSuspected cause:\nIt seems the Docker entrypoint checks database connectivity without TLS, which fails because MariaDB enforces require_secure_transport=ON.\n\nThanks!", "priority": "medium", "type": "support", "createdByEmail": "riley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please report docker issues on docker repository\n\nOriginal response date: 2026-04-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4178105150, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23752#issuecomment-4178105150", "createdAt": "2026-04-02T14:00:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23752, "url": "https://github.com/glpi-project/glpi/issues/23752", "author": "sylvainblanchouin", "anonymizedAuthorEmail": "riley.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-04-02T13:37:54Z", "updatedAt": "2026-07-12T00:46:12Z", "closedAt": "2026-04-02T14:00:47Z" } }, { "title": "Fix TicketTest::testCanAddDocument()", "detail": "Issue description:\nJesse Blair\n\nIt seems this test you added is invalid because it create a change instead of a ticket.\n\nIf I change the item to Ticket, two cases of the providers fails (number 3 and 6, the ones with // requester can always add docs if the ticket is not modified).\n\nCould you look into it and see why?", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Fixed by #23192\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4159843180, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23140#issuecomment-4159843180", "createdAt": "2026-03-31T04:44:16Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23140, "url": "https://github.com/glpi-project/glpi/issues/23140", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "MyvTsv", "anonymizedEmail": "jesse.blair@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-17T10:40:56Z", "updatedAt": "2026-07-10T00:48:45Z", "closedAt": "2026-03-31T04:44:16Z" }, "assignedTo": "jesse.blair@peppermint.local" }, { "title": "GLPI 11 API getFriendlyNames() fails for items_id_target fields", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nThe getFriendlyNames() method in GLPI API fails when add_keys_names includes items_id_target because getItemtypeForForeignKeyField('items_id_target') returns null.\n\nReproduction steps:\nMake an API request to get TicketValidation items with add_keys_names parameter\nInclude status field in the add_keys_names array\n\nExample API call:\n\nbashGET /apirest.php/TicketValidation?add_keys_names[]=status&add_keys_names[]=items_id_target\n4. Observe the error in logs and API response issues\n\nAffected page:\nAPI endpoint: /apirest.php/TicketValidation\nAffected file: src/Glpi/Api/API.php (getFriendlyNames method)\n\nEnvironment details:\nGLPI Version: 11.0.4\nDatabase: MariaDB\nPHP Version: 8.3\n\nAdditional context:\nAffected Tables:\n\nglpi_ticketvalidations", "priority": "medium", "type": "support", "createdByEmail": "devon.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm the API method doesn't handle polymorphic relationships.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4120763998, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22842#issuecomment-4120763998", "createdAt": "2026-03-24T19:16:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22842, "url": "https://github.com/glpi-project/glpi/issues/22842", "author": "vishvas-u", "anonymizedAuthorEmail": "devon.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-27T03:33:04Z", "updatedAt": "2026-07-10T00:48:36Z", "closedAt": "2026-03-31T07:05:19Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "License form have strange comportment for the sub entity checkbox", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nDear glpi team,\n\nSince our software switch from 10.0.x to 11.0.6 we have lost the possibility to manage correctly the sub entities in the form \"licenses\" (/front/softwarelicense.form.php)\nIndeed, when I check the box sub entity to on and save it, the form saves it. But when I load or reload the page, the checkbox is always off.\n\nRegards,", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The child entities property is inherited from the linked software. If no software is linked, it cannot be visible to child entities.\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4162275373, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23698#issuecomment-4162275373", "createdAt": "2026-03-31T12:26:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23698, "url": "https://github.com/glpi-project/glpi/issues/23698", "author": "Sevengroup-IT", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-31T12:21:19Z", "updatedAt": "2026-07-10T00:48:30Z", "closedAt": "2026-03-31T14:54:40Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Form categories are not displayed", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nWith form categories enabled in all entities, I created different form categories with custom tiles (I also tried with default tiles). I assigned more than one form to a category, expecting that I could then view the category in the service catalog and thus expand the forms; however, the category does not appear in the catalog, only the forms contained within that category.\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\n[Image omitted]\n\nReproduction steps:\n1. Create a category using a custom or default GLPI tile.\n\n2. Assign one or more forms to a category.\n\n3. Go to the service catalog, using the standard or simplified profile.\n\n4. Only the forms associated with the category are displayed; the expected category is not shown.\n\nAdditional context:\nIf I need to configure something else to display the categories and it's not an error, please let me know. Thank you very much.", "priority": "medium", "type": "support", "createdByEmail": "riley.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "riley.bennett@peppermint.local", "text": "Hi! It was a translate error from English to Spanish(Ar). I have already performed the fix in Transifex.\n\nThanks!\n\nOriginal response date: 2026-03-31", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4164310163, "author": "Arkham1997", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23705#issuecomment-4164310163", "createdAt": "2026-03-31T17:41:08Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23705, "url": "https://github.com/glpi-project/glpi/issues/23705", "author": "Arkham1997", "anonymizedAuthorEmail": "riley.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-31T14:35:02Z", "updatedAt": "2026-07-10T00:48:22Z", "closedAt": "2026-03-31T17:41:22Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Words still getting cut on Ticket screen, this was not happening on version 10", "detail": "Affected version:\n11.0.2\n\nIssue description:\nWords still getting cut on Ticket screen, this was not happening on version 10\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "noel.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The issue did exist on GLPI 10, but the UI adapted at a certain screen width to show the labels above the fields.\nRemoving the glpi-full-width class from the form fields in the panel and removing the two-column layout restores the previous behavior.\n\nOriginal response date: 2026-03-27", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4139532563, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21857#issuecomment-4139532563", "createdAt": "2026-03-27T01:57:35Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21857, "url": "https://github.com/glpi-project/glpi/issues/21857", "author": "jcusto-acores", "anonymizedAuthorEmail": "noel.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-11-07T11:38:18Z", "updatedAt": "2026-07-09T00:48:44Z", "closedAt": "2026-03-30T08:00:51Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "In a child entity form, is not possible to restrict access to a root entity group", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nIn my root entity, i have a lot of recursive groups\n\n[Image omitted]\n\nIn my child entity, I need to restrict access to a specific group, but none of these groups shows to me for selection, even them show in \"groups\" tab\n\n[Image omitted]\n\n[Image omitted]\n\nit only works if I am a Super Admin in root entity super-admin, it is expected\n\nReproduction steps:\n1. In root entity, create a group and mark them as recursive\n2. Enter in sub entity and create a form\n3. The group not shows as selectable to restrict acess", "priority": "medium", "type": "support", "createdByEmail": "casey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Casey Adler, #23594 should fix your issue.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4117624695, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23337#issuecomment-4117624695", "createdAt": "2026-03-24T11:58:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23337, "url": "https://github.com/glpi-project/glpi/issues/23337", "author": "ViniciusgCaetano", "anonymizedAuthorEmail": "casey.adler@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-03T20:29:43Z", "updatedAt": "2026-07-09T00:48:32Z", "closedAt": "2026-03-30T09:04:21Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "npm audit failed (10.0/bugfixes)", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed by #23678.\n\nOriginal response date: 2026-03-30", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4154452414, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23676#issuecomment-4154452414", "createdAt": "2026-03-30T11:51:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23676, "url": "https://github.com/glpi-project/glpi/issues/23676", "author": "github-actions[bot]", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-30T10:27:05Z", "updatedAt": "2026-07-09T00:48:29Z", "closedAt": "2026-03-30T11:51:58Z" } }, { "title": "No popup \"Leave page\" or \"Stay on page\" when clicking \"Save\" on a ticket", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen a user clicks the \"Save\" button in the bottom right corner while currently editing an answer to a ticket, the answer text is lost.\nNavigating away from the page in this scenario correctly triggers a popup that asks whether the user wants to \"Leave page\" or \"Stay on page\". The same popup should be triggered when clicking the \"Save\" button to not lose any information typed in so far.\n\nAffected page:\n/front/ticket.form.php?id=1234\n\nReproduction steps:\n1. open a ticket in edit mode\n2. click \"Answer\"\n3. write some text for the new Followup but do not click \"Add\" yet.\n4. click \"Save\" on the bottom right corner, your text is lost\n\nEnvironment details:\nGLPI 11.0.5 Copyright (C) 2015-2026 Teclib' and contributors", "priority": "medium", "type": "support", "createdByEmail": "dakota.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This would likely be a little complicated to implement. Currently, the unsaved changes for forms is done globally for a page and wouldn't be able to handle multiple forms on the same page.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993567125, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23217#issuecomment-3993567125", "createdAt": "2026-03-03T21:12:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23217, "url": "https://github.com/glpi-project/glpi/issues/23217", "author": "cfuchs-mpi", "anonymizedAuthorEmail": "dakota.bennett@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "ux" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-24T08:40:49Z", "updatedAt": "2026-07-09T00:48:23Z", "closedAt": "2026-03-30T12:54:19Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Inversion of the tables inside glpi_assets_assets_peripheralassets", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\n[Image omitted]\nAfter updating to a 11.0.5 version we get a situation that old links are reversed, right now it can be seen that a monitor is connected to several PCs , while inside the card it is empty, via\nSELECT a.id\nFROM glpi_assets_assets_peripheralassets a\nLEFT JOIN glpi_computers c ON c.id = a.items_id_asset\nLEFT JOIN glpi_monitors m ON m.id = a.items_id_peripheral\nWHERE c.id IS NULL OR m.id IS NULL;\nI have found 1875 errors in the database\n\nReproduction steps:\n1. update the database via php bin/console db:update\n2. get this error\nWorked on several different db dumps", "priority": "medium", "type": "support", "createdByEmail": "dakota.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Sounds similar to my comment here:\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993579379, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23137#issuecomment-3993579379", "createdAt": "2026-03-03T21:14:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23137, "url": "https://github.com/glpi-project/glpi/issues/23137", "author": "mifimov345", "anonymizedAuthorEmail": "dakota.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-02-17T07:40:51Z", "updatedAt": "2026-07-07T00:51:59Z", "closedAt": "2026-03-28T15:06:49Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Field unicity didn't work correct on GLPI 11.0.4", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nAfter migration to GLPI 11.0.4 and moving all additional asset direct into asset definition, unicity of fields stops working for define assets.\nIt still works well for native assets like computers etc, but in assets created by me, it didn't see duplicates or even if see, didn't block creation of them, except one type of assets named Akcesoria. Only there this function works correct.\nI'm guessing that this might be connected to one table for all assets, which mean should I create unicity of field only once?\nBelow you can see the example\n\n[Image omitted]\n\n[Image omitted]\n\nEnvironment details:\nNormal GLPI instance 11.0.4 works on NGINX\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "bailey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm it seems that this feature doesn't take into account the criteria from CommonDBTM::getSystemSQLCriteria which allows different asset types to exist within the same table.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993796609, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22858#issuecomment-3993796609", "createdAt": "2026-03-03T21:57:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22858, "url": "https://github.com/glpi-project/glpi/issues/22858", "author": "geek95dg", "anonymizedAuthorEmail": "bailey.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-28T07:07:04Z", "updatedAt": "2026-07-04T00:48:59Z", "closedAt": "2026-03-25T07:51:20Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Language template: Incorrect plural in \"My\" plural word in dropdowns", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nReferense\n\nI opened an issue in transifex for the integration for a plural pronoun for an other language different than english\n\n\"There's a problem with the use of \"my\" in translations. For example, in English, \"my\" is used for both singular and plural (My Computer, My computers, My monitor, My monitors, etc.), but in Spanish, for instance, it's not the same. My = \"Mi\" (Mi computadora, Mi monitor) for singular, but for plural it's Mis (Mis comunicaciones, Mis monitores). This string needs to be adjusted for plurals. Example image:\"\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "In facts, there is no need for a plural form since it is always plural (Session::getPluralNumber()).\n A note should maybe be added for translators.\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4124405493, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23601#issuecomment-4124405493", "createdAt": "2026-03-25T07:36:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23601, "url": "https://github.com/glpi-project/glpi/issues/23601", "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [], "labels": [ "translation" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-24T17:20:15Z", "updatedAt": "2026-07-04T00:48:50Z", "closedAt": "2026-03-25T08:34:51Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "CSRF check fails for anonymous users on public/unauthenticated routes in GLPI 11", "detail": "Issue description:\nAfter upgrading to GLPI 11.0.6, CSRF validation rejects requests from anonymous (unauthenticated) users on routes that should be publicly accessible or that don't require CSRF protection (e.g., the login page /, /Session/ChangeProfile).\n\nThis appears to be a regression in the new Symfony-based routing/controller system introduced in GLPI 11.\n\nGLPI version:\n11.0.6 (upgraded from 10.x)\n\nPHP version:\n8.2 (CloudLinux/CentOS — Hostinger shared hosting)\n\nReproduction steps:\n1. Upgrade GLPI from 10.x to 11.0.6\n2. Monitor access-errors.log\n3. Anonymous users (bots, expired sessions, or users navigating to the login page) trigger CSRF failures on / and /Session/ChangeProfile\n4. Authenticated users occasionally get CSRF failures on forms like /front/itilfollowup.form.php (possible session race condition)\n\nExpected behavior:\n- Routes that are accessible without authentication (login page, public endpoints) should not enforce CSRF validation on anonymous users\n- The CheckCsrfListener should skip CSRF checks for routes that don't require authentication\n- Authenticated users should not get spurious CSRF failures on standard forms\n\nAdditional context:\n- The CSRF failures on / suggest that POST requests to the login page (form submission) are being rejected\n- The Session/ChangeProfile failures for anonymous users suggest expired sessions are not being handled gracefully — instead of redirecting to login, the CSRF check fires first\n- The itilfollowup.form.php failure for User 452 may indicate a session timeout race condition where the CSRF token expires before the form is submitted\n\nImpact:\n- Users with expired sessions get cryptic CSRF errors instead of a clean redirect to the login page\n- May block legitimate login attempts depending on the flow\n- Generates noise in access-errors.log making it harder to spot real security events", "priority": "medium", "type": "support", "createdByEmail": "parker.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Not a bug. GLPI protects all POST actions with CSRF tokens and there exists guidance for adding CSRF protection on login forms.\n\nWe are aware the CSRF protection leads to user experience issues in some cases if the token expires before an action can be performed.\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4125956852, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23606#issuecomment-4125956852", "createdAt": "2026-03-25T11:48:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23606, "url": "https://github.com/glpi-project/glpi/issues/23606", "author": "StbanMc", "anonymizedAuthorEmail": "parker.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-03-24T20:58:29Z", "updatedAt": "2026-07-04T00:48:47Z", "closedAt": "2026-03-25T11:48:14Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Firewall::computeFallbackStrategyForPlugin crashes with PcreException on invalid plugin-registered patterns", "detail": "Issue description:\nGlpi\\Http\\Firewall::computeFallbackStrategyForPlugin() passes plugin-registered patterns directly to preg_match() without validation. When a plugin registers a non-regex value (e.g., an array instead of a string, or a string without proper delimiters), GLPI crashes with a PcreException instead of handling it gracefully.\n\nThis is a GLPI core issue — the Firewall should validate/sanitize patterns received from plugins before using them in preg_match().\n\nGLPI version:\n11.0.6\n\nPHP version:\n8.2 (CloudLinux/CentOS — Hostinger shared hosting)\n\nReproduction steps:\n1. Install any plugin that registers a firewall strategy with a malformed pattern (non-regex string or wrong type)\n2. Navigate to any page — GLPI crashes on every request\n\nExpected behavior:\nGLPI should:\n1. Validate that the pattern is a non-empty string with valid regex delimiters before passing it to preg_match()\n2. Log a warning if the pattern is invalid and skip it\n3. Not crash the entire application because one plugin registered a bad pattern\n\nSuggested fix:\nIn src/Glpi/Http/Firewall.php around line 257, wrap the preg_match() call:\n\nImpact:\n- Crashes GLPI on every page load when a faulty plugin is active\n- The error is in core Firewall code, not in the plugin itself\n- Affects all GLPI 11.x installations with the new Symfony-based routing", "priority": "medium", "type": "support", "createdByEmail": "parker.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "In my opinion, this is primarily on plugin maintainers to write correct code and test it.\n\nThis case isn't a matter of some user-submitted data causing an exception but rather a plugin specifically defining a firewall strategy with an invalid pattern. Plugin code overall isn't sandboxed in any way and any bad code can cause issues globally on GLPI.\n\nGLPI should:\nValidate that the pattern is a non-empty string with valid regex delimiters before passing it to preg_match()\nLog a warning if the pattern is invalid and skip it\nNot crash the entire application because one plugin registered a bad pattern\n\nI disagree. A plugin may only want a resource to be accessible to users on the central interface or admin access but if you just skip bad patterns given by the plugin itself, it would use the fallback strategy for legacy scripts of STRATEGY_AUTHENTICATED. Even if it falls back to the STRATEGY_CENTRAL_ACCESS strategy, it isn't on GLPI to guess what the plugin maintainer intended.\n\nYou could argue that an admin may not have CLI access to disable a badly broken plugin, but that issue isn't specific to just this potential source of trouble with plugins.\n\nOriginal response date: 2026-03-25", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4122541817, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23604#issuecomment-4122541817", "createdAt": "2026-03-25T01:35:07Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23604, "url": "https://github.com/glpi-project/glpi/issues/23604", "author": "StbanMc", "anonymizedAuthorEmail": "parker.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-03-24T20:58:02Z", "updatedAt": "2026-07-04T00:48:44Z", "closedAt": "2026-03-25T11:50:12Z" } }, { "title": "Ghost link created when associating Form to Service Catalog Category during Form creation", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen creating a new form and assigning it a Service catalog category directly within the creation screen, the link is partially established, but the form itself becomes \"invisible.\"\n\nThe Service Catalog Category recognizes a linked form (the counter in the \"Forms\" tab increments), but the tab itself remains empty. Furthermore, the newly created form does not appear in the main Forms list.\n\nThis looks like a classic database inconsistency or \"orphan record\" bug during the creation process.\n\nWorkaround: Creating the form first without a category, then assigning the category after the form has been saved, works as expected.\n\nAffected page:\n/front/form/form.php and /front/form/category.form.php\n\nReproduction steps:\n1. Navigate to Administration > Forms (/front/form/form.php).\n2. Click Add to create a new form.\n3. Fill in the required fields.\n4. In the Service catalog category dropdown, select an existing category.\n5. Click Save changes.\n6. Go to Setup > Dropdowns > Service catalog categories (/front/form/category.form.php) and open the category used in Step 4.\n7. Observe the Forms tab: The counter increases, but the list is empty.\n8. Go back to Administration > Forms: The new form is missing from the list.\n\nAdditional context:\nIf I click on the \"Untitled Form\" on tooltip, it allows me to type a name to the form and shows the [Add] button. When clicking on [Add] button, it updates the text of the button to [Save].", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Skyler Adler,\n\nThe form is considered a \"draft\" until you click the \"Add\" button.\nSo if you only saved the \"Service catalog\" tab but did not click the \"Add\" button on the main tab, it will be invisible until you finally confirm its creation on the main tab (or deleted automatically after a few days).\n\nYou are right that it cause an invalid number to be displayed in the tab counter here:\n\n[Image omitted]\n\nThis will be fixed in #23579.\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4110982495, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23088#issuecomment-4110982495", "createdAt": "2026-03-23T14:19:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23088, "url": "https://github.com/glpi-project/glpi/issues/23088", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-11T14:54:03Z", "updatedAt": "2026-07-03T00:50:06Z", "closedAt": "2026-03-24T07:30:30Z" } }, { "title": "Undefined array key \"glpiID\" on Assignable item while inventory", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.6", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I guess this isn't more widespread because it requires a unicity check to fail while adding/updating an asset from Inventory/CLI/Cron.\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4048562787, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23460#issuecomment-4048562787", "createdAt": "2026-03-12T17:19:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23460, "url": "https://github.com/glpi-project/glpi/issues/23460", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-12T15:31:01Z", "updatedAt": "2026-07-03T00:50:00Z", "closedAt": "2026-03-24T09:40:33Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "KB article link UI broken and cannot link Entities", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0/bugfixes, main\n\nIssue description:\nBroken UI:\n[Image omitted]\n\nTrying to add KB article from Entity's Knowledge base tab:\n\"Mandatory fields are not filled. Please correct: itemtype\"\n\nTrying to add Entity from KB article's Associated items tab:\n\"Mandatory fields are not filled. Please correct: itemtype\"\n\nTrying to add Computer or other itemtypes I tested from KB article works.", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It seems I was mistaken about not being able to link entities; you simply need to make sure the article is visible for the entity.\n\nOnly the UI issue remains.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4115114439, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23214#issuecomment-4115114439", "createdAt": "2026-03-24T03:23:05Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23214, "url": "https://github.com/glpi-project/glpi/issues/23214", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "ui" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-23T20:36:59Z", "updatedAt": "2026-07-03T00:49:57Z", "closedAt": "2026-03-24T09:51:00Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Issues with dropdowns in tickets and very laggy performance since GLPI 11", "detail": "Affected version:\n11.0.4\n\nIssue description:\nRandomly when editing a ticket, when you click on some of the dropdown it glitches and the dropdown opens in the top left corner\n\n[Image omitted]\n\nAnd if you click again on the category dropdown it reopens at the right place\n\n[Image omitted]\n\nThe overral page is very sluggish on chrome based browser on linux.\nThis was way smoother on GLPI 10.\n\nI don't know if there are some kind of race conditions or issues in the javascript on this area\n\nReproduction steps:\n1. Open a tickets\n2. Tries to change category\n3. It randomly glitches", "priority": "medium", "type": "support", "createdByEmail": "jamie.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "We are aware of the performance degradation introduced in GLPI 11. There is already a bug report open for general performance issues on the ticket/change/problem timeline view in #21115.\n\nI believe this specific case is caused by TinyMCE which I noted as one of several potential causes in the referenced bug report. The forms for new followups/tasks/etc are all existing on the page immediately and the rich-text editors (TinyMCE) are initialized when the page loads and this is not the fastest process especially when each editor loads nearly 2MB of CSS for it to be styled properly. The CSS is cached by the browser, but that still takes time to parse. While the browser is busy with that, it cannot properly work on other things like initializing the dropdowns (Select2) or handing user actions like clicks.\n\nOriginal response date: 2026-03-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4122138512, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22598#issuecomment-4122138512", "createdAt": "2026-03-24T23:44:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22598, "url": "https://github.com/glpi-project/glpi/issues/22598", "author": "SteadEXE", "anonymizedAuthorEmail": "jamie.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-09T08:58:58Z", "updatedAt": "2026-07-03T00:49:52Z", "closedAt": "2026-03-24T23:44:48Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "It is not possible to link a \"dropdown list\" question to an entity or group in a public (unauthenticated) form.", "detail": "Contribution description:\nContext :\n\nHello,\n\nI'm using GLPI forms with unauthenticated access (public forms).\n\nMy need is to allow the user to select, via a custom dropdown list question, a value corresponding, for example, to:\n\n\"Choose your group\"\n\n\"Choose your entity\"\n\nThe goal is to associate each possible answer with an existing requesting entity or group in GLPI, so that the created ticket is automatically assigned based on the selected option.\n\nProblem encountered\n\nThe most suitable solution seemed to be to use the following option in the response destination settings:\n\n\"Response from a specific question\"\n\nHowever, when I select this option, the \"dropdown list\" type questions in my form do not appear in the selection.\n\nFurthermore:\n\nI understand that the \"Element\" question type should be used to directly reference a GLPI entity or group.\n\nHowever, \"Element\" type questions are not visible in unauthenticated public forms, which makes this approach unusable in my case.\n\nExpected Outcome\n\nIt would be desirable to be able to:\n\nEither allow dropdown list questions to be used in the \"Answer from a specific question\" option for linking to an entity or group.\n\nOr make \"Element\" type questions compatible with unauthenticated public forms.\n\nOr offer an intermediate mechanism for mapping custom values ​​to GLPI objects (entity, group, etc.).", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hello Emerson Bennett,\n\nWe only handle bugs in issues, new features or behavior changes should be discussed here instead:\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4111011608, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23080#issuecomment-4111011608", "createdAt": "2026-03-23T14:23:33Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23080, "url": "https://github.com/glpi-project/glpi/issues/23080", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-11T08:57:04Z", "updatedAt": "2026-07-02T01:02:51Z", "closedAt": "2026-03-23T14:23:38Z" } }, { "title": "Contracts, cost field not order by date", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.23 / 11.0.5\n\nIssue description:\nHi,\nWhen you display the list of contracts, and you have enabled the display of one of the cost columns (and there are multiple costs), they are sorted by creation order and not by date. If you open the contract and go to the cost tab, then it is sorted by date.\n\nAffected page:\n/front/contract.php\n\nReproduction steps:\n1. Create a contract\n2. add more than 1 cost (first with a date in 2025, and another with a date in 2024 ...)\n3.\n[Image omitted]\n\n4. go to the list of contracts, add the column cost (name, price or start date)\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "rowan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This is not a bug. You may make a suggestion to change this behavior in the discussions here:\n\nOriginal response date: 2026-03-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4114072263, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23108#issuecomment-4114072263", "createdAt": "2026-03-23T22:17:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23108, "url": "https://github.com/glpi-project/glpi/issues/23108", "author": "TheRoby", "anonymizedAuthorEmail": "rowan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-13T10:25:40Z", "updatedAt": "2026-07-02T01:02:45Z", "closedAt": "2026-03-23T22:17:11Z" } }, { "title": "[11.0.6] Issue with the display of linked items", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nHello,\n\nAfter updating from 11.0.5 to 11.0.6, I noticed that there is an issue with the linked items.\n\nThey no longer display correctly in the associated section. Regardless of the number of associated items, the list displays dozens of unrelated items that have never been associated with the current item.\n\nFor example, I have an item (Xbox Series S) here that is linked to only one another item (the Xbox controller). The number of linked items is showing correctly (1), but the list shows a lot of items that are not related nor linked, instead of showing the only linked item.\n\nThis is very annoying, because it is no longer possible to see which items are associated with the item you are currently viewing.\n\nThis issue is identical on both of my GLPI instances after the update.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "This should be fixed by when it is merged.\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4030018060, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23429#issuecomment-4030018060", "createdAt": "2026-03-10T09:43:32Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23429, "url": "https://github.com/glpi-project/glpi/issues/23429", "author": "SachaKeserovic", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-03-10T09:39:59Z", "updatedAt": "2026-07-01T01:07:14Z", "closedAt": "2026-03-10T09:43:05Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Massive Actions for status visibility do not work", "detail": "Affected version:\n11.0.1\n\nIssue description:\nTwo issues seen while looking at another bug report:\n- Visibility for custom asset types do not show in the update massive action for statuses\n- Updates through massive actions for core itemtypes does not work.\n\nAffected page:\n/front/state.php", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I have a fix for issue 1 (_Updates through massive actions for core itemtypes does not work._)\nI'll push it on monday.\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3756050703, "author": "SebSept", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/21520#issuecomment-3756050703", "createdAt": "2026-01-15T17:29:57Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 21520, "url": "https://github.com/glpi-project/glpi/issues/21520", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "SebSept", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-10-16T09:56:16Z", "updatedAt": "2026-06-26T01:05:43Z", "closedAt": "2026-03-17T14:10:02Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "npm audit failed (11.0/bugfixes)", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "- flatted has been upgraded by #23491\n- the version of yauzl we use seems to not be vulnerable, see\n\nOriginal response date: 2026-03-16", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4066712666, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23494#issuecomment-4066712666", "createdAt": "2026-03-16T10:37:43Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23494, "url": "https://github.com/glpi-project/glpi/issues/23494", "author": "github-actions[bot]", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-16T10:19:49Z", "updatedAt": "2026-06-25T01:02:35Z", "closedAt": "2026-03-16T10:37:43Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "\"Project Tasks\" tab crashes on a Ticket, doesn't display linked project tasks.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI: 11.0.6\n\nIssue description:\nThe \"Project Tasks\" tab in Tickets does not display the linked project tasks. Instead, the tab crashes with the following error. However, the \"Tickets\" tab of that same Project Task will display the linked tickets.\n\n[Image omitted]\n\nReproduction steps:\n1. Create a Project Task and link it to a Ticket. The linked Ticket will then be visible in the \"Tickets\" tab of that project task\n\n[Image omitted]\n\n2. Open the ticket you linked in Step 1. Select the \"Project Tasks\" tab of that same Ticket. Instead of showing the linked project tasks, the tab crashes with the following error\n\n Note the \"Project Tasks\" tab displays the count of linked project tasks (e.g. 1), although it doesn't display the content.\n\n[Image omitted]\n\nEnvironment details:\nGLPI: 11.0.6 ( => /var/www/)\nInstallation mode: TARBALL\nCurrent language: en_GB\nSource Integrity: 16 files changed\n A: inc/downstream.php\n A: public/favicon.ico\n M: public/pics/favicon.ico\n M: public/pics/fd_logo.png\n M: public/pics/login_logo_glpi.png\n M: public/pics/logos/logo-G-100-black.png\n M: public/pics/logos/logo-G-100-grey.png\n M: public/pics/logos/logo-G-100-white.png\n M: public/pics/logos/logo-GLPI-100-black.png\n M: public/pics/logos/logo-GLPI-100-grey.png\n M: public/pics/logos/logo-GLPI-100-white.png\n M: public/pics/logos/logo-GLPI-250-black.png\n M: public/pics/logos/logo-GLPI-250-grey.png\n M: public/pics/logos/logo-GLPI-250-white.png\n M: public/pics/logos/sources/GLPI_Logo-color.svg\n M: public/pics/logos/sources/GLPI_Logo-white.svg\n\nAdditional context:\nI can reproduce this issue on a fresh instance of GLPI running on a separate server.", "priority": "medium", "type": "support", "createdByEmail": "jordan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "fixed by #23436. it will be part of GLPI 11.0.7.\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4044369035, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23454#issuecomment-4044369035", "createdAt": "2026-03-12T06:42:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23454, "url": "https://github.com/glpi-project/glpi/issues/23454", "author": "shanel-svi", "anonymizedAuthorEmail": "jordan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-12T05:03:02Z", "updatedAt": "2026-06-21T01:13:35Z", "closedAt": "2026-03-12T06:42:40Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "[BUG 11.0.6] Helpdesk search broken: Failed to resolve module specifier 'IndexController.js' (importmap path mismatch)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\nAfter upgrading from 11.0.5 to 11.0.6, the central search bar in the Simplified Interface (Helpdesk) stopped working completely. Typing or pressing Enter does nothing.\n\nUpon checking the browser console, the following fatal error is thrown immediately when loading the page:\nTypeError: Failed to resolve module specifier 'js/modules/Helpdesk/IndexController.js'. Relative references must start with either \"/\", \"./\", or \"../\".\n\nRoot Cause Analysis:\nThe bug is caused by a path mismatch between the importmap generated by GLPI and the actual import call in the HTML, specifically when running behind a Reverse Proxy.\n\nIn the generated , the key is generated with a leading slash:\n\"\\/js\\/modules\\/Helpdesk\\/IndexController.js\"\n\nHowever, the tag attempting to load the module calls it without the leading slash:\nconst module = await import(\"js/modules/Helpdesk/IndexController.js\");\n\nBecause the paths do not match exactly, the browser ignores the importmap and fails to load the module. Setting TRUSTED_PROXIES or GLPI_ROOT_DOC_URL does not bypass this discrepancy.\nNote: This was working perfectly in 11.0.5 and broke in 11.0.6.\n\nIt might be unrelated, but I tested it on two instances in different environments, both running Docker with the official image, updating manually with GLPI_SKIP_AUTOUPDATE=true enabled, thus updating through the GLPI interface itself instead of letting the process happen automatically.\n\n[Image omitted]\n\nAffected page:\n\nReproduction steps:\nInstall GLPI 11.0.5 in Docker with GLPI_SKIP_AUTOUPDATE=true using the official image.\n\nPlace the container behind a reverse proxy (e.g., Apache/Nginx) that supports HTTPS.\n\nUpdate GLPI 11.0.6 using the official Docker image (glpi/glpi).\n\nLog in with a profile that uses the Simplified Interface (Self-Service).\n\nAccess the Helpdesk page and try using the central search bar.\n\nOpen the browser console and observe the TypeError that prevents the search from working.\n\nUsing CTRL + U after the error occurs, you can also view the importmaps.", "priority": "medium", "type": "support", "createdByEmail": "finley.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "fixed by #23343. will be included with 11.0.7.\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4046576156, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23457#issuecomment-4046576156", "createdAt": "2026-03-12T12:59:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23457, "url": "https://github.com/glpi-project/glpi/issues/23457", "author": "erique-souza", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-12T12:47:04Z", "updatedAt": "2026-06-21T01:13:17Z", "closedAt": "2026-03-12T12:59:48Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Profile users list counter mismatch", "detail": "Affected version:\n11.0.4\n\nIssue description:\nSeveral display issues have been observed in the GLPI interface. They appear to be UI-related and reproducible.\n\n1. Users list pagination not respected\nPath: Administration > Profiles > Users\n\nWhen setting \"Entries to display\" to 40 (or any value greater than 10), the list still displays only 10 users maximum.\nThe pagination setting is not applied to the displayed list.\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "User originally reported a pagination issue, but it seems to me that this works properly. Instead, the issue likely stems from the tab counter counting deleted users, while the list itself ignores them.\n\nOriginal response date: 2025-12-29", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3696578359, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22498#issuecomment-3696578359", "createdAt": "2025-12-29T13:45:55Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22498, "url": "https://github.com/glpi-project/glpi/issues/22498", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-29T13:44:47Z", "updatedAt": "2026-06-20T01:05:57Z", "closedAt": "2026-03-11T08:43:01Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Dashboard cards for tickets by actor do not handle non-users correctly", "detail": "Issue description:\n_Originally posted by Taylor Adler in #23251_", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "fixed by\n\nOriginal response date: 2026-03-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4043113257, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23361#issuecomment-4043113257", "createdAt": "2026-03-12T00:37:46Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23361, "url": "https://github.com/glpi-project/glpi/issues/23361", "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "dashboard" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-04T22:23:44Z", "updatedAt": "2026-06-20T01:05:27Z", "closedAt": "2026-03-12T00:37:46Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "PHP 8.4.16 rejected by version check: upper bound excludes 8.4.x patch releases", "detail": "Issue description:\nGLPI is rejecting PHP 8.4.16 with the following error:\n\n| [REQUIRED] PHP Parser | [ERROR] | PHP version must be between 7.4.0 and 8.4.0 (exclusive). |\n\nThis seems to be caused by the PHP version check using 8.4.0 as an exclusive upper bound, which also rejects all PHP 8.4.x patch releases such as 8.4.16.\n\nExpected behavior:\nGLPI should accept supported PHP 8.4.x patch versions, or the compatibility check should be clarified if PHP 8.4 is intentionally unsupported.\n\nObserved behavior:\nPHP 8.4.16 is detected as incompatible because the validator says the version must be lower than 8.4.0 exclusively.\n\nTo reproduce:\n1. Install PHP 8.4.16\n2. Run GLPI installation or requirements check\n3. See the error:\n\ntext\n[REQUIRED] PHP Parser [ERROR] PHP version must be between 7.4.0 and 8.4.0 (exclusive).", "priority": "medium", "type": "support", "createdByEmail": "robin.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "robin.bennett@peppermint.local", "text": "downloaded wrong version\n\nOriginal response date: 2026-03-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4031541702, "author": "DevDorrejo", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23437#issuecomment-4031541702", "createdAt": "2026-03-10T13:52:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23437, "url": "https://github.com/glpi-project/glpi/issues/23437", "author": "DevDorrejo", "anonymizedAuthorEmail": "robin.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-10T13:43:16Z", "updatedAt": "2026-06-19T01:16:06Z", "closedAt": "2026-03-10T13:52:34Z" }, "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "items duplicated for requester in ticket", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nin the de device list apears duplicated items\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "It seems like this could be recreated if an asset has the user assigned directly in the User field, and one of the user's groups in the Group field.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3993772132, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22914#issuecomment-3993772132", "createdAt": "2026-03-03T21:52:53Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22914, "url": "https://github.com/glpi-project/glpi/issues/22914", "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-30T06:33:18Z", "updatedAt": "2026-06-19T01:16:00Z", "closedAt": "2026-03-10T08:22:36Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Clear SMTP Authentication credentials not working in email followup configuration", "detail": "Affected version:\n10.0.18\n\nIssue description:\nI've been trying to migrate email followups from SMTP Auth via SMTP+TLS to SMTPOAuth as Microsoft is soon deprecating SMTP Auth and i've discovered an issue when trying to migrate protocol.\n\nOn already setup GLPI instances, if we try to setup the OAuth2 app details and then try with the test email, the test will always fail.\n\nNavigating to the all section of /front/notificationmailingsetting.form.php shows that SMTP login is still compiled and possibly being used, even though we're using another protocol.\n\nTrying to delete the SMTP auth credentials by using the clear button and then saving, doesn't actually clear the SMTP credentials. This is proven by the fact that if we logout and login again, navigate to the /front/notificationmailingsetting.form.php page and referr to the ALL section, the SMTP Login is again compiled.\n\nAffected page:\n/front/notificationmailingsetting.form.php\n\nReproduction steps:\n1. Setup email followps first using the SMTP Auth protocol with SMTP+TLS\n2. Send a test email to ensure it works\n3. Now try to migrate to SMTPOAuth, switching the dropdown from SMTP+TLS to SMTPOAUTH\n4. Compile each field of the dedicated section with the necessary details (provider, client id, client secret, tenant id etc.)\n5. Proceed with the authorization using the mailbox that GLPI will use to send emails\n6. Save\n7. Try to send a test email, the expected output is the red popup on the bottom right stating \"Failed to send a test email to the administrator\"\n8. Logout and login\n9. Navigate to the email followup configuration page and click the \"all\" section on the left\n10. Under the mail server oauth2 configuration, where client id etc. fields are located, you should still see the smtp login fields compiled (only email as password is hidden)\n\nAdditional context:\nPlease do not hide this kind of information in the ALL section, it's frustrating to troubleshoot when even the menus do not collaborate.\n\nThis issue do not happen on new and clean GLPI instances that have email followup yet to be configured.\n\nThe workaround to fix this issue and successfully migrate from SMTP AUTH to SMTPOAUTH is to override the SMTP AUTH credentials, as when i tried to put a random not correct password in the SMTP AUTH PASSWORD field and saved, the SMTP OAUTH test email worked.", "priority": "medium", "type": "support", "createdByEmail": "hayden.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "drew.blair@peppermint.local", "text": "This PR #24517 should fix it.\n\nOriginal response date: 2026-06-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4661421423, "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/19835#issuecomment-4661421423", "createdAt": "2026-06-09T15:38:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 19835, "url": "https://github.com/glpi-project/glpi/issues/19835", "author": "xBounceIT", "anonymizedAuthorEmail": "hayden.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-05-28T13:22:15Z", "updatedAt": "2026-06-18T07:45:33Z", "closedAt": "2026-06-18T07:44:58Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Undefined array key \"usercategories_id\" in TreeBrowse.php line 284", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWhen navigating to Administration > Users, a PHP Warning is constantly generated in the logs. It appears that the TreeBrowse trait is trying to access the usercategories_id key in an array where it does not exist. This does not block the UI but floods the php-errors.log.\n\n[Image omitted]\n\nReproduction steps:\n1. Log in as a Super-Admin.\n\n2. Go to Administration > Users.\n\n3. Check the files/_log/php-errors.log file.\n\n4. Observe the glpi.WARNING: Undefined array key \"usercategories_id\" error.\n\nEnvironment details:\nOperating System: Linux Ubuntu server 24.04\nPHP: 8.3.6\nGLPI Version: 11.0.4 Community\nDatabase: MariaDBVer 15.1 Distrib 10.11.13-MariaDB\n\nAdditional context:\nI have analyzed the file src/Glpi/Features/TreeBrowse.php around line 284. The code tries to access $category[$cat_fk] (where $cat_fk is usercategories_id) without checking if the key exists in the $category array.\n\nProposed Fix: I manually tested a patch adding the null coalescing operator, and it stopped the warnings.\n\nCurrent code (line 284):\n\nPHP\n$parents[] = $category[$cat_fk];\n\nWorking fix:\n\nPHP\n$parents[] = $category[$cat_fk] ?? 0;", "priority": "medium", "type": "support", "createdByEmail": "avery.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please open a pull request with your fix proposal\n\nOriginal response date: 2026-01-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3798180976, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22819#issuecomment-3798180976", "createdAt": "2026-01-26T07:13:01Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22819, "url": "https://github.com/glpi-project/glpi/issues/22819", "author": "00Venfan00", "anonymizedAuthorEmail": "avery.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-24T18:56:49Z", "updatedAt": "2026-06-18T01:10:28Z", "closedAt": "2026-03-09T12:59:06Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Unable to link/unlink software from License form", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nWhen creating a License (Management > Licenses) without assigning a software, there \"Software\" field do not allow to select an existing software, but\n\nAffected page:\n\nReproduction steps:\nFirst scenario: do not assign a software during license creation:\n\n1. Go to Management > Licenses.\n2. Create a license without assign a software.\n3. Try to assign a software to the license after creation: Message \"Not linked to any software\" is shown\n\n[Image omitted]\n\nSecond scenario: assigning a software during license creation:\n\n1. Go to Management > Licenses.\n2. Create a license assigning a software.\n3. The Software name is shown, but it's impossible to change the software or unlink it:\n\n[Image omitted]\n\nIn both scenarios, I can still assign/unasign a software to a license through Massive Actions into Management > Licenses page:\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "After looking at this more, I don't think it is a bug. It seems the intention was for licenses to not be transferable. If you have a license, you cannot associate it to a new/different software later in its life.\n\nFeel free to suggest a change on the roadmap discussions (the new home for suggestions).\n\nOriginal response date: 2026-03-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4016315630, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22906#issuecomment-4016315630", "createdAt": "2026-03-07T11:47:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22906, "url": "https://github.com/glpi-project/glpi/issues/22906", "author": "eduardomozart", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "ux" ], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-29T19:49:46Z", "updatedAt": "2026-06-16T01:16:03Z", "closedAt": "2026-03-07T11:47:48Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Unexpected error after login: Class \"Normalizer\" not found", "detail": "Issue description:\nI installed glpi yesterday and take a look everywhere and it was find. But today i have an error after the login:\n\nPhp version:\n\nGlpi version: 11.0.6\n\nI have done nothing yet in the app, i login as admin with glpi/glpi credentials.\n\nHow can i fix it ?\n\nEdit: The result the check requirements command:", "priority": "medium", "type": "support", "createdByEmail": "skyler.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.bennett@peppermint.local", "text": "It was a php issue, the intl extension was not loaded even if it was enabled in the php.ini.\n\nI followed this solution:\n\nI found a way to do that which works for me. What I did is to copy the all the files containing this name icu.dll from my php directory into the Apache bin directory then restart my server.\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4010391891, "author": "Asmitta-01", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23391#issuecomment-4010391891", "createdAt": "2026-03-06T08:47:04Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23391, "url": "https://github.com/glpi-project/glpi/issues/23391", "author": "Asmitta-01", "anonymizedAuthorEmail": "skyler.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-03-06T08:01:31Z", "updatedAt": "2026-06-15T01:13:51Z", "closedAt": "2026-03-06T08:47:04Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "invalid memory_limit warning in log php-errors.log", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI believe GLPI may attempt to set an invalid memory_limit value automatically from src/Toolbox.php.\n\nToolbox::getMemoryLimit() tries to calculate an “optimal” memory limit based on the detected system memory.\nIn containerized or cgroup-limited environments, the detected system memory may be incorrect or effectively unlimited, which can lead to extremely large calculated values.\n\nWhen this value is later applied via Toolbox::safeIniSet(), PHP rejects it and emits warnings such as:\n\nFailed to set memory_limit to XXX bytes.\nSetting to max_memory_limit instead\n\nThis can occur even when memory_limit is already explicitly defined in php.ini.\n\nProposed fix\n\nThe fix does not remove GLPI’s memory optimization logic.\nIt only validates computed values before applying them, ensuring GLPI never attempts to exceed PHP’s effective limits.\n\n1. Clamp calculated memory limit in getMemoryLimit()\n\nAfter calculating $memory_limit (in bytes):\n\n$php_max = self::getSizeInBytes(ini_get($ininame));\n\nif ($php_max > 0 && $memory_limit > $php_max) {\n $memory_limit = $php_max;\n}\n\nThis prevents GLPI from generating values beyond PHP’s effective memory_limit.\n\n2. Guard safeIniSet() against invalid increases\n\nIn Toolbox::safeIniSet() before calling Safe\\ini_set():\n\nif ($key === 'memory_limit') {\n $current = ini_get('memory_limit');\n $current_bytes = self::getSizeInBytes($current);\n $target_bytes = is_numeric($value) ? (int)$value : self::getSizeInBytes($value);\n\n if ($current_bytes > 0 && $target_bytes > $current_bytes) {\n return;\n }\n}\n\nThis avoids unnecessary calls that PHP will reject, preventing warnings while preserving existing behavior.\n\nAdditional context:\nGLPI should never attempt to set memory_limit higher than the effective PHP limit already enforced by php.ini or inc/downstream.php.\nIf PHP already defines a valid limit, GLPI should respect it and avoid triggering warnings.", "priority": "medium", "type": "support", "createdByEmail": "drew.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "fixed by #22934\n\nOriginal response date: 2026-03-06", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4013887454, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22933#issuecomment-4013887454", "createdAt": "2026-03-06T20:10:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22933, "url": "https://github.com/glpi-project/glpi/issues/22933", "author": "monta990", "anonymizedAuthorEmail": "drew.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-31T01:26:16Z", "updatedAt": "2026-06-15T01:13:37Z", "closedAt": "2026-03-06T20:10:41Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "ESX Inventory Task does not list agents with CustomAsset itemtype as Actors", "detail": "Environment:\n- GLPI version: 11.5\n- GLPI Agent version: 1.16\n- ESX task installed via RPM module\n- Inventory tasks enabled\n\nIssue description:\nWhen configuring an ESX Inventory task, only agents linked to Computer itemtype are available in the Actors dropdown.\n\nAgents linked to a Custom Asset (e.g. Glpi\\CustomAsset\\ServerAsset) do not appear in the Actors list, even though:\n\n- The agent is online\n- ESX task is installed and enabled\n- The agent supports ESX inventory\n- Network connectivity to vCenter/ESXi is working\n\nReproduction steps:\n1. Install GLPI 11.5\n2. Install GLPI Agent 1.16 on two hosts\n3. On agent 1, keep default itemtype = Computer\n4. On agent 2, configure: itemtype = Glpi\\CustomAsset\\ServerAsset\n5. Ensure ESX task module is installed on both agents\n6. Go to: Setup → Inventory → ESX Tasks\n7. Create or edit an ESX Inventory task\n8. Open the Actors dropdown\n\nCurrent behavior:\nOnly the agent linked to Computer appears in the Actors list.\n\nThe agent linked to Glpi\\CustomAsset\\ServerAsset does not appear.\n\nExpected behavior:\nAny agent with:\n\n- ESX task enabled\n- Online status\n- Proper connectivity\n\nshould be selectable as Actor, regardless of its linked itemtype.\n\nAdditional notes:\nThe restriction seems to be related to how GLPI filters agents for Inventory Tasks based on their associated itemtype.\n\nIt looks like only agents linked to Computer objects are considered eligible Actors.\n\nPlease confirm whether this is:\n\n- an intended limitation\n- a missing feature for CustomAsset support\n- or a bug\n\nAgents config\n[Image omitted]\n[Image omitted]\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jamie.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Hi, this is not related to GLPI, but to inventory plugin.\nAlso, this would be a feature, that would require a lot of work. This is not planned right now.\n\nOriginal response date: 2026-03-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4002750614, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23354#issuecomment-4002750614", "createdAt": "2026-03-05T07:04:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23354, "url": "https://github.com/glpi-project/glpi/issues/23354", "author": "Xlebati", "anonymizedAuthorEmail": "jamie.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-03-04T15:57:20Z", "updatedAt": "2026-06-14T01:11:27Z", "closedAt": "2026-03-05T07:04:11Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "[10.0.23 and 11.0.5] Inability to filter by future dates in Project Management", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.23\n\nIssue description:\nIn the Project Management module, the filter options do not support searching for future dates using the \"+\" prefix (e.g., +1 day, +1 month).\n\nIn contrast, the Contract Management module does include this functionality. For instance, it allows users to filter contracts with an end date set to occur within the next month.\n\n[Image omitted]\n\nIn Project Management, there is no option to filter by future dates, such as \"planned end date before +1 month.\"\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "reese.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm. These planned date search options are missing the maybefuture property in the code.\n\nOriginal response date: 2026-02-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3904750412, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23122#issuecomment-3904750412", "createdAt": "2026-02-15T16:14:03Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23122, "url": "https://github.com/glpi-project/glpi/issues/23122", "author": "luisjosemachado", "anonymizedAuthorEmail": "reese.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-15T15:37:22Z", "updatedAt": "2026-06-14T01:11:18Z", "closedAt": "2026-03-05T14:24:58Z" }, "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "followup.author.actortype value always return '0'", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nIn the code of my notification mails, the variable followup.author.actortype always returns 0 even if the user is either the ticket author, observer or responsible technician.\n\nThis bug already exists in GLPI 10.0.20 (my prod version)", "priority": "medium", "type": "support", "createdByEmail": "noel.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I'm not sure it is a bug. The actor data function call explicitly uses actor type 0 for followup actors. The only time it is really used are for tags like \"ticket.authors\". If you want to know if a followup is from a requester or assigned technician, I don't know if it can be done currently but I suppose it could be possible when notifications are changed to use Twig for the templates instead of the custom template language currently used.\n\nOriginal response date: 2026-02-26", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3967255486, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23254#issuecomment-3967255486", "createdAt": "2026-02-26T15:12:25Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23254, "url": "https://github.com/glpi-project/glpi/issues/23254", "author": "RandomFrenchAdmin", "anonymizedAuthorEmail": "noel.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-26T14:23:56Z", "updatedAt": "2026-06-13T01:09:26Z", "closedAt": "2026-03-04T10:33:16Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "The network port traffic graph looks bad", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n10.0.22\n\nIssue description:\nThe date data is not displayed correctly in the graph.\n\n[Image omitted]\n\nAffected page:\nfront/networkport.form.php?id=xxxxxx", "priority": "medium", "type": "support", "createdByEmail": "riley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "10.0.22 is outdated, this issue has been fixed.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3989056967, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23323#issuecomment-3989056967", "createdAt": "2026-03-03T06:53:09Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23323, "url": "https://github.com/glpi-project/glpi/issues/23323", "author": "ftoledo-opensa", "anonymizedAuthorEmail": "riley.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-03-02T19:18:10Z", "updatedAt": "2026-06-12T01:11:34Z", "closedAt": "2026-03-03T06:53:09Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "GLPI [11.0.5] Impossible to update Tickets custom fields via API", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHey,\nSince updating from GLPI 11.0.2 to 11.0.5, i cannot modify the custom fields of my tickets with the API (tested with legacy rest API and the newer one ). For the custom fields, i use the plugin Fields 1.23.3. To modify i use this kind of body :\nPATCH \"\" -H \"Content-Type: application/json\" -d \"{\"input\":[{\"id\":103,\"c_id\":13,\"customfield\": \"TEST\"}]}\"\nIt worked well with the 11.0.2 version.\nRight now, only standard fields are updated ( like name )\n\nReproduction steps:\n1. Try to update a custom field for a ticket with API in GLPI 11.0.2 => It works\n2. Try to do the same with GLPI 11.0.5 => It doesn't work anymore", "priority": "medium", "type": "support", "createdByEmail": "micah.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Issues posted here should only be about GLPI core, not the plugins. You may post this again on the plugin GitHub.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3992095804, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23335#issuecomment-3992095804", "createdAt": "2026-03-03T16:15:49Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23335, "url": "https://github.com/glpi-project/glpi/issues/23335", "author": "bapt1508", "anonymizedAuthorEmail": "micah.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-03-03T16:05:08Z", "updatedAt": "2026-06-12T01:11:31Z", "closedAt": "2026-03-03T16:15:49Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Search input: Enter key no longer triggers search in Assistance > Tickets filters", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nIn Assistance → Tickets, when using the search fields inside the filters, pressing the Enter key no longer launches the search.\n\nThe only way to apply the search is to manually click on the “Search” button.\n\nThis results in a degraded user experience compared to previous behavior, where pressing Enter was sufficient to trigger the search.\n\nReproduction steps:\n1. Go to Assistance → Tickets\n2. Open or use the filters panel\n3. Click inside a search input field\n4. Type a value\n5. Press Enter", "priority": "medium", "type": "support", "createdByEmail": "finley.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I am not able to recreate the issue. If the issue is still present on the latest GLPI 11 release, feel free to reopen this.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3994261104, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22783#issuecomment-3994261104", "createdAt": "2026-03-03T23:44:40Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22783, "url": "https://github.com/glpi-project/glpi/issues/22783", "author": "blainvillem", "anonymizedAuthorEmail": "finley.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-21T16:57:08Z", "updatedAt": "2026-06-12T01:11:28Z", "closedAt": "2026-03-03T23:44:40Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Rack background color not applied in Server rooms rack grid view (GLPI 11.0.4)", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nWe have set different Background color values for several rack objects (Home → Assets → Racks) but when viewing the server room grid (Home → Management → Data centers → Server rooms → Racks tab), all racks appear with the same color in the grid regardless of the color configured.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "logan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I believe this should be fixed in GLPI 11.0.6 via #23136. If the issue remains on the latest release, feel free to reopen this.\n\nOriginal response date: 2026-03-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3994265037, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22767#issuecomment-3994265037", "createdAt": "2026-03-03T23:45:50Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22767, "url": "https://github.com/glpi-project/glpi/issues/22767", "author": "pheamakara", "anonymizedAuthorEmail": "logan.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-21T09:51:41Z", "updatedAt": "2026-06-12T01:11:25Z", "closedAt": "2026-03-03T23:45:50Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Approver Not Visible", "detail": "Affected version:\n11.0.4\n\nIssue description:\nIn the Ticket Creation section, approver is not coming. I am not able to select user for approval. While in the older 10.0.11 versions it had this.\n\nReproduction steps:\n1. Login to glpi\n2. Goto assistance.\n3. click on create ticket.", "priority": "medium", "type": "support", "createdByEmail": "jordan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I'm not aware of any feature in GLPI 10 that lets you create an approval directly from the new ticket form. If this is still an issue with the latest release, feel free to reopen with some more details about the behavior on GLPI 10.\n\nOriginal response date: 2026-03-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3994367509, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22702#issuecomment-3994367509", "createdAt": "2026-03-04T00:14:54Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22702, "url": "https://github.com/glpi-project/glpi/issues/22702", "author": "Dheemant6", "anonymizedAuthorEmail": "jordan.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-16T12:22:18Z", "updatedAt": "2026-06-12T01:11:22Z", "closedAt": "2026-03-04T00:14:54Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "service@pinecrest-financial.peppermint.local" }, { "title": "Unable to import Ruckus ICX7650 stack through Inventory.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI am unable to import properly a Ruckus/Brocade ICX7650 2 switch stack. From what I gathered, it seems to detect the stack, tries to seperate it into several switches but fails to copy the model around, which makes the import fail since the value is null.\n\nAffected page:\n/Inventory/ImportFiles\n\nReproduction steps:\ninventory.xml\n\nWith this inventory file (Generated from glpi-agent), try to import it in Administration / Inventory / Import from file.\n\nIt should fail like this in debug mode:\n\n[Image omitted]", "priority": "medium", "type": "maintenance", "createdByEmail": "hayden.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please try with #23289\n\nOriginal response date: 2026-03-02", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3982708125, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23261#issuecomment-3982708125", "createdAt": "2026-03-02T07:50:58Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23261, "url": "https://github.com/glpi-project/glpi/issues/23261", "author": "greatman", "anonymizedAuthorEmail": "hayden.adler@peppermint.local", "assignees": [], "labels": [ "inventory" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-26T15:32:19Z", "updatedAt": "2026-06-11T01:08:20Z", "closedAt": "2026-03-02T11:03:09Z" }, "clientEmail": "care@lumen-retail.peppermint.local" }, { "title": "Error when changes in purge history", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.7\n\nIssue description:\nAs our GLPI starts to become wuite old, we want to clean come old history events (like in computer, software...)\nSo when we go on page History purge in Configuration > General > Purge history.\nI tried to change some values to add \"delete if older than x month\".\nWhen i then clic on save, the sql error appears, but if i return to that menu, only the first value modified has been changed.\nwe tried on 3 categories, the error appeared for each one :\n- install/uninstall softwares\n- installed/uninstalled version\n- delete component\n\nOn the SQL error it says Unknown column 'old_id', but I don't understand because, yes this column do not exist on the database :\n| Field | Type | Null | Key | Default | Extra |\n+------------------+------------------+------+-----+---------+----------------+\n| id | int(10) unsigned | NO | PRI | NULL | auto_increment |\n| itemtype | varchar(100) | NO | MUL | | |\n| items_id | int(10) unsigned | NO | | 0 | |\n| itemtype_link | varchar(100) | NO | MUL | | |\n| linked_action | int(11) | NO | | 0 | |\n| user_name | varchar(255) | YES | | NULL | |\n| date_mod | timestamp | YES | MUL | NULL | |\n| id_search_option | int(11) | NO | MUL | 0 | |\n| old_value | varchar(255) | YES | | NULL | |\n| new_value | varchar(255) | YES | | NULL | |\n+------------------+------------------+------+-----+---------+----------------+\n\nsame for the \"new_id\" even if there is no errors about that one\n\nAffected page:\n\nReproduction steps:\n1.Configuration\n2.General\n3.Purge history\n4.change some values \"delete if older than x month\"\n5.save\n6.error\n\nEnvironment details:\nThe server runs on GLPI 11.0.7. It's a server that received many upgrades since maybe 9.2\nBefore 11.0.7 it was on 10.0.25, no error in the upgrade", "priority": "medium", "type": "support", "createdByEmail": "parker.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Your database seems broken, this field should have been created during v11 migration. Run the check_database_schema_consistency console tool; this may not be the only problem.\n\nOriginal response date: 2026-06-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4666698019, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24518#issuecomment-4666698019", "createdAt": "2026-06-10T04:59:51Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24518, "url": "https://github.com/glpi-project/glpi/issues/24518", "author": "plburguet", "anonymizedAuthorEmail": "parker.adler@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-06-09T15:37:29Z", "updatedAt": "2026-06-10T05:00:08Z", "closedAt": "2026-06-10T05:00:08Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "npm audit failed (11.0/bugfixes)", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed by #23213.\n\nOriginal response date: 2026-02-24", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3952387079, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23204#issuecomment-3952387079", "createdAt": "2026-02-24T14:30:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23204, "url": "https://github.com/glpi-project/glpi/issues/23204", "author": "github-actions[bot]", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-23T10:18:08Z", "updatedAt": "2026-06-05T01:05:46Z", "closedAt": "2026-02-24T14:30:42Z" } }, { "title": "Oauth IMAP plugin page column name bad typo", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nIn the Oauth IMAP plugin page, column name caracter are display with ' instead of ' :\n\n[Image omitted]\n\nAffected page:\nplugins/oauthimap/front/application.php\n\nReproduction steps:\n1. Oauth IMAP plugin activate\n2. Go to Setup --> Oauth IMAP\n3. You can see column name with bad typo \"'\"\n\nEnvironment details:\nOn Ubuntu 24.04, PHP 8.4 and 8.3", "priority": "medium", "type": "support", "createdByEmail": "emerson.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Please report plugins issues against plugins, not GLPI core.\n\nOriginal response date: 2026-02-23", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3943031047, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23196#issuecomment-3943031047", "createdAt": "2026-02-23T07:01:02Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23196, "url": "https://github.com/glpi-project/glpi/issues/23196", "author": "Bigthibo", "anonymizedAuthorEmail": "emerson.blair@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-20T21:48:35Z", "updatedAt": "2026-06-04T01:15:06Z", "closedAt": "2026-02-23T07:01:02Z" } }, { "title": "11.0.5 Issue after bug fix error creating ticket#22940", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nSo after this fix:\n\nThe change on the 'CommonITILObject.php' file does fix the problem. However, it introduces another one: we are unable to\nchange the requester or assign the ticket to another person before validating the ticket, we see the message 'Results cannot be loaded' displayed\n\n[Image omitted]\n\nit also brock the personnal view\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "jesse.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "It's better to test on a nighly build rather than picking arbitrary commits.\n\nYou have to provide error logs, and test without plugins.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3869769472, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23029#issuecomment-3869769472", "createdAt": "2026-02-09T07:11:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23029, "url": "https://github.com/glpi-project/glpi/issues/23029", "author": "yajih", "anonymizedAuthorEmail": "jesse.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-05T14:29:05Z", "updatedAt": "2026-05-31T01:07:08Z", "closedAt": "2026-02-19T14:30:43Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Cant remove the last shown item in a list view", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nI can't remove the latest shown items on a list\n\nAffected page:\n/front/entity.php\n\nReproduction steps:\n1. Add one items to show\n2. try to remove it", "priority": "medium", "type": "support", "createdByEmail": "lane.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "jordan.blair@peppermint.local", "text": "Cannot reproduce. Please check if any plugin or custom settings may interfere.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3897148438, "author": "f2cmb", "anonymizedAuthorEmail": "jordan.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23028#issuecomment-3897148438", "createdAt": "2026-02-13T13:05:14Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23028, "url": "https://github.com/glpi-project/glpi/issues/23028", "author": "ichatenet", "anonymizedAuthorEmail": "lane.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-05T14:07:03Z", "updatedAt": "2026-05-31T01:07:05Z", "closedAt": "2026-02-19T14:31:16Z" } }, { "title": "Unknown property getType", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\n\npages\\management\\document_item.html.twig\n\n{% if item.getType == 'Ticket' %}\n\nReplace by\n\n{% if item.getType() == 'Ticket' %}", "priority": "medium", "type": "support", "createdByEmail": "casey.blair@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed in #23154\n\nOriginal response date: 2026-02-18", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3918744734, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23145#issuecomment-3918744734", "createdAt": "2026-02-18T05:15:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23145, "url": "https://github.com/glpi-project/glpi/issues/23145", "author": "tsmr", "anonymizedAuthorEmail": "casey.blair@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-17T12:49:01Z", "updatedAt": "2026-05-30T01:00:43Z", "closedAt": "2026-02-18T05:15:47Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Can not link custom asset and computer", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI'm unsure if this is a bug or a feature request. Currently it's impossible to link custom assets to a computer or define them as component for a computer.\nIt feels inconsistent that you can link i.e software, tickets, changes but not computers. I guess the capability Elements would be needed for custom asset", "priority": "medium", "type": "support", "createdByEmail": "taylor.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "That's not a bug, custom asset currently have several limitations; it will be improved in the future.\n\nOriginal response date: 2026-02-13", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3896240991, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23106#issuecomment-3896240991", "createdAt": "2026-02-13T10:06:36Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23106, "url": "https://github.com/glpi-project/glpi/issues/23106", "author": "tograss", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-13T09:37:11Z", "updatedAt": "2026-05-25T01:04:00Z", "closedAt": "2026-02-13T10:06:41Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Error creating template", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nI'm creating a template to later create a recurring ticket. I've noticed that when I paste a 6x40 table, the template is created correctly; however, when I paste a 6x50 (columns and rows) table, an error appears.\n\nReproduction steps:\n1. create a new template\n2. Enter fields such as request type, urgency, etc.\n3. In the \"description\" field, paste a 6x40 Excel table or similar.\n\nAdditional context:\nThis error also occurs when inserting a table of this size into forms.", "priority": "medium", "type": "support", "createdByEmail": "hayden.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Ticket template (and probably change/problem too) only accept TEXT datatypes which limits them to 65,535 characters while tickets themselves accept LONGTEXT for the content (4 billion characters). It is possible that a large table's HTML representation, especially if it has inline styles, would exceed the TEXT limit. Perhaps the datatypes in the template tables should be changed to align with the main item tables.\n\nOriginal response date: 2026-02-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3867376339, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23034#issuecomment-3867376339", "createdAt": "2026-02-08T15:11:01Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23034, "url": "https://github.com/glpi-project/glpi/issues/23034", "author": "german-giraldom", "anonymizedAuthorEmail": "hayden.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-06T01:12:07Z", "updatedAt": "2026-05-24T01:03:03Z", "closedAt": "2026-02-11T06:59:14Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "The requesting group is not displayed in the \"Requester\" column", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nGLPI 11.0.5\n\nIssue description:\nHello,\n\nWhen a ticket is created with a group selected as the requester, it does not appear in the \"Requester\" column of the ticket list in the Support module.\n\nThe ticket is correctly saved with a group as the requester, but this information is not visible in the list view.\n\nReproduction steps:\nteps to reproduce the problem:\n\nCreate a new ticket.\n\nSelect a group as the requester.\n\nSave the ticket.\n\nGo to Support > Ticket List.\n\nCheck the \"Requester\" column.\n\nAdditional context:\nObserved result:\nThe requesting group is not displayed in the \"Requester\" column.\n\nExpected result:\nThe name of the group selected as the requester should appear in the \"Requester\" column.", "priority": "medium", "type": "support", "createdByEmail": "emerson.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Not a bug. Requester group is technically a separate field but GLPI shows both Requester and Requester group in the same field in the timeline view.\n\nOriginal response date: 2026-02-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3890917142, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23098#issuecomment-3890917142", "createdAt": "2026-02-12T13:19:42Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23098, "url": "https://github.com/glpi-project/glpi/issues/23098", "author": "picinformatique", "anonymizedAuthorEmail": "emerson.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-12T13:13:39Z", "updatedAt": "2026-05-24T01:02:54Z", "closedAt": "2026-02-12T13:19:42Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Incorrect translation of Tickets “Title” in Ukrainian. It should be “Назва”.", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nIncorrect translation of Tickets “Title” in Ukrainian. It should be “Назва”.\n\nIn GLPI 11.0.5, “Title” was translated as “Посада” (Position), which is not a correct translation.\n\n[Image omitted]\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "logan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Translations are done on Transifex please fix there.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3877288654, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23067#issuecomment-3877288654", "createdAt": "2026-02-10T12:27:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23067, "url": "https://github.com/glpi-project/glpi/issues/23067", "author": "balyasbob", "anonymizedAuthorEmail": "logan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-10T11:24:23Z", "updatedAt": "2026-05-22T01:01:44Z", "closedAt": "2026-02-10T12:27:11Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Adding properties of tickets to content of ticket (description)", "detail": "Contribution description:\nI would like, in the content of the tickets, have some information that we know already, like the requester name or email (or any other information of the user who filled the form), but without asking any question.", "priority": "medium", "type": "support", "createdByEmail": "harper.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The contribution request template is only for people to open discussion on a code contribution they are willing to make themselves. For general feature suggestions, please post them on UserEcho. GitHub issues are only used for bug reports and these contribution discussions.\n\nOriginal response date: 2026-02-10", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3880339104, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23072#issuecomment-3880339104", "createdAt": "2026-02-10T19:47:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23072, "url": "https://github.com/glpi-project/glpi/issues/23072", "author": "grandjeane", "anonymizedAuthorEmail": "harper.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-10T13:51:29Z", "updatedAt": "2026-05-22T01:01:35Z", "closedAt": "2026-02-10T19:48:13Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "Large number of CVEs in container scan via trivy?", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\nlatest\n\nIssue description:\nHello!\nI was going to try glpi using docker images and downloaded the latest image from docker hub. Before running it i scanned it using Trivy ( I disccovered a large number of CVE's (1075) which was very suprising. Most of them seems to be fixed per the description but do not have a fixed version per trivy which is curious. (see attached scan report).\n\nscan.txt\n\nI believe this is a false positive due to the fact that you seem to build your image by using github actions to run commands in a pre-buiilt image instead of using a dockerfile to create the image. But I am not sure how to confirm.\n\nCould you shed some light over this?\n\nReproduction steps:\n1. install trivy in your prefered way\n2. run trivy image glpi/glpi:latest", "priority": "medium", "type": "support", "createdByEmail": "morgan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Your issue/question is related to docker build, not GLPI. Please use the dedicated repo.\n\nOriginal response date: 2026-02-09", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3869802732, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23036#issuecomment-3869802732", "createdAt": "2026-02-09T07:21:20Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23036, "url": "https://github.com/glpi-project/glpi/issues/23036", "author": "dygland", "anonymizedAuthorEmail": "morgan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-06T09:10:16Z", "updatedAt": "2026-05-21T01:03:36Z", "closedAt": "2026-02-09T07:21:20Z" } }, { "title": "Issue with Dropdowns > IP networks wrong number", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHi,\nWe migrated from version 10 to 11 and since then we have had a display problem in setup > dropdowns > IP Networks.\nWhen we look at an IP address, there are certain elements to indicate, but on the display there are a multitude of them.\n\n[Image omitted]\n\nRegards,\n\nAffected page:\n/front/ipnetwork.form.php?id=1167", "priority": "medium", "type": "support", "createdByEmail": "finley.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "I confirm. The counters may be correct, but the list seems to show every IP Address even when not related to the IP Network.\n\nOriginal response date: 2026-02-08", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3867364565, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23031#issuecomment-3867364565", "createdAt": "2026-02-08T15:04:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23031, "url": "https://github.com/glpi-project/glpi/issues/23031", "author": "NauGui", "anonymizedAuthorEmail": "finley.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-05T16:19:39Z", "updatedAt": "2026-05-21T01:03:24Z", "closedAt": "2026-02-09T10:29:27Z" }, "clientEmail": "technology@bluebird-hospitality.peppermint.local" }, { "title": "Changes in the interface.", "detail": "Issue description:\n[Image omitted]\n\nThere used to be a user login button here. Why was it removed?", "priority": "medium", "type": "support", "createdByEmail": "lane.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "The implicit ability for users with permission to update the configuration (Super-Admins) was removed in 11.0.3. Only users with a profile with the explicit Impersonation permission can do it now.\n\nOriginal response date: 2026-02-05", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3852558957, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23024#issuecomment-3852558957", "createdAt": "2026-02-05T10:16:48Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23024, "url": "https://github.com/glpi-project/glpi/issues/23024", "author": "BadgerDwarf", "anonymizedAuthorEmail": "lane.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-02-05T07:11:36Z", "updatedAt": "2026-05-17T01:00:15Z", "closedAt": "2026-02-05T10:16:48Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "composer audit failed (10.0/bugfixes)", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed by #23001.\n\nOriginal response date: 2026-02-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3846931807, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23003#issuecomment-3846931807", "createdAt": "2026-02-04T11:37:34Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23003, "url": "https://github.com/glpi-project/glpi/issues/23003", "author": "github-actions[bot]", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-04T10:08:03Z", "updatedAt": "2026-05-16T00:54:03Z", "closedAt": "2026-02-04T11:37:34Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "npm audit failed (11.0/bugfixes)", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed by #23001.\n\nOriginal response date: 2026-02-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3846932052, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23004#issuecomment-3846932052", "createdAt": "2026-02-04T11:37:38Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23004, "url": "https://github.com/glpi-project/glpi/issues/23004", "author": "github-actions[bot]", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-04T10:08:03Z", "updatedAt": "2026-05-16T00:54:00Z", "closedAt": "2026-02-04T11:37:38Z" } }, { "title": "npm audit failed (10.0/bugfixes)", "detail": "", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Fixed by #23001.\n\nOriginal response date: 2026-02-04", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3846932462, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/23002#issuecomment-3846932462", "createdAt": "2026-02-04T11:37:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 23002, "url": "https://github.com/glpi-project/glpi/issues/23002", "author": "github-actions[bot]", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-04T10:08:00Z", "updatedAt": "2026-05-16T00:53:57Z", "closedAt": "2026-02-04T11:37:44Z" }, "clientEmail": "systems@civicbridge.peppermint.local" }, { "title": "Problem creating a ticket", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.5\n\nIssue description:\nHello,\nI'm currently experiencing a problem with version 11.0.5, which is as follows:\n\nWhen any user creates a ticket, an error message appears indicating that the description field is not defined, as shown in the screenshot below.\n\n[Image omitted]\n\nIt seems the problem stems from the fact that there are empty lines in the description field.\n\nAs you can see in the screenshot, when I remove the empty lines, I am able to create the ticket.\n\n[Image omitted]\n\n[Image omitted]\n\nI checked, but no problems on this subject have been reported so far.\n\nReproduction steps:\nUpgrade to GLPI version 11.0.5\n\nCreate a ticket and enter blank lines in it\n\nClick \"Add\"\n\nEnvironment details:\nI couldn't find the tab in GLPI", "priority": "medium", "type": "support", "createdByEmail": "morgan.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Already fixed, see and\n\nOriginal response date: 2026-02-03", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3840480189, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22984#issuecomment-3840480189", "createdAt": "2026-02-03T10:30:27Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22984, "url": "https://github.com/glpi-project/glpi/issues/22984", "author": "sspoiden", "anonymizedAuthorEmail": "morgan.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-02-03T10:27:50Z", "updatedAt": "2026-05-15T00:57:14Z", "closedAt": "2026-02-03T10:30:27Z" } }, { "title": "followup notifications issue from html", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.6\n\nIssue description:\n6. ticket.name: ##ticket.name##\n\n7. followup.content: ##followup.content##\n\n8. followup.description: ##followup.description##\n\n9. followup.text: ##followup.text##\n\n10. followup.body: ##followup.body##\n\n11. followup.message: ##followup.message##\n\n12. followup.comment: ##followup.comment##\n\n13. followup.note: ##followup.note##\n\n14. ticket.followup: ##ticket.followup##\n\n15. ticket.followups: ##ticket.followups##\n\n16. ticket.lastfollowup: ##ticket.lastfollowup##\n\n17. ticket.last_followup: ##ticket.last_followup##\n\n18. ticket.solution: ##ticket.solution##\n\n19. ticket.answer: ##ticket.answer##\n\n20. ticket.response: ##ticket.response##\n\n21. followup.author: ##followup.author##\n\n22. followup.date: ##followup.date##\n\n23. followup.datetime: ##followup.datetime##\n\n*\n\nGLPI 11.0.6 - New Followup notification tags not working.\n\nWorking: ##ticket.id##, ##ticket.title##, ##ticket.status##, ##ticket.content##\n\nNOT working (output as plain text):\n##followup.content##, ##followup.description##, ##followup.text##, ##ticket.lastfollowup##, ##ticket.followups##, ##lang.followup.content##\n\nWhat is the correct tag to display followup content in email notification? Is this a bug in 11.0.6?\n\nDebug output attached.", "priority": "medium", "type": "support", "createdByEmail": "logan.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "logan.bennett@peppermint.local", "text": "updated to 11.0.7 same issue\n\nOriginal response date: 2026-05-07", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 4396765035, "author": "gutsu77", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/24166#issuecomment-4396765035", "createdAt": "2026-05-07T11:38:31Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 24166, "url": "https://github.com/glpi-project/glpi/issues/24166", "author": "gutsu77", "anonymizedAuthorEmail": "logan.bennett@peppermint.local", "assignees": [], "labels": [ "support" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-05-07T11:30:40Z", "updatedAt": "2026-05-09T19:09:52Z", "closedAt": "2026-05-09T19:09:52Z" }, "clientEmail": "support@harborview-logistics.peppermint.local" }, { "title": "Handle ID conflicts for entities.", "detail": "Issue description:\nThe entity class do not use the auto increment feature and instead manually compute the next id.\n\nThis can lead to concurrent INSERT requests picking the same id and thus failing the primary key constraint.", "priority": "medium", "type": "support", "createdByEmail": "skyler.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "IMHO, we could use the NO_AUTO_VALUE_ON_ZERO SQL mode during the installation to be able to have both the native auto increment logic activated and the ability to force the 0 ID of the root entity.\n\nIt should be pretty easy to validate this solution.\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3738184284, "author": "cedric-anne", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22625#issuecomment-3738184284", "createdAt": "2026-01-12T11:50:47Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22625, "url": "https://github.com/glpi-project/glpi/issues/22625", "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "assignees": [], "labels": [ "good first issue" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-12T11:41:49Z", "updatedAt": "2026-05-08T00:54:27Z", "closedAt": "2026-01-21T13:32:39Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "Missing expand/collapse triangle in table headers on GLPI 12 dev frontend", "detail": "Affected version:\nGLPI 12.0.0-dev\n\nIssue description:\nIn the GLPI 12 development version frontend, the expand/collapse triangle icon that used to appear next to each table name is no longer displayed.\n\nPreviously, when a page containing tables was loaded, a small triangle icon appeared in the table header, allowing the user to expand or collapse the table results. In the current GLPI 12 dev frontend, this icon is missing, which removes the ability to toggle the visibility of the table content.\n\nThis issue affects usability, especially on pages with many or large tables, since users can no longer collapse sections to better navigate the interface.\n\nExpected behavior\n\nEach table header should display the expand/collapse triangle icon, allowing users to toggle the visibility of the table rows.\n\nActual behavior\n\nThe triangle icon is not rendered anymore, and tables are always fully expanded with no way to collapse them.\n\n[Image omitted]", "priority": "medium", "type": "support", "createdByEmail": "avery.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Probably a duplicate of #22634\n\nOriginal response date: 2026-01-14", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3748611680, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22659#issuecomment-3748611680", "createdAt": "2026-01-14T09:29:17Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22659, "url": "https://github.com/glpi-project/glpi/issues/22659", "author": "FelipeBasilio1991", "anonymizedAuthorEmail": "avery.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-14T09:10:44Z", "updatedAt": "2026-05-04T00:55:40Z", "closedAt": "2026-01-23T06:34:00Z" }, "clientEmail": "helpdesk@northstar-health.peppermint.local" }, { "title": "API Patch Change Status failed", "detail": "Affected version:\n11.0.4\n\nIssue description:\nHello,\n\nI'm trying to close a change with the API in Python.\nSince 11.0.3 I can't update the status of the change.\n\nHere the code as it worked before :\n headers = {\n \"accept\": \"application/json\",\n \"Authorization\": f\"Bearer {token}\",\n \"Content-Type\": \"application/json\",\n }\n\n url = f\"{GLPI_URL}/api.php/Assistance/Change/{change_id}\"\n\n data = {\"status\": {\"id\": 3, \"name\": \"Closed\"}}\n response = requests.patch(url, headers=headers, json=data)\n\nEven from the doc page\napi.php/v2/doc\nI can't update the status.\nReturned body :\n \"id\": 103,\n \"name\": \"Test\",\n \"content\": \"\",\n \"is_deleted\": false,\n \"urgency\": 1,\n \"impact\": 1,\n \"priority\": 1,\n \"actiontime\": 0,\n \"begin_waiting_date\": null,\n \"waiting_duration\": 0,\n \"resolution_duration\": 0,\n \"close_duration\": 0,\n \"resolution_date\": null,\n \"date_creation\": \"2025-12-19T12:14:22+01:00\",\n \"date_mod\": \"2025-12-19T12:14:22+01:00\",\n \"date\": \"2025-12-19T12:14:22+01:00\",\n \"date_solve\": null,\n \"date_close\": null,\n \"global_validation\": 1,\n \"status\": {\n \"id\": 1,\n \"name\": \"New\"\n },\n\nSorry i'm not used to create issues on github\n\nRegards\n\nEnvironment details:\nDocker v11.0.4", "priority": "medium", "type": "support", "createdByEmail": "casey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "sage.blair@peppermint.local", "text": "Similar problem with the ../Assistance/Ticket/{id} endpoint.\n\nOriginal response date: 2026-01-12", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3738987877, "author": "Simeonov98", "anonymizedAuthorEmail": "sage.blair@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22450#issuecomment-3738987877", "createdAt": "2026-01-12T15:00:12Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22450, "url": "https://github.com/glpi-project/glpi/issues/22450", "author": "mgiguet", "anonymizedAuthorEmail": "casey.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-19T15:34:55Z", "updatedAt": "2026-05-03T00:57:23Z", "closedAt": "2026-01-22T08:42:32Z" }, "assignedTo": "taylor.adler@peppermint.local", "clientEmail": "operations@apex-manufacturing.peppermint.local" }, { "title": "Cannot change own picture in Simplified Interface", "detail": "Troubleshooting performed:\nThe issue was reproduced with all plugins disabled.\n\nAffected version:\n11.0.4\n\nIssue description:\nChanging the picture under \"My Settings\" appears to be linked to having the 'Update Users' permission under the Administration permissions. This set of permissions is not present while the Interface is Simplified, leading to the user being unable to change the picture.\n\nReproduction steps:\n1. Create profile with Simplified Interface\n2. Attempt to change the user's own picture, unsuccessful\n3. Convert profile to Standard Interface, and apply 'Update Users' permission\n4. User is able to change their own picture\n\nAdditional context:\nUpon some further testing - Adding additional email addresses is possible while in the Simplified Interface, as well as selecting the radio buttons (although I'm not entirely sure what that is for?).\nChanging Default Entity/Profile & Language are also possible, no other fields in the 'Main' tab can be edited.\n\nShould Language be under 'Personalisation?' - There appears to be a field already in there that requires 'Setup' permission under the 'Setup' tab in order to change, which is also only present when in the Standard Interface.", "priority": "medium", "type": "support", "createdByEmail": "casey.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "casey.bennett@peppermint.local", "text": "Apologies - I clearly didn't search far enough back in the closed issues!\n\nOriginal response date: 2026-01-22", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3783519275, "author": "FMG-Jay", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22792#issuecomment-3783519275", "createdAt": "2026-01-22T09:56:41Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22792, "url": "https://github.com/glpi-project/glpi/issues/22792", "author": "FMG-Jay", "anonymizedAuthorEmail": "casey.bennett@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "duplicate", "createdAt": "2026-01-22T09:48:31Z", "updatedAt": "2026-05-03T00:57:20Z", "closedAt": "2026-01-22T09:53:38Z" } }, { "title": "Form migration merges questions when a trashed form has the same name as an active one", "detail": "Affected version:\n11.0.4\n\nIssue description:\nDuring the upgrade process from GLPI 10.0.22 to GLPI 11.0.4, I identified an issue related to form migration.\n\nIf there is a form in the trash that has the same name as a form currently in production (active), the migration process appears to merge the questions of both forms, resulting in an incorrect and inconsistent form after the migration.\n\nTo make the migration work correctly, I had to rename the forms located in the trash before starting the upgrade/migration process.\n\nIt is important to note that this renaming must be done before the version upgrade, as this is the only moment when it is possible to rename trashed forms. After upgrading to GLPI 11, these trashed forms are no longer available or accessible, making it impossible to apply this workaround post-upgrade.\n\nReproduction steps:\n1. Install and configure GLPI 10.0.22 with the Formcreator plugin enabled.\n2. Create a form (Form A) and add at least one question to it.\n3. Move Form A to the trash (do not permanently delete it).\n4. Create a new form with the same name as the trashed form.\n5. Add at least one question to the new form.\n6. Start the upgrade process from GLPI 10.0.22 to GLPI 11.0.4.\n7. Run the form migration process during the upgrade.\n8. After the upgrade completes, open the migrated form in GLPI 11 and review its questions — the questions from both forms are merged/duplicated, resulting in an incorrect form structure.", "priority": "medium", "type": "support", "createdByEmail": "bailey.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Jordan Blair tried to reproduce the issue on his side but without success.\nMaybe there is something else required to trigger the issue that we are missing?\n\nWe'll close for now as you have been able to bypass the issue, we'll see if it happens again for someone else as it seems quite rare and we can't really work on it without more examples.\n\nOriginal response date: 2026-01-21", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3777883414, "author": "AdrienClairembault", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22505#issuecomment-3777883414", "createdAt": "2026-01-21T12:32:44Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22505, "url": "https://github.com/glpi-project/glpi/issues/22505", "author": "twmarcelo", "anonymizedAuthorEmail": "bailey.adler@peppermint.local", "assignees": [], "labels": [ "forms" ], "state": "closed", "stateReason": "completed", "createdAt": "2025-12-30T12:39:07Z", "updatedAt": "2026-05-02T00:52:53Z", "closedAt": "2026-01-21T12:32:43Z" }, "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Alert Issue and Missing Form Response Notification", "detail": "Affected version:\nGLPI 11.0.2\n\nIssue description:\nWhen we set a file field as required in the form and do not fill it in, no alert is displayed indicating that it must be provided.\n\nReproduction steps:\n1. Access the form\nLog in to the system and open the form that contains the File field marked as required.\n\n2. Fill in the other fields\nNormally complete all the other fields in the form:\nText\nDropdown list\nPriority\nCategory\n(in short, everything except the File field)\n\n3. Do not attach any file\nLeave the File field blank, without selecting any attachment.\n\n4. Submit the form\nClick Submit / Register / Confirm.\n\nAdditional context:\nThe same issue also occurs in GLPI 11.0.4", "priority": "medium", "type": "support", "createdByEmail": "kai.bennett@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "bailey.bennett@peppermint.local", "text": "Hi team.\n\nThis issue occurs in 11.0.4\n\nOriginal response date: 2026-01-15", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3756643763, "author": "SilvaFernando", "anonymizedAuthorEmail": "bailey.bennett@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22667#issuecomment-3756643763", "createdAt": "2026-01-15T20:04:11Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22667, "url": "https://github.com/glpi-project/glpi/issues/22667", "author": "stwartelearte", "anonymizedAuthorEmail": "kai.bennett@peppermint.local", "assignees": [ { "sourceLogin": "AdrienClairembault", "anonymizedEmail": "skyler.adler@peppermint.local" } ], "labels": [], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-14T13:22:23Z", "updatedAt": "2026-05-02T00:52:41Z", "closedAt": "2026-01-21T15:05:33Z" }, "assignedTo": "skyler.adler@peppermint.local", "clientEmail": "it@meridian-education.peppermint.local" }, { "title": "Read issue with HL API", "detail": "Affected version:\n11.0.4\n\nIssue description:\nI noticed that when using the HL API, we cannot list the items (locations, users, etc.) that belong to a higher-level entity declared as recursive.\n\nHowever, some of these items are still accessible from this sub‑entity through the web interface.", "priority": "medium", "type": "support", "createdByEmail": "quinn.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "taylor.adler@peppermint.local", "text": "Fixed by #22741\n\nOriginal response date: 2026-01-20", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3771943497, "author": "cconard96", "anonymizedAuthorEmail": "taylor.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22740#issuecomment-3771943497", "createdAt": "2026-01-20T09:44:28Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22740, "url": "https://github.com/glpi-project/glpi/issues/22740", "author": "stefjes", "anonymizedAuthorEmail": "quinn.adler@peppermint.local", "assignees": [ { "sourceLogin": "cconard96", "anonymizedEmail": "taylor.adler@peppermint.local" } ], "labels": [ "api" ], "state": "closed", "stateReason": "completed", "createdAt": "2026-01-19T17:06:21Z", "updatedAt": "2026-05-01T00:59:01Z", "closedAt": "2026-01-20T09:44:27Z" }, "assignedTo": "taylor.adler@peppermint.local" }, { "title": "GLPI11 - MiniDashboard doesn't appear on the profiles with standard interface. It only works on the superadmin profile.", "detail": "Affected version:\nGLPI 11.0.2\n\nIssue description:\nThe MiniDashboard appears only on the superadmin profile. It doesn't appear on the others profiles with standard interface.", "priority": "medium", "type": "support", "createdByEmail": "drew.adler@peppermint.local", "status": "done", "isComplete": true, "comments": [ { "userEmail": "skyler.adler@peppermint.local", "text": "Try with latest version.\n\nOriginal response date: 2026-01-19", "public": true, "source": { "project": "glpi-project/glpi", "commentId": 3766808468, "author": "trasher", "anonymizedAuthorEmail": "skyler.adler@peppermint.local", "url": "https://github.com/glpi-project/glpi/issues/22719#issuecomment-3766808468", "createdAt": "2026-01-19T07:11:30Z" } } ], "source": { "project": "glpi-project/glpi", "issueNumber": 22719, "url": "https://github.com/glpi-project/glpi/issues/22719", "author": "KerieVelu", "anonymizedAuthorEmail": "drew.adler@peppermint.local", "assignees": [], "labels": [], "state": "closed", "stateReason": "not_planned", "createdAt": "2026-01-17T11:15:57Z", "updatedAt": "2026-04-30T00:55:23Z", "closedAt": "2026-01-19T07:11:30Z" }, "clientEmail": "care@lumen-retail.peppermint.local" } ], "clients": [ { "name": "Northstar Health Systems", "email": "helpdesk@northstar-health.peppermint.local", "contactName": "Avery Morgan", "number": "CL-1001" }, { "name": "Harborview Logistics", "email": "support@harborview-logistics.peppermint.local", "contactName": "Jordan Wells", "number": "CL-1002" }, { "name": "Meridian Education Group", "email": "it@meridian-education.peppermint.local", "contactName": "Casey Bennett", "number": "CL-1003" }, { "name": "Pinecrest Financial Services", "email": "service@pinecrest-financial.peppermint.local", "contactName": "Riley Patel", "number": "CL-1004" }, { "name": "Apex Manufacturing", "email": "operations@apex-manufacturing.peppermint.local", "contactName": "Cameron Diaz", "number": "CL-1005" }, { "name": "Bluebird Hospitality", "email": "technology@bluebird-hospitality.peppermint.local", "contactName": "Taylor Brooks", "number": "CL-1006" }, { "name": "CivicBridge Public Services", "email": "systems@civicbridge.peppermint.local", "contactName": "Morgan Reed", "number": "CL-1007" }, { "name": "Lumen Retail Group", "email": "care@lumen-retail.peppermint.local", "contactName": "Quinn Foster", "number": "CL-1008" } ] }