Can we please talk about how crazy it is to actually relocate/rename a project?

I've approached this subject before with mixed results. The conversation was useful in that I learned about the archive functionality. However, we never really got to the root of the problem which is how insanely strange the whole work flow is around how to save projects, how to save a project from a working session spawned from a template, and more importantly, how to relocate a project.

Here's what we know.

Nobody knows they're going to sit down and write a song named "Panda" (or whatever, I just like to use my cat's name at random). Instead, what people (hopefully) do is load up a session from a pre-configured template and start writing music. At some point, if they like what is happening, it becomes a good idea to save it. Of course, it's not reasonable to expect they actually know what the thing is yet.... it's more reasonable to expect they'll treat it like the thing it is; a scratch track or an idea of sorts. Given the odds on that, they want to save it to /data/music/ideas/idea1/idea1.qtr

We all know how weird the above is to accomplish.. It's so strange... it's like you have to navigate to /data/music/ideas and then specify a "Project" directory (I think?) and then... I don't even know as I can't exactly remember. All I know is that there's some kind of forced logic applied that makes very little sense from a end user perspective. Of course, I completely believe this portion of the work flow was created to try and make things easier on the end user. It just doesn't feel that way at all and instead has a very "Microsoftish" kind of feel to it. I just want to know specifically where I'm saving my .qtr file. The only way for me to clearly know is to allow me to specify that exactly and remove all the abstraction. Of course, there's also this need to save what I'll call the "session data". This is where I'm assuming the need to hide all the specificity comes into play but why is that so necessary? Just allow me, as the end user to specify *exactly* where to store it? I don't want black magic to decide. I don't want to "have to know how this particular software thinks and behaves" when it comes to something as basic as knowing where my data is stored.

So let's say you made it through that and now you've got your little idea stored in a proper location on disk. At some point, it's reasonable to believe that idea is going to grow into an actual song. It's not going to be referred to as "idea1" forever. At that point you're going to want to relocate the data to a more appropriate location on your disk. Please, let's just all admit... this is a nightmare. I could certainly take the time to sit here and document all the tedious steps involved, making use of .qtz functionality, verifying, etc... but we should all know at this point how much of a challenge this process is. In fact, I'd even suggest maybe we do not know simply because there really is no documented or built in process at all. Don't get me wrong, I've fought the battle time and time again, enough to be able to accomplish the task at hand. However, I have to take the stance that nobody should have to work this hard (archiving, unarchiving, editing files by hand, verifying, etc) just to manage files.

So seriously, can we just admit this area of Qtractor has been overlooked for far too long? This is such a good DAW for so many reasons. It's a shame basic project management is so neglected.