Bridge Request Trello Board

Bridge Request Trello Board

Bridge Request Trello Board

If you’re unfamiliar with Trello, it’s a web service that allows you to organize information in "swim lanes" or columns so that we know where each bridge request is in the process. This information is organized in what Trello calls cards.

To get access to the Trello board contact your PM. If you’re a PM who doesn’t know how to give access to the Trello Board, reach out to your VP of PM who should be able to give you access or point you in the direction of someone who can.

The Trello Swimlanes we use are:

  1. Not Started: This is where Trello Cards are Created automatically after a bridge request fee has been submitted.
  2. Bridges Requested But Not Marked In Deliverables In Salesforce: This is a list of bridges that have been requested but not marked under deliverables for the client in Salesforce. We will not move forward with a bridge until this box is checked.
  3. Bridges Requested But Not Charged Deposit: This is a list of bridges that have been requested but we're not charged the bridge deposit. We will not move forward with a bridge until the client has been charged the deposit, or it has been approved by (idk who this should be)
  4. Bridges Requested but Not in Contract: This is a list of bridges that have been requested but are not in the client's contract. We will not move forward with a bridge until this has been approved by (idk who this should be)
  5. Bridge Requested and Confirmed (Deliverable, Contract, Charged): This is a list of bridges that have been requested, have have been marked as deliverable in salesforce, have been charged the bridge build deposit, and have a bridge in the contract. The next step is to get and confirm the login information for the system if we do not have it already.
  6. Need Logins: this is a list of bridges that we do not have login information for. We cannot move forward with the bridge if we do not have this login information.
  7. Incorrect Logins: this is a list of bridges that we have login information for, but does not work when we try to login.
  8. Awaiting Final Confirmation of Details from Pod: This is a list of bridge requests that is awaiting confirmation of details from the pod. This includes all of the types of information we would like to be able to access through the bridge.
  9. Looking for API Documentation: This is a list of bridges that have been requested and need to be built by Cyclr. To do so we will need API documentation. Until we have this information we cannot move forward with this bridge.
  10. Looking for API Documentation - Escalated: This is a list of bridges that have been requested and need to be built by Cyclr that we have not been able to find API documentation for. These have been escalated as a final attempt to find this information.
  11. Ready for Cyclr: These are bridges that have everything they need to submit to Cyclr
  12. Submitted to Cyclr: These are bridges that have been submitted to Cyclr to create connectors for.
  13. Roadblocks with Cyclr: These are bridges that have been submitted to Cyclr but have hit a roadblock. Common road blocks are needing more information, needing a higher level of access, or the bridge does not allow access to the type of data we need to run offline data.
  14. Recommended to Refund: These are bridges that we are likely not able to complete, and have been recommended to be refunded.
  15. Bridges Ready to Test: These are bridges that we should be able to build, and are ready to be tested before they are finished.
  16. Tested and/or Ready for AM to Build: These are bridges that have been tested and are ready to be completed.
  17. Waiting on Client/Pod: These are bridges that that need more information to complete and we are waiting to get that information from the pod members or from the client themselves
  18. On Hold: These are bridges that have been put on hold by the team or the client.
  19. Stuck: These are bridges that are stuck and cannot move forward because of a roadblock
  20. Cancelled: These are bridges that have been cancelled by the client before they could be completed
  21. Bridges Completed: These are bridges have been completed
  22. Dead Bridge: These are bridges that cannot be completed.
  23. Cannot Build or No/Bad Data: These are bridges we know cannot be built for various reasons such as the system not having an API, the API not giving access to the data we need, etc.
  24. List of API Secrets and Client IDs: this is known information about bridges we need to complete the build of them.

    • Related Articles

    • Bridge Basics

      What is a bridge? A Bridge is the connection of two or more APIs What is an API? API stands for Application Programming Interface, which is a software intermediary that allows two applications to talk to each other. Each time you use an app like ...

    • Bridge Request Form

      The Bridge Request Form asks for some basic information we need to begin building the bridge. This information is: Client's Business Name - This is the name of the client's Business Client's Email - The Clients Email Address Provide the AE on this ...

    • Trello Cards

      A Trello Card is where all of the information about each individual bridge request is kept. The main sections of a Trello Card are: Header: This is where we display the name of the system we would like to bridge into and the name of the business we ...

    • Cyclr

      Cyclr is the third party that we use to build our bridges. We use Cyclr because their system enables users who do not know much about code, to create data integrations. The way they do this is by creating what Cyclr calls “connectors''. Connectors ...

    • Release Notes 10/18/22

      Ad Builder Campaigns Table Changes We've updated the "status" field to now indicate if a campaign is scheduled for a future date. This is much easier to visually parse than looking at the start and end dates. The "Edit Campaign" button has been ...