Vote #68862: List of statuses in REST API - redmineorg-copy202205 - Redmine

編集操作

リンクをコピー

Vote #68862

完了

List of statuses in REST API

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

ステータス:

Closed

優先度:

高め

担当者:

カテゴリ:

REST API_32

対象バージョン:

1.3.0_36

開始日:

2010/12/27

期日:

進捗率:

50%

予定工数:

Redmineorg_URL:

https://www.redmine.org/issues/7180

category_id:

version_id:

issue_org_id:

7180

author_id:

25727

assigned_to_id:

comments:

status_id:

tracker_id:

plus1:

affected_version:

closed_on:

affected_version_id:

ステータス-->[Closed]

引用

説明

Now it is impossible to get the list of all available statuses through Rest API.

journals

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.
--------------------------------------------------------------------------------
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), can anyone do something about this?
--------------------------------------------------------------------------------
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 access
index 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.
--------------------------------------------------------------------------------
milki milk wrote:
> I've exposed index/show for issue-status - no longer needs admin access
I 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.
--------------------------------------------------------------------------------
I submitted a pull request:

https://github.com/edavis10/redmine/pull/31
--------------------------------------------------------------------------------
+1

This is a bit of a showstopper for my friend's iPhone App RedminPro: http://itunes.apple.com/us/app/redminepro/id415596033?mt=8

I 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 of Status (and other fields) all developers of plugins and desktop software will be similarly stuck.

Related: #7402, #7506, #7819
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
This is related or duplicate of #4968 and/or #7402.

It would be great to get this or one of those reviewed and committed.
--------------------------------------------------------------------------------
I meant #7819, not #7402.
--------------------------------------------------------------------------------
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 enumeration of 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@ that would return an xml/json representation of possible statuses and all other properties that can be changed (assignee, priority...).
--------------------------------------------------------------------------------
Or maybe a way to include optionnaly all this information in the response to /issues/:id.
--------------------------------------------------------------------------------
in 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...
--------------------------------------------------------------------------------
REST-blocking for instances which don't set a default Status.
--------------------------------------------------------------------------------
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?
--------------------------------------------------------------------------------
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?
--------------------------------------------------------------------------------

related_issues

relates,New,7819,REST API Populating issue field enumerations + Issue list filters
relates,New,7402,REST API - Enumerations
relates,Closed,8596,Make possible to obtain issue_priorities and issue_statuses via RESTful WS
duplicates,Closed,7866,Get all issue statuses for project