Improve journal rendering and journal-oriented issue inspection

[aarondpn]

Problem

The CLI already includes journals on issue fetch, but the presentation is shallow. It prints notes and largely ignores structured journal detail changes, which makes issue history less useful than it could be.

Requested change

• Improve journal rendering so field changes are shown, not just free-text notes.
• Consider a dedicated history-focused output mode for issue inspection.
• Preserve machine-readable output for scripting.

Why this matters

The basic journal workflow already exists, so this is incremental rather than foundational.

Reference

• https://www.redmine.org/projects/redmine/wiki/Rest_IssueJournals

[Bodge-IT]

Looks like I arrived at the right time...just looking into how I can leverage issue info(inc. comments) and meta to further enhance solution knowledgebase. Trying to tag a comment that contains the solution to an issue. mechanism available to me is a thumbsup(like) mechanism. not sure if that's core Redmine or arrives as part of my helpdesk integration. Would your new enhancement be able to include that sort of meta on comments? And comments with closing commits?

[aarondpn]

Looks like I arrived at the right time...just looking into how I can leverage issue info(inc. comments) and meta to further enhance solution knowledgebase. Trying to tag a comment that contains the solution to an issue. mechanism available to me is a thumbsup(like) mechanism. not sure if that's core Redmine or arrives as part of my helpdesk integration. Would your new enhancement be able to include that sort of meta on comments? And comments with closing commits?

The thumbs up feature is unfortunately not available via the REST API. It seems they have deliberately decided against including it: https://www.redmine.org/issues/42630#note-10

The reactions should also be included in the API responses for issues, messages, ..., possibly behind an include flag

I suggest we leave it out of the scope of this patch for now and only consider it when there is a concrete proposal or demand for API integration, including discussions around the API specification. The reasons are:
We need to discuss both the necessity and the design of API support.
Keeping the scope of this patch minimal will help facilitate focused discussions and reviews.

Regarding your question about closing commits, this may already work. Do you see anything in the journals?

redmine issues get <closed-ticket-id> --include journals -o json

[Bodge-IT]

Thanks for such quick response. The response on that API request looks good enough. we can virtualise meta status with injected keywords as opposed to 'like' mechanism for "comment contains solution" or similar.