Team 2021 AMA with Justine Davis and Amita Abraham

[#1]

Hey Atlassian Community!

Amita and Justine just gave a talk, How high-velocity Dev and Ops teams fuel digital transformation, at Team 2021. 

Now is your chance to ask this superstar team anything about Atlassian's latest investments to bring dev, IT, and business teams together to operate at high velocity and to deliver exceptional digital and product and services experiences that are always on and FAST! If you don't have a question, drop your #1 takeaway from their session in the comments below. 

[Dirk Ronsmans]

It was mentioned that the Knowledge Base would become built-in to JSM/brought in to JSM

How can interpret that?

• Will it be some kind of Confluence lite where the data will be stored within JSM/Jira to provide you with something if you don't have a full Confluence product
• Or will this be something more like providing a seamless integration between Confluence as a KB within JSM?

Would love to hear some more details about that!

[Amita Abraham]

Hi Dirk,

The short answer is that Jira Service Management will now include knowledge base functionality out of the box. So users of Jira Service Management will be able to create and edit knowledge base articles without a separate Confluence license. It makes for a much more seamless experience. Of course, a lot of the knowledge base capabilities in Jira Service Management leverage similar features that are in  Confluence (e.g., the collaborative editor). If you do have Confluence , we’ve built a seamless integration that allows you access to the same content from either products.

[Dirk Ronsmans]

Hi @Amita Abraham ,

Thank you for the short answer :)

So if I get it right my idea of a Confluence light version built-in to JSM sounds correct then?

If I understand correctly, there will be 2 different paths that can be taken:

1. JSM with Knowledgebase built-in (Confluence like but not linked to a real Confluence instance/space)
2. JSM linked to a Confluence space that you have on your own instance.

This might be nice once for a lot of smaller companies/teams who don't really need a full blown Confluence but would love to have some Knowledge management. Excellent idea!

Maybe going in a bit more technical (if those details are available yet), would that then also allow a segregation between internal knowledge documents and customer facing documents? Or would that use-case then justify going to a true JSM-Confluence setup?