Consent screen buggy with Jira and JSM scopes

Forge Forge Modules and Product Triggers
, ,
1

Hello there,

so we are having a Jira Software Forge app and recently added a feature for Jira Service Management.
We had to add some JSM scopes and everything worked fine…

…as long as the instance has the product JSM. If the app is installed in a Jira Software only instance, the user consent can’t be given (at all).

image
image1357×619 40.8 KB

Is there any workaround for this? To me it seems like a bug…

Thanks in advance,
paul

EDIT: I found an issue [FRGE-1193] - Ecosystem Jira

1 Like
2

As this is not possible at the moment, we end up adding a second app, which adds the functionality (and scopes) for JSM. You might have a look at it: Awesome custom fields for JSM | Atlassian Marketplace

1 Like