CMS Document 2852-v7

JIRA tutorial for CMS ECAL

Document #:
Document type:
Submitted by:
David Barney
Updated by:
David Barney
Document Created:
03 Aug 2010, 10:19
Contents Revised:
11 Mar 2011, 12:15
Metadata Revised:
11 Mar 2011, 12:15
Viewable by:
  • Public document
Modifiable by:

Quick Links:
Latest Version

Other Versions:
The CMS Electromagnetic Calorimeter (ECAL) has been operational throughout LHC running and is very stable. However, there are occasions when pieces of hardware fail, or subtle firmware/software bugs appear etc. There is also the need to follow software developments, updating software installations as necessary. These interventions, on any part of the ECAL system, require tracking in order to keep an archive of what was done (and when, by whom, why etc.) as well as to help debug future similar issues through the lifetime of the ECAL (10-20 years).
The commercial product “JIRA” has been selected for tracking ECAL bugs, interventions etc. as it is flexible, easily configurable to our requirements and has some support at CERN (it is used by the LHC Operations group – more than 80 software developers – for all of their software development), including a site-wide license.
This document aims at giving a brief introduction to the use of JIRA for the CMS ECAL group. The term “issue” in all that follows refers to any “problem”, “upgrade”, “bug-fix” etc. – a generic term for any intervention on the CMS ECAL.
Files in Document:
Referenced by:
  • CMS-doc-2856: Création d’un Work-Package pour accéder à l’UXC (Francais)
  • CMS-doc-2850: UXC Work-Package Creation Tutorial for CMS ECAL (English)