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; } } }

Is there a disadvantage of having 2 projects and creating boards to manage releases of both together

Jeyesh Jeykhar

There are 2 projects created:

1. One project for EPIC creation

2. Another project for Other Issue Types (User stories, Tasks and Sub-tasks) creation

This is done so that EPICs and other issue types can be identified with a different key names (For e.g. EPIC will be identified as FR-1, FR-2; Other Issue Types will be identified as ENG-1, ENG-2,..)

We make sure that EPICs are linked appropriately with the User Stories. We will use boards that connects both the projects to generate graphs. Note that both are scrum boards.

The Question:

Is there any limitation of using the full potential of JIRA if we use 2 projects instead of a single project?

Accepted answers

Wouter Bruinings

The first that comes to mind is that in dashboards you will have to be a bit more creative with your SQL to make sure everything rolls up to Epic level.

It is not a limitation it is something to consider when moving in the direction you are describing.

All comments

Wouter Bruinings

The first that comes to mind is that in dashboards you will have to be a bit more creative with your SQL to make sure everything rolls up to Epic level.

It is not a limitation it is something to consider when moving in the direction you are describing.

Jeyesh Jeykhar

Thanks Wouter.

If you have a specific example, it will be good.

Another Question:

With Release version specific to a Project, we cannot link Epics (In one project) with the same release version to User stories (In another project). In this case, is this not a limitation to create certain dashboards or generating certain graphs/ reports?

If yes, can you give me some examples of the reports/ graphs/ dashboards that cannot be generated.

Wouter Bruinings

Sorry, I don't have specific examples.

Yes you are correct in pointing out that a release is per project, this means that the automatically generated reports based on release will always only include the project on which you generate it.

You have to figure out how valuable such a report is and weigh it up against how valuable it is to have Epics with a different name.

What I would do in your situation is to create a dashboard myself to and figure out if I can aggregate and display the data in a dashboard in a way that is similar to the automated report. Then I decide if I can live without the automated report.

You don't need two boards though as you can display tickets from both the projects in one board.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud