Jira Mobile Application - Actions Tab on iOS, Missing on Android

[Kameel Naidoo]

Hi, 

Could not find anything to address this issue online. 

I just rolled out a feature that uses the Actions Tab to input a customer number and have it dial out from jira and log info into the ticket. This is working well and is fine for Desktop users 

I as the admin made a fatal flaw, while using my personal ios device saw the actions tab and was very pleased with the process and assumed that by default the mobile apps are the same thing re-packed for platform, however it would seem Android has no option for Actions

I am interested to know if this can be replicated, enabled or if anyone has a cool work-around to use. 

I currently capture 2 inputs 

Intended number to Call -
Your Extension -

This takes these variables in automations and passes them to a few subsequent API requests to initiate dialing, in my mind I can only think of rolling out 2 number fields to input this on android, and then make a dropdown to initiate it, this has drawbacks as it may need to be done a few times, so wondering if anyone got a nifty trick for this 

Thanks in Advance 

@atlassian this is a weird thing to have going on, yes I failed by not checking. But in 2024 sync dev on mobile or make it a PWA. 

[Анна]

Hey Kameel, yeah this one's annoying but it's not something you're missing on your end. The Actions tab just isn't there on Android yet, a few other people ran into the exact same thing and got confirmation from Atlassian staff that it's simply not built for that platform right now, only iOS had it and even there people said it started disappearing too at some point.

As for a workaround, the only thing I've seen mentioned is having people go through the browser version on their phone instead of the native app, since the browser experience isn't limited the same way. Not ideal if you wanted a clean native flow, but it at least keeps things working while you wait for it.

Might be worth raising it as a feature request if there isn't one already, that seems to be the only real path to getting Android support added at this point. Sorry I don't have a proper fix, just wanted to confirm you're not alone on this one.