[PRD-DOC] - Tasks card enhancement document

[Pratiyushkumar]

PRD for Tasks card enhancement Requirements

Author - @Pratiyushkumar

Overview To make task card UI and functionality the same on status-site and my-site we are bringing enhancement because currently, we have two different designs and functionality for one feature.

Problem

• Basically we have a task card feature available on 2 different sites, Ideally expected behavior of the task card feature should be the same on both my-site and status-site, but currently, the ideal condition is not being followed, and on both sites UX is different.
• Currently to update the progress of tasks developers have to go to my site to update their task progress and on status-site they are only able to track their tasks.

Objectives After this proposed enhancement is done, the user will be able to have a similar UX on both sites because the user will be able to perform all the actions from any of the sites and the output will be the same on both sites.

1. User will be able to track the progress of their tasks from any of the sites.
2. User will have a progress bar to update their task progress from any of the sites.
3. Users will be able to raise extension requests from any of the sites.
4. Users should be able to change their task status from any of the sites.
5. Either super user/admin/task assignee will be able to do the above Objectives.

Personas There will be two types of target personas -

• Task assignees
• Super user or admin.

Use Cases

1. Users will be able to update the progress of the task through the progress slider only if tasks are in progress status.
2. Users will have the option to change the status of tasks.
3. Users will be able to raise the extension request for tasks.
4. Users will be able to track their tasks.

Features In

1. On my site we can change the status of the task, update the progress of tasks through the progress slider, and raise an extension request for tasks.
2. On the status site superuser can edit the task title, and assign and re-assign tasks to developers, Inside the feature flag there is a progress slider that is used to update the progress of the site, and when clicking on the title of the task.

Success Metrics This Enhancement if implemented will be successful if the user experience of the task card feature is be same on both websites. on both the site functionality of the task card should be the same.

Features need to be Implemented

• The progress slider design should be the same on both sides and should follow the functionality of the progress slider as per the https://github.com/Real-Dev-Squad/website-members/issues/161
• Task card should get red when the task deadline is about to be reached with no/less progress on the task.
• On status-site users who are assignees or super_users or admin should be able to change the progress of the tasks.
• There should be a loader of the same design.
• Task Cards should have the same width and height on both sites.
• In both sites when the task is in "In Progress" status only users should be able to update the task progress through the progress slider.
• When a user is a super_user, then he should not see an option for an extension request.
• When the Task has the status DONE and 100% completed then only extension requests should not be visible.
• Responsiveness of task cards should be taken care of.
• on hovering over the tooltip after the estimated completion time/ started time it should show the time/date.
• we need to remove tabs from the status site which will help us control the width of the task card and also we have filters as alternatives to tabs.
• in my-site we need to use /task API instead of /task/self API to filter out the assignee's task.
• The feature needs to be behind the feature flag.

Designs and wireframes

DISCLAIMER - These are the rough wireframes, the styling part will be taken care of during the development phase...these wireframes are to make my idea about designs clear

Design Doc

• https://github.com/Real-Dev-Squad/website-my/issues/497
• https://github.com/Real-Dev-Squad/website-status/issues/931

Task-Status Flow Diagram

[iamitprakash]

why i do see edit icon everytime @Pratiyushkumar

[Pratiyushkumar]

why i do see edit icon everytime @Pratiyushkumar

I have corrected it, I missed the part where the edit icon should not be visible but now I added that also.

[RitikJaiswal75]

Task card should get red when the task deadline is about to be reached with no/less progress on the task.

(This should not happen for completed tasks)

As per the image i see in edit mode as well we have request extension button. But do we have to do this in edit mode i.e. (for super user)?

if a task is 100% completed then we need to change its status to completed/in review. I dont think it should it should still be in progress.

[Pratiyushkumar]

Task card should get red when the task deadline is about to be reached with no/less progress on the task.

(This should not happen for completed tasks)

As per the image I see in edit mode as well we have a request extension button. But do we have to do this in edit mode i.e. (for super user)?

if a task is 100% completed then we need to change its status to completed/in review. I dont think it should it should still be in progress.

for point 1. The agreed task card should get red and it is mentioned in the Features to be Implemented section for point 2. Thank you for pointing this out, will note this out. for point 3. Yes, I just presented the design in the image, When actual implementation is done task status will change according to requirment.

[AnjaliDeshwani]

Suggestion - In edit mode for superuser, instead of showing "Request Extension" button you can rather show "Extension status" for that particular task. (Only If assigned user has raised any extension request)

You can add one more feature for showing spinner and checkmark when progress is updated, similar to other editable fields. (As you said it will be part of enhancement only).

[iamitprakash]

Suggestion - In edit mode for superuser, instead of showing "Request Extension" button you can rather show "Extension status" for that particular task. (Only If assigned user has raised any extension request)

You can add one more feature for showing spinner and checkmark when progress is updated, similar to other editable fields. (As you said it will be part of enhancement only).

this suggestion looks good to me @Pratiyushkumar

[Pratiyushkumar]

Suggestion - In edit mode for superuser, instead of showing "Request Extension" button you can rather show "Extension status" for that particular task. (Only If assigned user has raised any extension request)

You can add one more feature for showing spinner and checkmark when progress is updated, similar to other editable fields. (As you said it will be part of enhancement only).

done

[shubhamsinghbundela]

Suggestion - In edit mode for superuser, instead of showing "Request Extension" button you can rather show "Extension status" for that particular task. (Only If assigned user has raised any extension request)

You can add one more feature for showing spinner and checkmark when progress is updated, similar to other editable fields. (As you said it will be part of enhancement only).

great suggestion

[shubhamsinghbundela]

When the Task has the status DONE and 100% completed then only extension requests should not be visible.

@Pratiyushkumar for above point - In my site when task in verified then assignee can see extension status.

So my suggestion is to keep extension status even task got verified for super-user and assignee

[Pratiyushkumar]

When the Task has the status DONE and 100% completed then only extension requests should not be visible.

@Pratiyushkumar for above point - In my site when task in verified then assignee can see extension status.

So my suggestion is to keep extension status even task got verified for super-user and assignee

@shubhamsigdar1 so we are modifying both my site and status-site task card hence the suggestion is great that when task is completed then user should not be able to see the extension request option.

[shubhamsinghbundela]

1 more suggestion- In my site there is problem- when user change status to verified then user do not able to access progress slider, So we have to handle this case also ->If you not understand what I said please ping me on discord

[AnjaliDeshwani]

Looks good to me.

[Pratiyushkumar]

got @iamitprakash approval https://discord.com/channels/673083527624916993/729399523268624405/1151568327265747084

[Ajeyakrishna-k]

@Pratiyushkumar Got confirmation from @ankushdharkar that we would be preferring the progress bar with blocks to be implemented on status site.

[Pratiyushkumar]

status that we don’t use like Smoke testing, sanity check, Regression check, and Released will be removed in the first deliverable and in the second deliverable we will include it as per discussion with @ankushdharkar.

[iamitprakash]

@Pratiyushkumar please accommodate required changes in design as discussed

[Pratiyushkumar]

Suggestion to implement - we should change the name of available to unassigned and completed to done and if the task has an unassigned status the name of the assignee should not be visible and the task should not be assigned to any user also in my-site task should task should be removed.

• as per the discussion with @iamitprakash this is not the ideal solution as we will be implementing a logs feature and if we unassign some tasks and the task doesn't have any assignee, suppose after 6 months will we check logs for that task to check if the task had some assignee or not, so are we going to check logs of all 6 months. So, need to find an alternative of this.

[Pratiyushkumar]

Suggestion to implement - we should change the name of available to unassigned and completed to done and if the task has an unassigned status the name of the assignee should not be visible and the task should not be assigned to any user also in my-site task should task should be removed.

• as per the discussion with @iamitprakash this is not the ideal solution as we will be implementing a logs feature and if we unassign some tasks and the task doesn't have any assignee, suppose after 6 months will we check logs for that task to check if the task had some assignee or not, so are we going to check logs of all 6 months. So, need to find an alternative of this.

As per @ankushdharkar, we should remove this unassigned status as a user should not be able to unassign the task from self.