Project

General

Profile

Actions
Copy link

Feature #31559

closed

Support "active" attribute in Enumerations REST API

Added by Michel Albert almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Go MAEDA
Category:
REST API
Target version:
4.1.0
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

Expected behaviour

When doing a HTTP request to /enumerations/time_entry_activities.json it should only return activities marked as "active"

Observed behaviour

  • All activities are returned
  • Additionally, the returned values don't contain the values for the "active" field, so filtering on the client-side after fetching is not possible either.

Additional notes

  • This was observed on Redmine 3.3.2
  • I also came across #8573 which notes something similar, but not for the API.

Files

31559.patch (2.5 KB) 31559.patch Go MAEDA, 2019-06-29 11:15
Actions
Copy link
 #1

Updated by Go MAEDA almost 5 years ago

Michel Albert wrote:

Expected behaviour

When doing a HTTP request to /enumerations/time_entry_activities.json it should only return activities marked as "active"

I think it is better to add "active" field to the response instead of omitting inactive enumerations. What do you think?

Actions
Copy link
 #2

Updated by Michel Albert almost 5 years ago

Yes. That would work perfectly as well.

Actions
Copy link
 #3

Updated by Go MAEDA almost 5 years ago

  • File 31559.patch 31559.patch added
  • Tracker changed from Defect to Feature
  • Subject changed from The API on enumerations returns inactive entries as well to Support "active" attribute in Enumerations REST API
  • Target version set to 4.1.0

Here is a patch to add "active" attribute to Enumerations API.

Actions
Copy link
 #4

Updated by Go MAEDA almost 5 years ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the patch.

Actions
Copy link

Also available in: Atom PDF