Orphan Story assigned to a PI/Iteration, later moved to Team backlog on ART report. Automation?

[Razy Kased]

Is there a way to automate that the PI is also set to unassigned once an orphan story is moved to Team backlog still being reported at the ART-level as an orphan story? I included a screenshot of the view of the user story in Jira Align which shows the unassigned backlog, this was triggered by the change of the sprint in Jira from a future sprint in the same PI to none (backlog). The issue is that Jira Align doesn't update the program increment to reflect that it is no long in PI3 and as a result is reported as an orphan story. screenshots below.

[Prasanth Kumar · Accepted solution]

Hi @Razy Kased 

There is no out of the box solution for this issue:

The workaround that we can try is:

1. Create a custom field (Program Increment) in Jira for the issue types(User story & bugs)
2. Once you move a user story / bug to unassigned backlog, execute a rule to set the custom field also to unassigned backlog.
3. When the sync happens between Jira and Jira Align, the respective PI field in Jira Align will also be updated as needed.

Hope it serves your purpose?