プロジェクト

全般

プロフィール

Vote #71380

未完了

The issues API filters out closed issues by default

Admin Redmine さんがほぼ4年前に追加. ほぼ4年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
REST API_32
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
32
version_id:
0
issue_org_id:
10260
author_id:
49990
assigned_to_id:
0
comments:
2
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
41
ステータス-->[New]

説明

The @GET /issues.xml@ API only shows open issues when called without arguments.

For an API it is strange to apply such a filter by default?

I understand that the API uses the same code as the web interface for queries, but an API does not show that this default filter is on, as the web interface does.

(adding a warning/notice in the API docs would be nice too for versions where this is already the norm)


journals

Confirm that. It's still the same behaviour in 2.0.3

I need all issues regardless their Status when called without parameters for implementing in our company intranet.

--------------------------------------------------------------------------------
I was about to write "hey, this is still a problem" until I read the API notes again. To pull all types of issues, use
status_id=*

--------------------------------------------------------------------------------

Admin Redmine さんがほぼ4年前に更新

  • カテゴリREST API_32 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0