Project

General

Profile

Actions
Copy link

Defect #33113

closed

Default version and assignee are not exposed via projects API

Added by Rasmus Eneman about 4 years ago. Updated about 4 years ago.

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

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

I would like either a field on project or a field the specific version but now there is no way of knowing which version id set as default on a project

Files

0001-Show-default-asignee-and-default-version-in-projects.patch (3.15 KB) 0001-Show-default-asignee-and-default-version-in-projects.patch Marius BĂLTEANU, 2020-03-14 17:25

Related issues

Related to Redmine - Feature #1828: Default target version for new issuesClosedJean-Philippe Lang2008-08-28

Actions
Related to Redmine - Feature #482: Default assignee on each projectClosedJean-Philippe Lang

Actions
Actions
Copy link
 #1

Updated by Go MAEDA about 4 years ago

  • Subject changed from Default Version is not exposed via the API to Default version and assignee are not exposed via projects API
  • Status changed from New to Confirmed

I think the default assignee should be in the API response as well.

Actions
Copy link
 #2

Updated by Go MAEDA about 4 years ago

  • Related to Feature #1828: Default target version for new issues added
Actions
Copy link
 #3

Updated by Go MAEDA about 4 years ago

  • Related to Feature #482: Default assignee on each project added
Actions
Copy link
 #4

Updated by Marius BĂLTEANU about 4 years ago

The following JSON response is enough (keys default_version and default_assignee)?

{
  "project": {
    "id": 1,
    "name": "eCookbook",
    "identifier": "ecookbook",
    "description": "Recipes management application",
    "homepage": "http://ecookbook.somenet.foo/",
    "status": 1,
    "is_public": true,
    "inherit_members": false,
    "default_version": {
      "id": 3,
      "name": "2.0" 
    },
    "default_assignee": {
      "id": 3,
      "name": "Dave Lopper" 
    },
    "custom_fields": [
      {
        "id": 3,
        "name": "Development status",
        "value": "Stable" 
      }
    ],
    "created_on": "2006-07-19T17:13:59Z",
    "updated_on": "2020-03-10T21:23:11Z" 
  }
}
Actions
Copy link
 #5

Updated by Rasmus Eneman about 4 years ago

That would be perfect for my use case

Actions
Copy link
 #6

Updated by Marius BĂLTEANU about 4 years ago

Here is the patch, I think we can deliver this fix in a minor release. If not, please move it to 4.2.0.

Test results here.

Actions
Copy link
 #7

Updated by Go MAEDA about 4 years ago

Marius BALTEANU wrote:

I think we can deliver this fix in a minor release.

I agree. The two attributes should have been added in Redmine 3.2 or 3.4. And adding attributes does not break existing API clients if those are properly implemented.

Actions
Copy link
 #8

Updated by Go MAEDA about 4 years ago

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

Committed the patch. Thank you.

Actions
Copy link

Also available in: Atom PDF