JIRA Overview


The ticketing system JIRA, based on JIRA Enterprise Edition, is now in place to replace the Remedy system for VLT SPR and DFS PRS scheme.

Jira is accessible from the link : https://jira.eso.org/

Please report to jiramgr any problem you encounter using the system.

You can find the complete JIRA User Guide under Getting started

The VLT SPR Remedy Sheme has been migrated to the VLTSW JIRA project, with a list of components, corresponding to the former remedy "packages" list

And the DFS Remedy Scheme has been split into two different JIRA "projects" with multiple components each:

  • DFS : for the subsystems archive, front-end, infrastructure, .
  • PIPE : for the pipeline subsystems

The old Remedy ticket number (ex: VLTSW20120378 or DFS00065 ) has been added in the JIRA issue summary. So it is possiblle to search for an old ticket with its Remedy number for example from the JIRA "Quick search".

The DFI-TEST JIRA project has also been merged to the new JIRA DFS project, and DFI-TEST old issue can be searched with the old key (ex: DT-12) in the "Quick search".

General Definitions

Issue Types

JIRA can be used to track different types of issues. The currently defined issue types are listed below. Others can be added in the administration section

  • JIRA Types:
    • Bug: A problem which impairs or prevents the functions of the product.
    • Improvement: An improvement or enhancement to an existing feature or task.
    • New Feature: A new feature of the product, which has yet to be developed.

  • Additional types:
    • Doc-bug: A problem which appears in a document.
    • Support: A task that needs to be done.

Priority Levels

An issue has a priority level which indicates its importance. The currently defined priorities are listed below. Some more priority levels can be added in the administration section.

  • Blocker: Blocks development and/or testing work, production could not run.
  • Critical: Crashes, loss of data, severe memory leak.
  • Major: Major loss of function.
  • Minor: Minor loss of function, or other problem where easy workaround is present.
  • Trivial: Cosmetic problem like misspelt words or misaligned text.


Each issue has a status, which indicates the stage of the issue. In the default workflow, used by the project CROSSPROJECT, issues start as being Open, progressing to In Progress, Resolved and then Closed. Other workflows may have other status transitions.

  • Open: The issue is open and ready for the assignee to start work on it.
  • In Progress: This issue is being actively worked on at the moment by the assignee.
  • Reopened: This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
  • Resolved: A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
  • Closed: The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.


An issue can be resolved in many ways, only one of them being "Fixed". The defined resolutions are listed below. Others can be added in the administration section.

  • Fixed: A fix for this issue is checked into the tree and tested.
  • Won't Fix: The problem described is an issue which will never be fixed.
  • Duplicate: The problem is a duplicate of an existing issue.
  • Incomplete: The problem is not completely described.
  • Cannot Reproduce: All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.


For all the projects (VLT, DFS, PIPE) the Basic workflow of the system is used.


Content of JIRA screen

When you login to JIRA the first page you can see is your Dashboard (HOME link). It contains links which give you quick access to many of JIRA's most useful functions. It can be configured to display many different types of information; see details on the page https://confluence.atlassian.com/display/JIRA062/Customising+the+Dashboard

From the JIRA navigation bar you can access also to the following view:

  • Browse Project: from this view you can access to the main information for a project and in particular to Opened Issues
  • Find issues: Used to find issue with possible advanced search
  • Create new issue: Used to create a new issue

Notification scheme

JIRA can generate email notifications for various events that happen throughout the lifecycle of an issue.

Notifications are defined within a notification scheme (see below the default one), which associates particular events with particular email recipients.

Note: The recipient All watchers correspond to the watchers list added at issue level plus the default watchers list defined per component.

Events Notifications
AllWatchers CurrentAssignee Reporter
IssueCreated X X X
IssueUpdated X X  
IssueAssigned X X  
IssueResolved X X X
IssueClosed X X X
IssueCommented X X  
IssueCommentEdited X X  
IssueReopened X X X
IssueDeleted X X X
IssueMoved X X X
WorkLoggedOnIssue X X  
WorkStartedOnIssue X X  
WorkStoppedOnIssue X X  
IssueWorklogUpdated X X  
IssueWorklogDeleted X X  
GenericEvent X X  

Basic procedures

How to login/change your password

Jira is accessible from the link : http://jira.eso.org/

When the login page is shown, provide your identification in terms of username and password. If you have problems accessing the system or if you need an account please contact jiramgr

see https://confluence.atlassian.com/display/JIRA062/Logging+in+to+JIRA

You can change your password from your User Profile, see https://confluence.atlassian.com/display/JIRA062/Changing+your+Password.

How to create a ticket

To create a new issue go to the Create new issue link on the JIRA navigation bar.

see https://confluence.atlassian.com/display/JIRA062/Creating+an+Issue

How to find an issue

To find an issue go to the Find issues link on the JIRA navigation bar.


You can also use the Browse project view to directly access the opened issue of a component.

How to link issues

Issue linking allows you to create an association between two issues. For instance, an issue may duplicate another, or its resolution may depend on another's. The types of links defined are:

  • relates to / relates to
  • duplicates / is duplicated by
  • blocks / is blocked by
  • clones / is cloned by (this is used when issues are cloned)

Issue linking also allows you to:

  • Create an association between a JIRA issue and a Confluence page.
  • Link a JIRA issue to any other web page.

To link to another issue, on the 'view issue' page, select Link from the More Actions menu. After adding a link the Issue Links section will be visible with the details.

See also https://confluence.atlassian.com/display/JIRA062/Linking+Issues#LinkingIssues-Creatingalinktoanotherissue

-- SylvieFeyrin - 08 Jan 2013

Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r10 - 2017-02-22 - SylvieFeyrin
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding DOE (ex-SDD) TWiki? Send feedback