camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <>
Subject [jira] [Commented] (CAMEL-7792) JIRA component
Date Mon, 22 Sep 2014 08:16:34 GMT


Willem Jiang commented on CAMEL-7792:

Applied the patch into camel master branch with thanks to Brett. We need update the wiki page
and add some unit tests.

> JIRA component
> --------------
>                 Key: CAMEL-7792
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Brett E. Meyer
>            Assignee: Willem Jiang
>             Fix For: 2.15.0
> For Overlord (, we need to consume "events" from JIRA, as well
as produce "actions". We're moving towards using Camel as a backbone for various capabilities,
and as such are writing the endpoint functionality as new Camel components. I'd love to see
this incorporated as another mainline Camel component.
> Work in progress:
> Consumer ideas:
> jira://newIssue (new tickets)
> jira://newComment (new comments on tickets)
> Producer ideas:
> jira://newComment (add comment to a ticket)
> Obviously, that's only a small portion of the capabilities. The JIRA API is extensive
and opens a large variety of possibilities.
> It uses the Atlassian's jira-rest-java-client SDK (,
released under an Apache V2 license.
> Similar to what I did for camel-twitter, the Exchange payloads would be the SDK-provided
objects themselves (Issue, Comment, etc.)

This message was sent by Atlassian JIRA

View raw message