Feature Request: Comments / Notes within items

theschles
theschles
Community Member

Hi all,
I just added a CPK gift card number and pin to 1Password and thought "I'd like to keep track of how I'm using this".

I don't see a way to add comments / notes within items. Am I blind and it's there?

If not, please add?


1Password Version: 8.10.44
Extension Version: Not Provided
OS Version: macOS 14.6.1
Browser: Not Provided

Comments

  • @theschles

    The notes field is only visible in edit mode (if it's blank). I suspect you've viewed one of your items in normal mode where it would not be visible until you add your first comment to it.

  • theschles
    theschles
    Community Member

    Hi @ag_tommy ,

    I'm wary of putting an item in edit-mode just to add notes...as there's always a risk of fat-fingering the important content...

  • You'll always have your version history if needed.

    👀 💾 View and restore previous versions of items

  • theschles
    theschles
    Community Member

    True...but still...there's a reason why the default mode for a selected item is "view" and not "edit".

    Commenting in visual collaborative applications is often provided as a midway level of access between:

    • "view only" (or no access), and
    • "full edit"

    In those visual collaborative applications, comments are considered "annotations" on items.

    For instance: when using a collaborative diagramming tool like LucidChart, if I don't want a user to change my diagram -- or critique it directly within the diagram -- I can grant a user "view only" access so he/she can use that diagram as a reference elsewhere.

    OTOH, if I'd like a user to critique my diagram -- but still not actually change it (I'll do the edits, thank you very much) -- I can grant that user "view and comment" access.

    The "view and comment" access user can then -- for instance -- view a flowchart, select any Process, Subroutine, or Decision block, and annotate those blocks with comments. The blocks don't change...they're merely annotated.

    Does this make sense?

  • ag_tommy
    edited September 20

    Ok, let's turn in on its end. What about tags? That's how I keep track of some things without directly editing it. I have tags for the city, store, year, and so on. You can drag and drop to apply tags. Otherwise, you have to enter edit mode to allow data entry. It's not possible otherwise. The item is locked in a view-only mode, which is where the feature request comes in.

    I'm not trying to argue with you. Please don't take it that way. I'm only trying to offer some suggestions that you might use now. Feel free to use any or none of them. That's the beauty of this community. So many of the suggestions I use have been shared by others at one time or another.

    Would I be correct if I said you're looking for a hybrid approach where the note section is always exposed? The only trouble I see with this is that some folks might accidentally remove a note by errantly typing. Some of our users store very important information in their notes. That unlocked behavior could expose them to potential data loss.

    I'm happy to pass the recommendation along to the team for further review and consideration.

  • theschles
    theschles
    Community Member

    Hi @ag_tommy -- welcome to the pleasure of requirements gathering...one of my specialties.

    I'm actually asking for a concept of either:

    a) CHANGE the current design of the "Notes" field:
    FROM a "Notes" field with a multiplicity of 1 -- where the initial value is empty
    TO a "Notes" field with multiplicity of 0..*

    ...with actions:

    • "add a note"
    • "delete a note"
    • "edit a note"

    -- OR --

    b) LEAVE the current design with a "Notes" field with a multiplicity of 1 note -- where the initial value is empty
    AND ADD A NEW FIELD named "Comments" with a multiplicity of 0..*

    ...with actions:

    • "add a comment"
    • "delete a comment"
    • "edit a comment"
  • theschles
    theschles
    Community Member

    I'll also add that "tags" are usually used for small-quantity keyword/term categorization of items -- made user-friendly by developing a quick lookup table of previously-used keywords/terms to make it easier to categorize items into distinct buckets.

    In this case, this concept of 0..* notes / comments per item are one-offs just for that item; their content might be searchable -- but not intended as categorization.

  • Wonderful, I'll get this information before the team. Thank you for sharing and the good conversation. I appreciate the back and forth you provided helping me understand your desire.