For example, let's say I want to use legend to keep my "mental context" for tasks I have to do. But at work maybe I am using something like Azure Devops to keep track of my workload (<barf emoji here> Don't judge, it's just a theoretical example, ok?). When looking at an ADO ticket ideally I would want to quickly open up the Legend item that it refers to by embedding a link.

This is not something that can be done "out of the box" in part because Legend's SPA design. When I move between items, Legend does not expose a link in the browser URL bar could potentially be used to navigate directly back to that item. The suggestion is to either 1) have the browser URL follow the currently viewing page (https://www.legendapp.com/?id=<big ugly guid>) or else create a new function to generate such a link from the command menu. The target of the link provided would open a web page directly focused on the item.

This would be even more powerful if the link provided could take the user directly to the view of the item as well. That would allow linking to specific boards / views. However the most important point would be to go to a specific item.

It doesn't seem possible to restore normal expected behavior without force-quitting Legend and restarting it, afterwhich the behavior is normalized.

I am unable to reproduce the behavior in a predicable manner.

I'm also rebooting my personal "bugs log". Since bug-squashing is the current mission, I'm going to share it here regularly. I'm thinking probably weekly.

So, here's what I hit in my first 7 days (without even trying). All are on W11 desktop app unless tagged #mobile, in which case it's iOS 26.3 / iphone 17. Beta version, in both cases. My definitions for "priorities" are at the end; if we are using some standard prioritization here, I didn't find it, but I'll start using it if someone can point me to it.

I'll admit right up front that I log a LOT of what I think count as "UX" bugs. These aren't functional but they send a very clear message to me as a user about the quality of the app. Especially given that Legend is going to be unfamiliar and strange to any new users, and that it has to claw its way up from the bottom of SEO, I think it's very important to show that it has been made with attention and quality. When I hit UX issues while trying out a new app, I immediately start to question how long that app is going to be around, and whether I should even keep trying it. Normally, severe UX issues are justification enough for me to just delete an app straightaway. It smacks of a lack of attention to detail.

High Priority

• None

Med Priority

1. #mobile app works for viewing but is unusable for editing/entry. Any interaction with the screen or keyboard while in "item edit" mode scrolls all contents off the top of the screen. Typing works, but happens offscreen.

2. Dismissing the add-hyperlink dialog box from within #notes by pressing "return" dismisses the box, but does not apply the link as expected; clicking on the "Insert" button does apply the link and dismiss

   • Works as expected when adding a hyperlink to Item text, just not within notes.

3. Multi-item operations do not work on contents of popup pane. Includes hotkeys and RMB-menu actions (like delete)

   • Works for a single item, but if >1 are selected, no response

4. Can't type after indenting in popup #panes

   • Create an item or place insertion at end of existing leaf item.

   • Press Return

   • Press Tab to create a child (insertion point moves as expected)

   • Attempt to type -- nothing happens

   • Press Return again (creating a second child)

   • Attempt to type -- now it works

5. #panes bottom status bar: "document" item count increments correctly when adding a new item but decrements by two when deleting it. It will even go negative!

   • Occurs in new document with just 20 items. Bullet and Task prefixes, no projects, no parents. No filters applied. Video at: https://app.screencast.com/2IX4EiNR3CzFa

6. Null focus for #keyboard navigation after zoom-out.

   • Pane will scroll with arrow keys but there is no insertion point. Does not happen after zoom-in, only out

Low Priority

1. "Collapse" commands toggle between expand/collapse, but "Collapse to level X" commands only collapse #hotkeys

   • Inconsistent, AND there is no explicit "expand" or "expand all" command to pair with "collapse to X"

2. #settings in "hotkeys": "highlight in all panes" should be renamed to show in all panes"

   • Otherwise, "highlight" and "highlight in all panes" are confusing because they are talking about two totally different kinds of "highlighting".

3. #settings in "hotkeys": "Focus Mode" is listed under both the "Screen" and "Pane" sections. The entry under "Screen" doesn't work.

4. #settings in "hotkeys": "Ctrl + L" can not be assigned to any function (UI does not respond).

5. #settings in "hotkeys": key combinations that have already been used for other commands are accepted without complaint.

   • This used to be flagged and prevented

   • When allowed, it stops the hotkey from working for either of the commands

6. #hotkeys after invoking "Search" with the keyboard, pressing "Esc" does not dismiss the search modal but instead shifts focus to the Filter field.

7. ALL #tags in the tag autocomplete-picker are rendered with the style from .tag{} in: Display Settings→Colors, even if they have unique styles defined in the #theme under: Display Settings→Tags.

   • Also, there's not enough padding around them and the picker is crowded, especially near the number showing how many instances there are.

8. #performance lags after large-ish multi-item copy-pastes, ~50 lines

   • Really bad when pasting from workflowy. Still bad even when coming from Obsidian though, and that's native .md

PRIORITIES

• Low - Efficiency, Convenience, & Polish
  Aka "UX" bugs. A function does work, but is either difficult, slow, frustrating, or incomplete.

• Medium - Noncritical
  A standard feature does not work as expected, or only partially works.

• High - Risk of data loss
  An action either directly causes data loss or sets up a situation where loss is more likely.

Solution: Check with the user before making any changes that result in Google Calendar changes. Adding a new item with autosave is fine.

Problem scenarios

1. Trying to drag an item into your notes may move the calendar item to a different time. The drag experience is touchy; it will even sometimes move the calendar block if you just click once

2. Deleting a note with a calendar item (the item itself or as part of a block). This will delete the calendar event completely.

These two scenarios, when there are additional participants in the calendar event, create confusion, embarrassment, and personal brand damage to our users. In today's scenario, a customer that I met with this week sent a canceled RSVP for an event that already happened.