Field changed trigger in the Jira Advanced Roadmaps 'Team' yields inconsistent results

Issue Summary

When creating a rule that is triggered by the Fields changed trigger while looking for changes in the 'Team' Portfolio field, we are getting inconsistent results depending on how the action is executed.
Rule example:

When changing the Team associated with the issue, we are able to capture the old and new team names with the fieldChange smart value(both within Advanced Roadmaps plan and on the issue edit page).

When creating a new issue form within the Advance Roadmap plan and associating a team name at the same time, we are also able to capture the team name.

However, when creating an issue from the default create an issue page and also selecting a Team value, instead of capturing the name of the team, we are capturing the ID of the team.

Important note, at all times the value that is stored in the JSON of the issue seems to be the team ID, when searching for the backend information we do not see any mentions to the Team name.

Smart value utilized:

{{fields.Team}}

{{fieldChange.fromString}}

{{fieldChange.toString}}

Steps to Reproduce

Steps to reproduce in the Advanced Roadmaps side:

1. Go to the Portfolio plan.
2. Click on Create issue and input the summary.
3. Select the Team.
4. Click on Review changes.
5. Keep everything checked and hit Save selected changes in Jira.

Steps to reproduce in the Jira side:

1. Have the Team field showing up on the create an issue screen.
2. Have a shared team created in Advanced Roadmaps.
3. Hit create issue, and while creating the issue select a team value.

Expected Results

Get the team name regardless of how the filed was filled.

Actual Results

The results depend on how the field was filled.

Workaround

To be able to capture the Team name it is necessary to first create the issue then edit it, or create it with the associated team from within an Advance Roadmap plan.