send issue updates to a Microsoft Sharepoint List

[Christian Schneider]

Hi,

we are a small IT-Team using Jira Service Desk for our first level support. In the future, we would like manage our open incidentes and planed maintenance downtime in a Jira project. Then, we would like to mirror these issues to a sharepoint list in our intranet.

I was wondering, if I coud use Scriptrunner for this?

Microsoft Sharepoint offers a Rest-API, Scriptrunner should be able to send the rest statements to sharepoint.

Is there anybody having done this? 

Or is there a best practice on who to publish e.g. maintenance work to customers?

Any ideas are very much appreciated.

[Christian Schneider · Accepted solution]

It took me a couple of hours/nights: I wrote a little groovy script, which puts changes of issues into a sharepoint list.

for better reference:

Solved: NTLM Authentication in groovy (Scriptrunner -> Sha... (atlassian.com)

Scriptrunner listener: get current issue data (atlassian.com)

[Will C]

I think you could get this to work by posting to the Sharepoint list rest api however I'm always against duplicating this, what is the business need for wanting to duplicate the issues in both places?

[Christian Schneider]

Hi Will C,

thank you for your reply. Do you know, how to address the Sharepoint list rest api? I would be very much interested in an example, which was done in scriptrunner or groovy.

Business need:

Our customers do not work with Jira and do not have a jira-licence. There prefered tool is the intranet, which is based on Sharepoint. We, as an IT-Team, want to be more transparent and inform our customers more active about planed downtime (e.g. due to maintenance work) or unplaned downtime in case of major incidents. They should have kind of a portal where they could see the health state of their applications. The beauty of a sharepoint list is, that you can have an email, whenever there is an update on that list. Our customers could decide themselfs, if they would like to get the email or if it is sufficient to have a look on the list, if something is not working.

[Christian Schneider]

Do you have a better solution? How do you keep your customers up to date? (Email is not an option :-))

[Will C]

Every place I have worked with Jira have had their customers directly in Jira, but sounds as though yours are not.

I would start here https://library.adaptavist.com/entity/using-external-apis-in-sr

as that will show you how to do external rest calls through scriptrunner, you would need to do this on the creating issues but also on editing them and any transitions etc so that the Sharepoint list is reflective of the issue in Jira.

I hope that helps to get you started.

[Christian Schneider]

Every place I have worked with Jira have had their customers directly in Jira, but sounds as though yours are not.

Well, I could set up another service desk project, so that customers have access on these issues. but then, who do you publish them to all customers? Create a confluence page with an overview of all open issues and then publish this link within our intranet?

The Scriptrunner side of things are more or less understood, where I am struggling, is the sharepoint API.