Console feature gaps v2/v3

[kschiffer]

Summary

We need to organize our work towards closing the current feature gap of the v2 and v3 console. This umbrella issue keeps track of the progress.

Why do we need this?

• We should not work on completely new features until the v3 console can provide all features of v2 console.
• Organizing our process / roadmap

What is already there? What do you see now?

We already provide most of the features that users know from v2, but there are still some gaps.

What is missing? What do you want to see?

General

• Profile settings (Name, Description, Email, Profile Picture, Delete own account) ⟶ Introduce new account app (to replace oauth app) #1422
• Providing Japanese and Chinese language version of the console ⟶ Provide web UI and backend message language translations #2435
• Filters for event streams ⟶ Event stream filters in console #2231
• Using maps to set location values ⟶ Set Devices and Gateway location with map #1380

Applications

• Providing payload format testing (dry-running byte payloads through the payload formatted) ⟶ Payload format testing #2232
• Providing template tiles for webhook integrations ⟶ Tiles for supported webhook integations #945
• Storage integration (TTI issue) #1830

End Devices

• Showing end device statuses in end device list ⟶ Determine end device statuses #2436
• Showing the Device EUIs in the end device list ⟶ Show the end device's EUIs in the end device list #2437
• Showing end device last seen and frame counts in device overview ⟶ Show latest uplink message and up- & downlink fcount #2167
• Resetting frame counts for end devices ⟶ Resetting frame counts for end devices in the Console #2434
• Scheduling downlinks ⟶ Support Downlinks via the Console #1948
• Simulating uplinks ⟶ Simulate uplinks in the console #2234
• Setting frame counter widths ⟶ Allow setting frame counter widths of end devices in the Console #2438

Gateways

• Setting and displaying gateway manufacturer info (Brand, Model, Antenna(s), etc) ⟶ Setting and displaying gateway manufacturer info in the Console #2441
• Setting automatic update behavior ⟶ Setting gateway automatic update behavior in the Console #2439
• Setting Indoor/Outdoor location flag ⟶ Setting indoor/outdoor location flag for gateway antennas #2440
• Show "Last seen" when a gateway is offline ⟶ Show "Last activity" when a gateway is offline #4850

@htdvisser @johanstokking please review the list. There might be things in there that we actually don't want to add to v3, or in different form.

[johanstokking]

I'm very happy with the overview issue. And I think it's good to have the issues filed. We can then prioritize them and put them in the concerning milestones.

[kschiffer]

I filed all issues now. @laurensslats any specific priority you want us to respect?

[benolayinka]

@kschiffer how about creating users in the console? This is still CLI only

[kschiffer]

Yes but this is not a v2/v3 feature app. You can open a separate issue for this so we can track this.

[kschiffer]

I'll move this to the Backlog milestone since the individual issues are already prioritized correctly and this issue is more to keep track overall.

[johanstokking]

I think it's time to close this, especially because we have individual issues that can be tracked.