I have 9 teams contributing to 1 project all have their own back log Edited

Each team has their own backlog which includes work for various different projects.  I want each team to single out the work in their backlog that is for my specific project I am managing so I can create a dashboard to track progress of the teams deliverables.

 

Would you recommend each team assigns labels to the relevant work do this so I can the create a DB?

2 comments

Hi @Jennifer Fernandez

each team can have its own board and the board is defined by a filter query. If there is no set of criteria that identifies the issues to select then I would definitely use labels. Get the teams to agree on a set to use up front for consistency.

HI Tom, 

Thanks for the reply.  Each team does have their own backlog, but on each backlog, there is work which is assigned to different projects on the backlog.  I only want to have visibility into the work for my specific project.  

 

What is the best way to extract/view this?

 

Thanks,
Jennifer 

Hi Jennifer

I'm trying to understand your requirement.

By projects do you mean Jira projects or real world projects ( I wish a different name had chosen for Jira project as it has different meanings to organisations ;-) )

Or do the teams up boards that collate issues from different Jira projects i.e. include issues from your jira project.

If you create your own board based on a filter showing issues in a project you want to see, then the board should show you progress. Although may allow you to move issues which could be undesired.

What would you like to see on a dashboard?

My favourite is two dimensional views by status and assignee.

Hope I haven't completely missed the point here.

We have a similar requirement so I have created a status "Backlog" in the worklog and a custom field with an entry for each team that specifies which team is responsible.

With this you can easily create filters/boards for each team.

I attached a screenshot, although it's german you should get the gist of it.

Edit — test - Jira_2018-11-02_10-13-46.png

And the selection of the specific backlog using the custom field.

Zu Backlog - Jira_2018-11-02_10-15-58.png

 

 

 

tHi @Michael Bachmann

I was assuming a Jira Software project created as a Scrum Software Development that has a built in backlog feature.

My comment was merely an alternative to using labels to define the specific "backlog", which might be a misleading term in this case.
I find labels rather error prone, especially if you are also using other labels not related to this.

How you then use or name the status and custom field doesn't really matter, this is just to identify the correct issues in the JQL used for the boards.

Sorry for not making that clear.

Like 1 person likes this

Comment

Log in or Sign up to comment
Community showcase
Posted Oct 16, 2018 in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

1,223 views 17 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you