Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Update modules: Onboarding

Description

In MEN-2284 we create the most common application-based update modules out-of-the-box. In order to improve onboarding experience, we leverage one or more of these to deploy application updates. This will replace today's full-image updates and have wide-ranging impact; we can remove demo images, virtual devices both for on-prem onboarding and HM.

User value (why)

  • For new users to more easily get started with real application deployments using Mender

Size (SP)

  • TBD

Acceptance criteria

  • Onboarding tutorial (UI help tips) uses a demo application (MEN-2393) instead of full image updates

  • Getting started documentation updated

  • Mender server (& Hosted) Help section updated

  • Unused images for physical devices removed from docs & not generated during HM signup

References

Risk & mitigation

TBD

Market Goal

Improve time-to-value by lowering barriers to real application deployment during onboarding
100% Done
Loading...

Checklist

Activity

Show:

eystein.maloy.stenbergApril 23, 2019 at 8:32 PM

There were 11 SP "left" in capacity this sprint we should use against this Epic. Perhaps you could start planning the implementation tasks and add the first one(s) to the current sprint?

eystein.maloy.stenbergApril 22, 2019 at 11:39 PM

given the user tests I think we are ready to start implementation here now.

Could you please create appropriate development tasks together with and update the ticket status accordingly?

We should ideally pull in some tasks into next sprint (starting Apr 23rd). If there is not enough time to create the initial tasks I suggest we simply use remaining capacity against this epic. Does that make sense?

eystein.maloy.stenbergApril 4, 2019 at 6:43 PM

Nice!

Michael ClellandApril 4, 2019 at 10:17 AM

makes sense - I adjusted the wireframes at https://invis.io/NQRDDIWX8TG

Clicking inside the copy&paste box will now show "waiting for device" in place of the "continue" button, and when a device tries to connect it will automatically go to the "Pending" tab. (I mocked this in the wireframes by using a timer)

eystein.maloy.stenbergApril 3, 2019 at 7:33 PM

Main area of confusion now is where user is expected to copy & paste commands into the terminal of the device.
It is a context switch (from Mender UI to device shell).

Can we make this more explicit or perhaps halt the next steps of the tutorial until the device is connected?

Fixed

Details

Assignee

Reporter

Labels

Epic Name

Goals

None

Priority

Backlog

yes

Zendesk Support

Checklist

Created February 11, 2019 at 9:56 PM
Updated November 28, 2019 at 1:41 PM
Resolved July 31, 2019 at 5:19 PM