Charge for admin

Any gauge on the buckets of activities that an admin will do and how best to x-charge for these within an enterprise. Per project, and per n x issues, with H-M-L as project starts then expires.

1 answer

0 votes
Daniel Wester Community Champion Mar 09, 2015

Due to the nature of JIRA - any JIRA admin can make a change only impact one project and but then another admin can make another change  such as adding all projects to the custom field the first added - it's kinda hard to track. Your best approaches are:

  1. to limit the number of admins. 
  2. Since you're using Cloud - have multiple Cloud instances.
  3. Use an equal allocation of cost approach. (ie. you've got 25 admins – eek - that's 1/25 charge per admin).

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,409 views 15 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you