Issue Types and Request Types Query

[Drishti Maharaj]

Hi, this might seem like a silly question and I'm trying to figure out why Cloud would work so differently as this was not the case in Server.

If I click create on JIRA Cloud and change issue type then I see it says no request type configured and then the form does not have all my configured fields.

So I then assume each issue type would need to be created with an associated Request Type as well in Cloud?

Would that be correct?

Thanks.

[Ste Wright]

Hi @Drishti Maharaj 

Each Request Type is linked to one, specific Issue Type.

When you press "Create Issue" from within the platform, you can select a Request Type (regardless of Issue Type) by clicking on the Request Type drop-down list - but when selected, it will modify Issue Type to whatever type is associated with that request.

By default, it will then only show what fields are on the Request Type - you can change this using the toggle Use request type fields, which is located between the Request Type drop-down and the field list.

In my experience, the toggle will remain ON or OFF based on your last choice.

Ste

[Dave Mathijs]

Hi @Drishti Maharaj , only add the issue types to your issue type scheme for which you have at least one request type in your JSM project.

Tip: don't use the create button in JSM to create a ticket in your service project, use the portal just like your customers.

[Drishti Maharaj]

Hi @Dave Mathijs

Yes that is the plan to only add the issue types that we need however there are some specific to certain projects so that project for example will have 6 issue types or so. 

It's a big change in the organization to use the portal instead of clicking create but that needs to be managed for the fields to be configured correctly.

I assume then using the portal ensures the fields are configured correctly and once the ticket is logged, changing an issue type would not cause such a problem then.