One project with a version for each customer or a project for each customer.

Let's say we have a project named "Bakery App". For each customer we created a version, let's say we have "Alice's Bakery" and "Tom's Bakery". They share the same core functionality, but got some custom stuff and each their design. We created a bunch of user stories and then marked each story with the right versions. But now we see that this might be a bad approach because you can only change the status from "in progress" to "resolved" for all versions, and not just one.

If we create a project for "Alice's Bakery" and "Tom's Bakery" there will be a lot of stories that we have to copy back and forth, a lot of duplicates.

What is the best approach to this in your opinion? :) Thank you for any answer, much appreciated!

3 answers

1 accepted

Hi Johannes,

I would simply create a project per Bakery (so one for Alice's Bakery, one for Tom's Bakery) and use these projects to contain all stories that are custom for this customer (design,...).

I would then create a global project which contains all you common stories (the core functionality).

You now have a clear project per customer and your core functionality doesn't have to be copied everywhere.

What do you think about that idea?

Best regards,

Peter

Hi Johannes,

Could you please accept my answer?

This will mark your question as answered.

Best regards,

Peter

HI Johannes

I dont think i understand your statement

you can only change the status from "in progress" to "resolved" for all versions, and not just one.

Can you clarify this>

Of course, sorry.

When you say that one issue (story) affects several versions (Alice's - and Tom's Bakery) and resolve the issue, it will be resolved for both versions. There is no functionality in resolving the issue for one version only, and then the other later on. So you have to create two stories, one for each version - which is tedious.

So I'm asking how other users deal with this. Do you create several projects and create the same issues for each project where they share core functionality, or do you create one project like me and use versions? If so, how do you deal with the status for each issue that affects more than one version?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,831 views 12 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot