Issue Summary

While creating scoped access using API scopes or a service account, we can choose classic/granular scopes. 

While all the Jira cloud classic scopes are available, all classic scopes related to JSM, as mentioned in JSM-specific Classic scopes  are missing. 

We will have to go through 100s of granular scopes to find JSM-specific granular scopes or asset related scopes

Steps to Reproduce

1. Try creating a service account credential or an API token with scopes. 
2. While searching for App scope, only Jira Confluence and Atlassian is listed. 
   
3. If we select Jira, only Jira classic scopes are visible: 
   

Expected Results

• JSM classic scopes should be visible. 
• We should be able to filter scopes based on product (App) for JSM and Assets. 

Actual Results

There is no product differentiation, and classic scopes are missing. We need to search through all granular scopes to create a service account for JSM use. 

Workaround

Currently there is no known workaround for this behaviour. Customer will have to add related Granular scopes one by one. With a limit of 50 scopes customer will run out of scopes for a single API token.