Request: "I’m on it"

[webjay]

• Ownership for Urgent request. There should be no “WIP” in the menu. I had “I own it”, and actually I would like back to my first idea “I’m on it” instead. Once you pick this, it does 2 things simultaneously:
  • changes the status of the request from “Open” to “in progress”
  • give ownership to the person who clicked

[ghtca]

Jacob: "Btw, statuses can be edited here: https://app.mongohq.com/asapp/mongo/asapp/collections/status"

Watch out! Statuses are handled differently whether it is a "FYI" request or a "Urgent" one. There is no concept of "Work in progress" for a FYI request.

[webjay]

I now remember/see you want it like this:

FYI:

• 10-4
• Closed

Urgent:

• I'm on it
• Closed

The problem with that is that, from a user experience point of view, a select tag is interpreted as a property of the object, in this case the request, whereas a button can be interpreted as something related to the user. So how about a button group?

With that we don't really need the status, only a way to set the request as open or closed.

[webjay]

I made some changes to the chat page: http://asapapp.herokuapp.com/#chat/53d8ed4604adee0200461176

Acknowledgements needs work, something like owner. (#107)

Let me know what you think. (I like it)

[ghtca]

you are talking about the "Monitor" page, not "Chat" right?

I don't see how I can close or re-open the Request. There is a "10-4" on urgent requests, which should not exist, and a "I own it" on FYI request, which should not exist either.

And now we're using 2 lines when there is an Owner, instead of 1 on my design.

I really want you to stick to my design. For the record, I spent almost a full day on it, trying different things, different UI / functionality. I thought it was the best way to explain requirements, since the prototype has every case / state for each type of request, with the corresponding buttons/drop down. I don;t care so much about colors, but functions, labels, space are important. Thanks!

[ghtca]

Also, when I submitted a Help request for "Record" with thierry2, and I was monitoring with thierry, and I had subscribed to only AV, I still saw the request coming in the monitoring page. Looks like the filtering is still not done? Let me know if this is the case or if it is buggy and should investigate.

[webjay]

The reason I have the same buttons on a 10-4 and urgent, just one disabled, is because the user will learn their position.

But okay, I'll follow your UI. This is the latest, correct: http://evt.dispeak.com/dispeak/asap/test2/Monitor-5.htm

One more note, you would have to click the select to see the 10-4 option.

[webjay]

thierry is an admin and will see everything. (https://github.com/webjay/asapp/issues/100#issuecomment-50718000)

[ghtca]

I did not see one was disabled. not clear enough. Even if clear, would be confusing, would wonder what I need to do to make it visible.

The dropdown is an extra click to Ack or "own", but I actually like it here, because it practically almost acts like a confirmation button without one. You need to be committed to Ack or Own, and I don't want ppl to click on those by mistakes. And because you won;t need to Ack and Own too often

[ghtca]

ok for "thierry is admin". I need to do testing with other accounts then. Thx. I have some ideas about filtering to make it more clear. I think we may want to add a super small line on top saying something like "Displaying AV / Records requests". + a configure button.... But takes valuable space... After more testing and playing I'll have a better idea.

[webjay]

I'm using bootstrap-select for the select box.

[webjay]

I'm having some trouble styling bootstrap-select but the functionality is there. Might need some polish.

[webjay]

@ghtca I got to here and saw more problems than solutions, so I'm bringing buttons back, and did that in about 10 minutes. I suggest we use buttons until everything else is as you want it. Otherwise I need to redo the select as the path I chose didn't go in a good direction. Sorry.