We have created a simple stream integration with Github, and we have a stream integration with Jira that is based on StreamOnce.
Overall the process of creating a simple stream integration is really.... simple
Do you have any specific questions?
Basically I'm looking for a way to display results from Jira filters in Jive (for a starter). Most of the documentation I found was about Appfusion but since its not supported anymore I would like to try making an add-on. But since I'm Jive 8 "on premise" and dont have access to Stream Once, I was wondering what my option where.
Also, seeing that Simple Stream Integration was coming to Jive 9, I was wondering if that would make it easyer for us.
Anyway, any information or exemple on how to build this type of add on would be welcome!
1 person found this helpful
Depending on the user experience, you might be able to do this via a simple stream integration, but this sounds more like a standard App to me.
See Common Jive Add-On Use-Case Patterns wrt to Apps w/Jive Connects.
You'll create an app, perhaps use the Apps Canvas (available from Apps Menu in Jive toolbar) or Place Tab on a given set of Spaces.
Once the app is created, you'll need to establish a means for Jive to connect to JIRA. This is where Jive connects comes into play. Create an App in JIRA to get clientId/secret credentials for Jive to connect to JIRA. Use that information when setting up Jive Connects to establish the profile.
Connect your Jive Connects profile to your app via the app.xml (see: Jive Connects API - Client Application Configuration and API Usage) and then you can setup your app to call the JIRA services through the OSAPI broker Making REST API calls directly from a Jive app or tile and Jive Connects. This will protect/encrypt the user's OAuth tokens and allow you to call ANY JIRA API the user is authorized to call.
Once you have the results, you simply output them to the UI.
There's a lot of simple steps but together they can be a bit hard to follow. Happy to answer any questions you might have along the way, but hope that helps.
Thanks Ryan for the information. I'll look into it to see if this fits our needs and our model.