Arvados

21944-work-launch-description @ f1a4461e3171a687d85c1306662ddd067b6930ca

developer-run-tests: #4377

21944-work-launch-description @ 7b21bc70083b7cc2ab240d99256ab33ff6471143

developer-run-tests: #4386

• All agreed upon points are implemented / addressed.
  • now displays the workflow description on the launch page.
• Anything not implemented (discovered or discussed during work) has a follow-up story.
  • I didn't make it collapsible as this seemed like it would require setting up a more complicated React component with states than I'm used to dealing with.
• Code is tested and passing, both automated and manual, what manual testing was done is described
  • updated tests
• Documentation has been updated.
  • improves ability of workflow authors to provide documentation to end users
• Behaves appropriately at the intended scale (describe intended scale).
  • no changes to scale
• Considered backwards and forwards compatibility issues between client and server.
  • n/a
• Follows our coding standards and GUI style guidelines.
  • uses the theme for the title sizing

I ended up moving the 'description' field (for the individual workflow run) to the 'advanced' section, as it isn't frequently used in my experience. I also decided that the initial idea of putting the title and description between the basic form and the inputs was a bad one, which also led to rearranging the fields slightly.

This lgtm!

21944-work-launch-description @ 9ae80e98c68259816e536fed4fee7a2609fed097

Formatted description shows up on workflow launch and in the registered Workflow page.

developer-run-tests: #4390

21944-work-launch-description @ eda85be076f259d5f74b21edf9708cb513b20943

Fix typo.

developer-run-tests: #4392

developer-run-tests: #4395

lgtm!