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

      JIRA today determines no of licensable users for add-ons based on total user count on the system. This is a problem especially when the add-on does not apply to some users in the system.

      e.g. We are evaluating Zephyr for JIRA and ZAPI for our test case management, and will likely not buy them since JIRA charges for all of our users. We are now forced to  buy an API license for every single user when in reality there are only 2 automated application who will talk to them.

      The funny thing is Atlassian support advised us to reduce our JIRA users to match our Zephyr users, which in reality means take 95% of our users out of JIRA

      Thanks

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

            We have the same requirement (and also stands for Confluence) : 

            • Gliffy is only used by 30 users out of 500
            • EazyBI is only used by 20 users out of 500. This one is even more strange as I have to create accounts in the plugin itself. So the members of EazyBI are clearly identified
            • Salesforce & JIRA cloud is used only by the members of the 8 projects configured in the plugin (something leki 50 people out of 500 JIRA members.

            Sebastien Ribiere added a comment - We have the same requirement (and also stands for Confluence) :  Gliffy is only used by 30 users out of 500 EazyBI is only used by 20 users out of 500. This one is even more strange as I have to create accounts in the plugin itself. So the members of EazyBI are clearly identified Salesforce & JIRA cloud is used only by the members of the 8 projects configured in the plugin (something leki 50 people out of 500 JIRA members.

              Unassigned Unassigned
              c81edf5b76e3 viswa_redlock
              Votes:
              23 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: