Locked 걸린 필드의 잠금해제 방법

Owned by 이병욱
2018-11-22
2 min read

 

1.JIRA SW 의 DB에 접근하여 커스텀필드 ID의 아래의 쿼리를 실행

SELECT id,customfieldtypekey,cfname from customfield where customfieldtypekey like 'com.pyxis.greenhopper.jira%';

 

결과값
+-------+-------------------------------------------+-------------+
| id    | customfieldtypekey                        | cfname      |
+-------+-------------------------------------------+-------------+
| 10100 | com.pyxis.greenhopper.jira:gh-epic-link   | Epic Link   |
| 10101 | com.pyxis.greenhopper.jira:gh-epic-status | Epic Status |
| 10102 | com.pyxis.greenhopper.jira:gh-epic-label  | Epic Name   |
| 10103 | com.pyxis.greenhopper.jira:gh-epic-color  | Epic Color  |
| 10104 | com.pyxis.greenhopper.jira:gh-sprint      | Sprint      |
| 10105 | com.pyxis.greenhopper.jira:gh-lexo-rank   | Rank        |
+-------+-------------------------------------------+-------------+

 

2. managedconfigurationitem 테이블의 item_id와 Locked를 풀기원하는 ID가 일치 되는지 확인

SELECT * from managedconfigurationitem;


결과값

+-------+-------------------+--------------+---------+--------------+--------------------------------------------------------------------------------------+-----------------------------------+
| ID | ITEM_ID | ITEM_TYPE | MANAGED | ACCESS_LEVEL | SOURCE | DESCRIPTION_KEY |
+-------+-------------------+--------------+---------+--------------+--------------------------------------------------------------------------------------+-----------------------------------+
| 10000 | customfield_10000 | CUSTOM_FIELD | true | LOCKED | com.atlassian.jira.plugins.jira-development-integration-plugin:reserved-field-locked | devstatus.customfield.locked.desc |
| 10100 | customfield_10100 | CUSTOM_FIELD | true | LOCKED | com.pyxis.greenhopper.jira:reference-select-locked | gh.customfield.locked.desc |
| 10101 | customfield_10101 | CUSTOM_FIELD | true | LOCKED | com.pyxis.greenhopper.jira:reference-select-locked | gh.customfield.locked.desc |
| 10102 | customfield_10102 | CUSTOM_FIELD | true | LOCKED | com.pyxis.greenhopper.jira:reference-select-locked | gh.customfield.locked.desc |
| 10103 | customfield_10103 | CUSTOM_FIELD | true | LOCKED | com.pyxis.greenhopper.jira:reference-select-locked | gh.customfield.locked.desc |
| 10104 | customfield_10104 | CUSTOM_FIELD | true | LOCKED | com.pyxis.greenhopper.jira:reference-select-locked | gh.customfield.locked.desc |
| 10105 | customfield_10105 | CUSTOM_FIELD | true | LOCKED | com.pyxis.greenhopper.jira:reference-select-locked | gh.customfield.locked.desc |
+-------+-------------------+--------------+---------+--------------+--------------------------------------------------------------------------------------+-----------------------------------+

 

3. 풀기원하는 필드의 managed column을 false로 변경 ex) Epic Status, Epic Name 변경

UPDATE managedconfigurationitem set managed='false' where item_id in ('customfield_10101','customfield_10102');

<참고> 위의 변경사항을 반영하고, Access_level열은 Locked로 남아있지만 UI에서는 잠금해제됨.

 

4. 필드에서 required 변경

 

5. managed column의 값을 true로 변경 ex) Epic Status, Epic Name 변경

UPDATE managedconfigurationitem set managed='true' where item_id in ('customfield_10101','customfield_10102');

 

재시작(startup)되면, 해당필드는 자동으로 잠긴다.