@CharlesGibbsNam First thanks a million times for doing this. This should help:
Plus when you onen New Issue>Bug report it will list some things to fill in, just fill them in as best and completely as you can. If anyone needs more info they will ask.
I will be able to confirm this as a valid “bug” or as I prefer “BUG”. There are 2 problems IMO. User should be able to use UUID in KDE Partition Manager. Second I am less positive of but unless some convention has changed in Linux or OMLx then using device node in /etc/fstab should result in a mounted partition and that is not happening. But the current situation is not achieving the desired results.
Edit: I should add that currently OM devs are buried trying to get a much needed new release out. As a practical matter one needs to manually set entry in /etc/fstab using UUID.
For me this works for my /Data partition which I use without formatting ofc in multiple system partitions.
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=1C54-AB1D /boot/efi vfat noatime,umask=0077 0 2
UUID=2b9f19dd-4588-43ac-bb06-a9a4199b54c6 /Data ext4 noatime 0 2
UUID=26365bee-8e68-4e8a-b7c0-f1db3fcd2856 / xfs noatime 0 1
UUID=4c3cce41-bf13-4a68-8c90-2cb7d2a00b8c /home xfs noatime 0 2
tmpfs /tmp tmpfs noatime,mode=1777 0 0
/dev/nvme0n1p8 /dev/nvme0n1p8 xfs nofail 0 0
/dev/nvme0n1p8 is the one added with KDE Partition Manager. I question that nofail also, perhaps should be noatime followed by 0 2.