Release vehicle confusion
Asked by Johnny Ringo:

Release Vehicles (aka as Releases or FixVersions in Jira)

* As a note: Release Vehicles are either synced with Jira or not synced at all so we can't just turn this off.
* The Planning Increment is randomly getting changed by "External System". Planning Increment is not even a field on the Jira side so why is "Release Shipped In" getting changed and then I have to change back the Planning Increment.
* If someone Releases a FixVersion or changes the dates on the Jira side - sometimes they land in Jira Align while other times they get set back to Unreleased and overwritten with the last set of dates in Jira Align. Why is the Push v. Pull at different times? How would we ever know which side is going to "win"?


Answers:
author: Jamie Giantonio
body: [@Johnny Ringo](/t5/user/viewprofilepage/user-id/5524561) there is a setting in the Admin Panel under Jira Settings, Jira Setup tab- "Update planning increment dates based on sprint or fix version dates"- is that set to Yes or No?

Setting this to no will keep the Planning Increments set on the Feature (Jira Epics) and the associated stories based on when you worked them vs Fixed Version Dates.

![2024-08-02_10-38-18.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/339715iDE0B7A6141B0D1EA/image-size/large?v=v2&px=999 "2024-08-02_10-38-18.jpg")

comments: author: Johnny Ringo
body: It was set to yes previously, but it seemed random when things were being changed. As stated

"

* If someone Releases a FixVersion or changes the dates on the Jira side - sometimes they land in Jira Align while other times they get set back to Unreleased and overwritten with the last set of dates in Jira Align. Why is the Push v. Pull at different times? How would we ever know which side is going to "win"?"

can you provide any assistance with this please?


author: Jamie Giantonio
body: [@Johnny Ringo](/t5/user/viewprofilepage/user-id/5524561) it's hard to answer that question without being able to look at the change logs for the work items.

There is a help page that goes a little deeper into release vehicle updates that might shed some light: <https://help.jiraalign.com/hc/en-us/articles/115000088393-Jira-data-synchronization>

If that doesn't help, if you can find an example and expand on it, providing what action was taken in Jira and what the audit log in jira Align shows, we can try and dig in deeper.


author: Mayer Marni
body: We are having the same exact problem and have not been able to find any resolution!

We have many examples and the steps are typically as follows:

1. We create a Release Vehicle in Jira Align and select the Jira Project for the sync to push it to Jira.

2. During that creation we select the Planning Increment.

3. Randomly, the Planning Increment gets updated exactly as described above.

4. We manually fix it on the Align side since this field does not exist nor is part of any field mapping.

5. Then it randomly gets updated again and so on.

We see this happening in the Audit Log but it is a bit difficult to share as the naming is some confidential information.

Please note that in instances where this is happening we do not yet have any Jira Epics or Stories that would have the wrong PI causing a conflict. We solely have Planning Increments \& Release Vehicles with only Release Vehicles syncing from Jira Align to Jira Software.


Tags: cloud