Redmine - Feature #7180
List of statuses in REST API
2010-12-27 13:50 - Mark Kofman

ステータス:

Closed開始日:

2010-12-27

優先度:

High

期日:

担当者:

Jean-Philippe Lang

進捗率:50%

カテゴリ:

REST API

予定工数:0.00時間

対象バージョン:1.3.0

Resolution:

Fixed

説明
Now it is impossible to get the list of all available statuses through Rest API.
関連するチケット:
関連している Redmine - Defect #7819: REST API Populating issue ...

New

2011-03-09

関連している Redmine - Feature #7402: REST API - Enumerations

New

2011-01-21

関連している Redmine - Defect #8596: Make possible to obtain is...

Closed2011-06-13

次のチケットが重複 Redmine - Feature #7866: Get all issue statuses...

Closed2011-03-15

関係しているリビジョン
リビジョン 7878 - 2011-11-20 15:25 - Jean-Philippe Lang
Adds API response to /issue̲statuses to get the list of all available statuses (#7180).

履歴#1 - 2011-01-07 22:49 - Alex Last
- 担当者 を Jean-Philippe Lang にセット
Jean-Philippe, I hope you don't mind that I'm assigning this request to you. Maybe you could find some time to implement this in 1.1.0.
#2 - 2011-03-15 23:42 - Rodrigo Recio
I've made a pull request on edavis10's github (my github is rrecio) of a code that expose issue̲statuses through REST (I did for trackers too), cananyone do something about this?
#3 - 2011-03-26 01:59 - milki milk
I believe I have a better patch than rrecio:
https://github.com/milki/redmine/compare/master...issue-status-api
I've exposed index/show for issue-status - no longer needs admin accessindex will list all the statuses
show will allow you to retrieve one either by id or name
I've added 3 tests for each one of them.
#4 - 2011-03-26 02:30 - milki milk
milki milk wrote:
I've exposed index/show for issue-status - no longer needs admin accessI should clarify this. Index is only exposed via api for everyone. Only admin can access the web interface still.
Show only exposes an api interface since its not useful otherwise.
#5 - 2011-04-15 21:10 - milki milk
I submitted a pull request:
https://github.com/edavis10/redmine/pull/31

2024-10-11

1/3

#6 - 2011-04-29 02:40 - Ewan Makepeace+1This is a bit of a showstopper for my friend's iPhone App RedminPro: http://itunes.apple.com/us/app/redminepro/id415596033?mt=8I can use it to reject my developers work, but as soon as I find an issue that is completed I am stuck - he is only able to populate the status menu
with options seen in the list of issues I pull - and since I only get open issues, he never sees a Closed status, and so it is not on the menu...
Clearly populating menus with the values seen in a small sample of records is no way to be writing a UI but until REST provides enumeration ofStatus (and other fields) all developers of plugins and desktop software will be similarly stuck.
Related: #7402, #7506, #7819#7 - 2011-04-30 23:35 - milki milk
I guess this should be moved to patches instead of feature. Maybe patches are actually seen by developers? Is it stands, the assignee seems too busy
or doesn't care about the REST API.
#8 - 2011-06-16 07:16 - Bevan Rudge- 進捗率 を 0 から 50 に変更
This is related or duplicate of #4968 and/or #7402.
It would be great to get this or one of those reviewed and committed.
#9 - 2011-06-16 07:19 - Bevan RudgeI meant #7819, not #7402.
#10 - 2011-07-21 23:48 - Jean-Philippe Lang
Ewan Makepeace wrote:
Clearly populating menus with the values seen in a small sample of records is no way to be writing a UI but until REST provides enumerationof Status (and other fields) all developers of plugins and desktop software will be similarly stuck.

Populating the menu with all existing statuses that /issue̲statues would return is (maybe slightly better but) not the right solution. All statuses are
not applicable to all issues.
I think the API should offer a way to retrieve the statuses that a particular issue can be changed to by the user. Something like /issues/:id/edit thatwould return an xml/json representation of possible statuses and all other properties that can be changed (assignee, priority...).
#11 - 2011-07-21 23:52 - Jean-Philippe Lang
Or maybe a way to include optionnaly all this information in the response to /issues/:id.
#12 - 2011-07-22 01:13 - Alex Lastin some cases I need to retrieve "*what are the available statuses for this issue*",but sometimes I need to get "*what are all possible statuses in this project*" - that is if I'm building a search form for issues in some application...
#13 - 2011-08-29 10:09 - Etienne Massip- 優先度 を Normal から High に変更- 対象バージョン を Candidate for next major release にセット
REST-blocking for instances which don't set a default Status.
#14 - 2011-11-14 02:42 - Rodrigo Recio
Why don't you just create a json/xml response for a path like this projects/:project̲name/issues/new.json so its response is all current project
available trackers and statuses?
#15 - 2011-11-20 15:29 - Jean-Philippe Lang- ステータス を New から Closed に変更- 対象バージョン を Candidate for next major release から 1.3.0 に変更- Resolution を Fixed にセット

2024-10-11

2/3

The list of all statuses is now available, see r7878.
Rodrigo Recio wrote:
Why don't you just create a json/xml response for a path like this projects/:project̲name/issues/new.json so its response is all current project
available trackers and statuses?

Similar to my proposal in note-10. Could you try to design this response so we can get some feedback?

2024-10-11

3/3