How do I manage projects that share the same user stories?

[Gilvan Júnior]

Hi all,

I would like to know how to manage the development of an application that will have the mobile version, web and api.

I ask this because all three of these projects share the same epics and most of their stories.

I would like it to be even separated into three projects because it is better to define the versions that each front will have: Web, Mobile and Api

[Nic Brough -Adaptavist-]

An issue lives in a single project.  If you break up your development into those three parts by doing it by project, you are going to have to duplicate each issue into each project separately.

Consider either using components, a custom field or sub-tasks to break up a story into each element instead.  This does have the weakness that it won't directly support different versioning like three projects would, but you could mostly fix that with a naming scheme like w_ m_ and a_ being stuck on the front of each version.

[Gilvan Júnior]

Hi, thanks for the tip. But we decided to follow through with projects for each area of development, thus controlling the versions independently. And doubling the epics and user stories

[Nic Brough -Adaptavist-]

That is going to make managing them together quite difficult, as you're setting them up in a structure that means managing them separately.

I would take a look at Apps that help you deal with many projects, things like Portfolio for example.

[Gilvan Júnior]

In my view, the ideal was a project with the epics and stories and the other projects - web, mobile and api - tasks as sub - tasks of user stories