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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.