Problem

Now that Drupal 8 has been launched and users are working with configuration management some obvious usability issues are arising. The purpose of this meta issue is to list and prioritize them so we can see a significant improvement in usability by 8.1.

Issues prioritized by UX impact

  1. #2642398: Add an option to strip UUIDs from imported/exported config files
  2. #2642386: Imported configuration is placed in an inaccessible subdirectory (bug, but one that seriously impacts usability)
  3. #2572503: Add confirm dialog before full configuration import
  4. #2540794: Configuration synchronization UI does not distinguish between an empty staged configuration, and staged configuration that matches active.
  5. #1714396: Offer ability to 'lock' config changes
  6. #1497268: Add revert functionality to Config entities
  7. #2378503: Save configuration in a consistent order
  8. #2503263: Config import validation needs to provide error messages
  9. #2428045: Comparing active storage to install storage is problematic, install storage may change anytime
  10. #1914362: Allow configuration system to recursively search directories

Priority here is an initial swag by tkoleary to stimulate discussion.

Comments

tkoleary created an issue. See original summary.

tkoleary’s picture

tkoleary commented
Issue summary: View changes
tkoleary’s picture

tkoleary commented
Issue summary: View changes
tkoleary’s picture

tkoleary commented
Issue summary: View changes
tkoleary’s picture

tkoleary commented
Issue summary: View changes
tkoleary’s picture

tkoleary commented
Issue summary: View changes
tkoleary’s picture

tkoleary commented
Issue summary: View changes
jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Just a suggestion about this Meta -- use the Related Issues field to add the issues as well. Pick a direction -- either add them all here as Related to this one, or on each sub-issue, add this issue as Related there. Either way. But having them as Related is much better than just listing them in the issue summary here because they will maintain links in the sidebar.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Or, alternatively, edit each of those issues and mark this issue as the parent issue in all of them. Then they'll show up as children here.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Yes... They should all have some issue relationship to this issue, one way or the other. I don't care which, but without the relationship being defined issues get lost.

tkoleary’s picture

tkoleary commented

I was not even aware that was the way to do it.

Discoverability problem in D.O. :)

xjm’s picture

xjm
she/her
Primary language English
commented

d.o has now added an "add child issue" link in the sidebar, which should help in the future. :)

Meanwhile, I will make this meta the parent of those.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.