How to Automate SharePoint Folders and Attachments in Jira Using Native Automation

[#1]

If your team stores project files in SharePoint and manages work in Jira, there's a good chance two things happen every time a new issue is created: someone manually creates a SharePoint folder for it, and someone else eventually attaches a file directly to the Jira ticket instead of putting it in SharePoint.

Both are small friction points. But they compound. The first means your SharePoint folder structure is only as consistent as people's memory. The second means files end up scattered, some in SharePoint, some in Jira attachments, some in both. Over time, nobody knows where to look, version control becomes a headache, and SharePoint permissions lose their meaning for anything that ended up in Jira instead.

Research from McKinsey estimates that automating repetitive tasks saves knowledge workers an average of 3.6 hours per week, and folder creation and file routing are precisely the kind of tasks that should never require human intervention.

SharePoint Connector Automation for Jira by ikuTeam now integrates directly with Jira's native automation engine, giving you custom actions you can drop into any automation rule, with full access to smart values, any workflow trigger, and all the conditions and branching Jira automation supports. No separate configuration panel, no parallel automation system to learn. Just SharePoint actions that live right alongside everything else you already automate in Jira.

---

The Custom Actions Available

Once SharePoint Connector for Jira is installed, these actions appear inside Jira Automation under Other apps:

• Create folder - creates a new folder in SharePoint inside a parent location you define, with a name you control using smart values. Outputs the new folder ID so it can be passed directly into the next action in the same rule.

• Connect a folder - attaches any SharePoint folder (including one just created in the previous step) to the current Jira issue as an internal team folder, making it visible in the connector panel on the issue.

• Connect a customer folder - same as above, but attaches the folder as a customer-facing folder for Jira Service Management projects, where request participants also need access.

• Connect folder to space - attaches a SharePoint folder at the Jira project space level, so it appears in the sidebar for all issues in that project rather than on a single issue.

• Upload all attachments to folder - takes all files currently attached to a Jira issue and uploads them to a target SharePoint folder, then removes them from Jira's native attachment storage. Keeps issues clean and SharePoint as the single source of truth.

These actions can be combined freely in a single rule, chained with any of Jira's built-in actions, and triggered by anything Jira automation supports, issue created, status changed, field updated, scheduled, manually triggered, and more.

---

Jira Automation Examples: 2 Real-World Use Cases

Use Case 1: Auto-Create and Attach a SharePoint Folder on Issue Creation

What it does:

Every time a new issue is created, a dedicated SharePoint folder is created inside a pre-defined parent location, named exactly the way you want, and immediately attached to the issue, without anyone doing anything manually.

How to build the rule

1. Go to Space Settings → Automation → Create flow

2. Set the trigger: work item created
   
   

3. Add the action: Create folder

   • Select the SharePoint parent folder where new issue folders should be created

   • Set the folder name using a smart value, e.g. {{issue.key}} or {{issue.key}} - {{issue.summary}}

   • The action outputs the newly created folder ID for use in the next step
     

4. Add the action: Connect a folder

   • Use the folder output from the previous step as the input
     

5. Save and enable the rule
   

Every new issue in the project now gets a consistently named, correctly placed SharePoint folder, attached automatically, and visible immediately in the work item panel.

Why is this powerful?

With Jira native automation:

Smart values give you full naming control. Use any Jira field: {{issue.summary}}, {{issue.assignee.displayName}}, {{project.name}} , or any combination that matches your SharePoint naming conventions.

Any trigger works. Only need a folder when a ticket moves to In Progress? When a specific label is added? When a custom field is set? Set the trigger accordingly.

Conditions scope it precisely. Add a condition: issue type is Epic, priority is High, label contains "client-project", so the automation only fires for issues that actually warrant a dedicated SharePoint folder.

Chain with anything else. Send a Slack notification, assign the issue, update a custom field, and create the SharePoint folder, all in the same rule, in one pass.

Customer-facing JSM variant. For service management projects, swap Connect a folder for Connect a customer folder to give request participants direct access to the folder created for their request.

---

Use Case 2: Auto-Upload Jira Attachments to SharePoint and Keep Jira Clean

The problem this solves

Even with folder automation running, teammates still attach files directly to Jira issues by habit. The attachment button is always there. The result: files split across Jira and SharePoint, no reliable way to know which copy is current, and SharePoint permissions applying to only part of the picture.

How the action works

Upload all attachments to folder Upload all attachments to folder takes every file attached to a Jira issue and uploads them to a target SharePoint folder, then deletes them from Jira's native attachment storage. Files land in SharePoint, version-controlled, permission-governed, auditable, and the Jira issue stays clean.

The key is targeting the right folder per work tiem/issue. Rather than uploading everything to a single fixed folder, you configure the action using a smart value to find the folder by name. For example, you can configure it to target the folder whose name contains {{issue.key}} , so attachments from PROJ-142 always go into the PROJ-142 folder that was created when the issue was opened.

How to build the rule 

1. Go to Space Settings → Automation → Create Flow
   
   
   

2. Set the condition: Work item attachments (exists)
   
   
   

3. Add the action Upload all attachments to folder

   • Select the SharePoint parent location to search within

   • Define the smart value to find the correct target folder, e.g. folder name containing {{issue.key}} 
     
     

4.  Save and enable the rule
   
   
   

Any file attached to an issue is immediately routed to the right SharePoint folder and removed from Jira, automatically, every time, with no manual step from whoever attached it.

---

Putting It All Together: Full Lifecycle in Two Rules

For teams that want a completely hands-off setup from issue creation through to ongoing file management, here's what two rules together look like:

Rule 1: On issue created:

1. Trigger: Issue created

2. Action: Create folder → named {{issue.key}} - {{issue.summary}} inside your project's SharePoint library

3. Action: Connect a folder → attach the folder just created to the issue

Rule 2: On attachment added:

1. Trigger: Attachment added to issue

2. Action: Upload all attachments to folder → target the folder whose name contains {{issue.key}}

With these two rules active, the full lifecycle is covered without anyone thinking about it: the SharePoint folder exists the moment the issue is created, and any file that lands on the issue as a Jira attachment is immediately moved to the right folder in SharePoint and cleaned up from Jira.

---

What the End State Looks Like

• Every new Jira issue has a SharePoint folder, named consistently, placed correctly, linked immediately

• Jira's attachment storage stays empty, files are routed to SharePoint in real time as soon as they're added

• SharePoint is the single source of truth: one place to look, with the correct permissions applied, and a clean audit trail

• All automation rules live in Jira's native automation interface, alongside your other rules, visible to anyone who manages automations on the project

A team of 100 creating 500 issues a month, spending just 2 minutes each on manual folder creation, recovers close to 16 hours of collective time per month (yes, 2 full days) from folder automation alone, before counting the time saved by never hunting for files split across Jira and SharePoint.

---

Try It Free

All automation actions are included in SharePoint Connector Automation for Jira, available on the Atlassian Marketplace with a free trial.

Are you already using Jira Automation for other workflows in your projects? What triggers are you finding most useful? Drop a comment, always good to compare setups. 👇