Hey everyone, I’m trying to set up an automation in JIRA. The goal is to create a new folder in SharePoint whenever a certain issue type is made in a specific project. I’ve got a script that’s supposed to do this, but I’m having trouble with the authentication part. It’s not letting me access the SharePoint API.
Here’s what I’ve done so far:
Made a listener script that checks if the right issue type is created in the right project.
Wrote some code to handle the SharePoint folder creation.
The code uses Java to send a POST request to SharePoint. It’s supposed to create a new folder at a given path. But when I run it, it’s not working. I think the problem is with the authentication, but I’m not sure.
Has anyone done something like this before? Any tips on how to get the authentication working? Or maybe there’s a better way to do this whole thing?
I’d recommend exploring Power Automate (formerly Microsoft Flow) for this task. It’s designed specifically for these kinds of workflows and integrates seamlessly with both Jira and SharePoint. You can set up a trigger for when a specific issue type is created in Jira, then use the SharePoint connector to create the folder. This approach eliminates the need for custom coding and complex authentication processes. It’s more maintainable in the long run and allows for easier modifications if your requirements change. Just ensure you have the necessary licenses and permissions set up in both systems.
hey emmad, i’ve done something similar before. instead of using java, try microsoft graph api. it’s easier to authenticate and works great with sharepoint. you’ll need to set up an azure app registration first, then use the client credentials flow. lemme know if u need more help!
I’ve tackled a similar challenge in my organization by using a no-code integration platform like Zapier. In my case, it simplified the whole process, primarily because it handles the authentication issues with SharePoint automatically. I set up a trigger in Zapier for when new Jira issues of the specific type appear, and then configured Zapier to create the folder in SharePoint accordingly. An important aspect was ensuring consistent naming, perhaps by incorporating the Jira issue key, which allowed for easier tracking and management. This approach has proven both flexible and reliable.