Well, here we are, Day Two. Today is supposed to be more ITIL and Software, so lets see what they have.
Supposedly they will open up the keynotes for on-demand access tomorrow, so I may come back and touch up some of the Screenshots then. As for today, I likely will not be able to capture every detail to come up, but I’ll get as much as I can to keep you informed!
Shh….they are starting now:
And now we hear from the other Founder, Scott Farquhar. He goes over a bit of what we saw yesterday, and a bit of detail on JWM. As I said, I’ve already gone into detail on that, so I won’t bore you here.
New Product, Compass
It’s meant to be a single hub for your Dev teams to compile information from a myriad of sources to see a full picture of a Software project
See what Repositories are a part of the Project, as well as Docs.
Check on dependencies and owners…
As well as get a Scorecard to see the health of the overall project.
See who owns a project, who is on call, and how to contact them when things go wrong.
You can also see a Security scorecard to see where you stand on security
Compass brings together information from where ever it may be to give you a full picture of everything. As a former coder, it looks interesting, and I’ll be seeing what it can do for my local lab stack.
It looks like they are going to go over three overarching themes.
So familiar with all of these problems. One company I worked with had four separate SCM systems. And now, they were all from the core company, not from acquisitions.
They then introduce Open DevOps. Basic premise: use any tool, and it will just work. I’m skeptical, but interested.
Looks like a who’s who of Dev tools, though.
So some details.
a) If you setup an integration, you don’t have to reset it up for every project.
b) If you include the issue key on any of these tools, whatever is included is attached to that issue. ANYWHERE. That can be big.
You don’t have to setup individual repos to be a part of the project. You just include the issue key in a PR or Commit, and the entire repo is added to the Project.
Track deployments the same way. If it has an issue key, it’s included.
Still uses JSM’s Deployment and Risk Assessment Engine, but is designed to work with any CI/CD tool you are using.
OpenDevOps also includes a number of Confluence templates that are automagically generated for different events.
This was just announced before Team ’21. ThinkTilt was one of the earliest groups to share the blog with others, and had a big hand in the growth. Glad to see this for them, and looking forward to see what the future holds!
ProForma from Thinktilt allows you create dynamic forms in Jira to help you get the information you need to do work.
Another Acquisition, Halp is being integrated into Jira Service Management – Cloud AND DC!
Built in Knowledge base articles in JSM, but powered by Confluence? The line between the two in Cloud keeps getting blurrier.
Some more details on OpenDevOps – they too include insights and metrics.
Including Deployment Frequency and Cycle Time.
Honestly, you have to be careful with metrics. It’s all to easy to have a manager focus so much on the metric that the environment gets toxic.
A Good Deployment frequency because all the roadblocks are removed is great. A Good Deployment frequency because the devs are told “Or Else!” – not so much.
In speaking of Deployments, a bit of the Deployment Approval Flow on JSM.
Including relevant information, like current outages and such.
As well as Upstream and Downstream services.
In speaking of Outages, a bit on Op Genie in coordination.
And the ability to schedule a deployment
So that was Summi…er…Teams ’21.
So, that was a firehouse. But we got a lot of good information about what Jira will look like over the next year.
And as news and updates continue to come out, you can follow me on Facebook, LinkedIn, Instagram, and Twitter to get the latest. Don’t forget, you can also subscribe below to get new posts sent directly to you! But until next time, my name is Rodney, asking, “Have you updated your Jira issues today?”