Issue Summary

When removing the Feature from a Story in JA does nothing for the sync in Jira and it eventually will be reverted in JA

This is reproducible on Data Center: yes

Steps to Reproduce

1. In given story in Jira Align that is synced to Jira, update the Story to remove the parent feature.
2. Wait for the sync, it will not sync.
3. Remove the Program Increment from the Story
4. Wait for the sync, it will not sync.
5. Add a tag in the Story
6. The sync will happen but Jira will revert the Feature and Program increment changes.

Expected Results

When removing the Feature from the Story in JA it should be synced over to Jira and not be reverted in JA when any other update is made in the Story

Actual Results

Issue is reproed both locally using a Jira Server and on Cloud, and on the Server, what we can see is that the flow for the sync goes as:

• When a Feature is created, JA sends a POST to create it on Jira
• When the Story is created, JA sends a POST to create it on Jira
• After both exist, JA sends a PUT to update the Story and update its parenting to the Feature

Like this:

Story Creation:
0:0:0:0:0:0:0:1 o997x7616x1 diego [05/Aug/2024:16:37:38 -0300] "POST http://diegoinstance:8080/rest/api/2/issue HTTP/1.1" 201 88 0.3910 - "JiraConnector.Services/1.0.0.0 AgileCraft_Jira/11.1.1.29552 (Microsoft Windows NT 6.2.9200.0)" "qwesd2"
    	___ Request _____________________________________________________
    	Request Data (total 206 bytes) : 
    
    {
        "fields":
        {
            "project":
            {
                "key": "LAR"
            },
            "summary": "Diego Test Story with Children 2.1",
            "description": "Diego Test Story with Children 2.1",
            "issuetype":
            {
                "id": "10002"
            },
            "priority":
            {
                "id": "3"
            },
            "assignee":
            {
                "name": ""
            }
        }
    }	___ Response ____________________________________________________
    	Response Data (total 88 bytes) : 
    
    {
        "id": "18503",
        "key": "LAR-284",
        "self": "http://diegoinstance:8080/rest/api/2/issue/18503"
    }
-----
Adding Parent:
0:0:0:0:0:0:0:1 o997x7625x1 diego [05/Aug/2024:16:37:39 -0300] "PUT http://diegoinstance:8080/rest/greenhopper/1.0/epics/LAR-283/add HTTP/1.1" 204 0 0.2810 - "JiraConnector.Services/1.0.0.0 AgileCraft_Jira/11.1.1.29552 (Microsoft Windows NT 6.2.9200.0)" "1xhpy3q"
    	___ Request _____________________________________________________
    	Request Data (total 45 bytes) : 
    
    {
        "ignoreEpics": true,
        "issueKeys":
        [
            "LAR-284"
        ]
    }	___ Response ____________________________________________________
    	Response Data (0 bytes).

So when the parenting is removed, we would expect to see a similar update to remove the parenting on the Story, but this is not happening, even when we force a new update on the Story (like changing the description), where we are going to see the update on the Story but the parent is kept.

If we look at the Jira Setup help, we can see that the configuration that controls it is:

Feature custom field on stories. The key for the Jira field is used for storing the epic link or
epic ID link when you assign a story to an epic. This will sync with the Feature name field on stories in Jira Align. Use the format: customfield_10001.

And the Data Sync, shows that Parent of Stories should sync in both ways:

Although, this is not a regression, because when testing it on v10.133, the behavior was the same, so this problem is lingered on JA for a while (the closest mention seen about this was on v10.132, with a not so similar bug JIRAALIGN-5944).

Workaround

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