Feature #10171
Updating journal notes via REST API
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Go MAEDA | % Done: | 0% | |
| Category: | REST API | |||
| Target version: | 5.0.0 | |||
| Resolution: | Fixed |
Description
Currently viewing journals via REST API is possible (with include=journals), but there is no way to update them.
Note that journal notes are edtiable in main ui.
add_put_journal_api.patch 
(3.96 KB)
Related issues
Associated revisions
Add support for PUT API to journals (#10171).
Patch by Mizuki ISHIKAWA .
History
#1
Updated by Taha Jahangir about 10 years ago
Is there any plan to fix this issue?
#2
Updated by Grigory Kirichenko about 8 years ago
It seems that we not only can't edit notes via REST API.
See http://www.redmine.org/boards/1/topics/16513?r=29807
We also can't ADD notes to issue through REST API.
Please write here if something changed.
#3
Updated by Kamil Franckiewicz almost 8 years ago
I would like to enjoy to this feature. Will it be possible in the future ? I found also similar issue Journals in REST API
#4
Updated by Toshi MARUYAMA almost 8 years ago
- Related to Feature #8630: Journals in REST API added
#5
Updated by Go MAEDA almost 4 years ago
- Duplicated by Feature #27870: API for editing/deleting notes in an issue added
#6
Updated by Brian Bouterse about 2 years ago
Without this feature, there is no way to clean spam from Redmine websites in an automated way. This is a serious problem for our usage of Remdine.
#7
Updated by Mizuki ISHIKAWA 3 months ago
- File add_put_journal_api.patch added
This patch adds a PUT update API for journal.
This API has the following functions similar to those available from the page:- Of the journal values, you can only update notes.
- When the notes of the journal that does not have the associated journal_details are changed to empty, the journal record is deleted.
Example:
curl -X PUT -d '{"journal": { "notes": "new notes" }}' -H "Content-Type: application/json" http://localhost:3000/journals/1.json?key=<api key>