Page Comparison

Originally developed for tracking software development and bugs, JIRA is flexible enough to be adapted to any process that follows a workflow.  It is a powerful collaboration tool that allows us to follow processes across and between platforms, enhancing information dissemination at the Broad. (And cutting down on email!)

Due to JIRA’s customizable nature, we’ve been able to develop different projects for multiple processes at the Broad including:

• Help Desk for support issues (example: Crazy Robots for requesting lab equipment maintenance.)
• Process JIRA for tracking units of work within a process (example: Tracking one set of libraries in LCSETs)
• Lab Notebooks, where individuals can track their experiments from design through conclusions. (example: DEV and CELL)

JIRA has several building blocks that are often referred to when trying to convey information:

• Issues – the unit of work that we want to track (ex: one library set, one flowcell, one experiment). Interchangeable with ‘ticket’. JIRA gives us the ability to create custom issue types, for example each type of library has its own issue type.
• Project – the highest level of groups of issues in JIRA. Every issue must belong to a project. Each project must have a unique key, and this is how people most often refer to an issue. Example – “I did an experiment looking at density, which is described in DEV-905.” DEVis the key for the Process Development project.
• Fields – the areas within an issue where data is captured. For example, “Summary”, “Hypothesis”, or “Number of Samples”.
• Status – The process step the issue is currently in. (e.g, "Closed", "In LC".)
• Resolution – A resolution is different than statuses in that this field tells you the ultimate result of an issue. Issues are finalized with a ‘closed’ status, whereas some could have a ‘Completed’ resolution and others would have a ‘Reworked’ resolution. Both will be closed, but resolution tracks how it got there. This specific example is from the flowcell tracking project when we want to rework failed flowcells.
• Transitions – the pathways to advance or return an issue to a particular status
• Workflows – the predetermined set of statuses and transitions an issue goes through.

We have multiple JIRAs (known as instances) in use in the Genomics Platform:

• LabOpsJIRA (labopsjira.broadinstitute.org) - Our main work horse for tracking most lab production processes , and other support itemsas well as lab automation inventory and request tracking.
• CRSP JIRA (crspjira.broadinstitute.org) - Structured similar to LabOpsJIRA, but tracks processes within our more tightly regulated Clinical Research Sequencing Platform (May show up as link broken if you don't have permission to view.)
• GP Informatics JIRA (gpinfojira.broadinstitute.org) - A more 'traditional' JIRA, used for requirements tracking, bug tracking, support requests and feature requests for our Informatics teams. See their confluence page here.
• Collaboration JIRA (colab.broadinstitute.org) - An external facing JIRA to allow GP team members to collaborate with external vendors and teams. (defunct as of March 2016)

Granting access to JIRA (Admin Use)
Adding new Illumina Instruments to JIRA (Admin Use)
Updating Instrument ticket summary (Crazy Robots) (Admin Use)