Background: we have JIRA projects set up in accordance with our products structure, i.e. a project "System" might have 'child projects' "Subsystem1" and "Subsystem2" (even though all three projects are in fact regular JIRA projects - the parent-child relation is only in our minds). We have several dev teams, each team responsible for one or more subsystems.
Scenario: In this case Team1 is responsible for Subsystem1 and Team2 responsible for Subsystem2. Both teams are working on issues/epics on the parent "System" level.
An Epic is created in "System" project, and this epic has one user story per subsystem project. Both Team1 and Team2 can see the epic on their respective scrum boards, and also their "own" story related to the epic.
Problem1: the teams can not easily see that the epic is actually affecting other teams, in the Scrum board Epic panel they only see their own story.
Problem2: when Team1 is done with their story, they close it and then mark the Epic as "Done" in the Epic panel. When this happens, the Epic disappear from Team2 scrum board, even though they have not finished their story. It should not be possible to mark an epic done unless all linked issues are resolved or closed.
Problem3: if the team is using a Kanban board, it's really hard to see that their story belongs to an epic, and even harder to see the dependency to another story belonging to another team.
Question: is there some way to set this up in Jira/Jira Agile, solving the problems mentioned above? All suggestions welcome!
Note: I know some problems would be probably be solved if we would have one project only for the whole system and use Components instead of splitting it up into several projects, but this makes it hard to handle versioning - each subsystem must be able to have it's own release cycle and version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.