Project

General

Profile

Actions

Defect #33113

closed

Default version and assignee are not exposed via projects API

Defect #33113: Default version and assignee are not exposed via projects API

Added by Anonymous over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
REST API
Target version:
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


Related issues 2 (0 open — 2 closed)

Related to Redmine - Feature #1828: Default target version for new issuesClosedJean-Philippe LangActions
Related to Redmine - Feature #482: Default assignee on each projectClosedJean-Philippe LangActions

Updated by Go MAEDA over 6 years ago Actions #1

  • 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.

Updated by Go MAEDA over 6 years ago Actions #2

  • Related to Feature #1828: Default target version for new issues added

Updated by Go MAEDA over 6 years ago Actions #3

  • Related to Feature #482: Default assignee on each project added

Updated by Marius BĂLTEANU over 6 years ago Actions #4

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" 
  }
}

Updated by Anonymous over 6 years ago Actions #5

That would be perfect for my use case

Updated by Marius BĂLTEANU over 6 years ago Actions #6

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.

Updated by Go MAEDA over 6 years ago Actions #7

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.

Updated by Go MAEDA over 6 years ago Actions #8

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

Committed the patch. Thank you.

Actions

Also available in: PDF Atom