-
Suggestion
-
Resolution: Won't Fix
When verifying a domain for an organization, one of the parts will be to claim the accounts, which will provide the administrator with a number of accounts to be claimed and an option to export this information.
When organizations have Atlassian Access, if the claimed accounts have access to specific Atlassian products, this will add the users to the Atlassian Access bill and make sure about the billing, the closest workaround is to export these accounts and add the number of billable users in the Atlassian Access pricing calculator.
Suggestion
For organizations that have Atlassian Access, this is a suggestion to also include the pricing/bill for the product during the claiming process based on the number of accounts that will be claimed.
This way, the administrators can already organize themselves with the company based on the pricing that will need to be paid for Atlassian Access.
[AX-368] Clarifications on pricing when claiming accounts
@Giuliano (reporter) pointed out that my prior comment is addressed by Export Managed Accounts which is available after claiming the domain [?] thus the original scope of this as a clarification during/before the claim process makes more sense. Thanks.
This issues encompasses more than just the "claiming account" process. Ongoing Atlassian Access bills will need to include a breakout of the users which allow the customer to do appropriate cross department charging. E.g. the Atlassian Access bill example shows the number of users but a large organization will also need to the list of users.
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!