Foreman Tasks Demo - Presented by Ivan
> > >
Edit fields icon too far away from fields. With multiple rows it can be
difficult to determine which edit icon goes with which row. In the event of
no item in the row, there is a large gap between the edit and field label.
This problem can be found throughout the application. Additional research
should be done to determine best solution/placement or if it is needed at
all being that there is a highlight - and an inline edit is available.
···
> Table
Icons for visual state for status
PatternFly Listview might be beneficial, we would have to look at the
content.
Notification drawer would be helpful in letting users know the task
status
Sort column headers - This issue has been bugging our customers.
Click an item>
Notification drawer would be helpful in letting users know the task
status
Start at vs Started at…. better define labels better.
Spinner + pending + status bar… two visual elements displaying the same
progress.
Perhaps “100% Complete” could show Completed items out of Total
items, which the bar displays the % complete.
-
Only show percentage as a whole number.
-
The arrangement of the content could be improved to group related items
and buttons together. I’ve made a note to look into this.
Perhaps show the details of statuses from Running steps tab near the
status.
Upon additional thought. Is there enough content in each of the tabs
to warrant their own tab? It seems like the tabs are heavily inter-related
and it may be helpful to have some of that information grouped together.
Moving from two-pane view would offer more screen space to potentially fit
content together.
Click an item>Errors Tab>
I do not think an inline notification box is needed here.
New Repository>General Information>
Required fields such as name, should be marked as required.
Other Notes:
Make Tasks more integrated into the workflow
Ivan Necas wants tasks in a table screens from other products.
dLobatog - “which proxy executes which task?”
During the meeting I had made the note that the content within the details
of a task could be arranged to be more easily understood. I wanted to share
some brainstorming/discovery mockups my peer Jessica did for me. We placed
the content in the order that we understood it, but welcome any feedback if
we assumed wrong on the order or grouping of content.
I'm also including some exploratory work done on the main tasks page and
conversion to list view.
···
On Tuesday, January 24, 2017 at 1:38:21 PM UTC-5, Roxanne Hoover wrote:
>
> Foreman Tasks Demo - Presented by Ivan
>
>
>
> > > >
>
> Edit fields icon too far away from fields. With multiple rows it can be
> difficult to determine which edit icon goes with which row. In the event of
> no item in the row, there is a large gap between the edit and field label.
> This problem can be found throughout the application. Additional research
> should be done to determine best solution/placement or if it is needed at
> all being that there is a highlight - and an inline edit is available.
>
>
> > Table
>
> -
>
> Icons for visual state for status
> -
>
> PatternFly Listview might be beneficial, we would have to look at the
> content.
> -
>
> Notification drawer would be helpful in letting users know the task
> status
> -
>
> Sort column headers - This issue has been bugging our customers.
>
>
> > > Click an item>
>
> -
>
> Notification drawer would be helpful in letting users know the task
> status
> -
>
> Start at vs Started at…. better define labels better.
> -
>
> Spinner + pending + status bar… two visual elements displaying the
> same progress.
> -
>
> Perhaps “100% Complete” could show Completed items out of Total
> items, which the bar displays the % complete.
> -
>
> Only show percentage as a whole number.
> -
>
> The arrangement of the content could be improved to group related
> items and buttons together. I’ve made a note to look into this.
>
>
> -
>
> Perhaps show the details of statuses from Running steps tab near the
> status.
> -
>
> Upon additional thought. Is there enough content in each of the
> tabs to warrant their own tab? It seems like the tabs are heavily
> inter-related and it may be helpful to have some of that information
> grouped together. Moving from two-pane view would offer more screen space
> to potentially fit content together.
>
>
> > > Click an item>Errors Tab>
>
> -
>
> I do not think an inline notification box is needed here.
>
>
>
>
> New Repository>General Information>
>
> Required fields such as name, should be marked as required.
>
>
>
> Other Notes:
>
> Make Tasks more integrated into the workflow
>
> Ivan Necas wants tasks in a table screens from other products.
>
> dLobatog - “which proxy executes which task?”
>
>
