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

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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,789 views 11 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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot