-
Suggestion
-
Resolution: Unresolved
-
645
-
Copied from this comment.
This is not currently on our public roadmap but we understand some customers have a need for greater purchasing flexibility and our desire is to make it as frictionless as possible for our customers to purchase Marketplace apps as part of the complete Atlassian solution. If/when Atlassian adds changes to our license policies tying user counts of apps to the host Atlassian product, we will share more details.
Jira is famous for its great ecosystem for plugins/addons. But not every Jira user is actually using every (commercial) addon productively. So I'm willing to pay e.g 100 Jira user licenses but only want to pay 10 licenses for a commercial addon. Currently this is not possible due to the license model which counts the licensed jira users.
As an impact of that, as an administrator I'm available to choose which of the Jira users are able to use a specific addon.
- duplicates
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Future Consideration
- relates to
-
- Closed
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
-
ACE-3569 Loading...
-
- is resolved by
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[MP-88] Separate license base for Addons / Allow admin to limit add-on licenses to specific users
| Link |
New:
This issue duplicates |
| Link | New: This issue relates to CONFCLOUD-39235 [ CONFCLOUD-39235 ] |
| Description |
Original:
{panel:title=Atlassian Update - June 2023 |borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
Copied from [this comment|https://jira.atlassian.com/browse/JRACLOUD-59932?focusedId=3299880&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3299880]. This is not currently on our public roadmap but we understand some customers have a need for greater purchasing flexibility and our desire is to make it as frictionless as possible for our customers to purchase Marketplace apps as part of the complete Atlassian solution. If/when Atlassian adds changes to our license policies tying user counts of apps to the host Atlassian product, we will share more details. {panel} Jira is famous for its great ecosystem for plugins/addons. But not every Jira user is actually using every (commercial) addon productively. So I'm willing to pay e.g 100 Jira user licenses but only want to pay 10 licenses for a commercial addon. Currently this is not possible due to the license model which counts the licensed jira users. As an impact of that, as an administrator I'm available to choose which of the Jira users are able to use a specific addon. |
New:
{panel:title=Atlassian Update - June 2023 |borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
Copied from [this comment|https://jira.atlassian.com/browse/JRACLOUD-59932?focusedId=3299880&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3299880]. This is not currently on our public roadmap but we understand some customers have a need for greater purchasing flexibility and our desire is to make it as frictionless as possible for our customers to purchase Marketplace apps as part of the complete Atlassian solution. If/when Atlassian adds changes to our license policies tying user counts of apps to the host Atlassian product, we will share more details. {panel} Jira is famous for its great ecosystem for plugins/addons. But not every Jira user is actually using every (commercial) addon productively. So I'm willing to pay e.g 100 Jira user licenses but only want to pay 10 licenses for a commercial addon. Currently this is not possible due to the license model which counts the licensed jira users. As an impact of that, as an administrator I'm available to choose which of the Jira users are able to use a specific addon. |
Some companies have enterprise licensing and they are expected to pay same amount for hundreds of add-ons which only useful for specific teams and projects! Not looking to be inclusive or flexible to other vendors or their partners.
| Labels | Original: jsw-s11 | New: jsw-s11 jws24 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 944555 ] |
This request has been repeatedly made over the years, yet Atlassian consistently overlooks it and shows no willingness to explore potential solutions to address this issue.
there should be flexibility in place, by way of allowing Security groups or lower tier allowance on the application host. it should only see that is it licensed or not.
| Remote Link | Original: This issue links to "ENT-764 (Jira)" [ 877793 ] | New: This issue links to "ENT-764 (Hello Jira)" [ 877793 ] |
We have about 20 total software developers who would benefit from using a particular Marketplace App (Plugin) but around another 230 other users from other areas of the company (mostly manufacturing-related) who have no need for that app on the Jira project they work on.
So now we are going from a $60 USD per month charge for the software developers ($3 each, which is reasonable) to a $520 USD per month charge ($26 each for the software developers), which is just NOT going to happen.
This sort of nonsense drives users away from Jira entirely, and surely prevents many Jira users from wanting to engage with a Marketplace App when the per-ACTUAL-user costs are artificially driven so high because App licenses can't be individually assigned or assigned to a specific subset of users.
The only solution I can think of is to literally create separate Jira Cloud instances for the software developers and for the rest of the business, but some people will inevitably cross over both Jira instances and then we'll be paying double for the Jira license for them- AARGH !!!!
Fix this please Atlassian!!!!