Redmine

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.

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

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?