Error 401 when Setting Issue Properties via Forge: Possible Restrictions on 'ari☁ecosystem::extension' Key?

Forge
, ,
1

Hello everyone,

Since it is not possible to activate issue context panels automatically, I have tried to activate them via their issue property. Using ‘ari:cloud:ecosystem::extension/id/environmentId/static/moduleKey’ as a property key, it is possible to activate an issue context of an app with an id, a timestamp and the “collapsed” attribute.

It also works well in postman. But when I try to add this property via Forge (CustomUI and Invocation), I get an error “401”. If I use a different property key for testing, the whole thing works.

Does Atlassian block the PUT endpoint of issue properties when using a key that contains “ari:cloud:ecosystem::extension”?

If not, what could be the reason?

Many thanks in advance
Regards
Adrian

2 Likes
2

Hi @AdrianSomesan! I see request URLs coming from what I believe is your app on this form:

https://api.atlassian.com/ex/jira/{cloud-id}/rest/api/3/issue/{issue-key}/properties/ari:cloud:ecosystem::extension/{appId}/{environmentId}/static/{extensionKey}

That URL isn’t recognized as matching Get issue property, so the OAuth 2.0 scope check fails. You need to percent-encode the property key path parameter.

2 Likes
3

Hi @epehrson,

thank you very much for your quick response.
Percent-encoding the property key did indeed work.
Funnily enough, I found the solution this morning and was just about to write it under this topic. So thank you very much :wink:

Regards
Adrian