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
-
Problem
- Track underlying causes of incidents. Created by Jira Service Desk.
-
IT Help
- For general IT problems and questions. Created by Jira Service Desk.
-
New Feature
- A new feature of the product, which has yet to be developed.
-
Incident
- For system outages or incidents. Created by Jira Service Desk.
-
Service Request
- Created by Jira Service Desk.
-
Service Request with Approvals
- For requests that require approval. Created by Jira Service Desk
-
Change
- Created by Jira Service Desk.
-
Black Duck Security Vulnerability
- Black Duck Security Vulnerability
-
Black Duck Policy Violation
- Black Duck Policy Violation
-
Bug
- A problem which impairs or prevents the functions of the product.
-
Epic
- Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
-
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.
-
Benchmarking
-
DSG - Text Insights
-
OPS - Custom Reports
-
Custom Reports
-
zAdvanced Analytics (AA)
-
CXA Analyst
-
DBA - Mongo
-
Executive Dashboards
-
zData Processing/Data Tables
-
Insight Review/QBR
-
DBA - Administration
-
Panel
-
zExcel Builder (XB)
-
DSG - Advanced Analytics
-
DEV - DB Dev
-
DSG - CXA Tool or Dashboards
-
zProgram Architecture (PA)
-
EMP - Flashboards
-
DSG - Custom Reports
-
zReports/Review (RPT)
-
EMP - Other
-
DSG - Employee
-
zResearch (RES)
-
DSG - Executive Review/Report
-
EMP - Data Migration
-
zSI/POV
-
DSG - Panel
-
OPS - Back-fill
-
zCXA Tool or Dashboards
- Set up or edits of an Executive Dashboard or CX Analyst Tool.
-
Security
- These are meant for security related items.
-
zMiscellaneous
-
Survey
-
Technical Issue
-
zTags (Custom)
-
Report
-
Social
-
Dashboard
-
Production Bug
- jira.translation.issuetype.bug.name.desc
-
Help Desk Office
-
Help Desk Security
-
EAST
-
Sentiment
-
Deconstructor
-
WEST
-
Support
- Ipsos project workflow support task
-
Ipsos Task
- Ipsos task for Ipsos support workflow
-
InMoment Task
- "InMoment" task for Ipsos project workflow
-
Submit Correction
- Issue type created for use by RC Project
-
Critical
-
Request Additional Content
- Issue type created for use by RC Project
-
InMoment (Internal)
- To be used ONLY for InMoment Internal Tasks
-
Leave Feedback
- Issue type created for use by RC Project
-
Maintenance Request
-
Campaign Insights Backfill Request for Pro Reporting
-
Contact Data Center Migration Request
-
Request_Conversions
-
Escalated
-
Sprint Task
-
Research Spike
-
Success Story
-
Fixes
-
Product Management Task
-
Design Concepts (DS Internal Only)
- This Issue type is to be used for internal data sciences projects and can only be accessed by data sciences teams.
-
EMEA
-
New Components
-
Help Desk Meeting Setup
-
Information Request
-
New Hire Request
-
Purchase Request
-
Help Desk Support
-
OPS - Exclusion List
-
Maintenance (fixes, clean-ups)
- Maintenance (fixes, clean-ups)
-
OPS - Translations
-
Updates (content adds/deletes)
- New Report/Survey
-
Build
- Brand new Org/Program
-
Training
- Training
-
Help Desk Telephone Request
- Problems with extensions/handsets
-
Help Desk FTP Credentials
- FTP credentials and setup
-
OPS - Data Fields
-
OPS - Misc.
-
Help Desk Hardware
- Request for equipment
-
Help Desk Software
- Request software for purchase and/or install
-
Fire
-
AWS Cloud Costs POC
- Tracking Cloud Expense
-
Security Vulnerabilities
-
DevStory
-
DeployStory
-
QAStory
-
PostDeployStory
-
Convergence Migrations
-
Development Bug Sandbox
-
Convergence
-
Program Excellence
-
ES_Custom
- Story
-
Help
- Jira / Confluence Help
-
ES_Di_Minimus_No_Support
- Story
-
Initiative
- A company level initiative spanning epics and potentially projects.
-
ES_UX/UI_Extensibility
- Story
-
ES_XI-Existing/Queued_Feature
- Story
-
Access/Permissions
-
Spike
- Spikes are a type of exploration Enabler Story in SAFe. Defined initially in Extreme Programming (XP), they represent activities such as research, design, investigation, exploration, and prototyping. Their purpose is to gain the knowledge necessary to reduce the risk of a technical approach, better understand a requirement, or increase the reliability of a story estimate.
-
ES_Survey_Extensibility
- Epic
-
ES_JS_Library_Feature
- Story
-
ES_XI_Product_Feature
- Story
-
New_Build_Request
-
AS: User Access / Permissions
-
AS: New Project
-
Admin
-
Migrate
-
Mthly_Quality_Check
-
Annotations
-
Incident Post Mortem
-
Machine Learning
-
SCIP
-
New Infrastructure Request
-
New Infrastructure Request (CE)
-
XI Account / Org Destruction
-
MI - Data Sciences
-
Graphics - Admin
-
Idea
- An idea for a new product or improvement to an existing product.
-
Ad-Hoc
-
None
-
zOther
-
zSales Support (SS)
-
zText Analytics/NLP
-
zCore (Industry)
-
Graphics [New Client]
-
zDiscover
-
Graphics [Change to Existing Client]
-
zR&D
-
zTags (Industry)
-
Graphics [New Survey]
-
Risk
-
Test Automation
-
Automated Access Control Audit
-
Development Bug
-
Documentation Fix
-
SSL Cert
-
New SVG
-
Graphics
-
Test Type
- Used to Test new workflows
-
Change Request (CAB)
-
Change Control
-
Platform Site Creation
-
Platform Site Cancellation
-
Technical Story
- A story that does not necessarily add business value, but adds technical value to the team or product.
-
Question
-
Meeting
-
Access Control Audit
-
Documentation
-
Privacy Request
-
Vendor Review
-
Contract Review
-
Customer Audit(Security & Privacy Questions)
-
Modeling
-
Request (external)
-
Generic/Other
-
XI/CXIC EMEA
-
XI/CXIC NA
-
Customer Commitments
-
Laptop Setup
-
Testing
-
Phone Request
-
Feature
-
Odyssey
-
PII Requests
-
Email Request
-
PII Request
-
Internal Platform Support
-
Department (smj use only)
-
Theme
-
Division (smj use only)
-
Studio
-
BZ2
- Test Issue Type for Test Project BZ2 = Bug Zero 2.0
-
DBZ Bug
-
Cost Approval
-
DM Task
-
Convergence New Features
-
Convergence Defects
-
New Infrastructure Request (CESD)
-
Chat
- Issue Type for Tech Support Chat tickets.
-
Industry Packs
-
ODS Migration
- ODS Migration
-
Choose an Issue Type...
- Please select an issue type from the list below.
-
BI - RapidMiner
-
Help Desk SOC Compliance
-
BI - Vertica
-
Help Desk DEV
-
Help Desk PROD
-
UX/UI
-
DSG - R&D
-
Feature Request
-
Request
-
RapidMiner
-
Data Mining Modelling
-
BI - Tableau
-
DSG - Text Analytics
-
Ad Hoc Analysis
-
BI - Netezza
For Sub-Task Issues
-
Sub-task
- The sub-task of the issue
-
Technical task
- Created by JIRA Agile - do not edit or delete. Issue type for a technical task.
-
Red Issue
-
Defect
- A defect found with an issue during review or testing.
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.
-
Escalated
-
Blocker
- Blocks development and/or testing work, production could not run.
-
Critical
- Critical bugs, or showstoppers as they are often called, are so severe that they prevent you from further testing. These issues manifest themselves in a number of different ways. They can range from an app that continuously crashes to a button missing in the user interface preventing you from loading or triggering a required part of the application. Critical bugs are the highest on the bug severity scale.
-
Major
- As you test an application, you should always have its requirements and/or user stories in mind. If you encounter an issue that prevents the application from meeting requirements or carrying out a feature, it classifies as a major bug on the bug severity scale. In most cases, major bugs are fairly obvious. For instance, if you are testing a game and the application fails to save your score the next time you login, then that is a major bug. Another example would be if the shopping cart function of an e-commerce app does not correctly tally totals and subtotals. In short, major issues prevent applications from doing what they were specified to do.
-
Medium
- Medium level of attention required.
-
Minor
- Minor defects are a little trickier to classify. While they still should not impede an application’s primary features or functionality, minor bugs will have a greater adverse impact than their trivial counterparts. For example, if you are testing an application and trigger a pop-up message that is incorrect – or even in the wrong language – this is a minor defect, so long as it has no effect on the general functionality of the application itself.
-
Recurring
- Recurring
-
High
- High
-
Low
- Low
-
No Priority
-
Trivial
- Trivial bugs are common and probably the easiest to identify. As a general rule, they have no real impact on the functionality of the application you’re testing. Trivial defects often come in the form of cosmetic or design errors, such as a text block exceeding its boundaries or an image out of alignment. This would be classified as minor on the bug severity scale.
-
ASAP
-
7 days
-
30 Days
-
🔥 Fire
-
P1 - Critical
-
P2 - High
-
P3 - Medium
-
P4 - Low
-
P5 - Undetermined
- Impact unknown, further review required.
-
Undetermined
- Impact unknown, further review required.
-
Priority 2
- Created by JIM during import process
-
Priority 3
- Created by JIM during import process
-
Priority 1
- Created by JIM during import process
-
Priority 4
- Created by JIM during import process
-
Priority 3+Q184
- Created by JIM during import process
-
General
-
Blocked
-
None
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.
- Reopened
- This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
- BACKLOG OLD
- Issues that are open and still not committed to.
- Scoping
- Schedule Request
- Pending Schedule Approval
- Pending Start Work
- Pledged
- Issues committed to be completed during current sprint.
- To Do
- Triage
- Determine the correct location of the request
- BACKLOG - Assessed
- Request has been assessed by work lead and is waiting to be prioritized during the next sprint kickoff.
- BACKLOG - Missing Requirements
- Request is missing requirements that need to be provided by the requestor before being resubmitted.
- BACKLOG - Submitted (Waiting Assessment)
- Request is waiting to be assessed by Work Lead.
- Selected for Development
- In Progress
- Fixing
- Review
- UAT
- Release to Production
- WORK COMPLETED
- Work that was verified on UAT has been deployed onto production. Please verify on production and close the ticket!
- WORK COMPLETED.
- Work has been completed. Please verify on production and close the ticket!
- In Review
- Requestor needs to review the work
- Hold for Next Month
- IN PREVIEW
- Changes are waiting on staging to be reviewed by the Reporter. Once verified, please ask for changes to be launched on production.
- PREVIEW APPROVED
- Staging has been approved and a desired launch date has been provided to the TSM to launch the project on production.
- Testing
- This status is managed internally by JIRA Software
- 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.
- Done
- Responded
- Triaged
- Requested
- A request has been submitted and is awaiting approval.
- Cube
- Planning
- Client meeting
- Dashboard Build
- Draft Review
- QA
- Cube Request
- Operations to complete and return the cube request form
- Set Tentative Date
- Set Committed Date
- Approve Tentative Date
- Ready for Work
- This status is managed internally by JIRA Software
- Updates
- Review Changes
- Approve Committed Date
- Needs Info
- The issue needs additional information before it can progress.
- Submitted
- The issue has been submitted with appropriate information for its issue type.
- Exploration
- The issue is undergoing exploration to determine its feasibility and viability.
- Design Phase
- The issue is currently undergoing design.
- Documents Required
- Prioritization
- The issue is being prioritized and assigned.
- Req Review
- The requirements for the issue are being reviewed to ensure understanding of how to fulfill them.
- Dev Backlog
- The issue has been assigned to a team and is ready for inclusion in the development backlog.
- Test Backlog
- In Test
- A solution for the issue is being tested by the assignee.
- Acceptance Testing
- Deploy Queue
- The issue has passed testing and is now available for an upcoming deployment.
- Review Documents
- Completed - Pending Acceptance
- Spot Test Troubleshoot
- R&D
- Provide Feedback/Report
- PARKED (CSM)
- On-Hold
- CSM REVIEW
- Additional Items Required
- CSM APPROVAL
- CSM FOLLOW UP
- IN QA
- CLIENT FOLLOW UP
- COMPLETE - PENDING APPROVAL
- Backlog - L2/L3
- BACKLOG - Renewals
- Under Review
- In Progress L2
- In Review L2
- Approved L2
- Escalated
- With CSR - Additional Info Required
- With CSR - Awaiting Completion
- With TSM - Additional Info Required
- PARKING LOT
- COMPLETED BY CSM
- Blocked
- This status is managed internally by JIRA Software
- AWAIT APPROVAL
- Used in the DevOps workflow
- CLIENT REVIEW
- WAITING ON INFO
- CLIENT REVIEWED
- ICEBOX
- Escalated - TSM
- Escalated - BUG
- Escalated - Feature
- Awaiting Feature Committee Approval
- Pending Committee Approval
- Approved - Schedule Request
- Schedule Sub-task
- Define
- Pending SI Council Approval
- READY FOR ESTIMATION
- TSM VERIFIED
- Pending Director/VP Approval
- BACKLOG - Missing Requirements (CSM)
- LEADERSHIP REVIEW
- PLAN
- IN QUEUE
- EXECUTE
- HR Triage
- DEV REVIEW
- CHANGE REQUEST
- PRODUCT COUNCIL APPROVAL
- Approved
- HAND OFF
- Waiting Hardware
- IDEAS
- MISSING REQUIREMENTS (No Need For Rescheduling)
- Pending Insights Council Approval
- Declined
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for support
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for customer
- This was auto-generated by Jira Service Desk during workflow import
- Pending
- This was auto-generated by Jira Service Desk during workflow import
- Canceled
- This was auto-generated by Jira Service Desk during workflow import
- Needs Approval
- This was auto-generated by Jira Service Desk during workflow import
- Awaiting CAB approval
- This was auto-generated by Jira Service Desk during workflow import
- Awaiting implementation
- This was auto-generated by Jira Service Desk during workflow import
- Implementing
- This was auto-generated by Jira Service Desk during workflow import
- Peer review / change manager approval
- This was auto-generated by Jira Service Desk during workflow import
- Completed
- This was auto-generated by Jira Service Desk during workflow import
- Under investigation
- This was auto-generated by Jira Service Desk during workflow import
- PUBLISHED
- PANTRY
- DOCS
- ANGULAR
- Resolution Implemented
- Notify
- User Confirmation
- IN PROGRESS: REACT
- IN PROGRESS: ANGULAR
- IN PROGRESS: DOCS
- IN PROGRESS: PANTRY
- Deployed to Prod
- WAITING FOR REVIEW
- Test Automation Backlog
- Test Automation In Progress
- Moving to FeatureZero
- New
- FEATURE VERIFICATION BACKLOG
- WITH SUPPORT - Need additional info
- Contracting
- Fulfillment
- Released
- IN PROGRESS: WEB COMPONENTS
- IN PROGRESS: DOCUMENTATION
- IN PROGRESS: FRAMER
- Scheduled
- Term Holding
- Hire Holding
- Ready
- Backlog
- RESEARCH
- AWAITING ACCEPTANCE
- AWAITING APPROVAL
- CHANGE CONTROL APPROVED
- PEER REVIEW
- 5 Sign-Off
- Rejected
- In Refinement
- READY FOR IMPLEMENTATION
- READY FOR QA
- READY FOR ACCEPTANCE
- Waiting on User
- Sales Review
- Technical Review
- TR Approved - SOW not signed
- Active
- Awaiting Development
- Awaiting Testing
- In Development
- In Testing
- Self-Test or Peer-Test the work.
- ASSIGNED
- VERIFICATION
- Peer QA Requested
- Peer QA In Progress
- PM QA
- Client QA
- Ready for Launch
- After Launch Check
- Customer Review
- Documentation Prep
- Production Prep
- New Laptop
- Quote Requested
- PO Submitted
- Order Submitted
- Received
- Hand off for setup
- Tier 1 Investigating
- Tier 2 Unassigned
- Tier 2 Investigating
- Escalated to Engineering
- In Patch Process
- Ready for Product Release
- Bug Fix Verified
- Pending Customer
- In Contracting
- Ready to Start
- Building
- Finalizing
- Meeting
- Launched Deliverables
- Parked
- PO Accepted
- Accepted
- Ready for Release
- In Production
- Ready for Development
- Client Approved
- Approval
- Revise
- Acceptance
- Publish
- Assessing
- Treating
- Approving
- Pending Review
- Remediation
- Code Review
- Awaiting Deployment
- Review to Close
- In QA (For Release)
- In Staging (Release)
- Staging Verified (Release)
- Ready for Production
- Production Verified
- QA Review (Patch Request)
- Awaiting Patch Approval
- Submit Merge Request
- Ready for Beta
- In Beta (Patch)
- Ready for Staging
- In Staging (Patch)
- Staging Verified (Patch)
- Data Fix Request
- Tier 3 Unassigned
- Tier 3 Investigating
- PO Review
- Awaiting Design/Req
- Business Understanding
- Data Architecture
- Data Preparation
- Deployment
- Documentation
- Waiting on Approval
- Reporter review
- Waiting on requestor
- Ongoing
- Escalated to TSM
- Escalated to NOC
- Escalated to CSM
- Log Work
- Waiting on Provisioning
- Denied
- Escalated to DBA
- Escalated to SysOps
- Incomplete Brief
- Client Sign Off
- Escalated To UTS
- FA Review
- Awaiting Dev Review
- Awaiting Ticket
- Awaiting Date
- Awaiting Release
- In Jira
- Work in progress
- This was auto-generated by Jira Service Management during workflow import
- Configure
- Test
- Data Import/Export
- Train
- Cancelled
- 1 Premigration
- 2 Verification & Set-Up
- 3 Data Run
- 4 Spot Test
- Spot Test Fail
- Approved for QA Dive Test
- 6 Deep Dive Test
- 7 Build Program
- Dive Test Fail
- Dive Test Troubleshoot
- Pending DM MGR Approval
- Dive Test Pass
- In Progress by Dev
- Ready for Approval
- Ready for Customer Deployment
- Ready for Customer Testing
- Ready for Deployment to QA Environment
- Ready for PO Review
- Ready for QA Review
- Ready for Sandbox Validation
- Ready for Tech Review
- Ready for Testing on QA environment
- Ready to Package
- Refined
- Unrefined
- Waiting for Defect Resolution
- Waiting for Internal Defects Resolution
- Requirements / Specs
- PM Review
- Pass
- Fail
- Dev / Testing Complete
- PM Approval
- 5 Build/Run Validation Reports
- Feedback
- Complete
- Done - Not Approved
- Fixed
- Deployed
- Product Review
- Request Log
- Accepted Requirement Summary
- Hand-off to Engineering
- Preview
- Enhance
- Create more Surveys and initial data migration
- Launch
- Archived
- Sunset
- 2023
- Build
- Reprocess Spot Test
- Reprocess Deep Dive
- 8-Schedule-Sync-Data
- Cut Over Program
- 9 Delete eSaaS data
- QA Pass
- QA Fail
- Assessment
- Communicate
- Reproduce
- Fix
- Doc/Communicate
- In Process
- Services Review
- Canceled / Addressed
- Document/Communicate
- Request is done. Log work, describe in Comment and add snapshots in the Jira ticket. Send to Reporter.
- Report
- Finished work. Log time, describe work in Comments, notify with Reporter.
- DDT Review Report
- Dev Done
- QA Done
- Awaiting
- DevStory Deploy Queue
- Received Termination Notice
- R&D Backfill Request
- Backfill Review
- Backfill Review Approved
- Candidate Identified
- Background Check
- Candidate Added to Bamboo
- CorpIT Set-Up
- Create
- Approval Phase
- Not Approved
- Incomplete
- Review Phase
- SS Work Complete
- Resubmit
- Waiting Line
- Reopen
- Awaiting Deploy
- Dev Epic Deploy
- To Resolve Issues
- Requirements/Specs
- Escalate
- Review Approved
- Notify Chief/ELT
- Preview Request
- Completion Checklist
- Client Submission
- Pending Client Response
- Obstructed
- Org Built & Hierarchy Enabled
- .bfs file Exported & Imported
- Surveys Built
- TA Model Enabled
- Data Migration Kicked-off
- Apps Configured
- Initial Reporting Finished
- Detailed Data Validation Complete
- Handed off to CS team
- Ready_to_Build
- On Hold
- NFR Issue Created
- Product DLC
- Code Release
- Knowledge Base
- Create Library Issue
- Code JS
- QA JS Code
- Inform & Educate
- Create Custom Build Issue
- Code Script & Solution
- Implement
- Confluence
- NFR Issue NOT Created
- GDE Issue Created
- GDE Issue NOT Created
- Ready to Build
- Build In Progress
- Build Complete
- PreMig In Progress
- EDM Requested
- Validation In Progress
- Rptg & Users In Progress
- Final Check
- Hand Off Prep
- Review-Internal
- Review-External-Product
- Review-External-Marketing
- Backlog -Assessed
- Backlog Assessed
- Cancel
- Reject
- SD Manager Review
- Assign Work Lead
- Reqmts Client
- Bugged
- Authorize
- Decline
- Rework
- Successfully_Converted
- TA Test Account
- Mapping
- Configuration Consolidated
- Consolidated Mapping
- Semantria Load
- XI Enabled
- Reproduce_Rsch
- ML Team
- Maintenance Required
- New Request
- Retired
- Reqmts Data/Business
- Analysis/Plan
- Specifications
- Data Run
- Presentation Prep
- Post Edits
- Presentation Phase
- to fix resolution status
- Waiting for approval
- This was auto-generated by Jira Service Management during workflow import
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.
- 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.
- Done
- Work has been completed on this issue.
- Duplicate
- The problem is a duplicate of an existing issue.
- Working as Designed
- Misconfiguration
- The issue was the result of the system being configured incorrectly.
- Fixed
- A fix for this issue is checked into the tree and tested.
- Won't Do
- This issue won't be actioned.
- Archived
- Issues that are no longer relevant.
- Incomplete
- The problem is not completely described.
- In Progress
- In progress of being completed
- Declined
- This issue was not approved.
- Enhancement Request
- Contract Cancelled
- This resolution is for the IMPL teams when a contract is cancelled
- Won't Fix
- The problem described is an issue which will never be fixed.
- Cancelled
- PO Accepted
- Pushed to Deploy Queue
- DEV DONE
- All Data Migrated
- None
- Work is in Progress
- Pushed to Production
- DEV DONE
- Unable to find Root Cause
- Cancelled / Addressed
- Fixed - Code Review
- Customer Churn
- No Code Change
- Existing Solution
- Manually Migrated
- Leadership Hold
- Manually Migrated - Custom
- Manually Migrated - Survox
- Missing Requirement
- No Migration Needed
- Not Future Vision
- Redesign Required
- Released
- NFR was released for a launch.
- Blocked