Skip to main content

Hey,

Before I start - love making folders mandatory. A+ feature in my book.

Unfortunately, what I’m struggling with how is: How do you distinguish which folders are which?

I’m going to have to use the old terminology to explain this but here we go:

  • Board Group name: Support Operations
    • Board Name: BCP
      • ​​​​​​​Section Name: Tool 1
      • ​​​​​​​Section Name: Tool 2
      • ​​​​​​​Section Name: Tool 3
  • Board Group name: Processes
    • ​​​​​​​​​​​​​​Board Name: Tool 1
    • ​​​​​​​Board Name: Tool 2
    • ​​​​​​​Board Name: Tool 3
  • Board Group Name: Release Notes and Updates
    • ​​​​​​​Board Name: Salesforce Release Notes 2023
      • ​​​​​​​Section Names: Jan, Feb, March etc
    • Board Name: Salesforce Release Notes 2022
      • ​​​​​​​​​​​​​​Section Names: Jan, Feb, March etc

I’m part of the Operations team, and the collection I have is a one stop shop for BCPs, Processes, Systems and Features that were previously seperated out by Board Groups, Boards and Sections. Because we could only add Boards, on the previous card creation, it meant that everything had a unique name, and in the example above, I was easily able to distinguish between where the card was supposed to go.

Now, because Board Groups, Boards and Sections are all called “Folders” it’s now a lot more difficult to figure out where cards should go, because “Tool 1” can actually appear multiple times when you’re searching for a folder.

Here’s a real life example from the collection, from the above:

 

Historically, I wrote  a card, assigned it to the Board, then dragged it into the it’s associated section, which was fine.

But now, because they’re all Folders, this is what I see:

There’s no way to distinguish which July a card should be going into, without going in and retrospectively updating all the naming conventions of the, previously known, sections.

Could you please add a directory to this section?

What would be VERY helpful would be:

We have multiple collections like this, and this is resulting in extra admin time of adding it to multiple folders, then going through each one to see where it is located, and then deleting it from where it shouldn’t be.

+1 to this - I run into this problem frequently!


Have similar structures here, and this is a common naming pattern for versioning documentation to match product versions, so being able to disambiguate folders with the same name in different places would make life a lot easier.

 


Same issue. We can rename our folders if needed, but wonder if there is a more universal solution. 


The following idea has been merged into this idea:

All the votes have been transferred into this idea.

The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Agreed. I would love to see less focus on AI features and more focus on basic usability features.