Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Development
-
Security Level: Public (Public: Anyone can view)
-
Labels:
-
Similar issues:
KULRICE-12998Test git with db install process KULRICE-12994Git Migration KULRICE-14065Update Rice docbook references from svn to git KULRICE-14002Develop scm replacement jobs and script for git migration KULRICE-13534Set up git KULRICE-13326Analysis: Identify Critical Path Plugins KULRICE-14066 Modify KSB_Bus_Security.xml and Subversion wiki page to reflect Git change KULRICE-13966 Update db install process for branch changes KULRICE-3309rice db changes for kfs KULRICE-49Document our process for making core DB changes in Rice -
Epic Link:
-
Rice Module:KRAD
-
Application Requirement:KFS, KC
-
Sprint:Middleware 2.5.2 Sprint 3, Middleware 2.5.2 Sprint 4, Middleware 2.5.2 Sprint 5
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
-
Code Review Status:Not Required
-
Include in Release Notes?:Yes
-
Story Points:5
Description
As part of the migration to git, db updates in versions through 2.4 need to be done manually. Analysis needs to be completed to determine and document the process for these updates.
Issue Links
- cloned from
-
KULRICE-11182
Clear out all locking keys on Maintenance copy, not just the main object
-
