Loading Profile...
Performance/Filtering of /api/projects/{project_id}/issues
Right now /api/projects/{project_id}/issues is our only entry point to get ALL the issues for a project. For big projects with many issues it'd be really great if we could add a filter too like say /api/projects/{project_id}/issues?closed=false&resolved={resolutionid}&assignedto={userid}
What would really help to speed this call up is if we were able to send ?lastmodified={date} which only returns issues modified after that date and <issue /> also returning <modifieddate />. The combination of id/modifieddate would allow me to cache known issues.
What would really help to speed this call up is if we were able to send ?lastmodified={date} which only returns issues modified after that date and <issue /> also returning <modifieddate />. The combination of id/modifieddate would allow me to cache known issues.
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?fixx 1.9 comes with the ability to run filters on /api/issues like you would on the normal /issues URL through the browser.
So you could do stuff like,
/api/issues?qStatus=closed&qResolution={resolutionid}&qAssignedTo={userid}
Unfortunately, the filter currently does not support filtering on last modified (or updatedOn) but I'll log this as a feature.
The company says
this answers the question
EMPLOYEE
