Project

General

Profile

Actions

Idea #20932

closed

Workbench 1 loose ends in the documentation to update for Workbench 2

Added by Brett Smith over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Documentation
Start date:
09/13/2023
Due date:
Story points:
0.5

Description

/user/topics/workbench-migration.html can remain as a background page explaining the migration, but it refers to Workbench switching features that either no longer exist or will no longer make sense to promote once Workbench 2 is the default.

/user/tutorials/tutorial-keep-collection-lifecycle.html has a section "Trashing a collection using workbench" that gives narrative instructions for Workbench 1, not 2.


Subtasks 1 (0 open1 closed)

Task #20959: Review 20932-wb2-docsResolvedBrett Smith09/13/2023Actions

Related issues 2 (0 open2 closed)

Related to Arvados - Bug #20890: Remove "switch to workbench 1" from wb2ResolvedPeter AmstutzActions
Related to Arvados - Feature #20850: Notification that workbench 1 is deprecatedResolvedPeter Amstutz09/03/2023Actions
Actions #1

Updated by Brett Smith over 1 year ago

  • Story points set to 0.5
  • Description updated (diff)
  • Subject changed from Update all Workbench 1 instructions throughout the documentation to Workbench 2 to Workbench 1 loose ends in the documentation to update for Workbench 2
Actions #2

Updated by Brett Smith over 1 year ago

  • Related to Bug #20890: Remove "switch to workbench 1" from wb2 added
Actions #3

Updated by Peter Amstutz over 1 year ago

  • Target version changed from Future to Development 2023-09-27 sprint
Actions #4

Updated by Peter Amstutz over 1 year ago

  • Assigned To set to Brett Smith
Actions #5

Updated by Brett Smith over 1 year ago

  • Related to Feature #20850: Notification that workbench 1 is deprecated added
Actions #6

Updated by Brett Smith over 1 year ago

20932-wb2-docs @ a3548962424791bf575eb1ef68aac09b785cfdbd - developer-run-tests: #3828

  • All agreed upon points are implemented / addressed.
    • Done
  • Anything not implemented (discovered or discussed during work) has a follow-up story.
    • N/A
  • Code is tested and passing, both automated and manual, what manual testing was done is described
    • See above. Note these are only doc changes, so only the linkchecker test should be relevant.
  • Documentation has been updated.
    • N/A, this is already a pure documentation update
  • Behaves appropriately at the intended scale (describe intended scale).
    • N/A, this is already a pure documentation update
  • Considered backwards and forwards compatibility issues between client and server.
    • This does remove Workbench 1 documentation from some pages. We are already doing that on other pages, so this is consistent with the general direction of our documentation.
  • Follows our coding standards and GUI style guidelines.
    • Done
Actions #7

Updated by Lucas Di Pentima over 1 year ago

This LGTM, thanks.

Actions #8

Updated by Brett Smith over 1 year ago

  • % Done changed from 0 to 100
  • Status changed from New to Resolved
Actions

Also available in: Atom PDF