Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding DONE to task status options #499

Open
wants to merge 20 commits into
base: develop
Choose a base branch
from

Conversation

chandrareddy7
Copy link

@chandrareddy7 chandrareddy7 commented Oct 8, 2023

Issue: #468

Design Doc: Link

Description:

Currently in task status options we are showing AVAILABLE as an option.
We are removing it as we do not want a user to UNASSIGN a task by themselves.

We are migrating our task status from COMPLETED to DONE. So COMPLETED task status is replaced by DONE.

Changes are under feature flag.

When dev is false we would have AVAILABLE and COMPLETED in task status options.
When dev is true we would have DONE in task status options and we do not show AVAILABLE.

Before changes:

image

After changes:

image

Update task status to DONE:

My.Tasks._.My._.Real.Dev.Squad.-.Google.Chrome.2023-10-08.17-45-25.mp4

@netlify
Copy link

netlify bot commented Oct 8, 2023

Deploy Preview for staging-my ready!

Name Link
🔨 Latest commit 2a94838
🔍 Latest deploy log https://app.netlify.com/sites/staging-my/deploys/653bc105aab34f00084cd949
😎 Deploy Preview https://deploy-preview-499--staging-my.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@chandrareddy7 chandrareddy7 changed the title Adding UNASSIGNED and DONE to task status options Adding DONE to task status options Oct 8, 2023
Comment on lines +35 to +43
{{#if @dev}}
{{#if (not (or (eq taskStatus.key this.TASK_KEYS.AVAILABLE) (eq taskStatus.key this.TASK_KEYS.COMPLETED)))}}
<option
value={{taskStatus.key}}
selected={{eq taskStatus.key this.status}}
>
{{taskStatus.displayLabel}}
</option>
{{/if}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of adding conditions inside a loop to populate the task status, can we just have two separate availableTaskStatusList?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You meant to maintain two seperate lists in the constants file itself?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Something like that where we don't have to write extra logic to maintain the old flow.

</option>
{{/if}}
{{else}}
{{#if (not (or (eq taskStatus.key this.TASK_KEYS.DONE)))}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we add new logic under the old flow, won't it defeat the purpose of adding a feature flag?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have added new task status to constants file. So have to do this.
Can we do it in any other way?

@Pratiyushkumar
Copy link

Also Please update your design doc in PR

PeeyushPrashant and others added 14 commits October 13, 2023 22:25
* feat: cancel OOO button enabled

* fix: styling issues

* feat: feature flag added

* fix: feature behind flag

* fix: test file

* fixed lint error

* removed redundancy
* create button to allow multiple extensions

* add test for multiple extension request form

* fix style

* fix style

* fix style and refactor component

* refactor form and details and fix styles

* fix test cases

* final fix
…either approved or denied (Real-Dev-Squad#503)

* Feat : Added reviewed by log in extension status modal

* Test : Added test cases to verify review log
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants