Not able to create a issue with issue type=Task

[Priyanka Soni]

We are using Jira cloud and we use an integration app to create jira issues.

I am able to create issues with issue type=Bug and New feature.

But when ever we try to create a issue with issue type=Task, the application throws below error:

17:02:51.793 [http-nio-8090-exec-10] DEBUG com.infosynergi.infolinkintegration.service.impl.JIRAServiceImpl - exception ::RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={issuetype=The issue type selected is invalid.}, errorMessages=[]}]}
17:02:51.793 [http-nio-8090-exec-10] DEBUG com.infosynergi.infolinkintegration.service.impl.JIRAServiceImpl - Error Message :: java.util.concurrent.ExecutionException:
RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={issuetype=The issue type selected is invalid.}, errorMessages=[]}]}

I re-verified the mappings and confirmed that mapping for issue type=Task is there in the code. So, I suspect it is not a code issue. 

However, I am able to create able to create a jira issue with issue type=Task from the jira web application page.

Is this a know issue? Are we missing some configuration in the jira web application? 

[Brant Schroeder · Accepted solution]

@Priyanka Soni Welcome to the Atlassian community

The issue type task needs to be part of the issue scheme in the project that you are trying to create the new issue.  Can you confirm that it is part of the issues scheme in the project?

[Priyanka Soni]

Thanks for the response.  I verified that issue type='Task' is a part of the: Issue Type Scheme which we migrated from JIRA Server 2 months back. This scheme is being used for all our  projects on JIRA cloud. And this is here:

[Brant Schroeder]

@Priyanka Soni I am assuming that this occurs in all projects when trying to create a task.  Do you have any other schemes that were not migrated?  Do you have project that was only created in cloud?  Can you create a task in that project?

If you can create a task in the cloud project I would suggest creating a new issue type scheme with the issue the same as above and applying it to the project in question to see if this resolves the issue.  It might be something is corrupt from the migration.  If that does not resolve the issue you will need to contact support.