Tomorrow, 4 February, we will deploy a new IETF ticketing system. This change is being made in an effort to improve the issue reporting process; it was announced as part of the 109 technical retrospective [1] and emerged from recent meeting survey feedback [2]. The new ticketing system is the first step towards making it simpler for the IETF community to request assistance and report issues. The plan is to have a single ticketing system (JitBit), and a single address for reporting all issues (support@xxxxxxxx), in place for IETF 110. This process will take place in several phases: 1. Tomorrow, all Secretariat reporting addresses will transition into the new IETF system, JitBit. All current reporting addresses (e.g., ietf-action, registrar, agenda, mtd) will continue to function as they do now. (Note that the current system, RT, will remain online for several months in order to allow for resolution of any currently active tickets). 2. The NOC is also working to move to JitBit prior to IETF 110. The current Trac system will remain online for several months post-transition. 3. Before IETF 110, the disparate support addresses will be replaced by a single point of contact: support@xxxxxxxx. The prior addresses will continue to function, but will not be publicly promoted on the website (or elsewhere) in an effort to encourage adoption of a single support address. Alexa Morris Managing Director, IETF Secretariat [1] https://www.ietf.org/blog/ietf-109-technical-retrospective/ [2] https://www.ietf.org/blog/ietf-108-meeting-survey/
