Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-141

Trello charges on Atlassian Access

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      As Atlassian Access will be rolled out in the near future for Trello there are some Organization admins that would like the option to prevent that from happening.

      The main reason for this is that their users in Trello are at a free tier and once Atlassian Access gets enabled they will start being charged for those users as they will be using Atlassian Access features.

      Suggested Solution

      Give the Organization admins the option to apply the Atlassian Access features just for the original Atlassian products so their Trello users can remain free of charge.

            [ACCESS-141] Trello charges on Atlassian Access

            Daniel Holmes added a comment -

            Why is this closed?  I'm trying to bring all my users under Access for SSO control of the account in the event they eventually join a cloud instance.  Problem is some people created an account ages ago, tried Trello for a week and never used it again. Now they are connected to Trello, even though it is not an active application for them and I will be billed under Atlassian access for that user forever.   This needs to be correctable if the product usage is not current and active.

            Daniel Holmes added a comment - Why is this closed?  I'm trying to bring all my users under Access for SSO control of the account in the event they eventually join a cloud instance.  Problem is some people created an account ages ago, tried Trello for a week and never used it again. Now they are connected to Trello, even though it is not an active application for them and I will be billed under Atlassian access for that user forever.   This needs to be correctable if the product usage is not current and active.
            Narmada Jayasankar made changes -
            Resolution Original: Fixed [ 1 ] New: Duplicate [ 3 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Narmada Jayasankar made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Narmada Jayasankar made changes -
            Link New: This issue duplicates ACCESS-605 [ ACCESS-605 ]
            Narmada Jayasankar made changes -
            Status Original: Gathering Interest [ 11772 ] New: In Progress [ 3 ]
            Narmada Jayasankar made changes -
            Assignee New: Narmada Jayasankar [ njayasankar@atlassian.com ]
            Narmada Jayasankar made changes -
            Component/s New: Flexible Auth [ 61297 ]
            Kat N made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 486021 ]

            Warren Rowe added a comment -

            What Darren said (above) is even more relevant today... without significant filtering and administrative effort my Atlassian Access user count would have doubled overnight.

            Warren Rowe added a comment - What Darren said (above) is even more relevant today... without significant filtering and administrative effort my Atlassian Access user count would have doubled overnight.
            Dave Meyer made changes -
            Link New: This issue is related to ACCESS-679 [ ACCESS-679 ]

              njayasankar@atlassian.com Narmada Jayasankar
              akasper André K. (Inactive)
              Votes:
              10 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: