Brett E. Meyer created CAMEL-7792:
-------------------------------------
Summary: JIRA component
Key: CAMEL-7792
URL: https://issues.apache.org/jira/browse/CAMEL-7792
Project: Camel
Issue Type: New Feature
Reporter: Brett E. Meyer
For Overlord (http://projectoverlord.io), 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:
https://github.com/brmeyer/camel-jira
Consumer ideas:
github://newIssue (new tickets)
github://newComment (new comments on tickets)
Producer ideas:
github://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
(https://marketplace.atlassian.com/plugins/com.atlassian.jira.jira-rest-java-client),
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
(v6.3.4#6332)
