View Assignments in Work List [2]

[michaelkleinhenz]

Reference: 1608E068

Description

As a user, I want to see the assignment of a work item in the work item list view.

Functional Acceptance Criteria

1. The work item list view shows the current assignee in the list entries.
2. The assignee is not editable in the list view.

Non-Functional Acceptance Criteria

None.

Note: the implementation should use the new api done in story #526.

Dependencies

1. Userstory Set / Remove / Update Assignments in Detail View [13] #341

Refer UX design here

Core Tasks

• Make WorkItem-List API to follow jsonapi specifications Make WorkItem-List API to follow jsonapi specifications  #528

UI Tasks

• Consume jsonapi based WorkItem List Consume jsonapi based WorkItem List fabric8-ui/fabric8-planner#377

[Mgranfie]

@michaelkleinhenz the current designs have the ability to assign a user from the list view. Is this a dev limitation? If so let us know @mindreeper2420 so we know how to move forward with you.

[aslakknutsen]

@Mgranfie This is not a dev limitation.

[pranavgore09]

The assignee is not editable in the list view.

Considering this comment is old, I am just confirming that it is still valid @michaelkleinhenz . We are not updating assignee from list view.

@Mgranfie : Can you please give me the link to wireframe of list view with assignee column ?

[michaelkleinhenz]

@pranavgore09 in general, UX works ahead of implementation and defines features that are not necessarily in the current "iteration step" of the the implementation (aka this story). You, as the assignee, should decide if it is in the story or not. Some points to be considered:

• is the story getting too large? So is it still a "reasonable" chunk of focussed work that can be done in a sprint by the team without compromising other implementation work?
• is the story "exceeding context", does the story implement several different usecases or contexts?
• is the task to be added to the story difficult to implement or will add considerably more work? (this is basically a condensed consideration of the above two things).

My 0.02€ on this: I think allowing change of assignee from the list does not add considerably more work and would not exceed the scope, so I would add it to the story.

[Mgranfie]

@pranavgore09 @michaelkleinhenz @mindreeper2420
InVision Links to the Wireframes:
(I don't have permissions to edit this story, adding links here...)

Desktop Prototype:
https://redhat.invisionapp.com/share/2D92EG6BH

Mobile Prototype:
https://redhat.invisionapp.com/share/AH8X9RLU3

Mobile Workflow:
https://redhat.invisionapp.com/share/PW95K913C

[pranavgore09]

thanks @michaelkleinhenz , 😆 Got better clarity.
As per the designs by @Mgranfie , assignee is visible on detail page only.

Story: View Assignments in the work item list.

UX:

• Wireframe - where to show assignee on work item list.

UI:

• Read work item fields and show assignee on list view.

Core:

• No additional tasks (Assignee is already present in the fields.)

[pranavgore09]

Hey @mindreeper2420
Can you please help UI team to show the place where to display assignee on list view ?
https://redhat.invisionapp.com/share/2D92EG6BH this List view is without assignee column. We will need the prototype which has list view with assginee column.

[AdamJ]

@pranavgore09 here is the correct link: https://redhat.invisionapp.com/share/T89G321KQ#/195933683_A-0100.

The Assigned User's profile picture appears to the left of the kabob menu. If there is no picture, then the generic user icon (pficon-user) is shown, with a box around it.

[pranavgore09]

@mindreeper2420 thanks, got it.
Currently it is only assignee but in future there will be more like created_by in the same fashion(show profile pic).
And we do not have column headers like - title, id, assigned to etc etc.
So, when we show created_by in future, it will not be predictable that which column means what.

I can think of - when we hover on the icon it should say Assigned to USER_FULL_NAME in this story.
Is something like this already there ? I could not interact with the link you given so I thought I just write you this.

[michaelkleinhenz]

Completed in Sprint#124.