Your organisation requires your device to run on at least Android 13 to use Jira.

[Dave L_]

Why have I started getting this message when I open the Jira app on Android 12?

Your organisation requires your device to run on at least Android 13 to use Jira.

The Jira google play listing says it requires Android 11 and up. My phone is Android 12. The same Jira version opens fine in my work profile (different email/jira instance) on the very same phone. Why does the message state it's a requirement from my organization? Are there some organization settings somewhere that can change this? I'm using a personal Jira account.

[Gor Greyan]

Hi @Dave L_

Welcome to the Atlassian Community!

This is controlled by Atlassian Access mobile app policies—admins can enforce a minimum OS version (in your example, Android 13), which overrides the app’s general requirements.

See this documentation:
https://support.atlassian.com/security-and-access-policies/docs/mobile-policy-mam-security-controls-and-supported-apps/

[Arkadiusz Wroblewski]

@Dave L_ 

@Gor Greyan 

just to add a small clarification here 

the message you’re seeing is indeed coming from an organization-level security policy, not from Jira itself.

However, this kind of minimum OS requirement is part of mobile app policies, which require Atlassian Guard Standard. It’s not something that comes from the Jira Free plan alone.

So if your site is on Free, then one of these is true:

your organization has Atlassian Guard Standard enabled

or this policy is enforced outside of Atlassian (for example via company device management)

In any case, this is not something you can change on the Jira side it has to be adjusted by your org admin / IT team.

If your phone are a Work Phone, then it would be easy to explain as most of this devices are managed.

[Dave L_]

Hi, this is my personal email, used to sign up to my personal free Jira plan. I'm not aware of any organization unless somehow Atlassian adds one to my free plan by default. I'm not signed up to any Atlassian Guard subscription.

The app on my work profile is my work email, with my work organisation. That's not signed up to Atlassian Guard either. I manage the work instance and have never set any mobile policies.

[Dave L_]

This is my personal phone. Only the work profile on my phone is managed by my work IT department. They do not manage my work Jira instance, I do.

But the problem is with my personal Jira account on my personal free Jira instance on my personal phone.

[Arkadiusz Wroblewski]

Hello @Dave L_ 

Did you Opening on the same Device also your's Work Account in app for Jira cloud?

[Arkadiusz Wroblewski]

@Dave L_ 

with the extra details you added, I would not assume this is caused by an Atlassian mobile policy.

Atlassian does support minimum OS enforcement for Jira mobile, but that is documented under Atlassian Guard Standard mobile app policies. Since your site is Jira Cloud Free and you’re saying you do not use Guard, that explanation does not really match your setup.

Also, because the same phone still works with a different Jira account/instance, this does not look like a genuine device-wide Android requirement.

At that point I’d try basic app-side cleanup first, such as signing out, clearing app data, or reinstalling the app. If it still happens, I’d raise it with Atlassian Support, because based on the details here this looks more like an app/account-specific issue than an org policy you can change yourself.

[Dave L_]

Thanks, I get this trying to sign in. I've tried a reinstall, cache clean etc with no luck. I'm on the free plan with no support so 🤷. I've just been using the website instead 

[Arkadiusz Wroblewski]

Hello @Dave L_ 

Yeah, that does sound like one possible Solution for now. Something is clearly enforcing that minimum OS version.

Another angle could be the managed work profile on the phone. On Android, a managed work profile can have minimum OS or compliance requirements pushed through Intune, so it is possible that device management is affecting what the Atlassian app is seeing. If that is the case though, it would point more to an MDM/MAM policy issue than to anything SCIM-related.

The MDM angle is interesting, because in some tenants even signing in to certain apps can trigger tenant-side policies connected to managed profiles.

Maybe a Community Champion can flag this to support, because I am genuinely curious what is causing it in your case.

I do have a couple of ideas, but I would be careful not to go too far into speculation at this point.