Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

  •  
     
    story #6277 have a query parameter on trackers/id/artifacts
Summary
Empty
have a query parameter on trackers/id/artifacts
Empty

New route parameter

/v1/trackers/{id}/artifacts?query  GET

 The "query" parameter will be a URL-encoded JSON object. E.g.

{"field1_id" : "field1_value", "field2_id" : {"operator" : "OR", "value" : ["v1", "v2"]}, "field3_id" : {"operator" : "<", "value" : "field3_value"}}

 

field_id can be either the ID of the field or the shortname of the field. In the event that the shortname is a number, e.g. 123, then Tuleap will search for field with ID 123 THEN field with shortname 123 if not found.


There are two ways of specifying the field value:

  • by providing a direct value; the operator is then assumed to be "="
  • by providing an object. That object must provide the properties "value" and "operator"

The value formats are all those that are used with fields

There is also a "values" parameter as for /tracker_reports/:id route

Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#6277
dylan bowden (dylan)
2014-03-28 10:28
2014-02-21 14:09
6497

References

Follow-ups

User avatar
dylan bowden (dylan)2014-03-28 10:28
Integrated in Tuleap 6.11.99.41

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Status changed from On going to Done
  • Category set to
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Permissions set to