Using JIRA for a SAFe 6 implementation where each team is handling multiple clients

[Amitabh Mendiratta]

We are operating in SAFe and each team has been set up as a seperate project as they each cater to multiple clients who have their own boards within the squad project.

I need the following:

1. an epic having multiple stories to be picked up by multiple teams in different JIRA projects. The story should also show up on their board. Currently we can assign the story to anyone outside the project but it doesnt show up on their board. Can this be achieved by automation and how?

2. Creating the hierarchy of Epics - Features - Stories

3. A place for all features to be discussed before they go in for PI Planning

4. Is there a way to replicate Program board with dependency threads?

Thanks so much for your help.

[Jehan Bhathena · Accepted solution]

Hi @Amitabh Mendiratta ,

Adding my response to your query below:

• an epic having multiple stories to be picked up by multiple teams in different JIRA projects. The story should also show up on their board: 
  • There are 2 approaches you can take for this, for each Project Board you can configure the filter to show tickets project a different project when the Assignee is XYZ. The other approach would be to centralize your "Features" and then pipe the "Story" into different projects that you need

• Creating the hierarchy of Epics - Features - Stories: Out of the box the Hierarchy is Epic -> Story, since you want to change this I would suggest the below approach.

  • Since you need an issue type between Epic and Story, Rename "Epic" to "Feature", so this will create your "Feature" -> "Story" 
  • Create a new Issue Type called "Epic" and in the "Issue type hierarchy" give it "level 2". This will put it above the previously created "Feature".
  • This should give you the needed hierarchy
• place for all features to be discussed before they go in for PI Planning :
  • While I'm quite sure of this, I would recommend creating a status like "PI Planning" that can be used to track all tickets that need planning
• Program board with dependency threads:
  • You can try using "Plans" (previously known as Advanced Roadmaps https://www.atlassian.com/software/jira/guides/advanced-roadmaps/overview#what-are-advanced-roadmaps)

Hope this helps. Please mark this thread as Accepted if this fulfills your use case.

[Amitabh Mendiratta]

@Jehan Bhathena  Thank you so much for your response, I only just noticed it, I will give it a shot.

Another thing i am struggling with is that we have 2 definitions of done for a team board, with the first being done in Dev environment and the 2nd done being released. I needed a burndown only till dev done, any ideas on this?