{“errorMessages”:[“Archiving issues is only available for premium editions of Jira.”],“errors”:{}}
Therefore, I upgraded my Jira subscription to “Premium” and now endpoint works properly.
However, I wonder how this will going to be handled if I use this endpoint in my Jira App. Is it going to return error if the user who installed my app is not subscribed to “Premium” plan or this error will only be displayed when I use API key authentication (e.g. I authenticated with API key for testing purposes) and for marketplace apps will work with any subscription plan?
@ibuchanan Is there a way to tell if a customer is on premium plan without attempting an operation (such as archiving)?
For example, before an app offers archiving in UI to the users (which could fail without a premium plan), it’s arguably more desirable to detect the plan a customer has and hide the archiving functionality from UI unless the customer is on premium.
The Jira REST API v3 Get License endpoint is so close to what I’m looking for but it falls just short of providing what paid plan a customer is on.
No and yes? I agree it is better to not show users options they can’t perform. I think many apps already have “tricks” for checking what they can do, even before showing the UI.
To your point about “arguably”, I’m not sure it is a good idea to force apps to know the relationship between product plans (a licensing & billing concern) and the associated features. For one, that’s likely to be a complicated map. Especially over time when features might “commoditize” and flow from Premium to Standard, or maybe even down into Free. For another, not all capabilities are gated by plan; some are gated by configuration. For example, there are some things that can only be done in a team-managed project not in a company-managed project (or vice versa).
Regardless of the possible solutions, I recommend logging a feature request so you, and others who might stumble upon this thread, would have something formal to track. Could you please open a “suggestion” (our term for feature request) issue yourself in our open Jira (JAC) in the ECO project. While I see value in a generalized solution (like plans/capabilities for all products), I recommend narrowing the suggestion to your specific need. For example, your app wants to know if Jira issue archiving is available. Once you have the issue key, please let us know here so other folks can watch, vote, and comment.