-
Notifications
You must be signed in to change notification settings - Fork 1
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
MPDX-7864 - Task phases functionailty #949
base: main
Are you sure you want to change the base?
Conversation
Bundle sizes [mpdx-react]Compared against bc5798e
|
- Pull phase data into Constants graphql - Update test wrapper to handle and report errors - Allow for more customization on common modal
…s well as fixing their tests - Updating search with new Phase data - Fixing tests in reports - Updating settings test with new Phase data - Update tools to use new phase hooks
…t status and phase data.
- Show default views if no flows saved - Reset to default views modal
- Mass actions - Task row
a8858b7
to
8016eeb
Compare
Preview branch generated at https://MPDX-task-phases-new.d3dytjb8adxkk5.amplifyapp.com |
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.
const { t } = useTranslation(); | ||
const { openTaskModal } = useTaskModal(); | ||
const { enqueueSnackbar } = useSnackbar(); | ||
// TODO replace with ResultEnum when available |
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.
Does this TODO need to be address?
? activityType | ||
: null, | ||
changeContactStatus: false, | ||
nextAction: null, |
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.
I really liked how the next action would pre-populate, since normally after sending a text, I want to make the next task another text. Is it possible to add this feature back?
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.
This might take some work with the new way we have it set up. Maybe we could add this back later on.
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.
As a user, that's disappointing, but I understand it's a post go-live improvement.
src/components/Task/Modal/Form/Complete/TaskModalCompleteForm.tsx
Outdated
Show resolved
Hide resolved
src/components/Task/Modal/Form/Complete/TaskModalCompleteForm.tsx
Outdated
Show resolved
Hide resolved
src/components/Task/Modal/Form/Complete/TaskModalCompleteForm.tsx
Outdated
Show resolved
Hide resolved
}); | ||
break; | ||
|
||
case PhaseEnum.Connection: |
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.
accountListId: $accountListId | ||
tasksFilter: $tasksFilter | ||
after: $after | ||
first: $first | ||
sortBy: $sortBy |
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.
Some of these variables only have one possible value in the code. Personally, I'd hardcode them instead of making them variables in this operation. Also, $after
doesn't appear to be used when calling the lazy query and can be removed.
accountListId: $accountListId | |
tasksFilter: $tasksFilter | |
after: $after | |
first: $first | |
sortBy: $sortBy | |
accountListId: $accountListId | |
tasksFilter: $tasksFilter | |
first: 1 | |
sortBy: "START_AT_ASC" |
The message is shown in task modal that open as a result of a contact's status changing in flows view
[MPDX-8176] Add message to task modals in flows view
[MPDX-8175] Tweak reset flows warning message
* Rename Referral to Connection * Rename function for filters panel
* Use correctly formatted partner status name on reports * Use correctly formatted/translated Phase in modals
* Make the Result field an autocomplete * Make the Reminders fields Autocomplete * Add autoSelect
* Rename email newsletter to Digital
@@ -8,7 +8,7 @@ on: | |||
|
|||
env: | |||
# Use production API for codegen to make sure production is compatible with the code to be merged | |||
API_URL: 'https://api.mpdx.org/graphql' | |||
API_URL: 'https://api.stage.mpdx.org/graphql' |
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.
Make sure we revert this before going live. I know I have a commit on this. But putting it in multiple places.
@@ -62,6 +75,7 @@ const getAccountListAnalytics = (data: { | |||
text_message, | |||
start_date: startDate, | |||
end_date: endDate, | |||
contacts_by_status, |
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.
contacts_by_status, | |
contacts_by_status: contactsByStatus, |
Description
This pull request integrates the Task phases functionality into the MPDX application. The update encompasses several areas, including task initialization, contact management, and coaching updates.
Authors: @caleballdrin & @dr-bizz
Detailed Changes
Initialization
Contacts
Tasks
Coaching
Testing
Note on Branch Change
Due to the high number of commits (140) on the previous branch "MPDX-task-phases" and the resulting merge conflicts from multiple code changes, I had to move to a new branch "MPDX-task-phases-new." This new branch was created to make it easier to create and review new commits without the complexities of resolving numerous conflicts.
This approach should provide a clearer and more manageable review process.
Checklist: