Misleading behavior when copying style while using layer variables

[qgib]

Author Name: Martin HOFFMANN (Martin HOFFMANN)
Original Redmine Issue: 15912
Affected QGIS version: 2.18.0
Redmine category:gui

---

Qgis now offer a powerfull variable defining mechanism with three level (Global,Project,Layer)

On the other hand the "copy style" drop-down menu in the layers panel of the GUI offer a convenient way to re-use an existing style.

One is tempted to copy style from one layer to an other that share the same schema but have different variables.
However as of now copy style behavior is to overwrite variables from the destination layer using the copied layer variables.

This is in my opinion a very misleading behavior and greatly cripple the usefulness of the variables mechanism when both tools are used together.

It would be more coherent if "copy style" only overwrite the styling but let the layers variables untouched.
Variables in my opinion are a kind of data properties so it's very counter-intuitive that a styling tool get to alter them.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• easy_fix was configured as 0
• regression was configured as 0

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.

---

• resolution was changed from to end of life
• status_id was changed from Open to Closed