Summary

Example scenario:

1. Hierarchy levels:
   • Program - Program issue type
   • Initiative - Initiative issue type
   • Epic - Epic issue type
   • Story - Story issue type

After moving an Initiative to Program issue type, the Issue Property still intact.

Steps to Reproduce

1. Step up the Hierarchy levels as above.
2. Create an issue with Program issue type.
3. Create an issue with Initiative issue type.
4. Set the Initiative issue's Parent link to Program issue.
5. Move Initiative issue to change the issue type to Program issue type.

Expected Results

Checking the originally created Program issue:

1. <Base URL>/rest/api/2/issue/<Issue key>/properties/
   Result:

   {"keys":[{"self":"<Base URL>/rest/api/2/issue/10013/properties/sd.initial.field.set","key":"sd.initial.field.set"}]}
   

2. Hacking the request from the Actual Result to check jpo-issue-properties:
   <Base URL>/rest/api/2/issue/10013/properties/jpo-issue-properties
   Result:

   {"errorMessages":["The property jpo-issue-properties does not exist."],"errors":{}}
   

Actual Results

1. <Base URL>/rest/api/2/issue/<Issue key>/properties/:
   Result:

   {"keys":[{"self":"<Base URL>/rest/api/2/issue/10015/properties/jpo-issue-properties","key":"jpo-issue-properties"},{"self":"<Base URL>/rest/api/2/issue/10015/properties/sd.initial.field.set","key":"sd.initial.field.set"}]}
   

2. <Base URL>/rest/api/2/issue/10015/properties/jpo-issue-properties:
   Result

   {"key":"jpo-issue-properties","value":{"parent_id":"10013"}}
   

Notes

1. The Parent link information on the issue itself shows up fine and does not have any link to the old Parent after changing the issue type.
2. Parent Link JQL also returns the correct result.

Workaround

You can delete the Issue Property by using this REST API; DELETE /rest/api/2/issue/{issueIdOrKey}/properties/{propertyKey}.