API 2.0 : Milestones : Making a GET call towards Milestones endpoint results in HTTP 500

Issue Summary

• Making a GET call towards the following endpoints results in HTTP 500 errors:
  • /rest/align/api/2/Milestones
  • /rest/align/api/2/Objectives

Steps to Reproduce

• Ensure there are Objectives/Milestones entries with missing data in any of its required fields:
  • e.g. Program-type (tier=2) and no programId assigned

The required fields, per tier-type, are as follows:

Tier	Objective Type	Mandatory Fields
1	Team	tier, name, description, ownerID + targetSyncSprintId, programId, releaseIds, teamIds
2	Program	tier, name, description, ownerID + programId
4	Portfolio	tier, name, description, ownerID + portfolioId
5	Solution	tier, name, description, ownerID + solutionID
6	Individual	tier, name, description, ownerID

• The instance is running Jira Align release 10.105.0 or later

1. Browse to Swagger and authorize your user as usual
2. Make a GET call towards the following endpoints:
   • /rest/align/api/2/Milestones
   • /rest/align/api/2/Objectives
3. Notice the HTTP 500 response

Expected Results

• A JSON response-body containing results as per the GET call

Actual Results

• An HTTP 500 error is thrown

Workaround

Workaround #1 – Identify & fix missing data

• In Jira Align UI, manually browse to the Milestones/Objectives grid, identify and fix work items missing required parameters.

  

Workaround #2 – Narrow down GET results

• As a means to circumvent the "defective" entries, use a filter statement along with the GET call.
  • Example by Team-type tier: e.g. GET /rest/align/api/2/Milestones?filter=tier eq 1
  • Example by specific-Program assignment: e.g. GET /rest/align/api/2/Milestones?filter=programId eq 11