Best practice when you have both products and customer projects feeding in Stories?

What is the best way to set up JIRA (esp. Projects and Epics) when you have Stories being fed in from both our product lines and from our consulting projects? The Stories springing from the consulting projects include work that must be done in the products (i.e features) but also non-product work.

Product Management, Project Management, and Dev. Management feed stories in, and Dev Management and Staff complete the Stories.

We're also using Confluence for documentation and consulting project records, and I'd like to be able to consolidate all of the Stories associated with a consulting project. 


1 answer

We use a project per customer and one project for consulting in general. If a customer wants some product (e.g. a plugin) we create an epic / story in the customers project. We then link this epic with the consulting issue where it came from. You could also use the same label or component to show the connection.

On confluence side we use one space per customer for documentation.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,420 views 15 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you