nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tracking generic product and specific projects

yanir

Hi,

We have a generic product and we conduct customizations for specific clients.

But many developments will be part of the generic product. The same teams develop the generic product and the project-specific within the same branch, and sometime the same feature is relevant to more than one project.

My question is what is the best practice to manage it in Jira?

We thought that having a single project for everything and label tasks by the project would make sense - but that turned out to be very challenging in terms of "project view" - but

then we can manage only single sprints end dates for the generic product and all the projects
Jira Reports are a bit limited as it does not always let me filter by label

Accepted answers

unknown

Hi ,
my suggestion would be to use Epics to split your sprints up from the main generic product’s development and the various client specific variations. 
If you have more than one JIRA project your epics can link across them to standard issue types such as Stories. 
Hope this helps

All comments

unknown

yanir

thanks Danny, did not think about connecting an epic across projects. I hope that I will still be able to reflect the fact that even clients requirements should be incorporated into the generic product eventually, whereas the projects should just dictate the priorities and to have independent sprints dates, but sounds like I should take that direction, so thanks again.

unknown

Hi @yanir,

if you are happy with the answer please accept it as helps others in the future to find answers.

Thanks

yanir

sure thing, done

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-cloud