-
Type:
New Feature
-
Status: Done
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: Email communication
-
Labels:None
-
Company:CareerBuilder
-
Epic Link:
Overview:
Ability to see a historic record of all messaging (email / text / push) that has been sent from the portal so that I have an accurate trail of what has been done / what candidates have received.
Entry:
- User navigates to Communication History.
Acceptance Criteria:
- IF I am a user, I am able to navigate to a communication history section within portal or consuming app to see what communication was sent from portal.
- IF I am a user, I am able to see what was sent, when it was sent (date & time (timestamp)), to whom, what type of communication it was (text, email, push), if a template was used, which one.
- IF I am a user, I am able to see when an end user opened the communication.
- IF I am a user, there is an access level to determine whether I can see just my history, or all history.
Exit:
- User sees all communication sent from portal (email / text/ push notifications).
Prerequisites:
*User can can see communication history.
- relates to
-
DMS-377 Notification History in Communications Module
-
- Done
-
1.
|
UX for Communication History | DMS-374 |
|
Done | Samir |
|
Field | Original Value | New Value |
---|---|---|
Epic Link | DMS-219 [ 74297 ] |
Description |
Overview:
Ability to see a historic record of all messaging (email / text / push) that has been sent from the portal so that I have an accurate trail of what has been done / what candidates have received. Entry: * User navigates to Communication History. Acceptance Criteria: * IF I am a user, I am able to navigate to a communication history section within portal or consuming app to see what communication was sent from portal. * IF I am a user, I am able to see what was sent, when it was sent, to whom, what type of communication it was (text, email, push), if a template was used, which one. *IF I am a user, there is an access level to determine whether I can see just my history, or all history. Exit: * User sees all communication sent from portal (email / text/ push notifications). Prerequisites: *User can can see communication history. |
Overview:
Ability to see a historic record of all messaging (email / text / push) that has been sent from the portal so that I have an accurate trail of what has been done / what candidates have received. Entry: * User navigates to Communication History. Acceptance Criteria: * IF I am a user, I am able to navigate to a communication history section within portal or consuming app to see what communication was sent from portal. * IF I am a user, I am able to see what was sent, when it was sent (date & time (timestamp)), to whom, what type of communication it was (text, email, push), if a template was used, which one. * IF I am a user, there is an access level to determine whether I can see just my history, or all history. Exit: * User sees all communication sent from portal (email / text/ push notifications). Prerequisites: *User can can see communication history. |
Description |
Overview:
Ability to see a historic record of all messaging (email / text / push) that has been sent from the portal so that I have an accurate trail of what has been done / what candidates have received. Entry: * User navigates to Communication History. Acceptance Criteria: * IF I am a user, I am able to navigate to a communication history section within portal or consuming app to see what communication was sent from portal. * IF I am a user, I am able to see what was sent, when it was sent (date & time (timestamp)), to whom, what type of communication it was (text, email, push), if a template was used, which one. * IF I am a user, there is an access level to determine whether I can see just my history, or all history. Exit: * User sees all communication sent from portal (email / text/ push notifications). Prerequisites: *User can can see communication history. |
Overview:
Ability to see a historic record of all messaging (email / text / push) that has been sent from the portal so that I have an accurate trail of what has been done / what candidates have received. Entry: * User navigates to Communication History. Acceptance Criteria: * IF I am a user, I am able to navigate to a communication history section within portal or consuming app to see what communication was sent from portal. * IF I am a user, I am able to see what was sent, when it was sent (date & time (timestamp)), to whom, what type of communication it was (text, email, push), if a template was used, which one. * IF I am a user, I am able to see when an end user opened the communication. * IF I am a user, there is an access level to determine whether I can see just my history, or all history. Exit: * User sees all communication sent from portal (email / text/ push notifications). Prerequisites: *User can can see communication history. |
Sprint | DMS - Sprint 6 [ 134 ] |
Sprint | DMS - Sprint 6 [ 134 ] | DMS - Sprint 7 [ 148 ] |
Fix Version/s | Spring release [ 10444 ] |
Fix Version/s | Email communication [ 10450 ] | |
Fix Version/s | Spring release [ 10444 ] |
Sprint | DMS - Sprint 7 [ 148 ] | DMS - Sprint 1 [ 149 ] |
Assignee | Samir [ samir ] | Harshveer Singh [ harshveer.singh ] |
Status | To Do [ 10000 ] | In Progress [ 3 ] |
Dev Due Date | 25/Jan/2019 | |
Dev Estimates | 6 | |
Remaining Estimate | 6h [ 21600 ] | |
Original Estimate | 16h [ 57600 ] |
Status | In Progress [ 3 ] | Code Review [ 11801 ] |
Sprint | DMS - Sprint 1 [ 149 ] | DMS - Sprint 1, DMS - Sprint 2 [ 149, 150 ] |
Status | Code Review [ 11801 ] | In QA Testing [ 11901 ] |
Assignee | Harshveer Singh [ harshveer.singh ] | Jayshree Nagpure [ jayshree.nagpure ] |
Sprint | DMS - Sprint 1, DMS - Sprint 2 [ 149, 150 ] | DMS - Sprint 1, DMS - Sprint 2, DMS - Sprint 3 [ 149, 150, 152 ] |
Status | In QA Testing [ 11901 ] | In Progress [ 3 ] |
Assignee | Jayshree Nagpure [ jayshree.nagpure ] | Harshveer Singh [ harshveer.singh ] |
Status | In Progress [ 3 ] | Code Review [ 11801 ] |
Sprint | DMS - Sprint 1, DMS - Sprint 2, DMS - Sprint 3 [ 149, 150, 152 ] | DMS - Sprint 1, DMS - Sprint 2, DMS - Sprint 3, DMS - Sprint 4 [ 149, 150, 152, 153 ] |
Assignee | Harshveer Singh [ harshveer.singh ] | Jayshree Nagpure [ jayshree.nagpure ] |
Assignee | Jayshree Nagpure [ jayshree.nagpure ] | Harshveer Singh [ harshveer.singh ] |
Assignee | Harshveer Singh [ harshveer.singh ] | Jayshree Nagpure [ jayshree.nagpure ] |
Status | Code Review [ 11801 ] | In QA Testing [ 11901 ] |
Assignee | Jayshree Nagpure [ jayshree.nagpure ] | Priya Dhamande [ priya.dhamande ] |
Remaining Estimate | 6h [ 21600 ] | 5.5h [ 19800 ] |
Time Spent | 0.5h [ 1800 ] | |
Worklog Id | 164452 [ 164452 ] |
Status | In QA Testing [ 11901 ] | In Progress [ 3 ] |
Assignee | Priya Dhamande [ priya.dhamande ] | Harshveer Singh [ harshveer.singh ] |
Remaining Estimate | 5.5h [ 19800 ] | 5.25h [ 18900 ] |
Time Spent | 0.5h [ 1800 ] | 0.75h [ 2700 ] |
Worklog Id | 164452 [ 164452 ] |
Status | In Progress [ 3 ] | In QA Testing [ 11901 ] |
Assignee | Harshveer Singh [ harshveer.singh ] | Priya Dhamande [ priya.dhamande ] |
Sprint | DMS - Sprint 1, DMS - Sprint 2, DMS - Sprint 3, DMS - Sprint 4 [ 149, 150, 152, 153 ] | DMS - Sprint 1, DMS - Sprint 2, DMS - Sprint 3, DMS - Sprint 4, DMS - Sprint 5 [ 149, 150, 152, 153, 154 ] |
Resolution | Done [ 10000 ] | |
Status | In QA Testing [ 11901 ] | Done [ 10001 ] |
Status | Done [ 10001 ] | Done [ 10001 ] |
Assignee | Priya Dhamande [ priya.dhamande ] | Harshveer Singh [ harshveer.singh ] |
Remaining Estimate | 5.25h [ 18900 ] | 0.25h [ 900 ] |
Time Spent | 0.75h [ 2700 ] | 5.75h [ 20700 ] |
Worklog Id | 206003 [ 206003 ] |
Remaining Estimate | 0.25h [ 900 ] | 0h [ 0 ] |
Time Spent | 5.75h [ 20700 ] | 13.75h [ 49500 ] |
Worklog Id | 206080 [ 206080 ] |
Time Spent | 13.75h [ 49500 ] | 15.75h [ 56700 ] |
Worklog Id | 206003 [ 206003 ] |
Time Spent | 15.75h [ 56700 ] | 23.75h [ 85500 ] |
Worklog Id | 206085 [ 206085 ] |
Remaining Estimate | 0h [ 0 ] | 8h [ 28800 ] |
Time Spent | 23.75h [ 85500 ] | 15.75h [ 56700 ] |
Worklog Id | 206085 [ 206085 ] | |
Worklog Time Spent | 8h [ 28800 ] |
Remaining Estimate | 8h [ 28800 ] | 7h [ 25200 ] |
Time Spent | 15.75h [ 56700 ] | 16.75h [ 60300 ] |
Worklog Id | 206003 [ 206003 ] |
Remaining Estimate | 7h [ 25200 ] | 6h [ 21600 ] |
Time Spent | 16.75h [ 60300 ] | 17.75h [ 63900 ] |
Worklog Id | 206003 [ 206003 ] |
Transition | Time In Source Status | Execution Times |
---|
|
39d 15h 56m | 1 |
|
9d 12h 54m | 2 |
|
17d 5h 53m | 2 |
|
20d 7h | 2 |
|
17h 8m | 1 |
|
6d 5h 18m | 1 |
|
47s | 1 |
Hi Molly Ronovsky : Please elaborate below point
For below point i am thinking to use Tabs as we had used for Action Documents and Archived Documents
CC : Harshveer Singh Mohd Belal Samir Swapnil Pandhare ShashiKant Mishra Kristen