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 vote

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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

387 views 1 18
Join discussion

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