Feature #34040
open
Include all notes in issue list csv
Added by Mizuki ISHIKAWA over 3 years ago. Updated over 1 year ago.
0%
Description
Currently, only the latest note can be output as CSV, but I think that many people need all the notes.
Plugins for that are also being developed. https://github.com/suer/redmine_export_with_journals
Files
| draft.patch (6.75 KB) draft.patch | Mizuki ISHIKAWA, 2021-09-02 07:21 | ||
| screenshot.2021-09-02-13.59.56.png (77.4 KB) screenshot.2021-09-02-13.59.56.png | Mizuki ISHIKAWA, 2021-09-02 07:21 | ||
| feature-34040.patch (11.7 KB) feature-34040.patch | Mizuki ISHIKAWA, 2022-02-15 08:09 | ||
| sample-issues.csv (1.13 KB) sample-issues.csv | Mizuki ISHIKAWA, 2022-02-15 09:04 | ||
| feature-34040-v2.patch (11.3 KB) feature-34040-v2.patch | Go MAEDA, 2022-08-02 11:45 |
Updated by Mizuki ISHIKAWA over 3 years ago
In order to implement this feature, we need to think about how to include notes in CSV.
My idea:| # | Tracker | Status | Priority | Subject | Assignee | Updated | Note-# | Notes |
|---|---|---|---|---|---|---|---|---|
| 3 | Bug | New | Normal | Private issue on public project | 09/08/2020 01:40 PM | |||
| 3 | 1 | test1 | ||||||
| 3 | 2 | test2 | ||||||
| 3 | 3 | * test3 * test4 |
||||||
| 2 | Bug | New | Low | Subproject issue two | 09/01/2020 11:27 AM | |||
| 1 | Bug | New | Low | Cannot print recipes | User name | 09/02/2020 11:27 AM | ||
| 1 | 1 | The quick brown fox jumps over the lazy dog | ||||||
| 1 | 2 | Some notes with Redmine links: #2, r2. |
I've added a column called Note- # to make note sorting work.
For a issue with the same id: 3, there are 4 lines with 1 line of ticket information + 3 lines of notes.
Updated by Go MAEDA over 3 years ago
Mizuki ISHIKAWA wrote:
In order to implement this feature, we need to think about how to include notes in CSV.
My idea:
# Tracker Status Priority Subject Assignee Updated Note-# Notes 3 Bug New Normal Private issue on public project 09/08/2020 01:40 PM 3 1 test1
I think an additional column that represents the user who wrote the note (stored as journals.user_id) is necessary.
Updated by Go MAEDA over 3 years ago
Go MAEDA wrote:
I think an additional column that represents the user who wrote the note (stored as
journals.user_id) is necessary.
And it is better to have journals.created_on and journals.private_notes.
Updated by Mizuki ISHIKAWA over 2 years ago
- File draft.patch draft.patch added
- File screenshot.2021-09-02-13.59.56.png screenshot.2021-09-02-13.59.56.png added
I have created a draft patch for people to try out this feature. I have not written any tests.
If you output CSV from issues list and check "All notes" checkbox, notes related information will be added to CSV.
"All notes" checkbox is available only for CSV output.
Feedback is very welcome!
Updated by Mizuki ISHIKAWA about 2 years ago
- File feature-34040.patch feature-34040.patch added
I'm attaching a patch that improves draft.patch.
Once this feature is implemented, it will be possible to easily retrieve note information without using the API.
Updated by Mizuki ISHIKAWA about 2 years ago
- File sample-issues.csv sample-issues.csv added
I attached is a sample csv that outputs the issues and journal notes created by rake db:fixtures.
Updated by Go MAEDA about 2 years ago
- Target version set to Candidate for next major release
Updated by Go MAEDA over 1 year ago
- File feature-34040-v2.patch feature-34040-v2.patch added
Updated the patch for the current trunk (r21752).