Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-36830

Decouple JIRA license model from plugin license model

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None

    • 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.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      We are using JIRA in a small team of 10 people and plan on expanding it company-wide (500 users license).

      Additionally a small fraction of people is using plugins like FOLIO and TEMPO, but we are unlikely to want to pay for all our 500 users for these plugins because only approximately 20 users will in fact be allowed to use these plugins. Most of our users are developers which do not benefit from the functionality of these plugins.

      A possible fix would be decoupling the JIRA license from individual plugin licenses via user groups. We are already using these groups to control access to said plugins, so it seems to be strange to pay for 500 plugin users although only 20 users are in the plugin access group.

            [JRACLOUD-36830] Decouple JIRA license model from plugin license model

            Jessica Heffler added a comment -

            I'll add my voice to that. Maybe 1/4 of our users would need certain plugins, but I can't justify the difference in the pricing for 4 users vs 25 to myself, much less the purchasing department. We'll be sticking with an outside tool, even if it's a little wonky and doesn't talk to Jira quite as nicely as we would like.

            Jessica Heffler added a comment - I'll add my voice to that. Maybe 1/4 of our users would need certain plugins, but I can't justify the difference in the pricing for 4 users vs 25 to myself, much less the purchasing department. We'll be sticking with an outside tool, even if it's a little wonky and doesn't talk to Jira quite as nicely as we would like.

            Dieter Greiner added a comment -

            i just can agree with denis.koelewijn
            In the end this policy punishes the vendor of extremely specialized plugins.

            Dieter Greiner added a comment - i just can agree with denis.koelewijn In the end this policy punishes the vendor of extremely specialized plugins.

            Denis Koelewijn added a comment - - edited

            The current licensing model prevents us from buying plugins. We pay for 250 users on a private server. We want to start using Agile User Story Map, but only for 2 or 3 projects. Paying $600 for 25 users or $4000 for 250 users is a steep difference. Especially is only 10-20 people are actually using the plugin.

            So the only logic step that we can do is using an external (free) story mapping tool online. I would prefer an tool integrated in Jira, but not for this price.

            Denis Koelewijn added a comment - - edited The current licensing model prevents us from buying plugins. We pay for 250 users on a private server. We want to start using Agile User Story Map , but only for 2 or 3 projects. Paying $600 for 25 users or $4000 for 250 users is a steep difference. Especially is only 10-20 people are actually using the plugin. So the only logic step that we can do is using an external (free) story mapping tool online. I would prefer an tool integrated in Jira, but not for this price.

              Unassigned Unassigned
              3e6f753144cb Sebastian Rollwage
              Votes:
              29 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: