Android Jira app is using a completely different field scheme

[inspirednz]

This question is very similar to https://community.atlassian.com/t5/Jira-questions/Fields-in-the-mobile-are-not-ordered-by-scheme-settings/qaq-p/1306250

Although it differs in a significant way.

When I use the desktop browser interface, and I click the blue CREATE button, I am presented with a form for creating an issue. As per the above mentioned post the scheme is not in the same order. I see a feature request has been lodge with regards to that.

But in my case here is the problem:

On the browser one of the fields (right under the description field) is "Raise this request on behalf of". This is a really important field, as in our usage scenario Agents are only ever going to raise new issues on behalf of a client.

However, on the Jira App (for Android) that field does not show up.

I also notice the Assignee doesn't have it's default setting on the App. On our set up we have all tickets automatically assigned to one Agent. This occurs on the user portal, and on the browser desktop when an Agent creates a new issue the default selection is "Automatic" (which means they automatically get assigned as per what we configured it to do). But on the Android App the default Assignee is not selected. That field is blank. I think it should mimic what occurs on the web interface. Namely, it should have "Automatic" selected by default.

I also notice that the "Issue Type" selector on the App has a different range of options  than those I set up and see on the "Type" selector on a browser. On the App I don't see the issue types we use in our company. Obviously it's important I can select from the issues our organisation use configured for Jira to use.

Based on there response I saw on the above mentioned ticket, there is no way to customise the fields, etc., for the Jira App. Is that still true? If it is true, then it seems to me there's a few things that haven't been sufficiently thought through and implemented on the mobile App (at least on Android; I can't comment on iOS).

I would suggest that either we have the ability to configure the App field scheme (independent from the other schemes) and / or it at least take on the scheme set up for the same action (e.g., create a new ticket/issue as an Agent) on the rest of Jira (e.g., on the browser version of Jira).

Regards,

Jonathan

[inspirednz]

Regarding this:

I also notice that the "Issue Type" selector on the App has a different range of options  than those I set up and see on the "Type" selector on a browser. On the App I don't see the issue types we use in our company. Obviously it's important I can select from the issues our organisation use configured for Jira to use.

I can now see this was occurring because the only project available on the app was "Default Service Desk" (or something to that effect). After playing around with the Project selector it's now showing me the correct and only project that should be on there (the project we set up for our purposes). So now the Issue Type selector has the correct options.

I have no idea why it was showing show default project, as they have all be deactivated on the web dashboard.