Necesitamos aunque sea borrar el "query por defecto" que el usuario tiene asociado en el tracker ... para que pueda volver a trabajar con él ... aunque sea con la precaución de no volver a hacer una query del mismo tipo para evitar volver a quedar bloqueado ... Mando en copia a la lista para que tenga también en cuenta que tiene que resetear el estado de Miguel Carrillo en el tracker de Support ... El resto de usuarios/trackers está en el cuerpo del ticket. Nótese que este ticket está marcado como "Blocker" ... más allá de Critical ... Saludos, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro On 13/12/11 10:42, MIGUEL CARRILLO PACHECO wrote: > Falta el primero que se quejó de esto, ¡yo mismo en el tracker de support! > > El 12/12/2011 7:30, fforgesupport-fusionforgesupport at forge.fi-ware.eu > escribió: >> FusionForge Support item #1187, was opened at 2011-12-12 06:30 by Juanjo Hierro >> You can respond by visiting: >> https://forge.fi-ware.eu/tracker/?func=detail&atid=199&aid=1187&group_id=28 >> Or by replying to this e-mail entering your response between the following markers: >> #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ >> (enter your response here, only in plain text format) >> #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ >> >> Status: Open >> Priority: 5 >> Submitted By: Juanjo Hierro (jhierro) >> Assigned to: Roberto Andradas Izquierdo (randradas) >> Summary: Restore ability to work with tracker from user accounts that have got blocked because serious bug in tracker >> Severity: Blocker >> Workflow State: Open >> >> >> Initial Comment: >> Several user accounts have got blocked because of a serious bug in the tracker tools: whenever a user builds a query for tickets that have been assigned to a given user, the system returns a message like the following: >> >> Database Error: ERROR: syntax error at or near "assigned_to" LINE 1: ... AND aefd2.artifact_id=artifact_vw.artifact_idAND assigned_t... ^ >> >> Apparently the bug comes because the tracker software is appending two strings "...artifact_id" and "AND ..." and it doesn't leave a space in between. >> >> The issue is that such query becomes the default query on the tracker and this means that the user cannot longer access the tracker (even to change the query) >> >> We need to at least restore the user accounts that have got blocked. It should be feasible if we reset the default query assigned to a user account for a given tracker where he's blocked. >> >> We know that the following user accounts are blocked: >> + Juanjo Hierro on the "FI-WARE Theme/Epic/Feature requests" tracker in the FI-WARE project >> + Carlos Ralli on the "Backlog Management" tracker in the FI-WARE Data project >> + Thierry Nagellen on the "FI-WARE Theme/Epic/Feature requests" tracker in the FI-WARE project and/or on the "Backlog Management" tracker in the FI-WARE IoT project >> >> >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> https://forge.fi-ware.eu/tracker/?func=detail&atid=199&aid=1187&group_id=28 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy