P: Auto Import to folders organized by date

Adding my voice to the pile.

Would've been really cool to have this work in tandem with syncthing syncing photos from my camera.

I also wanted this feature and found this thread.

I don't *like* this solution but it works for me. 

• Inside of Lightroom, "Select All" on my autoimport folder
• Delete all photos from lightroom
• Run a "normal" import against my autoimport folder using "move"

The above allowed me to get the pictures organized in the folders I normally expect them in and it seems to auto find duplicates if I run the import from my camera as well.

I can't believe how old this request is, so not sure if my reply will help, but FWIW…

Please add the ability to organize by date and choose the folder naming scheme for auto imports, just like you can with a manual import. Basically, add these two controls (and their functionality) to the Auto Import Settings dialog:

On the issue of feature requests and bugs....

Had a quick chat with a friend with decades years of experience in UX. The challenge from their experience is summed up by discovering that forward looking companies don't typically look backwards. Old bugs aren't on the table.

There's a challenge here because the user community eventually loses motivation to report. Some people don't know how to report. Or, you find a work around, you just cope with it, you decide not to do that, you move to another product.

Fundamentally, there needs to be an internal champion who is prepared to take on the challenge and own the problem. In the ideal case, they have enough product experience that they could be seen as a subject matter expert for the product. 

They all use a voting / count system to figure out whether to pay any attention to an issue/bug. So to paraphrase, every vote counts, you need to  vote.  

This forum is the place to be the squeaky wheel.

But don't squeak just to vent, you need to articulate the problem in repeatable steps, what is the observed outcome, what did you expect to happen and what is the (business/design) impact?

Use a numbered list to define the steps you went through.

Developers need specific scenarios and use cases to test. They need to find bugs in a methodical repeatable way. They need enough detail to find the edge cases.

There's also the challenge where the end user and the internal developer don't use the same terminology....