170 likes | 637 Views
JIRA usage in the DAQ. An overview. JIRA. Project tracking system Record tasks, requests and bugs Track their progress Organize, assign and prioritize Search, filter and report Extensible & customisable Developed by a private company Official replacement of Savannah at CERN
E N D
JIRA usage in the DAQ An overview
JIRA • Project tracking system • Record tasks, requests and bugs • Track their progress • Organize, assign and prioritize • Search, filter and report • Extensible & customisable • Developed by a private company • Official replacement of Savannah at CERN • Central service at CERN
JIRA concepts: basics Project Categories Level 1 Projects Level 2 Components(sub-section) Versions(milestones) Issues Level 3 Issue Types Issue Types Sub-Tasks Sub-Tasks Sub-Tasks Sub-Tasks Level 4
JIRA concepts: basics • An issue belongs to one and only one project • An issue concerns zero to many components • Issue types, components and versions can be defined specifically for each project • Sub-tasks allows splitting a large issue • Issues can be linked (depends on, duplicates, relates to)
JIRA concepts: worfklows Create Issue Open In Progress Reopened Resolved
JIRA concepts: users • Reporter can also be the assignee • Access rights : • Roles can or cannot access/modify/create/comment… projects • Mapped to e-groups Issue Report Assign Reporter Assignee
JIRA features • Filter : saved search • Report : • Show statistics for particular people, projects, versions, or other fields within issues, based or not on a filter • Predefined reports available, extendable • Notifications • Emails : on creation and modification, if you are reporter or assignee. Customisable. • CVS/SVN integration (ABC-123 in commit log)
JIRA in the DAQ • ~40 projects range from software and hardware to documentation and operations • DATE • ACT • AMORE • amoreGUI • FXS • External tools • DDL • P2 Hardware and infrastructure • Conferences & Papers • SRC • …
JIRA in the DAQ • Issue types • Standard: bugs, tasks, improvements… • Interventions: software, hardware, system (specific workflow) • Operations: Hardware problem, Sys Admin task • Misc: Writing, Purchase • Planning – versions – milestones • Versions and milestones used in a certain SW projects (AMORE) • Planning : LS1 and LS2
Plugins • Subversion • Links commits with issues • Groovyrunner • Scripts everything (used in our workflows) • ALICE DAQ Projects and Categories • Home-made • Lists Categories and projects along with stats • Used in a dashboard for our weekly meeting • Gantt Chart Plugin • Gantt chart for planning (LS1, LS2)
DAQ simplifiedWorfklow Worfklowfor interventions : Automatictransition fromcreation to resolution & templated email notif. Not shownhere : Differentworkflow for HW problems : « repair », « commissioning », …
JIRA API • Injections of issues by • Orthos (alarms) • AMORE module self-service (under development) • Logbook (under development for RC, create ticket and read tickets)
Central service – custom instance • Benefits of central service: • SSO + e-groups • Backup • Database • Server • Fail-over • JIRA updates • Benefits of a custom instance: • Freedom to install plugins • Custom workflows • Custom fields, issue types, screens… (not sure if itisnowallowed in the central instance) • Need for a license !
DAQ experience • Very positive ! • Actively used every day and during the weekly meetings • 880 issues created since 1st january • Repository of all the things we do or plan to do • A lot more than just software tickets • Encouraged us to structure, analyse and group our projects and responsibilities