Teams v2
It's a good idea to understand what Teams on Middleware are.
Read the documentation here before you continue.
Is this the right page for me?
If you're interested in creating multiple teams in one go, refer to this page.
If you're looking to create one team at a time, please continue...
Creating a team can be a pretty straight-forward process, but it does require a few steps.
Tl;dr
In short, the whole journey is this:
- Ensure you have the relevant integrations linked here: https://app.middlewarehq.com/integrations
- Click on “Add new team” button on this page: https://app.middlewarehq.com/teams
- Fill in the team name (prefilled), and optionally add a manager and/or members. Adding people can be skipped.
- Don't forget, teams (managers & people only) can be bulk created.
- Add the relevant repos, projects, and incident sources.
- At least repos or projects are needed.
- Save & Exit
- Wait 5-10 minutes for the data to be loaded into Middleware.
- See your insights!
- Issues? Confusions? Reach out to our Live Chat support team from within the app.
Getting Started
Before you begin (optional)
It might be a good idea to link the integrations that your team uses. Such as Github, Jira, Pagerduty, etc.
BUT, you can skip doing this at this moment.
If needed, you'll be asked to link an integration during the team creation process.
- Go here: https://app.middlewarehq.com/integrations
- You'll see a UI like this:
Click to expand image for "Integrations page UI" - Of course, instead of “Manage” or “Unlink”, most buttons should say “Link”.
- Click the “Link” button on your relevant integration.
- Once you're done, that integration tile should have an “Unlink” button instead, and in most cases also a “Manage” button.
- That's it. Don't click on the Manage button (for now), you may or may not need that later, but for you can just move to “Initial setup” (right below).
Initial setup (name, managers, and members)
- Visit https://app.middlewarehq.com/teams
- Click “Create a new team”
Click to expand image for "Team creation screen" - Specify a team name
Click to expand image for "Team name input field" - Add a manager (optional)
- You can type the name to see if they exist. If they don't, you'll be prompted to add this user and fill in the name and email.
Click to expand image for "Prompt for adding new manager" - If they do exist, just select them:
Click to expand image for "Manager selection dropdown"
- You can type the name to see if they exist. If they don't, you'll be prompted to add this user and fill in the name and email.
- Add members (optional)
- Similar to adding a manager, either add a new user or pick an existing one.
Click to expand image for "Member addition interface"
- Similar to adding a manager, either add a new user or pick an existing one.
- At the bottom, click “Next” to continue.
Click to expand image for "Next button in team setup" - Next: You won't be able to save the team just yet.
Continue to see what's required next.
Mapping resources to actually see insights
Requirements for successfully saving a team
A team must have the following before you can successfully save it, otherwise you're prevented from saving it.
- Team name (it's is prefilled for you, but you can edit it)
- At least ONE Repo, or…
- At least ONE Project
At each step, if you're lacking the appropriate integration to proceed, the UI will let you know what you can link to continue. It might look something like this:
Of course, depending on whether you're on the repos, projects, or the incidents tab, you'll see a different set of integrations.
Click one of the big integration tiles shown above to be taken to the right place for that.
It'll likely be this UI: https://app.middlewarehq.com/integrations
Your data will be saved locally if you move away from the team creation process to link an integration. You can return where you paused.
All you have to do, is click on “Add new team” button on this page: https://app.middlewarehq.com/teams
Once you have a repo, or a project – one of either of those at least – you can save your team.
Moving on…
Configuring repos for the team
If you're more interested in seeing sprint or project based insights, you can skip this section, and move to the next one.
Go here to see the minimum requirements for creating a team.
Steps:
On the next screen, you'll be asked to add a repo to the team.
- In case you don't have a code integration (such as Github/Gitlab/etc.) integrated yet, you'll be prompted to do so.
- If you do have a relevant integration linked, you'll see something like this:
- The dropdown you see beside the input selects the organization/group under which you can search for repos. Make sure you've selected the right one.
- Note: You can change the selected organization/group to select repos across multiple of them.
- Once your desired repos are selected, click “Next at the bottom”, … or…
- You can also click “Save & Exit” if you don't need to configure projects or incident sources yet.
Configuring projects for the team
If you're not interested in seeing sprint or project related insights,
or wish to see code related insights – go here,
and/or CFR/MTTR related analysis – go here.
Go here to see the minimum requirements for creating a team.
Steps:
- If you clicked “Next” previously, or if you clicked the “Projects” step item at the top (see image), you'll be here.
Click to expand image for "Projects nav tab" - On this screen, you don't have to select an organization unlike repos, but you can search for a project across any of your project management integrations.
Click to expand image for "Project search interface" - Select your project (can skip if you've selected a repo previously).
Click to expand image for "Project selection list"
Configuring incident sources for the team
Linking Incidents integrations, and mapping those sources to a team is useful if you want to see comprehensive DORA Metrics with CFR and MTTR data.
If you'd prefer getting started with seeing your insights ASAP, you can skip this for now (you can configure this later). Click “Save & Exit” to create the team.
In case you're unable to “Save & Exit”, make sure you've met the criteria for saving a team.
Incidents related insights are anchored to code related data. To see any insights related to incident management integrations, please ensure any supported code related integrations are linked as well.
Steps:
- If you clicked “Next” above, or clicked the “Incidents” nav tab at the top, you should be here.
Click to expand image for "Incident sources configuration screen" - The steps are basically identical to how projects are configured, so we'll just point you there.
- Finally, click “Save & Exit” and your team would be created and the overlay UI automatically closed.
Post team creation
Linking Users
If you've added members to your teams, there's one more thing to do before you can see their dev-specific insights.
Go to “Linking Users” documentation for details.
If you're interested in only team or org-level insights at the moment, continue...
I'll see dev-insights later
Once the team is created, you'd want to see the variety of insights from repos/projects/incident sources you've just linked.
Depending on how much activity is there in your repos, and how many repos you've linked to Middleware - it usually takes 5-10 minutes for the data to start showing up.
For approx. 5-10 repos with a moderate amount of activity, backfilling the standard amount of data (last 90 days) should take about 5-7 minutes. Data refreshes every 6 hours, and subsequent refreshes happen a lot faster (even for 100+ repos).
If it takes longer, feel free to reach out to Middleware Support via the Live Chat button at the bottom-right of the page.
We're pretty confident that you've never experienced support this prompt and quick before.
