-
Notifications
You must be signed in to change notification settings - Fork 97
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
base: develop
Are you sure you want to change the base?
Adding DONE to task status options #499
Conversation
✅ Deploy Preview for staging-my ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
{{#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}} |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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)))}} |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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?
Also Please update your design doc in PR |
* 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
…s://github.com/chandrareddy7/website-my into Add-UNASSIGNED-and-DONE-in-task-status-options
…s://github.com/chandrareddy7/website-my into Add-UNASSIGNED-and-DONE-in-task-status-options
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
toDONE
. SoCOMPLETED
task status is replaced byDONE
.Changes are under feature flag.
When dev is false we would have
AVAILABLE
andCOMPLETED
in task status options.When dev is true we would have
DONE
in task status options and we do not showAVAILABLE
.Before changes:
After changes:
Update task status to DONE:
My.Tasks._.My._.Real.Dev.Squad.-.Google.Chrome.2023-10-08.17-45-25.mp4