Best practice: creating another project, or epic/component?

Ahmed Alghamdi_6u0l4m

We are developing a mobile app for a bnak acceesable by bank customers. Now we are also working in creating another app for only a segment of the bank customers (example, those with disabilities, or those with large money and such) thus so many services are essentially going to be the same.

Should we create another project for that segmented app? or just create one big epic inside the main project? notes that each of those app wil require updates and improvments moving forwards

Also, the same team working on main project, will be working in the segmented app, so i'd love to no hassle to navigate between both projects, simply search for an issue should search in both projects,, possible?

Walter Buggenhout

Hi Ahmed,

A quick way to help you take the right decision might be this: if your new app has its own components or a separate versioning, create a separate project. Both versions and components are project specific, so you should manage them in separate projects.

If that's not the case, your application might also become a component in your existing project.

No worries about having your team work on tasks across multiple projects. JQL filters will help you bring them together and integrate them on one and the same scrum or kanban board.