Why is no one looking into this?

+1 This is vital, as currently the only way to change the Request Type is manually using inline editing. We often have that turned off due to various other gaps (such as the inability to enforce Validators for simple inline edits).

We at times need to change an Issue Type after the issue is created, which causes JSD to set the Request Type to "No match". Without inline editing (which is far too deficient in capability to use in many cases) our users have no way to set Request Type back to a valid value.

This means that unless a user with inline editing enabled gets involved, customers (1) won't see the issue in the portal and (2) won't receive future notifications!

Please see this issue for more info: https://ecosystem.atlassian.net/browse/JSDECO-36

Bump! It seems like such a simple thing to fix, and possibly hugely error-prone.

It's difficult for me to understand why Atlassian is not fixing this. When users create their issues primarily via Email, and the project has several issuetypes, the use case for this should be pretty clear. In some/many cases, the Agent will need to reclassify the issue (by changing the issuetype). With the current flawed setup, the Agent always has to remember to re-assign the correct jsd request type. This is error prone and just not necessary.

This is a feature I would very much like. In theory you should be able to state that a Issue Type is linked to X Customer reference.

E.g Change and New Feature requests are different but to the customer they are just a Change.

I recently submitted a ticket on this issue as well (IS-1973). Having issues auto select their matching Service Desk Request Type upon changing of the JIRA Issue Type (if there is only one association in Service Desk) would be a small but extremely helpful improvement. I get asked for this by my help desk guys more than any other feature, so that they won't have to remember to set it!

bump.

any update?