We have various Jira instances - production, staging, UAT. They all have different base urls. And also different header colors to make it easy to tell them apart. Making changes in a prod Jira when you thought it was staging is not good.

As I was using the Jira Server mobile app I realized that the only way you can tell which Jira instance you are connected to is to look at the Settings gear, where the Admin, Settings, Title is shown. The problem with this is that we don't change that title in our different Jira instances because doing that can break Application Links, and the title isn't really shown anywhere in the UI.

So at the moment it's easy to make a change in a Jira instance without knowing which one you are connected to.

My suggestion is to add some way to tell mobile users when they look at an issue that they are not connected to their production Jira. Production Jira issues should not look any different

One way to do this would be to have a custom renderer that adds a prefix to the content of some field saying "Non Prod" based on checking the base url. But that's pretty specific to each customer.

If there were a setting in Jira admin properties that by default says the Jira is production, and then admins change that setting in non-prod instances, then the mobile app could use this info to change something about how the issue appears.