Auto-Generated Release Dates: Overlap Limitations in Jira Align 2024.1

Answer to the Core Questions

1. When does the auto‑generate feature produce overlapping releases?

• When two or more teams are assigned to the same Program Increment (PI) and Auto‑Generate is enabled for each team.
• The algorithm creates a linear, consecutive sequence of release windows per team. If the combined number of windows exceeds the PI’s total length, the algorithm re‑uses the same time slots for the next team, causing overlap.
• Deterministic condition: (teams sharing PI) AND (auto‑generate enabled) AND (total windows > PI length).

2. Does the Jira Cloud integration help reconcile or worsen overlaps?

• The integration syncs release dates only for issues linked to a single epic. If an issue belongs to multiple epics, its release date is dropped during sync, which can create gaps or duplicate windows that appear as overlaps in the UI.
• There is no built‑in conflict‑resolution mechanism in the integration; the only mitigation is to adjust the PI configuration or disable auto‑generate for the affected team.

3. How to detect a conflict via the REST API?

• The /api/releases/generate endpoint returns a plain list of windows with startDate and endDate. It does not flag conflicts.
• Programmatic detection: sort the returned windows by startDate and flag any pair where the previous window’s endDate is later than the next window’s startDate. Example pseudocode:

  windows.sort((a,b)=>a.startDate-b.startDate);
  for(let i=0;i windows[i+1].startDate){
      console.warn('Overlap detected between', windows[i], windows[i+1]);
    }
  }
  

Practical Steps for Your Environment

1. Verify the PI configuration: Check the PI’s total length (in days or sprints) and the number of release windows requested for each team.
2. Generate releases: Trigger /api/releases/generate for the PI and inspect the startDate/endDate pairs in the UI or via the API response.
3. Spot overlaps: Use the detection logic above or manually look for overlapping date ranges in the release calendar.
4. Mitigate:
   • Increase the PI’s total length or reduce the number of windows per team.
   • Disable Auto‑Generate for one or more teams and manually adjust windows.
   • Ensure issues linked to multiple epics are either re‑structured or excluded from release‑date sync to avoid gaps that look like overlaps.
5. Document the change: Update the PI plan and the team’s release strategy so that future auto‑generation will not exceed the PI capacity.

Missing Diagnostic Detail

If you are still encountering unexpected overlaps after following the steps above, please confirm the exact number of release windows configured per team for that PI. The recommendation changes if the total windows match or exceed the PI length.