If custom selection of versions to show is too much to implement, a toggle to hide all from the linked projects would be fine, as I find no value in cross-project version viewing. If I need to know when another projects releases are, I can check, or add them to my own project manually. The lowest level of implementation, only show versions from the primary project. 

I know its not an out of the box solution, we we use a plugin that does this called 

Agile Tools & Filters for Jira Software https://marketplace.atlassian.com/apps/1215334/agile-tools-filters-for-jira-software?hosting=datacenter&tab=overview 

Works perfectly!

I too would like to see this feature. 

It is quite common for multiple teams to be working on the same feature.  If my team has a contribution to make towards a feature mainly managed by another team, as soon as I pull in the Epic from the other team into my board, I get all their versions, which causes so much confusion.  While this scenario might not be the idea "Jira way", some sort of workaround to hide version from another project would be very helpful

10 years in and folks still want this. My company has many teams utilizing Jira and without the ability to filter for Versions on a board, we are going to have to sort through hundreds of versions to find the one we want. Furthermore, this creates a huge security risk for releases. Please implement and this has my vote.

We also REALLY want this please

Hi! any update?

Hey Atlassian, any update?

Yes, this is needed to help with decluttering the version panel and ensure the board is usable even if you are not a JIRA expert.

If I could vote again, I would.  This would be a great feature to add.

Still needed ; is there any update?

Thanks, Alex

Hi, we have our solutions (Jira projects) separated of the specific products (Others Jira projects) and when we attend a new customer we create a solution and link this to those products that are attending the new customer.

So, in every product we have some internal interaction not required to be reported to high level (solution) and also, some Epics and Versions created in the products are not required to be viewed in the solution board. When we have a lot of teams adding small pieces to an entire solution, the Epics, and Version lists can be unmanageable if we can not edit this.

In the other hand our company had defined two versioning levels in order to track the Milestones with the customers and track all the items we need to include for each milestone, but the products have the own versioning, so that is good for the products reports, but at customer level is required to track the specific milestones. So if we have this functionality, we can manage the specific version required for our milestone and include those for the internal products marked as candidate to be delivered to the customer.

If you think, the last part can be managed with the options "Archive" and "Released", for us the answer is not, because some versions remains unreleased while the teams are performing the QA interactions, and also some deprecated versions can have issues discovered later and we need also to reference them.

how many votes are required to implement this?

Same here !

We could definitely use this feature as well.

We are facing the same problem.

Definitely still needed.

This is really needing some attention.  We have boards that have a hundred versions in the tab because they're cross project which makes version management in the backlog nearly un-usuable.  A simple filter at the top of the column would suffice.

I am facing this issue, too.

I have scrum boards that shows only issues from project A or project B, respectively, but additionally the filter includes Epics from project X, so that I can assign issues from projects A and B to epics from project X.

This is because project X is the "cross-team" board and project A is the board of team A, project B is the board of team B, etc.

Because I included the Epics from project X, I see all versions from project X (which are, actually, duplicated in project A and project B).

So I either want to hide the versions from project X or be able to assign an issue from project A to a version from project X. In that case I could remove all versions from projects A and B. OR it would help if the colored Epic labels would be shown in the Backlog and Scrum Board view even if the Epic is not included in the filter.

Totally required