Jira Concepts - Issues
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
- Issue template (WBSGantt)
- Issue template
- 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.
- New Feature
- A new feature of the product, which has yet to be developed.
- Story
- Created by Jira Software - do not edit or delete. Issue type for a user story.
- Task
- A task that needs to be done.
- Improvement
- An improvement or enhancement to an existing feature or task.
- Fault
- Indicates a problem discovered during or after acceptance
- LRU Replacement
- New issue type solicited by Juan Pablo Caram
- PRTS Problem Report
- CMMS
- Documentation Request
- Test Case
- PIPELINE
- Action Item
- A specific event/task/activity that needs to be executed.
- Account
- IT Backup
- REDUCTION MACHINES
- SOFTWARE MAINTENANCE
- Smartsheet
- INFRAESTRUCTURE
- Observation
- DAR
- Document Approval Request
- Purchase Request
- Pincode
- Key Request
- Project Request
- CMMS Product Creation
- NGAS
- Meeting
- ARCHIVE
- CLEANUP
- ORACLE
- NETWORK
- DATA CENTER
- ERMA
- DSO
- Patch Request
- SCCB Software Patch Request
- DNR
- PRTS Investigation Report
- PRTS Investigation Report
- APOTEST
- RID
- Review Item Discrepancy
- Punch Item
- Items from the Antenna punch list
- CRE
- Resource Booking
- CAR
- Corrective Action Request for Project-Level issues.
- NCR
- Non-Conformance Report for Project Level issues.
- RFW
- Test Discrepancy
- Acceptance Test Non-Conformance
- Security
- Security Incident
- For record and tracking
- Security Incident
- For record and tracking
- Antenna Switch Request
- To record delivery of new CISCO C2960L Switches for Antennas.
- DS Main Project
- Creates a Main or Top Data Science Project, that follows the DS Workflow. It is possible to add sub-projecs if needed.
- LRU Repair
- Software Inspection for Teleworking
- Configuration Change
- Change to configurations
- Spikes
- Investigation
- DS-Tasks
- Enablers
- Incident
- Problems found in infrastructure
- NewCapability/Enhancement
- Change Request
- SCCB Software Change Request
- Persistent Data Structure Changes
- SCCB Software Persistent Data Structure Changes
- Test Task
- Test tasks and procedure(s) for integration testing.
- Feature
- Risk
- For use with the Risk Register add-on
- CyberSecurity Incident Report
- New User IT requests
- Faulty Card
For Sub-Task Issues
- Sub-task
- A component of a bigger parent Task.
- Sub-bug
- The sub-bug of the issue
- Technical task
- A technical task.
- AI
- Cyber Report Sub-Task
- Sub-action-item
- Anything that is not direct computing work (decision, information, purchase, ...)
- DS Secondary Project
- Create a Sub DS Project within the context of a Parent Main Project. It still follows the workflow, even when some steps are implicit and thus not need a explicit action.
- Obs-Proj
- Observational Project
- Sub-feature
- A Feature that is part of a bigger Capability (according to the Management Plan)
- MRB
- NCR Development
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 (online or offline) could not run.
- Critical
- Crashes, loss of data, severe memory leak.
- Major
- Major loss of function.
- Normal
- Normal priority for SCCB
- Minor
- Minor loss of function, or other problem where easy workaround is present.
- Trivial
- Cosmetic problem like misspelt words or misaligned text.
- Hold
- FELO project priority, solicited by Skip Thacker
- Medium
- Bug, missing functionality or action item that does not prevent normal operation, possibly with workarounds.
- High
- Fix/feature/action is needed urgently (crashes, potential loss of data, missing functionality)
- Low
- Minor loss of function, problem where easy workaround is present, or not urgent action item.
- Emergency
- For SCCB emergency tickets
- Typo
- Typo
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
- 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 validation by reporter or assignee. From here issues are either validated, or directly closed.
- Closed
- The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
- Approved - Team Leader
- Approved by Team Leader
- Approved - AIV
- Approved by System/Deputy Integration Lead
- PR Generated
- ESO only: PR generated within Navision
- PO Generated
- PO Generated
- Item Received
- Item Received in Lab and Inventoried.
- Idle
- No progress on task is possible (pending receipt of equipment, etc)
- Approved - DTS MGMT
- Approved - DTS Supervisor
- Accepted
- The assignee has accepted the issue.
- Rejected
- CSV_take_data
- Commissioning Task requiring data or measurements
- CSV_suspended
- Commissioning task suspended because, e.g. hardware or software not yet available
- CSV_awaiting_analysis
- Commissioning task where we need to analyse current data before deciding next steps
- CSV_awaiting_report
- Commissioning Task with data and analysis done but report is not complete
- Needs data
- CSV task needing data
- Needs analysis
- CSV task with data needing to be analysed
- Needs report
- CSV task needing report writing
- Suspended
- CSV task in suspended state, e.g. waiting for new software version
- BENDSOFT Step - Verify
- Software is awaiting verification
- Requested
- PR issuance requested by ADC Manager or Delegate.
- PR issued
- PR created in ERP
- PR approved by Manager
- PR approved by Finance
- PO prepared
- PO prepared by C&P Officer
- PO approved
- PO approved by Executive
- PO issued
- PO released by the Executives
- Cancelled
- Approved - Manager
- Awaiting Reply
- Initiated
- Action
- Disposition
- Upgrade to NCR
- Downgrade to DNR
- Rework/Repair
- Use as Is
- New
- Deferred
- On-Hold
- Recorded
- Interrupted
- Recovered
- Stopped
- Restored
- Coordinate
- Delegate
- Diagnose
- Review
- Repair
- Item Received Indirectly
- Item Received in another purchase
- Undegoing Approval
- Released
- To Do
- Done
- In Review
- Asset Disposed
- Deployed
- Enter Item Details
- Obsolete - Pending Approval
- Obsolete - Pending disposal
- Off-Site Service / Repair
- Reported Lost / Missing / Stolen
- Service Request
- Stock
- TAG Not in Use
- Under Review
- Approved
- Analysis
- Canceled
- Data Collection
- Formulation of Findings
- Goals and Elicitation
- On Hold
- Operationalization
- Operative
- Proposal
- Paused
- Ready for Pick Up
- OSF Stored
- Ready for Removal
- Taken Away
- Disposed
- Prioritization
- Gather Information
- Action Plan
- Implementation
- INVOICE APPROVED
- Partially Item Received
- Withdrawn
- Blocked
- Validating
- Undergoing Phase C testing
- Submitted
- The issue has been submitted, but is not yet analysed nor accepted by the assignee.
- Implemented
- The code/fix has been implemented and Phase-A tested by the developer.
- Verifying
- Executing Phase B testing.
- Waiting for ICT
- Issue is transferred to ICT project - see link.
- Assigned
- Proposed
- Reviewing
- Waiting for approval
- Sponsored
- Testing
- Ready For Testing
- The change is ready for testing in pre-production environment
- Ready For Merge
- Backlog
- Selected for Development
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.
- 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.
- Item Received
- Item has been received and logged in the inventory system.
- Transfer
- The issue is transferred to another area in JIRA for tracking and resolution.
- Done
- Work has been completed on this issue.
- In progress
- Unresolved
- Won't Do
- This issue won't be actioned.
- Rejected
- The issue has been rejected, i.e. there is no real problem or it will never be fixed.
- Validated
- The issue has passed Phase C validation.
- Verified
- The issue has passed Phase B verification.