Nexus Sprint Backlog in JIRA

Last post 05:19 pm July 31, 2020
by Mike Milen
7 replies
07:44 am July 24, 2019

Guys, how would you implement the Nexus Sprint backlog in JIRA? I know it is possible to have multiple sprints running at once. But how will you work on the Nexus Sprint Backlog since it contains "all" of the sprint backlog items of the individual teams.


Will you clone it and make a dependency?
or will you handle the Nexus SBL separately (outside JIRA or any other tool)

09:09 am July 24, 2019

Might the Nexus Sprint Backlog be represented as a filter or view of all Sprint Backlogs in the Nexus?

10:08 am July 24, 2019

Having used Jira in a multi-product and multi-team environment, here are some of my tips:

  • Each Jira project equates to a product. This better enables the use of the version related fields, ability to generate releases and release notes, and some other things without much manual effort.
  • The configuration of issue types, workflows, screens, and so on is attached to the project so all the teams follow the same general workflow. I recommend making the workflow generic enough to give the teams some flexibility, but specific enough to keep them aligned - this is an art.
  • If you have multiple teams on one product (Jira project), add a field to capture the team doing the work.
  • You can then create multiple boards within the project, either Scrum or Kanban style. Each team can have their own board filtered based on the team. You can also create boards and backlogs for the Nexus or to track individual releases. Since boards are just queries and filters, it's pretty easy.
10:13 am July 24, 2019

I would also add two more things:

  • Use labels. This can help show or hide things, either from the team backlogs or the Nexus backlogs. You can include these in your queries as appropriate. Some standard labels by convention can help, but labels also give the team a lot of internal flexibility.
  • Don't discount the Confluence integration. Being able to generate pages based on Jira queries showing issues or data graphs/charts can be hugely beneficial.
01:35 am July 25, 2019

Thanks for those tips Ian and Thomas!!!

11:50 am July 25, 2019

I personally like to use Jira Components, write a JQL to use the component, and then make a board using the JQL.

04:45 pm July 28, 2020

Thomas Owens, two questions:

1. Given your recommendations above, would you recommend keeping a copy of the Nexus Backlog board on every Jira project?

2. Have you encountered a way to represent Jira dependency links across teams & sprints automatically?  So far, I see a Server plug-in, but not Cloud.  (see   I'm currently looking for anything that could import story data and display this.

09:59 pm July 30, 2020

I've tried several of these approaches, but ended up using a single project and board with an active Jira "sprint" for each team in the Nexus. This allows each team to utilize the sprint/team functionality built into Jira (for example, sprint goals, planning, and closing out a sprint). In our version of Jira you can filter a Scrum board by a specific active "sprint" or by "all sprints".

We also use the Portfolio "Team" field for Nexus planning and then a filter on the backlog to allow each team to focus on their potential backlog candidates. We used a label (and looked into using a component) before Portfolio was available.