We are using Jira Assets via mobile browser (Edge) as it is company managed, however when we try to update our status fields, it doesn’t appear to save. Jira Cloud app is not approved; however, web access on mobile is with our current tenant configuration. All other fields are saving as expected. Is it a browser issue or a defect within Atlassian?
1) Are you stating that you can use Edge on mobile fine with fields updates for Jira Assets objects without any issue - but cannot update the "Status" field?
2) Are you able to update the "Status" using non-mobile devices (i.e. your laptop etc..)?
Verify your permissions: Confirm that your user account has the necessary Jira admin or Object Schema Manager permissions to modify object statuses within Assets.
Clear browser cache and cookies: Access Edge's settings and clear your browsing data, including cached images and files, and cookies.
Disable browser extensions: Try disabling all browser extensions in Edge and then test the functionality. If it works, re-enable extensions one by one to identify the problematic one.
Try a different mobile browser: Test if you can modify the object status using a different mobile browser (e.g., Chrome or Safari on iOS). If it works, it may indicate a specific compatibility issue with Edge on your device.
Check for known issues: Review Atlassian's documentation and community forums for any known issues related to using Assets on Edge, especially on mobile devices.
Report the issue to Atlassian Support: If the problem persists after trying the above steps, consider contacting Atlassian Support for further assistance. Provide them with details about your device, Edge version, and the specific steps you are taking when trying to change the object status.
It is my recommendation that you should contact Atlassian Support (https://support.atlassian.com) to obtain their support on Edge app via mobile device problem.
Hope this helps.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is like a rendering or compatibility issue with how Edge handles that specific field — worth testing in Chrome mobile 7 Brew menu 2025 or checking if there's a known bug in Atlassian’s mobile web handling for Assets.
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.