Use Case?

Joey Klein_y7zba7

Apologies in advance if this isnt the place to ask this kind of question but...i signed up for early access and this looks so cool.  My question is, is this supposed to be used along with JSW or Core or is this standalone?  Say we define epics as 'projects', does this take the place of epic reports?  Do we link these together somehow?  so many questions. 

Rachel Lin

Hi Joey! Great question - thanks for asking. We're also happy you have positive first impressions of Team Central so far. I think I may have answered it in the in-app feedback you sent, but just in case anyone else is wondering the same thing: 

Team Central is a standalone tool for project communications. It aims to solve the problem of communicating outwardly to your stakeholders or dependent teams who are not ingrained in your day to day work, but need to know what’s going on at the high level.

How this may play with Jira is: think of Jira as your direct team’s way of communicating, Team Central is your teams-of-team’s solution for communicating and managing dependencies. The level of granularity you communicate to these groups is different.

Today, you may want to link into Jira from Team Central to provide additional detail for readers. We have smart links that help provide context to these links. 

The epic in Jira could map to a project in Team Central (that's a good way to think about size of a TC project), but you would plan that epic in Jira. When the project has kicked off,  you use Team Central to communicate on its progress to other teams. Right now, there isn't a specific way to link these together and sync data between the two (what might you need to sync?) but we have been working on a lightweight Jira integration, which is coming soon.