Vote #79240
完了Support issue[assigned_to_id]=me when prefilling issues
0%
説明
h2. Current situation
This works:
- http://demo.redmine.org/issues.xml?assigned_to_id=me shows all issues assigned my account
- http://demo.redmine.org/issues/new?issue[assigned_to_id]=336461 create a new ticket, assigned to account 336461
This does not work:
- http://demo.redmine.org/issues/new?issue[assigned_to_id]=me create a new issue, assigned to my account. Note the selected assignee dropdown is empty
h2. Desired situation
We can use @issue[assigned_to_id]=me@ as part of the prefilling of issues as well.
journals
I wrote a patch that implements this feature.
This also works in the REST API:
* /issues.xml?assigned_to_id=me
I think that "me" should be available for "issues/new”.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
I think it would be even better if PUT supports 'assigned_to_id=me'. After applying the patch, GET and POST API requests support 'assigned_to_id=me' but only PUT does not.
Would you update the patch?
|_. Action |_. 3.4-stable |_. with the patch |
| GET /issues.json |=. OK |=. OK |
| POST /issues.json |=. - |=. OK |
| PUT /issue/1.json |=. - |=. - |
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Thank you for your feedback.
By adding change_me_to_usable_in_edit_and_update.patch in addition to change_me_to_usable.patch, you should be able to support to PUT actions.
--------------------------------------------------------------------------------
I changed change_me_to_usable_in_edit_and_update.patch a bit.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Committed, thanks!
--------------------------------------------------------------------------------