Uploaded image for project: 'Atlassian Marketplace'
  1. Atlassian Marketplace
  2. MP-88

Separate license base for Addons / Allow admin to limit add-on licenses to specific users

    • 645
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update - June 2023

      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.

            [MP-88] Separate license base for Addons / Allow admin to limit add-on licenses to specific users

            Pinned comments

            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.

            Harsh Dhaka added a 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.

            All comments

            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!!!!

            Jason Armistead added a comment - 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!!!!

            Om Joshi added a comment -

            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.

            Om Joshi added a comment - 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.

            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.

            Hien Thanh Ho added a comment - 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.

            Om Joshi added a comment -

            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.

            Om Joshi added a comment - 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.

            Jörg added a comment -

            Really Important Request!

            I can just agree with all the statement mentioned here. In our company the software developers would be the smallest group. But if we need a plugin for the SW development we need to buy it for the whole company Program Management, Project Management, Finance...

            This seems not to make sense for me.

            Jörg added a comment - Really Important Request! I can just agree with all the statement mentioned here. In our company the software developers would be the smallest group. But if we need a plugin for the SW development we need to buy it for the whole company Program Management, Project Management, Finance... This seems not to make sense for me.

            @Pooja Kapoor, is Zephyr Scale specifically limiting the number of users? 

            Atlassian itself enforces the restriction for Atlassian Marketplace apps to follow the Jira user tier. The Zephyr Scale app vendor doesn't control this. 

            Henri Seymour {Easy Agile} added a comment - @Pooja Kapoor, is Zephyr Scale specifically limiting the number of users?  Atlassian itself enforces the restriction for Atlassian Marketplace apps to follow the Jira user tier. The Zephyr Scale app vendor doesn't control this. 

            Could we ask Zephyr Scale's justification for not being able to limit the number of users? There should be a real reason for not being able to prioritize this ask(about 800 votes for this ticket already).

            Pooja Kapoor added a comment - Could we ask Zephyr Scale's justification for not being able to limit the number of users? There should be a real reason for not being able to prioritize this ask(about 800 votes for this ticket already).

            This is very much required. The push should also come from the Market Place companies. The model should work in everyone's benefit rather than one entity benefitting out of it.  

            Tushar Pant added a comment - This is very much required. The push should also come from the Market Place companies. The model should work in everyone's benefit rather than one entity benefitting out of it.  

            Let's all be realistic here.  A lot of us our software developers and we know how this game works.  If Atlassian had started off with the more preferred plugin model everyone would be happy and this wouldn't be a thing.  Unfortunately Atlassian now likely receives a large % of their profits from this business model and are likely risk adverse to try a different model that would make their customers happy.  There is a chance that people would be more likely to use plugins and Atlassian would recoup its lost income.  There is an equal likely chance that Atlassian would lose a ton of money.  So until there is a competitor that does this sort of thing better we are all for better or for worse stuck in this model.  This same thing applies to other features that should really part of the basics: Centralized project management. combined roadmps, product versions for multiple projects without having to switch to the extremely expensive premium version.  Without any real competition Atlassian does not really have to do what it's users want.

            Dan Cumings added a comment - Let's all be realistic here.  A lot of us our software developers and we know how this game works.  If Atlassian had started off with the more preferred plugin model everyone would be happy and this wouldn't be a thing.  Unfortunately Atlassian now likely receives a large % of their profits from this business model and are likely risk adverse to try a different model that would make their customers happy.  There is a chance that people would be more likely to use plugins and Atlassian would recoup its lost income.  There is an equal likely chance that Atlassian would lose a ton of money.  So until there is a competitor that does this sort of thing better we are all for better or for worse stuck in this model.  This same thing applies to other features that should really part of the basics: Centralized project management. combined roadmps, product versions for multiple projects without having to switch to the extremely expensive premium version.  Without any real competition Atlassian does not really have to do what it's users want.

            Santosh Kumar Devata added a comment - - edited

            Yes, we are badly looking forward for this.
            I have a plugin which costed 9K Dollars earlier when I'm in Server mode, but the same plugin with DC Mode costs me 25K Dollars, which is crazy.

             

            So, I would like to have a lesser licensing option to purchase add-ons.

            It will greatly benefit the customers and also the add-on vendors as people tend to try and buy more if such policy is approved by Atlassian. 
            Sad, to see it is not even assigned!

            Infact, we are all landlocked by Atlassian I can say.

             

            There were 1000s of customers reporting and voting for it ( multiple duplicated tickets were tagged to this ticket ), but not even a single one stays assigned, ill !

            Santosh Kumar Devata added a comment - - edited Yes, we are badly looking forward for this. I have a plugin which costed 9K Dollars earlier when I'm in Server mode, but the same plugin with DC Mode costs me 25K Dollars, which is crazy.   So, I would like to have a lesser licensing option to purchase add-ons. It will greatly benefit the customers and also the add-on vendors as people tend to try and buy more if such policy is approved by Atlassian.  Sad, to see it is not even assigned! Infact, we are all landlocked by Atlassian I can say.   There were 1000s of customers reporting and voting for it ( multiple duplicated tickets were tagged to this ticket ), but not even a single one stays assigned, ill !

              e6a780dea54b Harsh Dhaka
              e73eec3ea617 Thomas Liechti
              Votes:
              844 Vote for this issue
              Watchers:
              413 Start watching this issue

                Created:
                Updated: