QGIS 3.22 - Identical map names in print composer

[mik-cor]

What is the bug or the crash?

When adding multiple maps to a print layout, all maps are named "MAP 1", so it is impossible to correctly associate scale bars, legends etc..

Steps to reproduce the issue

Open new print layout
Add 2 new maps
Verify map's names

Versions

Versione di QGIS
3.22.3-Białowieża
Revisione codice QGIS
1628765
Versione Qt
5.15.2
Versione Python
3.9.5
Versione GDAL/OGR
3.4.1
Versione PROJ
8.2.1
Versione database del Registro EPSG
v10.041 (2021-12-03)
Versione GEOS
3.10.0-CAPI-1.16.0
Versione SQLite
3.35.2
Versione PDAL
2.3.0
Versione client PostgreSQL
13.0
Versione SpatiaLite
5.0.1
Versione QWT
6.1.3
Versione QScintilla2
2.11.5
Versione SO
Windows 10 Version 2009

Plugins Python attivi
changeDataSource
3.1
Cxf_in
9.2
fitgeometrybyarea
1.2
GeometryShapes
0.7
go2streetview
8.3
LocatePoints
0.3.4
mmqgis
2021.9.10
nominatim_locator_filter
0.2.4
profiletool
4.2.1
Qgis2threejs
2.6
QGISSortAndNumber-master
1.0
quick_map_services
0.19.27
Serval
3.10.2
shapetools
3.4.2
splitmultipart
1.0.0
SpreadsheetLayers
2.0.1
VectorBender
0.2.1
ViewshedAnalysis
1.7
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.5
processing
2.12.99
sagaprovider
2.12.99

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[elpaso]

I tried and I could not reproduce the issue: my second map is named "MAP 2" as expected.

[nicogodet]

@elpaso If you copy and paste, the name is identical (which, I believe, is expected).

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.