This removes a tedious friction point, as manually searching for the correct SharePoint folder on each issue wastes hours for teams. Binding the folder at the project and work item level is a sensible default.
For those considering whether to build or buy, the basic approach is to add the folder as a Smart Link or web link on the issue, then use automation on issue creation to attach a templated folder URL as a remote link. This handles straightforward situations. The managed files panel, along with issue browsing and permission-aware embedding, are where a dedicated connector provides significant value.
Klaida, at what level does Auto-Connect bind the folder, project plus type only, or can it point at a per-issue folder, and how does it handle portal visibility in JSM projects?
Thank you for your questions.
Auto-Connect is primarily designed to bind SharePoint folders based on the project and issue type configuration. This allows teams to automatically connect issues with the correct SharePoint location without manually searching for folders.
Regarding visibility, it follows Jira and SharePoint permission settings, ensuring that users only have access to the files and folders they are authorized to view.
The key value of the connector compared to a simple link-based approach is the deeper SharePoint integration, including file management, browsing, and permission-aware access within Jira.
If you are interested in learning more, feel free to book a call with me. I would be happy to show you how the SharePoint Connector for Jira works and discuss the best approach for your specific requirements.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.