Project

General

Profile

Actions

task #7269

closed

Use redmine as message hub for submitter curator communication

Added by Andreas Kohlbecker almost 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
New
Category:
cdm-vaadin
Target version:
Start date:
Due date:
% Done:

50%

Estimated time:
(Total: 0:00 h)
Severity:
normal
Tags:

Description

The Redmine issue system will be used to establish asynchronous communication between curator and submitters, which are also referred to as contributors.

Setup

Backups of the initial Redmine setup are found in Y:/GRUPPEN/BDI/Algenregistrierung/Registrierungs-Redmine

Workflow

  • All messages are stored in redmine.
  • For each registration entity an issue is created in redmine, when ever a message needs to be passed to submitter or curator
    • The User for the contributor is being created as long as it does not exist in redmine.
      • Email-Notification in user account settings:
        • Curator: mail_notification: all
        • Submitter: mail_notification: only_my_events
  • A comment to the issue will be created for each message, the user which is sending the message will become watcher of the issue.
  • The user to which the message is dedicated to will be set as Assignee and the priority is set to active
  • Once the Submitter has taken action in response of the message send by the curator, the issue should be returned to the curator by adding a comment, setting the curator as assignee.
  • The status of the issue is synchronized with the Registration.status
    • Setting the status to ready, published, or rejected will set the issue priority to inactive
  • Submitter and Contributor will become watchers of the issue so that both can receive email notifications when a new message is posted.

Message indicators in the registration UI:

The message indicator shows a new message when priority_id > 1 :

  • Submitter: Submitter_id == Assignee_id && priority_id > 1
  • Curator: `Submitter_id != Assignee_id && priority_id > 1'

Redmine REST api

Redmine has a REST api for basic CRUD operations (https://www.redmine.org/projects/redmine/wiki/Rest_api).

  • Authentication can be done using an API-key passed in as a "X-Redmine-API-Key" HTTP header (added in Redmine 1.1.0)
    • The API key is provided per user and can be retrieved from the "My account" page: ./my/account
    • All operations can be done by an admin user on behalf of an ordinary user by using the HTTP header (X-Redmine-Switch-User: jsmith). This only works when using the API with an administrator account!

Redmine Java API library is a FREE third-party Java library that can be used to access the Redmine API. It is released under Apache 2 open-source license. (support until Redmine 2.6.0 using REST API), see https://www.redmine.org/projects/redmine/wiki/Rest_api_with_java

<dependency>
    <groupId>com.taskadapter</groupId>
    <artifactId>redmine-java-api</artifactId>
    <version>3.1.0</version>
</dependency>

For our purpose the Issue and User services are relevant:

Users

  • Create a user: POST /users.json
{
    "user": {
        "login": "jplang",
        "firstname": "Jean-Philippe",
        "lastname": "Lang",
        "mail": "jp_lang@yahoo.fr",
        "password": "secret",
        "mail_notification": "only_my_events|all" 
    }
}

Issues, Issue Journals

  • Create an issue: POST /issues.json
{
  "issue": {
    "project_id": 1,
    "tracker_id": 1,
    "subject": "Registration: ${Registration.identifier}",
    "description": "",
    "priority_id": 1,
    "custom_fields": 
       [ 
          {"value":${Registration.identifier},"id":1},
          {"value":${Submitter_id},"id":2}
       ]
    "assigned_to_id": {user_id},
    "watcher_user_ids": [1,2,3] /* Array of user ids to add as watchers */
  }
}
  • Add comment: PUT /issues/[id].json
{
    "issue": {
        "notes": "Fixed in Revision 128" 
    }
}
  • Change custom field Unread: PUT /issues/[id].json
{
  "issue": 
  {
    "custom_fields":
      [
        {"value":"1","id":4} /* 1 for true or 0 for false */
      ]
  }
}
  • Find an issue by registrationId: GET /issues.json?cf_1=${Registration.identifier}
    • here cf_1 refers to the custom field with id=1, which is the Identifier field
    • Does the find also support journals or id a second request needed? /issues/[id].json?include=journals

Ids in redmine.phycobank.org

  • Project id = phycobank-registry
  • Tracker registration = 1
  • Custom field ids:
    • Identifier = 1
    • Submitter = 2
    • Curator = 3
    • Unread = 4 will be handled via the priority field
  • Issue statuses:
    • preparation = 1
    • curation = 2
    • ready = 3
    • published = 4
    • rejected = 5
  • Issue priorities:
    • inactive = 1
    • active = 2

Configure Workflow like:

Implementation requirements:

Settings:

  • adminUserApiKey
  • redmineURL
  • projectId

Test system for integration testing:

Configuration details of the redmine-registration-messages integration test system are documented in the subtask

Additional TODOs:

  • extract interface for service
  • issues must be private
  • issues must only be visible to the submitter and curator = watchers

Files

picture68-1.png (45.5 KB) picture68-1.png Andreas Kohlbecker, 02/19/2018 10:18 PM

Subtasks


Related issues

Related to EDIT - feature request #7270: Registration message controller implementedRejectedAndreas Kohlbecker

Actions
Related to EDIT - task #7315: remove workaround RedmineTransportAccessorRejectedAndreas Kohlbecker

Actions
Related to EDIT - task #7935: Discuss new solution to establish the communication between submitter and curator ClosedAndreas Kohlbecker

Actions
Related to EDIT - bug #7936: Consider complete removal of redmine communication hub code ClosedAndreas Kohlbecker

Actions
Related to EDIT - bug #8069: RegistrationUI: remove all messaging related code and message indicators from all viewsClosedAndreas Kohlbecker

Actions
Copied from PhycoBank - feature request #6868: Manage annotations and all Submitter-Curator communication in Ticktsystem (redmine) DuplicateAndreas Kohlbecker

Actions
Actions #1

Updated by Andreas Kohlbecker almost 5 years ago

  • Tags set to phycobank
  • Category set to cdm-vaadin
  • Assignee set to Andreas Kohlbecker
  • Priority changed from New to Highest
Actions #2

Updated by Andreas Kohlbecker almost 5 years ago

  • Target version deleted (Unassigned CDM tickets)
Actions #3

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #4

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #5

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #6

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #7

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #8

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #9

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #10

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #11

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #12

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #13

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #14

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #15

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #16

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #17

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #18

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #19

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #20

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • % Done changed from 0 to 10
Actions #21

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #22

Updated by Andreas Kohlbecker almost 5 years ago

Actions #23

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
  • % Done changed from 10 to 30
Actions #24

Updated by Andreas Kohlbecker almost 5 years ago

  • File picture626-1.png added
  • Description updated (diff)
Actions #25

Updated by Andreas Kohlbecker almost 5 years ago

Actions #26

Updated by Andreas Kohlbecker almost 5 years ago

  • File deleted (picture626-1.png)
Actions #27

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #28

Updated by Andreas Kohlbecker almost 5 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 100 to 50
Actions #29

Updated by Andreas Kohlbecker almost 5 years ago

Additional TODOs:

  • extract interface for service
  • issues must be private
  • issues must only be visible to the submitter and curator = watchers
Actions #30

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
  • Status changed from Resolved to In Progress
Actions #32

Updated by Andreas Kohlbecker almost 5 years ago

  • Related to task #7315: remove workaround RedmineTransportAccessor added
Actions #33

Updated by Andreas Kohlbecker almost 5 years ago

  • Status changed from In Progress to Resolved
Actions #34

Updated by Patrick Plitzner almost 5 years ago

  • % Done changed from 100 to 50
Actions #35

Updated by Andreas Kohlbecker almost 5 years ago

  • Target version set to Release 5.0
Actions #36

Updated by Andreas Kohlbecker over 4 years ago

  • Copied from feature request #6868: Manage annotations and all Submitter-Curator communication in Ticktsystem (redmine) added
Actions #37

Updated by Andreas Kohlbecker about 4 years ago

  • Related to task #7935: Discuss new solution to establish the communication between submitter and curator added
Actions #38

Updated by Andreas Kohlbecker about 4 years ago

  • Related to bug #7936: Consider complete removal of redmine communication hub code added
Actions #39

Updated by Andreas Kohlbecker about 4 years ago

  • Related to bug #8069: RegistrationUI: remove all messaging related code and message indicators from all views added
Actions #40

Updated by Andreas Kohlbecker over 3 years ago

  • Status changed from Resolved to Rejected
Actions #41

Updated by Andreas Kohlbecker over 3 years ago

  • Status changed from Rejected to Closed

even if it has been completely implemented this feature has been rejected afterwards

Actions

Also available in: Atom PDF