-
Type:
New Feature
-
Status: Done
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CBAT Offer Letter - Fall
-
Labels:
-
Company:All Clients/Multiple Clients
-
Epic Link:
Is there a way to replace a document that's already been sent to a candidate with an updated version of the document? For example, if an offer letter was sent, but the details have been re-negotiated and a new version should be signed instead. And if the document has already been signed by the candidate and we send them a new version - is there a way to indicate that the new version sent supersedes the previous version?
Ability to do the following on the document sent to a candidate.
- Replace
- Delete
- Rename
Field | Original Value | New Value |
---|---|---|
Priority | High [ 2 ] | Medium [ 3 ] |
Assignee | Samir [ samir ] | Robert Malony [ robert.malony ] |
Fix Version/s | CBAT Offer Letter - Fall [ 10607 ] | |
Fix Version/s | Integration with CBAT [ 10445 ] |
Summary | Rescinding and Replacing Already Assigned Documents | Resending and Replacing Already Assigned Documents |
Remaining Estimate | 24h [ 86400 ] | |
Original Estimate | 24h [ 86400 ] |
Sprint | DMS - Fall Sprint 3 [ 162 ] |
Assignee | Robert Malony [ robert.malony ] | Samir [ samir ] |
Epic Link | DMS-473 [ 75966 ] |
Description |
1) Is there a way to rescind a document that's been sent to a candidate? For example, if the document no longer applies to them, or was sent in error, and they have not signed the document yet. I don't see an option to do this.
2) Is there a way to replace a document that's already been sent to a candidate with an updated version of the document? For example, if an offer letter was sent, but the details have been re-negotiated and a new version should be signed instead. And if the document has already been signed by the candidate and we send them a new version - is there a way to indicate that the new version sent supersedes the previous version? |
Is there a way to replace a document that's already been sent to a candidate with an updated version of the document? For example, if an offer letter was sent, but the details have been re-negotiated and a new version should be signed instead. And if the document has already been signed by the candidate and we send them a new version - is there a way to indicate that the new version sent supersedes the previous version? |
Summary | Resending and Replacing Already Assigned Documents | Replacing Already Assigned Documents |
Summary | Replacing Already Assigned Documents | CBATS : Replacing Already Assigned Documents |
Sprint | DMS - Fall Sprint 3 [ 162 ] |
Attachment | Screen Shot 2019-05-30 at 2.09.57 PM.png [ 109017 ] |
Description | Is there a way to replace a document that's already been sent to a candidate with an updated version of the document? For example, if an offer letter was sent, but the details have been re-negotiated and a new version should be signed instead. And if the document has already been signed by the candidate and we send them a new version - is there a way to indicate that the new version sent supersedes the previous version? |
Is there a way to replace a document that's already been sent to a candidate with an updated version of the document? For example, if an offer letter was sent, but the details have been re-negotiated and a new version should be signed instead. And if the document has already been signed by the candidate and we send them a new version - is there a way to indicate that the new version sent supersedes the previous version?
!Screen Shot 2019-05-30 at 2.09.57 PM.png|thumbnail! Ability to do the following on the document sent to a candidate * Replace * Delete * Rename |
Description |
Is there a way to replace a document that's already been sent to a candidate with an updated version of the document? For example, if an offer letter was sent, but the details have been re-negotiated and a new version should be signed instead. And if the document has already been signed by the candidate and we send them a new version - is there a way to indicate that the new version sent supersedes the previous version?
!Screen Shot 2019-05-30 at 2.09.57 PM.png|thumbnail! Ability to do the following on the document sent to a candidate * Replace * Delete * Rename |
Is there a way to replace a document that's already been sent to a candidate with an updated version of the document? For example, if an offer letter was sent, but the details have been re-negotiated and a new version should be signed instead. And if the document has already been signed by the candidate and we send them a new version - is there a way to indicate that the new version sent supersedes the previous version?
!Screen Shot 2019-05-30 at 2.09.57 PM.png|thumbnail! Ability to do the following on the document sent to a candidate. * Replace * Delete * Rename |
Labels | BETA_SP19 |
Assignee | Samir [ samir ] | Rohan J Khandave [ rohan.khandave ] |
Summary | CBATS : Replacing Already Assigned Documents | CBAT : Replacing Already Assigned Documents |
Sprint | DMS - Fall Sprint 7 [ 166 ] |
Labels | BETA_SP19 | BETA_SP19 Integration-CBAT |
Assignee | Rohan J Khandave [ rohan.khandave ] | Priya Dhamande [ priya.dhamande ] |
-
- Time Spent:
- 1h
-
Production testing
Remaining Estimate | 24h [ 86400 ] | 23.5h [ 84600 ] |
Time Spent | 0.5h [ 1800 ] | |
Worklog Id | 188376 [ 188376 ] |
Assignee | Priya Dhamande [ priya.dhamande ] | Samir [ samir ] |
Assignee | Samir [ samir ] | Rohan J Khandave [ rohan.khandave ] |
Remaining Estimate | 23.5h [ 84600 ] | 23h [ 82800 ] |
Time Spent | 0.5h [ 1800 ] | 1h [ 3600 ] |
Worklog Id | 188376 [ 188376 ] |
Status | To Do [ 10000 ] | In Progress [ 3 ] |
Assignee | Rohan J Khandave [ rohan.khandave ] | Samir [ samir ] |
Sprint | DMS - Fall Sprint 7 [ 166 ] | DMS - Fall Sprint 8 [ 167 ] |
Assignee | Samir [ samir ] | Priya Dhamande [ priya.dhamande ] |
Status | In Progress [ 3 ] | In QA Testing [ 11901 ] |
Assignee | Priya Dhamande [ priya.dhamande ] | Samir [ samir ] |
Status | In QA Testing [ 11901 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In QA Testing [ 11901 ] |
Assignee | Samir [ samir ] | Priya Dhamande [ priya.dhamande ] |
Assignee | Priya Dhamande [ priya.dhamande ] | Rohan J Khandave [ rohan.khandave ] |
Status | In QA Testing [ 11901 ] | To Do [ 10000 ] |
Status | To Do [ 10000 ] | In QA Testing [ 11901 ] |
Assignee | Rohan J Khandave [ rohan.khandave ] | Priya Dhamande [ priya.dhamande ] |
Remaining Estimate | 23h [ 82800 ] | 22h [ 79200 ] |
Time Spent | 1h [ 3600 ] | 2h [ 7200 ] |
Worklog Id | 192652 [ 192652 ] |
Assignee | Priya Dhamande [ priya.dhamande ] | Robert Malony [ robert.malony ] |
Resolution | Done [ 10000 ] | |
Status | In QA Testing [ 11901 ] | Done [ 10001 ] |
Sprint | DMS - Fall Sprint 8 [ 167 ] | DMS - Gap Fall & Win Sprint 1 [ 173 ] |
Transition | Time In Source Status | Execution Times |
---|
|
82d 7h 37m | 1 |
|
2d 23h 3m | 1 |
|
9d 16h 41m | 2 |
|
4h 7m | 1 |
|
21h 19m | 1 |
|
1d 23h 45m | 1 |
BETA-440