understand from ACCESS-2256 that this is expected behavior for iOS (unlike the related Android bug described in that ticket).
Our questions:
1. Is there any way to allow users to copy an issue link specifically, while keeping the broader share/save/backup restrictions in place for other actions
2. Is the feature request ACCESS-2077 (referenced in ACCESS-2256) the correct place to track progress on allowing copy link while this policy is active? What is the current status/roadmap for that request?
3. Are there any recommended workarounds (e.g. scoping the policy to a subset of users, using Jira on desktop/web instead, or an alternate in-app "share to person" method) that would let users share issue links without fully disabling this security control?
thank you!
Hi @Devika Sahadevan, no on the first one, and ACCESS-2077 is where Atlassian says so. The request is asking for exactly the split you want, in its own words: a more granular option that restricts saving and backing up to external devices or the cloud while still allowing users to copy links to issues. It also records that the copy stays blocked even when Prevent cutting or copying data from within the app is left off. So the two don't come apart.
Right ticket to watch, yes. It's a Suggestion sitting at Gathering Interest, 30 votes, 17 watchers, last touched December 2025, and that status carries no committed date.
That leaves scoping. A mobile app policy applies to all users or a subset, and a subset can only be drawn from managed accounts, external users can't be picked into one. Security, then Device security, then Mobile app policies. Web sits outside the policy either way.
https://support.atlassian.com/security-and-access-policies/docs/create-a-mobile-policy/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.