I'm using Swagger UI in Jira Align to test this out and I am noticing these two options don't seem to work in tandem.
I am trying to use the Features GET endpoint to get a list of Features for a particular release / jira project(s), but I also want the expanded data for Program, Owner and Release.
If I leave the filter options blank in Swagger and just test it pulling the top 1-5 results it works, I get the fully expanded data JSON response.
If I then apply a filter to target a specific release (or put anything in the filter options at all) the data is still returned but not in the expanded format, effectively expand=true does not work when filter is also present.
Is this by design? Or have I stumbled across an annoying bug.
It works for me in the example below. Maybe you could post (no pun intended) the syntax you are using?
{{base_JA_url}}/Epics?EXPAND=true&$FILTER=id EQ 1414
@Allan Maxwell thanks for the reply.
In swagger UI:
{Base URL}/rest/align/api/2/Features?expand=true
This works and I can see the extra expand details.
{Base URL}/rest/align/api/2/Features?expand=true&filter=releaseId%20EQ%2021
Though this returns a response the expand detail is now omitted.
Thankfully this was enough for me to spot the issue. In Swagger UI the URL uses the format '&filter' which still works but it needs to be '&$filter' to work with the expand clause.
I've just tried this and can confirm it works.
Bit annoying that Swagger doesn't give you the output URL in that format.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same issue with Swagger that Gareth has documented above? Who owns the Swagger implementation of the "Jira Align API 2.0"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.