Feature #14872: Activities REST API - Redmine

Actions

Copy link

Feature #14872

open

Activities REST API

Added by Terence Mill over 11 years ago. Updated about 7 years ago.

Status:

New

Priority:

Normal

Assignee:

Category:

REST API

Target version:

Start date:

Due date:

% Done:

Estimated time:

Resolution:

Description

Allow creating activities with

event type
image (same domain/relative url of existing images)
topic + hyperlink for topic
descripton
author is taken based on user context of rest authorisation

via REST API.

This api would allow light integration of other system actions notification in redmine project activity stream, e.g.
events like

build failed
build sucess
build fixed
application updated/insatlled/deployed on environment
new build source code analysis results

The event type will be availabe on the right side context menu as new checkbox selectable for event type filter. checkbox list must be rendered dynamically based on the existing types found for the showed time range.

Related issues

Actions

Copy link

Updated by Toshi MARUYAMA almost 9 years ago

Has duplicate Feature #22109: REST API to get a list of the activites added

Actions

Copy link

Updated by Toshi MARUYAMA almost 9 years ago

Related to Feature #10402: get server activity through REST API added

Actions

Copy link

Updated by Vanessa Martinez over 8 years ago

Are there any news regarding this topic?

Actions

Copy link

Updated by Chris Burgess about 8 years ago

Redmine already uses the term "Activities" to refer to any existing Redmine entity that is updated within a certain date range (eg the view at http://www.redmine.org/projects/redmine/activity is composed of Issues, Wiki updates, News etc).

AFAIK this is not a stored entity though, and that view is most likely composed of queries against API for each entity. So can we expose that over REST? We could expose a view of it, but there's nothing to store to unless this ticket also adds a "Notification" entity (or similar name) which you may store simple events to.

I propose that this ticket be modified to focus on creating such an entity (could be done in extension) and that #10402 pursue exposing the existing Activity view via API for read only.

I'm not conviced that #22109 duplicated this ticket, but maybe it duplicates #10402. If you agree, please consider renaming this ticket so it does not appear to be a dupe of #10402 (perhaps "Simple notifications entity" or "events" or whatever name sounds good and is not a duplicated term.)

Actions

Copy link