With CodeStream 11.1 we are taking a first step toward eliminating the concept of a CodeStream “team” and moving toward a model similar to Slack where all developers from your company can be in a single CodeStream “organization.”
The notion of a CodeStream team was introduced to help manage the signal-to-noise ratio in your activity feed, but there were some drawbacks. When larger companies onboarded there was a tendency for duplicate teams to get created, and time had to be spent getting everyone consolidated onto the proper teams. The team-based model also unnecessarily limited access to your company’s knowledge base on CodeStream. For example, if a developer on the “frontend” team is checking out some code in the api server repo, they wouldn’t see any of the codemarks associated with that code added by someone from the “backend” team.
At this point we simply converted each team in an organization to a new organization, and you shouldn’t notice any impact nor changes to your CodeStream experience. The biggest difference is that if you were active in multiple teams, you’ll now use “Switch Organization” in lieu of “Switch Team” to move between.
Additionally the “My Team” section has been moved into the My Organization tab in the global nav.
The next step of actually consolidating multiple groups into one will be done on an on request basis. If you’d like to take advantage of the benefits discussed above...easier onboarding and a more available knowledge base, plus maximize the benefits of our new domain based joining (see below) please let us know.
As far as managing that signal-to-noise ratio in a large consolidated organization, you’ll be able to manage what you see in your activity feed by filtering it to show just activity related to the repositories you have open in your IDE.
CodeStream 11.1 also adds the option to allow anyone with an email address on certain domains to join your CodeStream organization without needing to be invited first. This will make it even easier for your teammates to get started on CodeStream.
Admins can configure this feature under Organization Admin > Onboarding Settings.
With CodeStream 7.4 we introduced our Blame Map feature for team admins but it is now available for everybody.
By default, when you comment on code, CodeStream mentions (or offers to email) the author(s) of the code you are commenting on. But if that person has left the company, or transitioned to a different role, it might not be the right thing to do. CodeStream’s Blame Map feature allows you to direct discussions about code that someone else may have worked on but you are responsible for to yourself. (Admins still have the ability to reassign code to anyone on the team.)
You can also use the Blame Map to add email addresses that you use for committing code that may be different from the email address you used to sign up for CodeStream. For example, your CodeStream email address might be email@example.com, but you might also commit code as firstname.lastname@example.org. Click "Add mapping", enter your git email address, and then select your entry from the list of organization members. That way, when someone comments on code committed by email@example.com, CodeStream will know to at-mention you (i.e., firstname.lastname@example.org).
The Blame Map is accessible under the “My Organization” in the global nav.
Please share your thoughts and feedback @teamcodestream.
New Relic CodeStream integrates all of your essential dev tools, such as GitHub, GitLab, Bitbucket, Slack, Teams, Jira, Trello and more, into VS Code, Visual Studio, and any JetBrains IDE.
During our daily stand-ups we demo features in development to allow everyone, which now includes you too, to stay in the loop and provide early feedback.