[UI] maas should allow comment on why a system is broken

Bug #1441160 reported by Scott Moser
48
This bug affects 7 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Wishlist
Unassigned
maas-ui
Fix Released
Unknown

Bug Description

we just had a situation where a collegue of mine asked "Why is system X in BROKEN". I did not know, as another team member had put it in.

It would be nice if maas did 2 things:
a.) stored the user who did this
this would allow me to ask the user who did, why it was in BROKEN
b.) stored a text field as "why".
this would allow us or the user to input a external tracking id or comments as to what was wrong.

Tags: ui oil
Changed in maas:
milestone: none → 1.8.0
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

This is a need we've come across in OIL, where we have multiple people marking nodes as 'Broken'.

tags: added: oil
tags: added: ui
Changed in maas:
importance: Low → Wishlist
milestone: 1.8.0 → next
Changed in maas:
milestone: next → 2.2.0
summary: - maas should allow comment on why a system is broken
+ [UI] maas should allow comment on why a system is broken
Changed in maas:
milestone: 2.2.0 → 2.3.0
Revision history for this message
Koaps (koaps) wrote :

I would extend this to allow comments in general for a machine, it would be nice to be able to note the asset tags for the machine without having to add a tag, or other info like deployment date

Changed in maas:
milestone: 2.3.0 → 2.3.x
Revision history for this message
Rod Smith (rodsmith) wrote :

I'd like to second Koaps' comment; this feature could be useful beyond broken systems -- to note system-specific peculiarities, the role it's playing in a network, etc.

Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: [Bug 1441160] Re: [UI] maas should allow comment on why a system is broken

I believe this is already supported in the backend, but would need UI
integration! Patches welcome!

On Mon, Jan 29, 2018 at 3:19 PM Rod Smith <email address hidden> wrote:

> I'd like to second Koaps' comment; this feature could be useful beyond
> broken systems -- to note system-specific peculiarities, the role it's
> playing in a network, etc.
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1441160
>
> Title:
> [UI] maas should allow comment on why a system is broken
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1441160/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; milestone=2.3.x; status=Triaged;
> importance=Wishlist; assignee=None;
> Launchpad-Bug-Tags: oil ui
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: jason-hobbs koaps rodsmith smoser
> Launchpad-Bug-Reporter: Scott Moser (smoser)
> Launchpad-Bug-Modifier: Rod Smith (rodsmith)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

Revision history for this message
Lilyana Videnova (lilyanavidenova) wrote :

As of 2.6 any admin can add a note to a machine in the UI - the notes are displayed in the listing and can be edited in the configuration pane of each machine.

We are working on surfacing the note field when a machine is specifically marked broken.

Changed in maas-ui:
importance: Undecided → Unknown
Changed in maas-ui:
status: New → Fix Released
Changed in maas:
milestone: 2.3.x → 2.9.0rc2
status: Triaged → Fix Committed
milestone: 2.9.0rc2 → 2.9.0rc1
status: Fix Committed → Won't Fix
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.