Issue Summary

Team field value for a subtask is getting stored in the “entity_property” table.

Steps to Reproduce

1. Create a Story
2. Create a Sub-task under a Story
3. Set Team "Alpha" on the Story - You can do this from the Advanced Roadmap plan with Issue source as the project where the story is created:
   
   
4. The Sub-task now gets the Team value from the Story
5. Change issuetype of Sub-task to Task, no Team configured - You can use More-> Convert to issue option
6. Set Team to Beta on Task - This can again be done from the Advanced Roadmap Plan
7. Change issuetype of Task back to Sub-task - Use More-> Convert to sub-task option
8. Team value should be empty
9. Link Sub-task back to Story
10. Team value in Sub-task should be Alpha again
11. Remove the Team value from the Parent
    
12. Run the below SQL in sequence in Jira DB:

    select * from jiraissue order by created desc
    
    select * from entity_property
    where entity_id ='id value from 1st sql result'
    and property_key='jpo-issue-properties'
    
    select * from "AO_82B313_TEAM"
    

Expected Results

For correct data management, the Team value should be wiped in the “entity_property” table when an issue gets converted to a Sub-task.

Actual Results

• The Sub-task still gets found in a query stating Team is empty:
  
• Team value is not wiped in the “entity_property” table when an issue gets converted to a Sub-task:
  

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available.