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

Version Management on a Board

Nick Knuth

I have several hardware and software teams that have their own JIRA projects and boards that they manage. They create most of there own tasks within their own project but can and do create tasks for other teams that they assign to the other teams as needed. In order for each team to see tasks assigned to them from other projects I have updated their board filters to pull those tasks in but doing this has made it so each team sees the other teams versions on their board creating a lot of clutter. I would like to keep the board filter since it does pull in the required tasks but I want to be able to remove the versions from each board that are not their own so the cluttered view is eliminated. So my ask is how can I make this happen and if I cannot, is there a plan to have this be an update to the JIRA tool in a future version of it?

Accepted answers

All comments

Jack Brickey

@Nick Knuth, If i understand your issue and goal correctly it is certainly solvable thru proper filtering for the board. However, to assist I would need more info from you. Can you provide the details of your current board filter?

Ahead of that let me ask a question and make some comments that may help.

Are the boards associated w/ projects or people? It may be a simply matter of creating boards based upon teams rather than projects. Such as:
- Board 1 = Assignee in (Fred, Sally, Juan)
- Board 2 = Assignee in (Betty, Stephen, Jill, Jen)

If any of the resources work on multiple boards then you will need to consider adding other qualifiers.

Nick Knuth

The current board filters are all based on projects instead of people because tasks are not initially assigned to individuals but rather to a team (software team, mechatronics team, etc.) for review, assignment, and completion. An example of a filter is below:

project = HW1 OR project = 16002 AND "Team Name" = "AGV HW1" OR project = HW2 AND "Team Name" = "AGV HW1" OR project = "AGV Mobile Automation Documentation" AND "Team Name" = "AGV HW1" OR project in ("AGV EAF Connector", "AGV Ensor Validation", "AGV Contour Navigation") AND "Team Name" = "AGV HW1" ORDER BY Rank ASC

Nick Knuth

If someone on Team HW2 creates a task and assigns it to Team HW1 they use a field 'Team Name' that has a drop down selection and they just select HW1 and then create the task and it falls to HW1's backlog because of that tag as you can see in the board filter example above. The added boards and versions that appear with this filter setup though is a bit much but going person by person would create other larger complexities I would think

Jack Brickey

that is a pretty messy filter. :-(

so...wouldn't simply creating the boards based upon the "Team Name" work? e.g.

AGV Board - "Team Name" = "AGV HW1"

If I am reading you correctly, all issues associated w/ a team ultimately will have the "Team Name" field set. If not already the case that field should be made required at creation so that all issues appear on a board.

I realize I keep going back to the people->board approach but it seems that is how the org works? I'm still missing something here I think so bare with me as I try to understand.

Prem Chudzinski _extensi_

Take a look at this

https://extensi.atlassian.net/wiki/spaces/ABF/pages/31850177/Epics+Versions+Lists+filtering+on+Backlog

Restrict the version or epic list by Project key for example: KEY1|KEY2|KEY3

Filtering will be saved so next time you'll open the backlog versions or epics will be filtered out by project.

32.Filter Versions.png

Welcome!

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

Quick Links

Find more posts tagged with

jira-software