Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Unresolved
Fix Version/s: None
Component/s: Licensing
Labels:
None

UIS:
84
Support reference count:
11
Current Status:

Hide

Atlassian Update – 28 May 2019

Hi everyone,

Thanks for your interest in this issue. This suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions. To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

I also encourage you to check out this community post on our investments and plans and their visibility on jira.atlassian.com.

We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

Kind regards,
Gosia Kowalska
Jira Server Product Management

Show
Atlassian Update – 28 May 2019 Hi everyone, Thanks for your interest in this issue. This suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions. To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . I also encourage you to check out this community post on our investments and plans and their visibility on jira.atlassian.com . We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . Kind regards, Gosia Kowalska Jira Server Product Management
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

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

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.

Attachments

Issue Links

is duplicated by

JRASERVER-36830 Decouple JIRA license model from plugin license model

Closed

relates to

CONFSERVER-52322 Allow for smaller plugin license based on usage

Closed

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

Gathering Interest

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

Gathering Interest

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

(12 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Thomas Liechti

Votes:: 731 Vote for this issue

Watchers:: 321 Start watching this issue

Dates

Created:: 23/Feb/2016 11:03 AM

Updated:: Yesterday 2:09 AM