Jira - Local help - CEH Project Issue Tracking

Jira tracks issues, which can be bugs, feature requests, or any other tasks you want to track.

Each issue has a variety of associated information including:

the issue type
a summary
a description of the issue
the project which the issue belongs to
components within a project which are associated with this issue
versions of the project which are affected by this issue
versions of the project which will resolve the issue
the environment in which it occurs
a priority for being fixed
an assigned developer to work on the task
a reporter - the user who entered the issue into the system
the current status of the issue
a full history log of all field changes that have occurred
a comment trail added by users
if the issue is resolved - the resolution

Issue Types

Jira can be used to track many different types of issues. The currently defined issue types are listed below. In addition, you can add more in the administration section.

For Regular Issues

Epic: Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Bug: A problem which impairs or prevents the functions of the product.
Story: Created by Jira Software - do not edit or delete. Issue type for a user story.
New Feature: A new feature of the product, which has yet to be developed.
Task: A task that needs to be done.
Improvement: An improvement or enhancement to an existing feature or task.
Assessment
Job
Meetings
Change Request: Request for change in system
Data Processing
Project Management: Project Management
Other
Track USB stick: For tracking USB sticks being sent to/from sites
Action
Request for data
Dataset
Data Management Plan
Facilities: Facility related issue
Section
Project Note: A minor issue or technical question passed between project team members
General Enquiry
Project: A project defines a set task or activity carried out for a period of time.This issue type is used to track projects at a high level (i.e. their overall goals, and likelihood to be delivered on time etc.).This issue type is designed to represent Projects as opaque markers, not groupings for issues within a project. This is what Jira Projects are for. As such lower level information such as issues, tasks and bugs should NOT be related to this issue type.
Feedback: Generic issue type for public/private feedback. This issue type is used before a more suitable issue type can be chosen, based on the nature of the feedback received.
System: Represents a system in an abstract form (e.g. SOUTH)
System Instance: Represents a single instance of a System, i.e. the internal SOUTH instance for use within BAS
SSL Certificate: Represents a SSL certificate and associated private key
Shared Hosting: Represents a resource that is used as shared hosting for multiple systems. Typically this will be a shared VM hosted by BAS ICT.
Domain Name: Represents a high level domain name. Resources within or under this domain should use the DNS Record issue type.
Observation
Opportunity for Improvement
BODC Web Production Deployment: A deployment of code to the Web Production Environment
BODC Web Environment Update: A non-code change to the BODC Production Web Environment. Note: Code deployments are covered by BODC Web Deployment issues
BODC Web Prod Problem: An underlying (root cause) issue that has manifested itself as a (or several) BODC Web Prod Incident(s)
BODC Incident: An unplanned incident has occurred in a BODC Production Environment (Web or Data Management) that has or could impact the quality of available service
BODC Deployment: A generic event of deploying something into an IT environment, whether a test, dev or production env
Data Management Tracking
DNS Record: Represents a DNS record used to address infrastructure within, and between, System Instances.
Map Request: A request for a mapping resource (including. aerial photography and GIS)
Compute Resource: Represents a virtual machine, container or cloud equivalents (such as an EC2 instance)
User Request
Fault
Risk
Squares planning
Data Rescue
Research collaboration opportunities
Data Capture
Science - Routine Monitoring - Waters: Science - Routine Monitoring - Waters
User Provisioning: Anything to do with modifying user accounts
Travel
System Log: Generated logfiles from any system
New set up
Feature
Technical - Irrigation Issues: Technical - Irrigation Issues
Help Desk Request: For issues coming from Intranet form or email
Science - Experimental - Lab: Science - Experimental - Lab
Engagement
BGS default issue type scheme: Simple set of issue types for BGS
Technical - Data System Issues: Technical - Data System Issues
Issue
Document: Create document
Request for Information
Request for contact details
Finance
Publication enquiry
Quote Request: Request for a quote for work required.
User Story
S & I Submission
BODC Underway data submission
Slocum fault
Sea Glider fault
IDP Data Submission
Internal Inspection
Task/Job Observation
Complaint
Surface vehicle fault
NOC Contract
NVS Request
Internal Audit
Audit by 3rd Party
Audit of 3rd Party
GDPR
Test Result
Variance
SAR - Subject Access Request
Consent
DPIA
Cruise
BODC DOI
BODC DOI Update
CEDA Underway data submission
Support
DMG Request
Verify
Non-conformance: Issue type of no-conformance with fields that have to be completed.
Deprecation: Planned removal of feature, due to a fault or replacement by a newer feature.
Data Request
Calibration
Administration
Students
Data Capture (Departing Staff): Data capture issue for staff leaving CEH
Data Capture (Relocating Staff): Data Capture Issue for staff moving sites
Design
Inquiry
Modification
Projects
Equipment Fault: Used to record issues related to faulty equipment
Technical - Roof Issues: Technical - Roof Issues
Science - Routine Monitoring - Gases: Science - Routine Monitoring - Gases
Suggestion
Ticket
Science - Experimental - Field: Science - Experimental - Field
Information
Engineering: Engineering related issue

For Sub-Task Issues

Bug (subtask)
Change Request (subtask)
Technical task: A technical task.
Issue (subtask)
Risk (subtask)
Task (subtask): Deliverable that contributes to a higher level deliverable
Project Note (subtask)
Engagement (subtask)
Audit by 3rd Party (subtask)
Help Desk Request (subtask)
Internal Audit (subtask)
GDPR (subtask)
Task Step: The step in a parent task
Inquiry (subtask)
Action (subtask)
Sub-Task: The sub-task of the issue

Priority Levels

An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels 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.

Statuses

Status Categories

Helps identify where an issue is in its lifecycle.
Issues move from To Do to In Progress when work starts on them, and later move to Done when all work is complete.

Done: Represents anything for which work has been completed
In Progress: Represents anything in the process of being worked on
No Category: A category is yet to be set for this status
To Do: Represents anything new

Issue Statuses

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

Open
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.
Data Questionnaire Received
1st Meeting Arranged
2nd Meeting Arranged
Main Data Capture in progress
UPC Assigned: Analysis ID assigned and logged
Ready: Documentation finished, change ready to go live
Live: Programs moved to live system
Allocated
Actioned
Signed Off
DRS Document Complete: Data Rescue Scoping document completed
With Section Head: Issue now with section head
With Core College: Issue with the core college
With EIDC: Issue with Environmental Informatics Data Centre
Data Rescue in Progress: Data Rescue in Progress
Not Supported: Issue not supported
Data request details entered: LOCAR
Check eligibility of requestor: LOCAR
Check data availability: LOCAR
Check if licences are required: LOCAR
Arrange appropriate licences: LOCAR
Data downloaded: LOCAR
Data sent: LOCAR
Waiting for contractor: The issue is on hold whilst waiting for contractor
Waiting for parts: The issue is on hold whilst waiting for parts to resolve the problem
Data Description Entered
Received Data
Data Complete
Data QC'd
Data Formatted
Data Loaded
Drive Housekeeping Completed
Records Updated
Contacted
Data NOT Complete
Data not QC'd
Pending
Testing: Software is being tested
DMP in Development: DMP in Development
Outline DMP Approved: Outline DMP Approved
DMP with DDPMG: DMP with DDPMG
Project Space Set Up: Project Space Set Up
DMP Active: DMP Active
Full DMP Reviewed: Full DMP Reviewed
Files in Archive Space: Files in Archive Space
Technical: Technical Status for notifying a group of technical users
Science: Scienctific Status for notifying a group of scientific users
Project Management: Project Management for notifying a group of Project Managers
Approved
Scheduled
On Hold
Posted: USB Key Posted
Acknowledged: Acknowledgement of item being posted.
Tracked: Item is in transit and being tracked.
Received: Item has been received.
Delivered: Item has been delivered to recipient
Checked: Item has been checked.
Confirmed: Item has been confirmed as acceptable.
Re-requested: Item not found to be acceptable, has been re-requested.
Accepted
Deployment Testing: This status is managed internally by JIRA Software
To Do
Done
Acceptance Testing: This status is managed internally by JIRA Software
Agreed DMP
Tech support
Project board
Hosting Provider: Issue currently with our external hosting provider.
Backlog
Selected for Development
Cancelled: Work will not continue on this issue.
Acceptance: This status is managed internally by JIRA Software
Needs Triage: New feedback has been received and needs to be triaged.
Requested: This status is managed internally by JIRA Software
DELAYED: This status is managed internally by JIRA Software
Resumed: This status is managed internally by JIRA Software
Blocked: WIP but can not progress until a dependent task or action is completed
Assigned
DMP Agreed
Cost Appendix Sent
Annual Review
Commissioned: System has been approved and proceed to further planning/implementation
Discovery: System is collecting user requirements and developing outline implementations, including proof of concepts, trails and software evaluation
Implementing: System is being implemented ready for active use by end-users, includes alpha and beta testing and planning for training as needed
Legacy: System is no longer under active support by the responsible team, however support for current features including bug fixes will be performed
Deprecated: System is planned to be retired and no support will be offered with the exceptions of data export or migration to a new system and for security issues
Retired: A system is now withdrawn or shutdown and no further support will be offered, data export may still be possible however
Change Requested: A change has been requested and is pending further action
Change In Progress: A requested change is being actioned
Provisioning: System Instance has is current being provisioned ready for use
Terminated: Resource is no longer needed and will be removed
On Order: A resource which has been ordered
Expired: Resource has expired
Revoked: Resource has been revoked
Design
Development
Test
Coding: Code is being written
Awaiting PI Response
DMP awaiting approval
DMP approved
Data Ingestion
Data Tracking
Requirements definition
User Acceptance
System Test
Dev Testing
Under Review
Rejected
Processing
Processing Audit
Trim
Trim Audit
Compile Sample Data
Calibration
Calibration Audit
Migration
Migration Audit
Waiting
Under Investigation
Fixing
Mitigation
Temporary fix
Done in dev: This status is managed internally by JIRA Software
To be Assigned
Tester Testing
In Review
In Test: This status is managed internally by Jira Software
New Requests: This status is managed internally by Jira Software
Metadata Template received
DOI in prep
DOI check
DOI with PDL group
DOI minted
Cruise Identified
PM notified
DMP template sent to PI
Cruise Planning Meeting attended
Post-cruise archive received
CSR received
Cruise report uploaded
New DOI Required
Update PDL Tables
Update RIS
Update XML
Check PDL tables
Creating JIRA ticket for WEBTABS
Checking JIRA issue for WEBTABS
HR: This status is managed internally by Jira Software
Finance: This status is managed internally by Jira Software
Projects: This status is managed internally by Jira Software
Approval to Be Prioritised: This status is managed internally by Jira Software
P1: This status is managed internally by Jira Software
P2: This status is managed internally by Jira Software
P3: This status is managed internally by Jira Software
Doing: This status is managed internally by Jira Software
Cross-Application: This status is managed internally by Jira Software

Resolutions

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

Resolved: A fix for this issue is checked and tested.
Not going to be addressed: The problem described is an issue which will never be fixed.
In-progress: The issue is still ongoing
Not yet addressed: No product associated with it as yet
Done: GreenHopper Managed Resolution
Won't Do: This issue won't be actioned.
Duplicate: The problem is a duplicate of an existing issue.
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.
Raised in error: Accidentally created or issue not required