Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    MP-88Separate license base for Addons / Allow admin to limit add-on licenses to specific users
  2. Suggestion
    MP-74Show user responsible for action on Add-on Audit Log
  3. Suggestion
    MP-345Need information about open quotes for a given license/customer
  4. Suggestion
    MP-291Enhancement Request for PDF Download and Page Persistence in Pricing Calculator
  5. Suggestion
    MP-290Marketplace App shown across products in calculator
  6. Suggestion
    MP-185Enable the "Uninstall" button no matter if it's under subscription or not
  7. Suggestion
    MP-407Option to display custom environment names for Github-Jira integration
  8. Suggestion
    MP-112Atlassian Assist for Jira Software and Work Management Projects
  9. Suggestion
    MP-354To be able to write release notes if a new version is automatically released
  10. Suggestion
    MP-395Ability to remove app suggestion from Navigation bar>Apps
  11. Suggestion
    MP-405Partners should be able to identify dummy refunds.
  12. Suggestion
    MP-401Enable Seamless Navigation Between Images in Highlights and Media Sections
  13. Suggestion
    MP-350Add a field to identify Cloud/DC licenses related via dual licensing
  14. Suggestion
    MP-398 Improving the error message for users trying to publish an app version that already exists and is awaiting approval
  15. Suggestion
    MP-98Improve Marketplace Error Messages for App Installs
  16. Suggestion
    MP-379Improve error messaging for app installation/subscription "We ran into a little trouble. Unfortunately, we're unable to process your request. Please retry again in some time."
  17. Suggestion
    MP-253Ability to deactivate Marketplace app requests
  18. Suggestion
    MP-330Request for Re-evaluation of Version Visibility Approach on Version History Page
  19. Suggestion
    MP-343Provide sales type for manual transactions
  20. Suggestion
    MP-389Support Request for Connect Apps in GraphQL Operations
  21. Suggestion
    MP-385Have information about open quotes for a given license/customer available in the UI
  22. Suggestion
    MP-382parentProductBillingCycle improvement
  23. Suggestion
    MP-369Include Account Owner Email in Marketplace APIs or Partner Reports
  24. Suggestion
    MP-375Not able to change hero video to a banner image.
  25. Suggestion
    MP-71Restrict the ability to add apps for Administrator only
  26. Suggestion
    MP-276Trial App subscription cancellation
  27. Suggestion
    MP-371To show Manual invoice flag in transactions API
  28. Suggestion
    MP-77Support mentions in MS Teams integration
  29. Suggestion
    MP-367Partner discount amount data rounding off in Get Transaction API
  30. Suggestion
    MP-347Discount_array amounts should follow same logic as the amounts on the rest of the Transaction
  31. Suggestion
    MP-372Allow Active Installation Filtering by Hosting Type
  32. Suggestion
    MP-278It should be possible to edit the profile of the Atlassian Account of the users created for marketplace apps
  33. Suggestion
    MP-368Allow admins to limit add-on access to specific projects in Jira
  34. Suggestion
    MP-194Ability to disable app requests
  35. Suggestion
    MP-365Allow EU as a Data Residency value
  36. Suggestion
    MP-255Forge App compatibility with Bitbucket for marketplace
  37. Suggestion
    MP-363REST API to return the count of reviews of the app
  38. Suggestion
    MP-360Add app "Access Token" support for Forge apps
  39. Suggestion
    MP-289Allow partners to transfer apps across partner accounts themselves (self-serve)
  40. Suggestion
    MP-357Enhanced License Record Visibility for Marketplace Partners
  41. Suggestion
    MP-351Filters on License Report should have same functionality in all cases
  42. Suggestion
    MP-355Allow Forge app admins to publish apps
  43. Suggestion
    MP-100Add the possibility to remove popular add-ons section from the Apps menu and add a scroll bar to show more installed apps
  44. Suggestion
    MP-349Add a notification in the UPM to redirect customers where to unsubscribe or uninstall apps
  45. Suggestion
    MP-336Align Sandbox maintenanceEndDate filed with Production
  46. Suggestion
    MP-333Adding the promo code details in the Reporting API for Manual discount types also
  47. Suggestion
    MP-202Unable to edit the installation instructions for App listed on Marketplace
  48. Suggestion
    MP-322Apps should have option to receive updates manually or automatically
  49. Suggestion
    MP-314Ability to view disabled addons in the Central user management
  50. Suggestion
    MP-309Updating Vendor Profile with Diacritic Characters Causes Error
Refresh results
1 2 3 4 5Next >>
1 of 225
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

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • DO NOT USE - placeholder for items assigned to previous component structure
      • jsw-s11
      • jws24
    • 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.

        duplicates

        Suggestion - JRACLOUD-78837 Please provide the ability to restrict access to apps to a group of users

        • Closed
        is duplicated by

        Suggestion - JRACLOUD-36830 Decouple JIRA license model from plugin license model

        • Closed

        Suggestion - JRACLOUD-67551 Ability to license add-ons for a subset of jira users

        • Closed

        Suggestion - JRACLOUD-71675 Add option to manage the users that will access apps

        • Closed

        Suggestion - JRACLOUD-74298 Allow administrators to enable/disable add-ons per project level

        • Closed

        Suggestion - MP-80 Restrict access for JIRA marketplace apps to specific JIRA user groups

        • Closed

        Suggestion - MP-90 Allow admin to limit add-on licenses to specific users

        • Closed

        Suggestion - MP-122 Allow admins to grant/revoke app permissions on a per-user/per-group basis

        • Closed
        is related to

        Suggestion - JRACLOUD-73586 Paying for apps based on your JIRA licenses

        • Closed

        Suggestion - JRASERVER-59932 Separate license base for Addons

        • Future Consideration
        relates to

        Suggestion - CONFSERVER-52322 Allow for smaller plugin license based on usage

        • Closed

        Suggestion - MP-80 Restrict access for JIRA marketplace apps to specific JIRA user groups

        • Closed

        Suggestion - MP-122 Allow admins to grant/revoke app permissions on a per-user/per-group basis

        • Closed

        Suggestion - CONFCLOUD-39235 Ability to Restrict Add-ons/Macros to Groups/Users in Confluence

        • Gathering Interest

        Suggestion - JRACLOUD-75009 Ability to hide third-party app fields

        • Gathering Interest

        Suggestion - JSWSERVER-25308 Detach Portfolio license model from default user tier license model

        • Gathering Interest

        ACE-3569 Loading...

        ACE-3570 Loading...

        is resolved by

        ENT-764 Loading...

        mentioned in

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        (3 is duplicated by, 2 is related to, 8 relates to, 1 is resolved by, 14 mentioned in)

              • All
              • Comments
              • Work Log
              • History
              • Activity
              Pinned comments

              Pinned by Eduardo Santos

              Harsh Dhaka added a comment - 09/Jun/2023 5:19 AM

              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 - 09/Jun/2023 5:19 AM 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

              Jörg Döpfert added a comment - 46 minutes ago

              Please fix this, it is a real blocker for us

              Jörg Döpfert added a comment - 46 minutes ago Please fix this, it is a real blocker for us

              Omar Vargas added a comment - 28/May/2025 2:40 PM

              https://getsupport.atlassian.com/browse/JST-1143344

              Omar Vargas added a comment - 28/May/2025 2:40 PM https://getsupport.atlassian.com/browse/JST-1143344

              Jason Armistead added a comment - 02/Jan/2025 2:06 PM

              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 - 02/Jan/2025 2:06 PM 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 - 25/Sep/2024 7:01 AM

              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 - 25/Sep/2024 7:01 AM 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.

              Hien Thanh Ho added a comment - 03/Jun/2024 4:43 PM

              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 - 03/Jun/2024 4:43 PM 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 - 31/May/2024 7:52 AM

              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 - 31/May/2024 7:52 AM 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 - 27/Mar/2024 4:11 PM

              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 - 27/Mar/2024 4:11 PM 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.

              Henri Seymour {Easy Agile} added a comment - 27/Mar/2024 3:09 AM

              @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 - 27/Mar/2024 3:09 AM @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. 

              Pooja D Kapoor added a comment - 27/Mar/2024 1:08 AM

              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 D Kapoor added a comment - 27/Mar/2024 1:08 AM 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).

              Tushar Pant added a comment - 21/Feb/2024 8:40 AM

              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 - 21/Feb/2024 8:40 AM 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.  

                e6a780dea54b Harsh Dhaka
                e73eec3ea617 Thomas Liechti
                Votes:
                857 Vote for this issue
                Watchers:
                425 Start watching this issue

                  Created:
                  23/Feb/2016 11:03 AM
                  Updated:
                  46 minutes ago
                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian