Jira - Local help - KP AES Jira

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

Test: Represents a Test
Test Set: Represents a Test Set
Test Execution: Represents a Test Execution
Pre-Condition: Represents a Pre-Condition
Test Plan: Represents a Test Plan
zephyr.issuetype.testcase: zephyr.issuetype.testcase.desc
Feature: Features describe work items that are too big to fit into one iteration but are small enough to fit into one release or Program Increment.
New Onboard
Spike Story
Effort
Subtask
Change Request: Change Request for ADDL
Action Item
Portfolio Epic: Portfolio Epic
Artifact Type
Task: A task that needs to be done.
Support: Support Request Category
Content Request: Content Request
Decision: A conclusion or resolution reached after consideration
Security Bug: Bugs reported by Whitehat or Nexus
Vendor Image Upload Request with Approvals: Vendor Image Upload Request with Approvals. This is for the pull, scan and push to Artifactory Jira workflow.
CRDC Data Onboard: CRDC Data Onboard
Testing_Workflow
Release Package: Release Package
Milestone: Milestone
Capability
AzDF/Synapse Deployments: AzDF/Synapse Deployments
Access: For new system accounts or passwords. Created by JIRA Service Desk.
OKR Objective
IT Help: For general IT problems and questions. Created by JIRA Service Desk.
Research: Research Work Item
SAFe Epic: SAFe container for a significant Solution development initiative
Upload: Upload
Migration Request: Migration Request
Idea
OKR: OKR
Gap: Gap
Requirement: Requirement
Data Request: Data Request
Charter
Service Request with Approvals: For requests that require approval. Created by JIRA Service Desk
Release: Issue type to track Software Releases
User Story
PI Objective: SAFe Standard - Program Increment Objective
Problem: Track underlying causes of incidents. Created by JIRA Service Desk.
IOC: This is where we keep IOCs
Change: For system upgrades or alterations. Created by JIRA Service Desk.
JWH Data Onboarding Story Flow: Initial Data Onboarding Story Flow
KPCC Deployment: KPCC Deployment
Deployment: Deployment
Program Epic: Program Epic
SAFe Capability: A higher-level solution behavior that typically spans multiple ARTs.
SAFe Feature: A service that fulfills a stakeholder need.
Service Request: Created by JIRA Service Desk.
Product: Product
Incident: For system outages or incidents. Created by JIRA Service Desk.
Test Case Template: Test Case Template (TestFLO Plugin)
Fault: Track system outages or incidents. Created by JIRA Service Desk.
Purchase: Track items that need to be bought. Created by JIRA Service Desk.
OKR Key Result
ScopeDetailing
SVT Task: Use when SVT is required
Capability Enabler: SAFe enabler at the Capability Level
Epic Enabler: SAFe enabler at the Epic Level
Batch: Batch
Small Enhancements: Small Enhancements
Squad Task
Testnone: Testnone
TapAP Special Update: TapAP Special Update
Kanban Story: User Story issues which are used in KP Insight projects which support both Scrum and Kanban boards.
Report Request: New Report Requirement
Epic Process Enabler
Epic Testing Enabler: Track the End to End Scenarios across Features & Capabilities.
Small Enhancement Testing Story: Small Enhancement Testing Story
Regulatory Requirement: Regulatory Requirement
Ad-Hoc Request: Ad-Hoc Request
Request: Request
Production Intake: Production Intake
Deployment Request: Product level issue
Deployment Package: Story level issue
Alert: Alert
Enabler
Approval: Approval
Insight
Capability Gap: Capability Gap
Deliverable: Deliverable
BotDeployment: BotDeployment
Design: Design
Regulatory Section: Regulatory Section
Regulatory Gap: Regulatory Gap
DB Package: DB Package
Change Task
Initiative: Initiatives represent large blocks of work that would not fit in one release or Program Increment. These portfolio items must be split into features to be scheduled for release
Groom
Bug: A problem which impairs or prevents the functions of the product.
Risk
Defect Fixed By: Defect Fixed By
Testing Story: Testing Story
Issue: Issues tracked by Operations Team. Once analyzed, these can be re-categorized to a Bug, Improvement etc.
KP Feature
KP Initiative: KP Portfolio Initiative
Enhancement: Enhancement
Accomplishments: Accomplishments
Dependencies: Dependencies
Child Story: Child Story
Intake: Intake
Technical Story
Spike
Technical Requirement
Functional User Story: Functional User Story
Technical Epic: Technical Epic
New Feature: A new feature of the product, which has yet to be developed.
Improvement: An improvement or enhancement to an existing feature or task.
NDStory
Template: Issue Type for Templates
Checklist: This issue type is used to track Readiness of a Squad to go to Production. The Checklist items are as defined in the "DoD"
Factory Story: Factory Story
Data Source: Issue type for sources of data for collection
Translation Request: Translation Request
Admin Task
CRQ
Client Engagement
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.
Defect: Defects occur when the application does not conform to the requirement specification.
C2C Automation Idea: Click to Cloud Orchestration and Automation Idea or improvement
C2C O&A Story: Click to Cloud Orchestration and Automation Story for collection of related tasks
C2C New Service: Click to Cloud New Service, Catalog item or custom catalog
Gate: A Gate review of an application
C2C O&A Bug: Click to Cloud Orchestration and Automation Bug

For Sub-Task Issues

Design Review
Sub Test Execution: Represents a Sub Test Execution
Dependency
Report Status: Supports executive reporting
C2C Defect: Click to Cloud Subtask for tracking defects and bugs
Exception: Ticket to Records any Exception and related approvals
Technical task: Created by JIRA Agile - do not edit or delete. Issue type for a technical task.
Kanban Sub-task: Sub-task issues for Kanban User Stories. Used in KP Insight projects which support both Scrum and Kanban boards.
Roadmap
Bugs: Bugs
RAID: Risks, Action Items, Issues, Decisions
Sub-Template: Sub-Issue Type for Templates
Manual Test Execution: Tasks to capture Manual Test Execution results for the Story/Task
C2C Sub Task: Click to Cloud Sub Task
Sub-task: The sub-task of the issue
Test Case: Test Case (TestFLO Plugin)
Change Log: Captures changes to be used in a change log

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.
Highest: This problem will block progress.
High: Serious problem that could block progress.
Medium: Has the potential to affect progress.
Low: Minor problem or easily worked around.
Lowest: Trivial problem with little or no impact on progress.
Minor: Minor loss of function, or other problem where easy workaround is present.
Expedite: This issue is being expedited by management
1 - Critical: Critical
4 - Low: Low
Blocking: This issue is blocking efforts
2 - High: High
3 - Moderate: Moderate
AYEC: This issue has low priority and should be done At Your Earliest Convenience
None: This issue has no Priority set or is unknown at this time
Fast Track: This issue being fast tracked through the promotion process due to urgency need
Major: Major loss of function.
Unassigned: Created by JIM during import process
BAU: Business as Usual
P1 - Critical: This problem will block progress.
P2 - High: Serious problem that could block progress.
P3 - Medium: Has the potential to affect progress.
P4 - Low: Minor problem or easily worked around.
Trivial: Cosmetic problem like misspelt words or misaligned text.
3 - Medium: Has the potential to affect progress.
High / Issue with workaround: High / Issue with workaround
Work Stoppage: Work Stoppage
Low / Enhancement Request: Low / Enhancement Request
Not Required: Not Required
0 - Blocker: 0 - Blocker
4 - 4 - Low: Created by JIM during import process
Not Determined

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.

New
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.
Assigned
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.
Draft
In Progress
Published
Accepted
Archived
Rejected
Funnel: This status is managed internally by Jira Software
In Review
Done
Backlog
Analysis
Rollback: "(red)"
Approved
Portfolio Backlog: This status is managed internally by Jira Software
Implementation: This status is managed internally by JIRA Software
1 - Backlog
2 - Defined
3 - In Progress
4 - QA
5 - Done
6 - Accepted
Defined: This status is managed internally by JIRA Software
Program Backlog: This status is managed internally by JIRA Software
To Do
QA
Demo
Selected for Development
Awaiting 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
Declined
Waiting for support: (greenyellow)
Waiting for customer: (lightcyan)
Blocked: Story is blocked
DTM Publish: This status is managed internally by JIRA Software
Business Q: This status is managed internally by JIRA Software
External Work: This status is managed internally by JIRA Software
Validation: This status is managed internally by JIRA Software
Design Approved: This status is managed internally by JIRA Software
Ready for the Team: This status is managed internally by JIRA Software
Content Entry: This status is managed internally by JIRA Software
Peer Review
Deployment: This status is managed internally by JIRA Software
Complete
Completed
BTS Testing: This status is managed internally by JIRA Software
Issue Resolution: This status is managed internally by JIRA Software
Ready for Entry: This status is managed internally by JIRA Software
Content Approved
Work In Progress
Pending: This was auto-generated by JIRA Service Desk during workflow import
On Hold: This status is managed internally by JIRA Software
Cancelled
Canceled: This was auto-generated by JIRA Service Desk during workflow import
Under investigation: This was auto-generated by JIRA Service Desk during workflow import
Under Review
Planning: This status is managed internally by Jira Software
Awaiting CAB approval: This was auto-generated by JIRA Service Desk during workflow import
Implementing: This status is managed internally by Jira Software
Peer review / change manager approval: This was auto-generated by JIRA Service Desk during workflow import
Review: This status is managed internally by Jira Software
Waiting for Approval
Escalated
Deployed: Deployed
Discussion: This status is managed internally by JIRA Software
To-Demo: This status is managed internally by JIRA Software
Next Weeks priorities: This status is managed internally by JIRA Software
Next Week: This status is managed internally by JIRA Software
Ready for Dev
Ready for QA
Solution Design: This status is managed internally by JIRA Software
Quarterly Planning Estimation: This status is managed internally by JIRA Software
Epic Funnel: This status is managed internally by JIRA Software
Build and Test: This status is managed internally by JIRA Software
Solution design review design: This status is managed internally by JIRA Software
Vision And Scope: This status is managed internally by JIRA Software
Targeted: This status is managed internally by JIRA Software
Ready for Review
Risk Acceptance In Progress
Deferred
In-Progress
Review & revisions (UX, Access: This status is managed internally by JIRA Software
UX in progress: This status is managed internally by JIRA Software
UX Backlog: This status is managed internally by JIRA Software
Groomed
Dev Backlog: This status is managed internally by JIRA Software
To groom: This status is managed internally by JIRA Software
Validating on Staging - In Progress
Validating on Staging - Ready
Releasing: This status is managed internally by Jira Software
Deploying to Production - In Progress
Deploying to Production - Ready
Ready To Test: This status is managed internally by JIRA Software
Development: This status is managed internally by JIRA Software
Release Readiness Review: DoD met by squad
Approval for Pre-Prod
Approved for Prod
Released: Issue has been Released or Closed
UX review: This status is managed internally by JIRA Software
All work complete: This status is managed internally by JIRA Software
In QA
QA Ready
Blocked in QA: Blocked in QA
4-In DEV
6-In QA
Dev-WIP
3-Peer Review
Dev Done
QA in Progress
1-PO/PM Review & Approval: Review & Approval by Prod Mgr
QA Done
Blocked in DEV: Blocked in DEV
4-QA (Ready for QA): This status is managed internally by JIRA Software
In Test
In Development
Reviewing: Reviewing
Retired: Stories that are no longer needed.
Testing: This status is managed internally by JIRA Software
In Promotion
Service Enablement
In BCS: Issue is in the BCS process with IBM
Need More Info: This status is managed internally by JIRA Software
Acceptance: This status is managed internally by JIRA Software
PROD Ready: This status is managed internally by JIRA Software
Selected for DEV: This status is managed internally by JIRA Software
No Action: Rejected - Will Not Address - No Action Will Be Taken
Test: This status is managed internally by JIRA Software
Blocked/On-Hold: This status is managed internally by JIRA Software
QA SVT Done - 7
Elaborating: Requirements track and UX teams are fleshing in the story
Ready
Inbox: This status is managed internally by JIRA Software
Won't Do: This status is managed internally by JIRA Software
QA SVT Done
Cancelled/Combined
Closed or Withdrawn: HPS/KP Determined this issue is no longer needed.
UAT Ready
UAT in Progress
UAT Blocked
Dev Accepted
Evaluation
Returned
Fail
Pass: Test Passed
QA Complete
Define: This status is managed internally by JIRA Software
Measure: This status is managed internally by JIRA Software
Implement: This status is managed internally by JIRA Software
Analyze
Control: This status is managed internally by JIRA Software
TAPA_Track: Send to Tools Automation backlog for development
Discovery
Refine
Ready to Code
Sprint To Do
In Design
Code
0-DRAFT: This status is managed internally by JIRA Software
1-In Progress
2-APPROVED and ready for DEV: This status is managed internally by JIRA Software
1-Requirements in Progress: This status is managed internally by JIRA Software
3-DEV WIP: This status is managed internally by JIRA Software
5-QA WIP: This status is managed internally by JIRA Software
6-UAT (Ready for UAT): This status is managed internally by JIRA Software
7-UAT WIP: This status is managed internally by JIRA Software
8-UAT Complete: This status is managed internally by JIRA Software
9-Ready to Deploy: This status is managed internally by JIRA Software
10-Deployed to Production: This status is managed internally by JIRA Software
X-Blocked: This status is managed internally by JIRA Software
X-Canceled
X-Deferred
1.5-AWAITING APPROVAL
1-Analysis
2-Not Reproducible
3-As Designed
5-Ready For QA
7-Ready For UAT
8-In UAT
9-Testing Complete
Selected
OPS WIP
In Prod: This status is managed internally by Jira Software
Release: This status is managed internally by JIRA Software
Intake
Icebox: This status is managed internally by JIRA Software
Release Entrance: Release entrance meeting between KP and HPS
In Dev
SIT in progress
UAT Entrance: UAT entrance meeting between KP and HPS
Release Readiness
Released To Production: Released To Production
Final UAT in Progress: UAT continues post Checkpoint gate.
PROD CRQ Ready
Dev Testing: This status is managed internally by Jira Software
Waiting on Customer: This status is managed internally by JIRA Software
Deployed in QA
Deployed to SIT: Deployed to System Integration Testing
In UAT: This status is managed internally by JIRA Software
Ready for Sign-off
Not Started
Abandon
Done Done
New request: This status is managed internally by JIRA Software
Review in progress: This status is managed internally by JIRA Software
Will Not Fix: This status is managed internally by JIRA Software
Governance: This status is managed internally by JIRA Software
Waiting on Vendor: This status is managed internally by JIRA Software
Waiting on KPIT: This status is managed internally by JIRA Software
Waiting
Enhancement request: This status is managed internally by JIRA Software
Descoped
UAT
System Testing
Groom: In Backlog Grooming
Grooming
Withdrawn
Validate
Sprint Demo: This status is managed internally by JIRA Software
Review (Owner): This status is managed internally by JIRA Software
2-Under Review
3-Approved
4-Denied
1-Complete
10-Ready to Deploy
11-Deployed to Production
1-Ready
2-In Progress
3-Complete
1-Open
3-Closed
4-Closed Incomplete
4-Resolved/Mitigated
5-Realized
4-Complete
Ready for Release: This status is managed internally by JIRA Software
Failed Testing
In QA SVT
In PROD SVT
Analyse: This is spelled incorrectly and should be consolidated with 10264
Requirement Gathering: Gather requirements to define work effort
Pending Release: Pending release to QA
Out Of Scope
Fix In-progress
Retest
Fixed
4-Ready for QA: This status is managed internally by JIRA Software
PO Approval 1: PO Approval 1
PO Approval 2: PO Approval 2
Deprioritized: This status is managed internally by JIRA Software
1-Requirements Gathering: This status is managed internally by JIRA Software
2-Sprint Planning: This status is managed internally by JIRA Software
6-Ready for PROD: This status is managed internally by JIRA Software
WIP
To be scheduled: Not Tested
Code Review: Solution is under review for transition out of Development.
Evaluate
Will Not Do: This status is managed internally by JIRA Software
On-hold
In Leadership Review
In Stakeholder Review
Approved with Changes
4. QA
3C ID AIO: This status is managed internally by JIRA Software
4C ID AIO: This status is managed internally by JIRA Software
4C RACI: This status is managed internally by JIRA Software
4C Schedule 4C: This status is managed internally by JIRA Software
4C Execute: This status is managed internally by JIRA Software
4C Validate: This status is managed internally by JIRA Software
4C Done: This status is managed internally by JIRA Software
Complete RACI: This status is managed internally by JIRA Software
3C Dev RACI: This status is managed internally by JIRA Software
3C RACI: This status is managed internally by JIRA Software
3C SOW: This status is managed internally by JIRA Software
3C Scheduling: This status is managed internally by JIRA Software
3C Execute: This status is managed internally by JIRA Software
3C Validate: This status is managed internally by JIRA Software
3C Complete: This status is managed internally by JIRA Software
4C Data: This status is managed internally by JIRA Software
4C Scheduling: This status is managed internally by JIRA Software
4C Workshop: This status is managed internally by JIRA Software
4C SOW: This status is managed internally by JIRA Software
1C AIO: This status is managed internally by JIRA Software
1C RACI: This status is managed internally by JIRA Software
1C SOW: This status is managed internally by JIRA Software
1C Survey: This status is managed internally by JIRA Software
1C Schedule: This status is managed internally by JIRA Software
1C Scheduling: This status is managed internally by JIRA Software
Create CHG: This status is managed internally by JIRA Software
1C Execute: This status is managed internally by JIRA Software
1C Validate: This status is managed internally by JIRA Software
1C Complete: This status is managed internally by JIRA Software
UAT Complete
BVT Ready
BVT In Progress
Performance Ready
Performance Blocked
BVT Blocked
Performance In Progress
PROD In Progress
First OCC Ready
SOW Approval: This status is managed internally by JIRA Software
Ready for Integration
Req Gathering
Refinement
UAT Testing: This status is managed internally by JIRA Software
Sign Off
Not a Candidate
Funding Request
PO Review
4C CHG: This status is managed internally by JIRA Software
3C CHG: This status is managed internally by JIRA Software
1C CHG: This status is managed internally by JIRA Software
Attestation
SBAR
Review/Demo: This status is managed internally by JIRA Software
Customer Review: This status is managed internally by JIRA Software
Accepted / Closed: This status is managed internally by JIRA Software
Team Backlog: This status is managed internally by JIRA Software
PO Acceptance
Ready to Work: This status is managed internally by JIRA Software
Integration Kick-off
Architecture Review: This status is managed internally by JIRA Software
Migrate Ready: This status is managed internally by Jira Software
In Analysis: This status is managed internally by Jira Software
Todo
Analysis & Design
IN QA TESTING: This status is managed internally by Jira Software
TESTING COMPLETE: This status is managed internally by Jira Software
READY FOR DEPLOY: This status is managed internally by Jira Software
Sprint Backlog: This status is managed internally by Jira Software
ADA Review
QA In Progress - 2
Engineering Review: This status is managed internally by Jira Software
Design: This status is managed internally by Jira Software
3-Service Review
4-Editorial Review
DEV Blocked: This status is managed internally by Jira Software
Ready in kptest: This status is managed internally by Jira Software
Ready in ICS-UAT: This status is managed internally by Jira Software
Testing Passed: This status is managed internally by Jira Software
Failed UAT Testing: This status is managed internally by Jira Software
PO Approval: This may be associated with a custom hidden workflow.
Approved for PROD deploy: This status is managed internally by Jira Software
Approved for UAT: This status is managed internally by Jira Software
Passed in UAT: This status is managed internally by Jira Software
Blocked/ OnHold: This status is managed internally by Jira Software
Ready for SIT Deploy: This status is managed internally by Jira Software
READY FOR QA DEPLOY: This status is managed internally by Jira Software
READY FOR PROD DEPLOY: This status is managed internally by Jira Software
Vendor To Do: This status is managed internally by Jira Software
Vendor Follow-up: This status is managed internally by Jira Software
Developing
Finalized
Spike/Research Analysis
Prep for Arch Reviews
In Arch Reviews
Prep for UAT
Ready for PROD
Done/Accepted
Rel in Prod
Release Backlog
Validation by Client: This may be associated with a custom hidden workflow.
Definition in Progress
Ready for Development
Ready For Testing: This status is managed internally by JIRA Software
Intake Analysis
Ready for Definition
Ready for Deployment
Testing in Progress: This status is managed internally by Jira Software
In Testing: This status is managed internally by Jira Software
Deployed to Prod: (green)
Do Not Use
Discover
Develop
Design Review: Issue is in Design review
MFI for Review
Pending Approval
Inegrate and Test: This status is managed internally by Jira Software
Build: This status is managed internally by Jira Software
Integrate and Teset: This status is managed internally by Jira Software
Validated
Open Risk: This status is managed internally by Jira Software
Contacted
Testing/Go-Live Prep
Deployment/Ticket Complete
Dev
Stage: This status is managed internally by Jira Software
VENDOR TO IMPLEMENT: This status is managed internally by Jira Software
Dev Ready
Submitted
Discovering
Measuring
Future Work: Work to be committed in the future
WILL NOT IMPLEMENT: This status is managed internally by Jira Software
Verified: This status is managed internally by Jira Software
QA TESTING IN PROGRESS: This status is managed internally by Jira Software
SIT TESTING IN PROGRESS: This status is managed internally by Jira Software
SIT TESTING COMPLETE: This status is managed internally by Jira Software
QA TESTING COMPLETE: This status is managed internally by Jira Software
Incoming
Digital Alignment - Assess Alternatives
Partner Alignment
Delivered
Cloned to Demand Management
Handed Off
Planning Defining: This status is managed internally by Jira Software
UX Sprints: This status is managed internally by Jira Software
Dev Sprints: This status is managed internally by Jira Software
SIT DEPLOYED: This status is managed internally by Jira Software
Product Review
Estimating
Estimate Complete
Triage
CODE REVIEW COMPLETE: This status is managed internally by Jira Software
Unit Testing
UNIT TESTING COMPLETE: This status is managed internally by Jira Software
Code & Unit Test Review: This status is managed internally by Jira Software
Ready for Code/Unit Test Review: This status is managed internally by Jira Software
Design Complete
IN WORK QUEUE: This status is managed internally by Jira Software
Passed QA
In Regression Test
Requirements
Status: This status is managed internally by Jira Software
Defer
Delivery in Progress
Waiting For Response: This status is managed internally by Jira Software
Temp: This status is managed internally by Jira Software
Approved for Deployment
Deployed to PRE-PROD
Acceptance Criteria Not Met
Ready for Test
In Progress / Development: This status is managed internally by Jira Software
Testing/Review: This status is managed internally by Jira Software
SIT: System Integration Testing
IN SIT TESTING: This status is managed internally by Jira Software
Requirements Gathering: This status is managed internally by Jira Software
Active
Dev Complete: This status is managed internally by Jira Software
Ready for Parallel Testing
Ready for SIT
Ready for UAT: This status is managed internally by Jira Software
Removed
Allocated For Fix
NPSA Validation: This status is managed internally by Jira Software
Load into HEP: This status is managed internally by Jira Software
RUW Validation: This status is managed internally by Jira Software
CR & MCR: This status is managed internally by Jira Software
SFRT: This status is managed internally by Jira Software
NPSA Processing: This status is managed internally by Jira Software
Data Available
Discussion Needed: This status is managed internally by Jira Software
Ready to Start: Approved, But Not Assigned
Signed-off: This status is managed internally by Jira Software
Ready for DSD: This status is managed internally by Jira Software
Release Management: This status is managed internally by Jira Software
Pre-Work: This status is managed internally by Jira Software
Soft Go Live: This status is managed internally by Jira Software
UAT Soft GoLive: This status is managed internally by Jira Software
Info: This status is managed internally by Jira Software
Pending Priority: Waiting for a review
Move Forward
Pending SNOW: Issue is pending SNOW SelfDev team to release to QA
Ready for PO Review: This status is managed internally by Jira Software
On Hold/Blocked: This status is managed internally by Jira Software
Kanban Backlog
Product Manager Acceptance
Product Backlog: Product backlog requested by partners
Assessment: This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
Definition: This status is managed internally by Jira Software
Closeout: This status is managed internally by Jira Software
On-going
Visible Light: This status is managed internally by Jira Software
Pre-Launch: Preparation for launch status
Launched: Program launching activity for go-live
Return Scheduled: This status is managed internally by Jira Software
Ready for Verification: This status is managed internally by Jira Software
Review and Approval: This status is managed internally by Jira Software
Approved for Development: This status is managed internally by Jira Software
Failed: This status is managed internally by Jira Software
In Pre-Prod SVT: Service Validation Testing
SQL Files Not Found
Jenkins Job Failed to attach files
Researching: This status is managed internally by Jira Software
Fixed-ReTest: This status is managed internally by Jira Software
QA DEPLOYED: This status is managed internally by Jira Software
Squads: This status is managed internally by Jira Software
Plan Items: This status is managed internally by Jira Software
Deployment (UAT): Ready for UAT
Ready for PI: Selected for Program Increment
Done (release-independent): This status is managed internally by Jira Software
Analysis in Progress
Ready To Deploy: This status is managed internally by JIRA Software
Release Ready: This status is managed internally by JIRA Software
Business Validating: This status is managed internally by JIRA Software
Analysis & Story Development: This status is managed internally by JIRA Software
Analyzing: This status is managed internally by Jira Software
Squad Doing: This status is managed internally by Jira Software
Squad Done: This status is managed internally by Jira Software
QA (2nd Tester): This status is managed internally by Jira Software
Monitor
DevOps To Do: This status is managed internally by Jira Software
Regression Testing: This status is managed internally by Jira Software
Waiting on QA: This status is managed internally by Jira Software
Waiting on (X): This status is managed internally by Jira Software
Assessment Factory
Control Build Queue
Controls Factory
Suspended
Hardening Guide Queue
Full Kit
Deploy Factory
Ongoing: This status is managed internally by JIRA Software
Completed Delayed: This status is managed internally by Jira Software
Ready for Demo
MEDIUM: This status is managed internally by JIRA Software
HIGH: This status is managed internally by JIRA Software
SOLUTION DEVELOPMENT: This status is managed internally by Jira Software
RELEASE DEPLOYMENT: This status is managed internally by Jira Software
REVIEW EDIT APPROVE: This status is managed internally by Jira Software
EDITS SUGGESTED: This status is managed internally by Jira Software
WAIT: This status is managed internally by Jira Software
DOD Complete
Waiting for Atlassian
Waiting On Response(s): This status is managed internally by Jira Software
Currently Working On: This status is managed internally by Jira Software
Completed Work: This status is managed internally by Jira Software
Exploring
Drafting
Getting Data
Baselining
Aligning w Stakeholders
Setting targets
Active in VDB
Hold: This status is managed internally by Jira Software
Exploration (draft): This status is managed internally by Jira Software
QC: This status is managed internally by Jira Software
Block: This status is managed internally by Jira Software
Refined
QA Promotion Approved: The promotion to QA is approved
QA SVT Ready: QA promotion is SVT ready
QA SVT Passed: The QA promotion has passed SVT
QA SVT Failed: The SVT in QA failed
PRE-PROD Promotion Approved: PRE-PROD Promotion Approved
PRE-PROD SVT Ready: PRE-PROD SVT Ready
PRE-PROD SVT Passed: PRE-PROD SVT Passed
PRE-PROD SVT Failed: PRE-PROD SVT Failed
PROD Promotion Approved: PROD Promotion Approved
PROD SVT Ready: PROD SVT Ready
PROD SVT Passed: PROD SVT Passed
PROD SVT Failed: PROD SVT Failed
New Control
Confirm Inventory
Tracking
Create Work Orders
Intake Approved
LOE Approved
LOE submitted
Moved to Future Release
Invalid
Pulled from Release
Deployed to Test
In Progress - Test: This status is managed internally by Jira Software
New Upload
Asset Approval
Uploaded
Ready to Release
Qualified Idea
In Planning
In Execution
DEPLOYMENT IN PROGRESS: (pink)
Backed Out
To Verify: This status is managed internally by Jira Software
Dev - Done: This status is managed internally by Jira Software
Ready for Production: This status is managed internally by Jira Software
SVT Failed: Service Validation failed
SVT Passed: Service Validation Passed
User Acceptance: This status is managed internally by Jira Software
Requirements Meeting: This status is managed internally by Jira Software
Verify (UT in SIT Env): This status is managed internally by Jira Software
Test In Progress
User Acceptane: This status is managed internally by Jira Software
EG Pursuing: EG Pursuing
Received
Resubmitted
Projects: This status is managed internally by Jira Software
Ready for Validation: This status is managed internally by Jira Software
Initiatives (Manufacturer): This status is managed internally by Jira Software
Epics (Device Name): This status is managed internally by Jira Software
CyberArk: This status is managed internally by Jira Software
Active Directory (AD): This status is managed internally by Jira Software
Firewall Config/Disable Ports: This status is managed internally by Jira Software
Validate Segmentation Profile: This status is managed internally by Jira Software
Kaseya/CrowdStrike/Qualys: This status is managed internally by Jira Software
Vendor Remote Access: This status is managed internally by Jira Software
Validate Patch Strategy: This status is managed internally by Jira Software
Validate Software Inventory: This status is managed internally by Jira Software
To Do - Projects: This status is managed internally by Jira Software
Communication: This status is managed internally by Jira Software
Customer UAT: This status is managed internally by Jira Software
Reviewed
New Intake
KPDDC Engagement
AppTeam Engagement
KPDDC Dev
AppTeam Dev Validation
KPDDC QA
AppTeam QA Validation
KPDDC DQ
KPDDC Prod
AppTeam Prod Validation
Prod Maintenance
Ad-Hoc
Up Next: This status is managed internally by Jira Software
In Queue
Tech Deployment: This status is managed internally by Jira Software
In QA Backlog
Internal Validation
Awaiting fixes
In KP Backllog
In KP Review
In Prod Queue
In KPCA Queue
Awaiting Publishing
Post-Prod Validation
Awaiting Redirect
Awaiting Redirect Validation
Awaiting Takedown
Documentation
Product/UX Review
MOBILE READY
Performance Testing: This status is managed internally by Jira Software
Business Validation: This status is managed internally by Jira Software
Data Encryption: This status is managed internally by Jira Software
SIT Done
Ready for UAT Deployjment
Deployed to UAT
BVT Done
Addressed by Another Issue
Returned for Clarification
Returned - New Requirement
To Verify (UT in SIT Env): This status is managed internally by Jira Software
Not Valid: This status is managed internally by Jira Software
Backlog Grooming
Dev In Progress: This issue is being actively worked on at the moment by the assignee.
Integrated
integration testing completed
integration testing in progress
QA - In Progress
Ready for Dev Integration
ready for integration testing
Ready for PO
Ready for Regression Testing
ready for scrum approval
ready for scrum test
Ready for system integration/closed
Regression Testing in progress
scrum approved
scrum test completed
scrum test in progress
Shelved: Identifies issues that have been put on hold
Fix-in-Progress
Ready for Retest
Retest in Progress
TestID: This status is managed internally by Jira Software
Delivered to EG
Aborted
Assessing
Internal Review
Publishing
Proof of Concept
WARRANTY PERIOD: (green)
WIT: This status is managed internally by Jira Software
Demo Needed: This status is managed internally by Jira Software
Approval: Approved
Deprecated
Re-work: Requires changes.
In Use
App Build POC Request
Pending AB Capacity Contraints
Pending-Under Review
Pending Technical Requirement Development
Pending Deployment Calendaring
SDC Review
SDC-Pending Business Impact
UAT Stand Alone Request
Microseg: This status is managed internally by Jira Software
Deferred Controls: This status is managed internally by Jira Software
Waiting for Epic
On Hold - Waiting for Partner
On Hold - Build Overlap
Build Complete - In Testing
Build in Progress
Acknowledged for Planning
Requirements/ Clarification Needed
Production Ready
Testing Complete - Waiting for Approval
Pending BRD Approval
01 - Evaluation: This status is managed internally by Jira Software
02 - Fix in Progress: This status is managed internally by Jira Software
To-Do: This status is managed internally by Jira Software
Monitoring: This status is managed internally by Jira Software
Done (Release-Indp: This status is managed internally by Jira Software
PM Team: This status is managed internally by Jira Software
Dev Team Review: This status is managed internally by Jira Software
Dev Team Review Complete: This status is managed internally by Jira Software
Develop Test Script: This status is managed internally by Jira Software
Validate Script: This status is managed internally by Jira Software
Watchlist: This status is managed internally by Jira Software
Requested: This status is managed internally by Jira Software
Partially Released
Cancel: This status is managed internally by Jira Software
Team evaluation: This status is managed internally by Jira Software
Reroute
Awaiting Acceptance
Project Manager Evaluation pending: This status is managed internally by Jira Software
Acceptance Testing
Acceptance Testing Complete
Pending Clarification
Discovery Meeting: This status is managed internally by Jira Software
No Further Action: This status is managed internally by Jira Software
Scope preparation: This status is managed internally by Jira Software
CERT NOT MET
CERTIFIED
Build Assigned: This status is managed internally by Jira Software
Build for QA: This status is managed internally by Jira Software
Build Ready for Scheduling: This status is managed internally by Jira Software
WAIVED
Clarification
Testing/SignOff: This status is managed internally by Jira Software
Done (RELEASE): This status is managed internally by Jira Software
Candidate: This status is managed internally by Jira Software
Planned Q1: This status is managed internally by Jira Software
Planned Q2: This status is managed internally by Jira Software
Planned Q3: This status is managed internally by Jira Software
Planned Q4: This status is managed internally by Jira Software
Create Regional DRI: Dev Analysts creating regional DRI
Create Instructions
Instruction Readiness
Regional Deployment Readiness
Released to Non-Prod
Pre-Production Validation
Deployment Validation
Require Product Review
Investigation In-Progress
Ready for IT Testing
Automation Analysis
Automation Development
Automation Out of Scope
Dry Run
Sunset
Engagement: This status is managed internally by Jira Software
Assigned to Pentest Lead: This status is managed internally by Jira Software
Scheduled Next Year: This status is managed internally by Jira Software
Pending Deployment
Not Done
Testing Completed
Recurring Projects: This status is managed internally by Jira Software
Waiting on Dev Team: This status is managed internally by Jira Software
To be groomed: This status is managed internally by Jira Software
Ready to Accept: This status is managed internally by Jira Software
Analyze & Solution Design: This status is managed internally by Jira Software
SIT & UAT: This status is managed internally by Jira Software
Override
ACA HOLD: This status is managed internally by Jira Software
Business Approved
Decompose
Impediment
Request
System Test
Get Server Access: To get server access – we need to add group membership to users.allow file. Please get the current server user.allow group membership. Please contact @Padma Kolli, If you need the current server details. Please get approval from JRM Role/Group owner. The Ownership will be available in JRM file here . UNIX JRM V. 1.1.cs.msds.kp.org.xlsx Submit ticket in this url (https://kp.service-now.com/sp?id=sc_cat_item_guide&sys_id=84fa2ec3dbdedc184e606a5b8a96199b) and select Unix and then select “Server JRM role update (users.allow)”
Get Root Access: Please get approval from michael.j.jenkins@kp.org Submit ticket in this url (https://kp.service-now.com/sp?id=sc_cat_item_guide&sys_id=84fa2ec3dbdedc184e606a5b8a96199b) and select Unix and then select “temp root”
Fix /Apps & /Logs: Contact IBM Unix build Engineer who shared the handover excel
Uninstall and Install a New Tomcat: -- As root disable default tomcat service systemctl status jws5-tomcat.service systemctl stop jws5-tomcat.service systemctl status jws5-tomcat.service systemctl disable jws5-tomcat.service systemctl status jws5-tomcat.service --As root remove default tomcat cd /opt/rh rm -rf jws5 -- As iamspdev mount the share for jws packages pbrun su -c 'mount -t nfs 10.15.76.36:/workfs/Software /mnt -o nfsvers=3 -o nolock' cd /apps/jboss unzip /mnt/JWSTomcat/jws-5.6.0-application-server.zip unzip -o /mnt/JWSTomcat/jws-5.6.0-application-server-RHEL8-x86_64.zip unzip -o /mnt/JWSTomcat/jws-5.6.2-application-server.zip unzip -o /mnt/JWSTomcat/jws-5.6.2-application-server-RHEL8-x86_64.zip
Make sure iamspdev owns /apps: If you need different version of jws tomcat, please contact D K Murthy Krish.Murthy@kp.org
Validate Disk Space: Validate Disk Space, CPU config between old vs new Servers
NFS mount point ticket: NFS mount point ticket, please contact Padma.
Ready for Fix
Sent to Caregility
Caregility Follow-Up
Pending Caregility Release
QA/Deploy/Share: This status is managed internally by Jira Software
Aligned
Committed
Ready for Assessment/Discovery
Roadblock
Ready for Testing - Ready for UAT
Ready for Testing - Blocked
Ready for Testing - Ready for SIT
Review Rejected
Implemented
BusinessOps: This status is managed internally by Jira Software
Customer Approval: This status is managed internally by Jira Software
Rollout Planning
Migrate to PROD: This status is managed internally by Jira Software
Ready for QA Dev: This status is managed internally by Jira Software
TST Dev Complete: This status is managed internally by Jira Software
TST Dev In Progress: This status is managed internally by Jira Software
Ready for Approval
Ready for Prod Deployment: This status is managed internally by Jira Software
Waiting On DevTeam: This status is managed internally by Jira Software
To Review: This status is managed internally by Jira Software
Pending Embed SRE: This status is managed internally by Jira Software
Not Approved: This status is managed internally by Jira Software
Approved to Work: This status is managed internally by Jira Software
Recurring Work Items: This status is managed internally by Jira Software
Ad-Hoc Work Items: This status is managed internally by Jira Software
UAT Done: This status is managed internally by Jira Software
On Hold/Waiting for Response: This status is managed internally by Jira Software
PO Review/Approval: This status is managed internally by Jira Software
Ready for OTS Dev: This status is managed internally by Jira Software
OTS Dev In Progress: This status is managed internally by Jira Software
OTS Dev Complete: This status is managed internally by Jira Software
Review/Refine with Market: This status is managed internally by Jira Software
BRD In Process
Resource Assigned
Team Assigned
Waiting for Customer (Response)
Ready for OTST
Deployed to OTST
Validated in OTST
Ready for PSUP
Deployed to PSUP
Validated in PSUP
Validated in PROD
Squad Self Waived
Supporting
SRE Backlog: This status is managed internally by Jira Software
Future Phase: This status is managed internally by Jira Software
Assigned to a Release
Results Approved
Partially Implemented
Feature Testing Complete
Acceptance Testing Initiated
Regression Testing Initiated
Regression Test Initiated
Regression Complete
Deploy to Production
Execution Setup
Execution
Awaiting Successful POC Testing
Referred
Request to Reschedule
Rescheduled per Request
Dev Integration In Progress
Design In Progress
Ready for Design
PO Approved
This Week: This status is managed internally by Jira Software
Deployment Completed
More Info Needed
Patrially Deployed
Under IT Review
Ready for Prioritization
Prioritized
In Discovery
Discovery Complete
Discovery Complete - Future
Staged Delivery – Build Complete
Yet to start: This status is managed internally by Jira Software
Done and Destroyed: Testing is complete and machines have been destroyed or requested to be destroyed.
Approved for Discovery
Discovery In Progress
DISCOVERY COMPLETE - FUTURE PRIORITY: (yellow)
Discovery Completed
Approved for Delivery
GOV DECISION IN-PROGRESS: (turquoise)
Delivery in Planning: (blue)
DELIVERY IN EXECUTION: (orange)
Discovery In-Progress
REQ-Deleted: This status is managed internally by Jira Software
REQ-APPROVED: This status is managed internally by Jira Software
REQ-PENDING APPROVAL: This status is managed internally by Jira Software
CR-APPROVED: This status is managed internally by Jira Software
CR-DELETED: This status is managed internally by Jira Software
CR-PENDING APPROVAL: This status is managed internally by Jira Software
Deployed to DEV
Deployed to PERF
Deployed to QA
Ready for FCAB
Prod Deployment: This status is managed internally by Jira Software
Test Ready: This status is managed internally by Jira Software
IT Testing: This status is managed internally by Jira Software
Business Testing: This status is managed internally by Jira Software
01 New
02 Analyze
03 Ready for PI
04 Implementing
05 Feature Testing Complete
06 Acceptance Testing Initiated
07 Acceptance Testing Complete
10 Ready to Deploy
15 Scheduled
30 Done
Exception
Uncommitted: This status is managed internally by Jira Software
Scheduled
New Story Triage
Development Complete
Pre-Groom
Code Complete
Pending Fixes
UXDC Review
Evaluation Backlog: Explore and Evaluate
Deploy: This status is managed internally by Jira Software
Code Fix Required
Ready to Approve: This status is managed internally by Jira Software
Validation/Testing: This status is managed internally by Jira Software
Pending Business Clarification
Pending TRD Updates
Waiting on Partner
New/Triage: This status is managed internally by Jira Software
Launch and Evaluate: This status is managed internally by Jira Software
FUTURE PRIORITY: (yellow)
APPROVED FOR PRE_DISCOVERY: (purple)
PRE-DISCOVERY IN-PROGRESS: (purple)
PRE-DISCOVERY COMPLETED: (purple)
Code Cleanup
Build Dashboard: This status is managed internally by Jira Software
Collect & Refine Data: This status is managed internally by Jira Software
Deployed to Production
Pending Review: This status is managed internally by Jira Software
DevOps Review
DevOps Approved
Design/Requirements
DEV/EEG
Handoff
PSUP
RESC
TSTS
WITS
Done with Issues
Ready for Analysis
20 Deployed
Dependency: This status is managed internally by Jira Software
Code Packaged
Ready for QA deployment: This status is managed internally by Jira Software
Planned
PO Ready: This status is managed internally by Jira Software
Staged: This status is managed internally by Jira Software
delayed: This status is managed internally by Jira Software
Frame: This status is managed internally by Jira Software
Assessing Impact: Assessing Impact
PI Backlog
Dev/UAT ROM Needed: This status is managed internally by Jira Software
Sprint Planning
Needs Prioritization: This status is managed internally by Jira Software
In UAT Testing
For Review
BRD Needed: This status is managed internally by Jira Software
Discovery Backlog: (brown)
Delivery Backlog: (brown)
Deleted: This status is managed internally by Jira Software
Deployed]: This status is managed internally by Jira Software
UAT/UBT: This status is managed internally by Jira Software
Inactive: This status is managed internally by Jira Software
Internal QA: This status is managed internally by Jira Software
UAT/Business Validation: This status is managed internally by Jira Software
TOSLOG: This status is managed internally by Jira Software
Initiate: This status is managed internally by Jira Software
Priority: This status is managed internally by Jira Software
DMS Review
DMS Approved
UDR UAT TESTING COMPLETE: This status is managed internally by Jira Software
Ready for Acceptance: This status is managed internally by Jira Software
1st level approvals
2nd level approvals
3rd level approvals
Complete and Wait: This status is managed internally by Jira Software
Ready for Solution Review
Moved to Development
Pending Ops SRE: This status is managed internally by Jira Software
UBT: This status is managed internally by Jira Software
Development in Progress
Approved & On Hold: This status is managed internally by Jira Software
Ready for Business Approval
Intake In Progress
Ready for Estimation
Ready for Scheduling
Ready for Go no Go
Deployed/Done
Expired
plan: This status is managed internally by Jira Software
Implementation Planning: This status is managed internally by Jira Software
Build + Test: This status is managed internally by Jira Software
Launch + Evaluate: This status is managed internally by Jira Software
Maintain: This status is managed internally by Jira Software
Ideate + Prototype: This status is managed internally by Jira Software
Ready for PI planning
No Further Action Require: This status is managed internally by Jira Software
Epic Refinement in Progress: Epic Refinement in Progress
Scrum Completed: Scrum Completed
Ready fo Relea
In-Validation
Code Change in Progress
Code Check-In Completed
Code Deploy Completed
Code Review Completed
Code Review Requested
Identified Code
Picked Up by Development
Reviewed or Reproduced
Reviewed with Business and Testing
Unit Test in Progress
UAT Testing in Progress
Deployment Validation in Progress
UBER DEPLOYMENT COMPLETE
UBER VALIDATION COMPLETE
Requirements & Solutioning
Request in Progress
Solutioning in Progress
Pre-Canceled
Denied
maint: This status is managed internally by Jira Software
Deployed to QA Staging
Deployed to Pre-Prod Staging
CODE AND UNIT TEST REVIEW: This status is managed internally by Jira Software
SIT TESTING: This status is managed internally by Jira Software
READY FOR STAGING/DEPLOY: This status is managed internally by Jira Software
STAGING DEPLOYED: This status is managed internally by Jira Software
STAGING: This status is managed internally by Jira Software
Pending Feedback: This status is managed internally by Jira Software
Ready for UAT Testing
Testing Done
Demo Accepted
Inprogress
Retesting
Analysis - In Progress
In Dev Analysis
Dev - In Progress
Ready for Reproduction
Test Case Done
51 NEW
55 READY FOR PI
60 TESTING INITIATED
65 TESTING COMPLETE
70 DEMO & APPROVAL INITIATED
85 DESCOPED
80 DONE
75 DEMO & APPROVAL COMPLETE
Scheduled for Grooming
Grooming In Progress
Scheduled for Design
Intake Done
Grooming Scheduled
Grooming Done
Design Scheduled
Design Done
KP-NON-PROD
KP IQA
KP REPRODUCTION
Approved by SMEs
Approved by Leads/Sponsors
Shared with DG Bodies
PDX DEV REVIEW
KP IQA RMA
KP APP SUPPORT RMA
3rd Party Code Change
Ongoing Consulting
Formalize
KT In Progress
Waiting on deployment
Verification: This status is managed internally by Jira Software
Ready for Implementation
ScopeDetailing
PreGroom Inprogress
Elaborated
Duplicate
Ready for Pretest
Pretesting
Pretest Complete
ACN Support
ACN Dev Review
ACN Dev
ACN QA
Closed Complete
Closed Skipped
Closed Incomplete
Wait for Deployment
Resolved in Non-Prod
Parking Lot
Impact
Ready For Delivery
Delivery
Dev / Test
Product Discovery
Solution Discovery
To Dos-Backlog: https://sd.ads.kp.org/sd/browse/ADSTS-3946
Work In Progress-Delivery: https://sd.ads.kp.org/sd/browse/ADSTS-3923
Initiated: This status is managed internally by Jira Software
CR-DRAFT: This status is managed internally by Jira Software
REQS DRAFT AND PENDING APPROVA: This status is managed internally by Jira Software
Request/Backlog
Planning/Reqs
Design/Wireframe
Implementation/Code
Testing/UAT
Deployment/Docs
Maintenance/Bugs
Validate Staging
Legacy Auth Navigation: This status is managed internally by Jira Software
MCE Navigation: This status is managed internally by Jira Software
Mobile App: This status is managed internally by Jira Software
3A Mobile App: This status is managed internally by Jira Software
Selected for Discovery: This status is managed internally by Jira Software
In Discussion: This status is managed internally by Jira Software
Content Authoring: This status is managed internally by Jira Software
Editorial Review: This status is managed internally by Jira Software
WARRANTY SUPPORT: This status is managed internally by Jira Software
ED/Director Approval
GHA Chief Engineer Approval
In Code Review
Scheduled for Demo
KP-APP-SUPPORT
PDX SUPPORT
PDX ARCHITECT
PDX DBA
PDX DESIGN
PDX DEV
PDX QA
CLOSED/RESOLVED
PDX IRC
KP APP SUPPORT RMA INTAKE
Review Needed
Design Fixed
Waiting for Deployment
DEV Fixed
IRC
Ready for Grooming: This status is managed internally by Jira Software
PE Test Planning: This status is managed internally by Jira Software
PE Testing Completed: This status is managed internally by Jira Software
PE Testing in Progress: This status is managed internally by Jira Software
Reproduction - in Progress
Architecture - In Progress
Waiting on Support - In Progress
Waiting on IT
Ready for Architecture
UAT Test Execution: This status is managed internally by Jira Software
UAT Test Planning: This status is managed internally by Jira Software
IQA Pass: This status is managed internally by Jira Software
Deployment complete/done
Pending Funding
Backlog - New
Demo Completed
Design Dev
Design Artifact Generated
Awaiting Deployment
To Be Release: This status is managed internally by Jira Software
Ready For Release To Prod: This status is managed internally by Jira Software
QMS Testing In Progress
A&D: This status is managed internally by JIRA Software
Validating on Staging: This status is managed internally by Jira Software
Deploying to Production: This status is managed internally by Jira Software
Testing / QA In Progress: This status is managed internally by Jira Software
Paused
Backlog - Validated
LOE Created
Dev Testing Completed
Leadership Rejected
Ready for SIT testing
UAT Testing InProgress
JIRA User Story Created
PRR Approved
Leadership Approved
In User Acceptance
Ready for Migration: This status is managed internally by Jira Software
Leadership Reviewed
QMS Certification Completed
Post-release validation: This status is managed internally by Jira Software
TRB Review
Sprint Dev In Progress
Validating: This status is managed internally by Jira Software
Blocker: This status is managed internally by Jira Software
Defect Fixing
Consulting
UI Development: UI Team is developing screen flows and front end shells
Consult In Progress
Ready for Assessment
QMS Testing InProgress
Track Other Teams Deliverables
Assessed
Demo/User Acceptance: This status is managed internally by Jira Software
LOE Reviewed
Edit: This status is managed internally by Jira Software
PROD Deployment Completed
Ready for Code Review
Released to Prod: This status is managed internally by Jira Software
Prod Pilot
Prod Support
New Items: This status is managed internally by Jira Software
End Point Available: This status is managed internally by Jira Software
QA Validation: This status is managed internally by Jira Software
Approved By PO/TL: This status is managed internally by Jira Software
Unit Test API (? days out): This status is managed internally by Jira Software
Dev Validation QA (? days out): This status is managed internally by Jira Software
PO/TL Review: This status is managed internally by Jira Software
Prep For Prod: This status is managed internally by Jira Software
Discovery/Design: This status is managed internally by Jira Software
Confirmed In PI5: This status is managed internally by Jira Software
In QA Env: This status is managed internally by Jira Software
Done (Sprint): This status is managed internally by Jira Software
Ready for Push To Prod: This status is managed internally by Jira Software
Expose API (? days out): This status is managed internally by Jira Software
GitHub Team Approval
Revisions needed
IN REVISION
Staged in QA: This status is managed internally by Jira Software
Staged in Arch: This status is managed internally by Jira Software
Passed Due: This status is managed internally by Jira Software
Deployed to HINT
Deployed to Regional
Refinement Complete
Refinement in Progress
Ready for App Integration
Active Backlog (R4D)
Project Intake
Stakeholder Review and Approval
Develop Project Artifacts
Publish Project Artifacts
Pre-Assessment
CCB Approval for Assessment
Assessment (SMG Analysis)
CCB Approval for Development
Consult
CR-PENDING MGR APPROVAL: This status is managed internally by Jira Software
CR-PENDING DIR APPROVAL: This status is managed internally by Jira Software
CR-PENDING GOVERNANCE APPROVAL: This status is managed internally by Jira Software
CR-NOT STARTED: This status is managed internally by Jira Software
REQ-IN PROCESS: This status is managed internally by Jira Software
REQ-PLACEHOLDER: This status is managed internally by Jira Software
CR-PLACEHOLDER: This status is managed internally by Jira Software
Pending Artifacts
DEPLOYED TO DR
Deployed to All-NonProd
ON TRACK - EXTENDED: (purple)
Migration Support
Go/no-go
KP Configuration
Feature in Progress
Deployed to POC
Deployed to TST
Blocked/On Hold: This status is managed internally by Jira Software
Dropped: This status is managed internally by Jira Software
Prod Initial Load & Validation
Prod Incremental Load & Validation
PO Accepted, Closed: This status is managed internally by Jira Software
Migrating: This status is managed internally by Jira Software
Final Migration: 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.

Done: Work has been completed on this issue.
Declined: This issue was not approved.
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.
Analyzing: Issue is in process of being analyzed for requirement gathering
Reviewing: Reviewing basic requirements for acceptance
Rejected: This issue was not approved.
Funnel: Intake Funnel for incoming requests
Pending Funding: Funding needs are being determined.
Development: Issue is being developed
QA Promotion: Issue is being promoted and tested in the QA Environment
Failed: Issue failed testing or bug found: C2COD Used Resolution
INT Promotion: Issue is being promoted and tested in the Integration Environment
Discovery: Issue is in Development Discovery for non standard or custom work
Code Review: Issue requires a code review
Retired: Retired Release
Partial Release: Issue has limited release visibility and may not have all GA options available
Closed: Issue is successfully released
Backlog: Issue is in O&A Backlog queue
Canceled: Issue was canceled
Pending Input: Issue is pending input and is blocked
Pending QA SVT: Issue is pending Service Validation in QA
Open: Open
Ready for Production: Issue is ready for Production release
In Production SVT: Issue is being validated in Production
Production Support: Issue is associated with Production Support
Passed: Issue has Passed the testing criteria
Out of Scope: Issue is out of scope
Initiating: Issue is being Initiated
Planning: Issue is in Planning Phase
Executing: Issue is in Execution Phase
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.
Incomplete: The problem is not completely described.
Closed/Withdrawn: HPS or KP has determined this issue is no longer required.
Completed
Known Error: The problem has a documented root cause and a workaround.
Software failure
Deferred/Postponed: Deferred or Postponed
Configuration Change: Configuration Changes made to resolve the issue
Withdrawn: KP has determined this issue is no longer required.
Pending Resource: Used by C2COD
Working As Designed: Product is working as designed - used by KP.org DDO Operations
Hardware failure
Implemented: TEMLKPD: Deployment Successful
Partially Implemented: TEMLKPD: Deployment Partially Successful
Backed Out: TEMLKPD: Deployment Backed Out
Cancelled: TEMLKPD: Deployment Cancelled
Code Change: Code Change made to resolve the issue
Database: Database Change made to resolve the issue
Content: Content Change made to resolve the issue
Requirement: Requirement Change made to resolve the issue
Environment: Environment Change made to resolve the issue
Service Bounce: Service Bounced to resolve the issue
Test Data
Invalid Test case
External Interfaces: Defect/Bug resides in the external interface causing the system to perform erroneously
Code Deployment: Issue caused due to unexpected / unwarranted modification while code branches were being merged or conflict during code promotion
Design: Issue caused due to erroneous design of the underlying requirements
Defect Fixed
Defect Fixed, new defect found
Resolved, no fix needed
Withdrawn-Business Decision
Withdrawn-Cannot Reproduce
Withdrawn-Change Request
Withdrawn-Duplicate Defect
Withdrawn-No Longer Valid
Withdrawn-Training Issue
Withdrawn-Working as Designed
Withdrawn-User Error
Withdrawn–Consulting Provided
Certified
Not Certified
Waived
Exception
Self-Waived
Pending Requirements
LOE Pending
LOE Submitted
LOE Approved
Pending Solution Discussion
Scheduled
Converted
Cannot Replicate
Resolved: Work has been completed on this issue