Workflow Reports/Pages papercuts #15220
Labels
area/pages
area/UI-UX
help wanted
also "hacktoberfest", beginner friendly set of issues
kind/bug
paper-cut
I've used pages "in anger" today, to try and make a report to share with my boss and encountered some paper cuts. None of these are fatal, but I think some of them would make the UX nicer if anyone has time.
Overall the pages experience with markdown editing is SO MUCH BETTER, that I'll continue to use it (especially once sharing/embedded pdfs are fixed), it's really such an incredible massive change that makes publishing reports so much nicer. Thank you everyone who worked on it! Now, on to to the complaint list 😅
<details><summary>...
to work (I'd prefer that to linking.) Workflow reporting - support for expandable sections, table of contents, multitabs etc. #15088"Link to dataset" could be improved by using the dataset name (and showing tags), rather than just the hashed ID. I gave them nice names on purpose.Ah you can uselabel
, which I only discovered by grepping Galaxy's source code. Is there a way this could be exposed in the UI? Or maybe that it defaults to using the HDA name, rather than defaulting to the ID, making discovering this less important?Embedding a "dataset" is different from an "embedded dataset", it wasn't clear why until I inspected the element and saw the Vue object had a URL including essetially "embed this as text" which wasn't what I wanted. Thus, the labels could use clarification that one is text-file only.Seems fixed in 22.05Workflow embed says "It's not shared with your user" (when logged out)Fixed in 22.05, yay!demo page available here: https://usegalaxy.eu/u/helena-rasche/p/test
The sharing really needs to trigger something recursive, looking at embedded objects, and asking the user "You've included this list of wfs/dataests/etc, and you're trying to share your page, would you like to also share all linked objects?" And I guess that needs to show a dialog every time they edit an already shared page to add a new item.
The text was updated successfully, but these errors were encountered: