Defect #28502
Support issue[assigned_to_id]=me when prefilling issues
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | 4.1.0 | |||
| Resolution: | Affected version: |
Description
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
- 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
Desired situation¶
We can use issue[assigned_to_id]=me as part of the prefilling of issues as well.
change_me_to_usable.patch 
(1.24 KB)
History
#1
Updated by Mizuki ISHIKAWA 4 months ago
- File change_me_to_usable.patch added
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”.
#3
Updated by Go MAEDA 4 months ago
- Status changed from New to Needs feedback
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 | - | - |
#5
Updated by Mizuki ISHIKAWA 3 months ago
- File change_me_to_usable_in_edit_and_update.patch added
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.
#6
Updated by Mizuki ISHIKAWA 3 months ago
I changed change_me_to_usable_in_edit_and_update.patch a bit.
#8
Updated by Go MAEDA about 1 month ago
- Target version changed from Candidate for next major release to 4.1.0