I can't seem to get my bitbucket account to send our BitBucket bills to our billing department.
I've tried assigning a Billing Contact to our License view at https://my.atlassian.com/products/index
But this didn't change anything.
Hi Rasmus, welcome to the Community!
The invoices will be sent to the primary billing contact, did you promote that email as the primary one already? You can find the instructions on the step 4a of the article How do I update the contacts for my Atlassian products?
Let us know if you need further assistance!
Bitbucket is built upon Teams, where Teams have Users. My Gmail email has been added to one of my company's Team, and I want to be the Billing Contact on that Team.
Logging into My Atlassian lists nothing for me, what do I miss?
How can I change my user to be Billing Contact, for a certain Team, in Bitbucket?
I followed the link you provided, but it fails here: "To establish a new Primary Billing or Technical Contact, the new contact will need to log into their My.Atlassian account and select Make Primary".
I logged in, and there is no option for "Make Primary" anywhere. (How would My Atlassian know, that my user has the proper permissions to be a Billing Contact? I found no such options in Bitbucket where I could set my user to be eligible for the role of Billing Contact).
Hi @karatedog ,
You won't be able to change the Billing contact for the team, only the current Billing contact can do that. The current Billing contact will need to go to my.atlassian.com, add your email address as a secondary Billing contact, and then promote you, so you become the primary one.
You don't need any special permissions to become a Billing contact, just the approval from the previous one :)
Hope this clarifies your concerns!
This solves our problem now, but I see a serious product design issue here. What if the current Billing Contact cannot add this new email? Say, if he/she dies in an accident, and he/she was put in the team with her 8 years old personal Gmail address?
No one will be able to access that personal email to regenarate the login password. The team's only possible way of solving this would be escaping to a new account (with accessible email) bringing along all the repositories.
If I'd be the decision maker in a such situation, I'd immediately change product...
From a general understanding, it's not a good practice to use a personal email address for company related stuff, so having a corporate email will mostly solve this. Putting this issue apart, let's say the Billing contact was using a personal email address for whatever reason and they die in an accident... then, in that case, one of the admins of the Bitbucket account can contact us to explain the situation and we'll help them sort this out.
Some documentation would be required to make sure that there's no security being breached, but there would be some kind of solution :)
Hope this explains,
"Billing contact was using a personal email address for whatever reason" -> this is the default way for growing teams. Nobody will have an experienced IT lead on the team on the start, who has knowledge about the dangers of using individual email address instead of company group email address.
I don't know all the permissions that a Billing Contact has, but I'm a simple admin and I can change the credit card details, and even the company name and address.
So I have the power to completely modify the monthly bill, and have it deduct from a different credit card which has, I think, a way greater impact than modifying the Billing Contact. I was Billing Contact for JIRA once, this role got me a new email a month, and that's all, I wonder what a Billing Contact for Bitbucket can do that no one else could do.
I know this is an old topic, but I totally agree here with Laszlo - we're currently in the situation where we have zero idea who the billing contact is (and there's no way of setting what email is set as billing contact, even though I'm an admin and can - as above - update credit card info, company address, etc.)... so we cannot receive any invoices and can't update any of the contact info without knowing something that we can't know unless we log in as the contact we don't know... see the issue here??
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events