Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redmine responder #342

merged 6 commits into from Feb 19, 2020

Redmine responder #342

merged 6 commits into from Feb 19, 2020


Copy link

@srilumpa srilumpa commented Sep 11, 2018


Here is a first draft for a responder used to create an issue in the Redmine ticketing system from a case. It will use the case title as the issue subject and the case description as the issue body. It will also use the case severity as the issue priority with the following mapping:

case issue
low low
medium normal
high high

To set it up in Cortex, you will need:

  • To define a user to allow Cortex to connect to Redmine and with access on the various project in which issues should be created
  • Define three custom fields in TheHive that will be used to select the project, the tracker and the assignee of the issue (the latest being optional) Those fields can be let free or can be custom fields with preset values

This is a minimal product (I am able to create an issue with the few parameters sent to Redmine) but here is a list on what I would keep on working to improve the responder:

  • Allow custom priority mapping
  • Allow filling Redmine custom fields
  • Push attachments of case as issue attachments
  • Set responder operation to fill a custom field with the issue id
  • Be able to call the responder from an alert or a task

@jeromeleonard jeromeleonard added this to the 2.5.0 milestone Jan 20, 2020
@jeromeleonard jeromeleonard requested review from dadokkio and garanews Feb 10, 2020
@jeromeleonard jeromeleonard changed the base branch from develop to release/2.5.0 Feb 10, 2020
@dadokkio dadokkio merged commit 688e8a4 into TheHive-Project:release/2.5.0 Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

Successfully merging this pull request may close these issues.

None yet

5 participants