-
Type:
Enhancement
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:
-
Module:BenAdmin - Export
-
Reported by:Support
-
Item State:Stage QA - Production Deployment on Hold
-
Sprint:BenAdmin Betterment & May 2017
-
Feature Category:New
-
Severity:Simple
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template.
- Carrier contact (name and contact details - text area)
- File upload, with category (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template.
- JIRA ID for discrepancy (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable).
Scheduler Stop Date (Template Delivery/ Expoer Scheduler/ Stop Date). We need this as there is no way one can program the scheduler stop exporting the file. Currently we have to manually change the frequency to calendar date or one time.Instead a flag blackout=y/n is suggested.- *
EDI Analyst* (Working on that template) Should be a drop down of all users? << Keep on hold as this is too dynamic. During OE this changes a lot.
- causes
-
WT-11284 Download button is not working
-
- Resolution Setting
-
-
-
- Rejected
-
-
-
- Resolution Setting
-
-
-
- Resolution Setting
-
-
-
- Resolution Setting
-
-
-
- Resolution Setting
-
- is cloned by
-
-
- Resolution Setting
-
- relates to
-
-
- Resolution Setting
-
(1 causes, 1 is cloned by, 1 relates to)
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Vijay Siddha [ vijays ] | Vinayak Kulkarni [ vinayak.kulkarni ] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. We need the feature to upload files for the template. These will be mainly the structure specifications. Currently structure specs are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. We need the feature to upload files for the template. These will be mainly the structure specifications. Currently structure specs are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. We also discussed how the discrepancy related files can be stored here. This will make it very convenient for everyone working on it. CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Module | Parent values: BenAdmin(10100) | Parent values: BenAdmin(10100)Level 1 values: Export(10110) |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. We need the feature to upload files for the template. These will be mainly the structure specifications. Currently structure specs are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. We also discussed how the discrepancy related files can be stored here. This will make it very convenient for everyone working on it. CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * Carrier contact (name and contact details - text area) * File upload, with category (text area) The files will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * Carrier contact (name and contact details - text area) * File upload, with category (text area) The files will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * Carrier contact (name and contact details - text area) * File upload, with category (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * JIRA ID for discrepancy (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Sprint | BenAdmin Betterment & May 2017 [ 65 ] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * Carrier contact (name and contact details - text area) * File upload, with category (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * JIRA ID for discrepancy (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *EDI Analyst* (Working on that template) Should be a drop down of all users? * *OE Feed Status* - Ongoing/ New/ Terminated (Check with OE Dashboard - may be it should be only on OE dasboard) CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *EDI Analyst* (Working on that template) Should be a drop down of all users? * *OE Feed Status* - Ongoing/ New/ Terminated (Check with OE Dashboard - may be it should be only on OE dasboard) CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *EDI Analyst* (Working on that template) Should be a drop down of all users? CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *EDI Analyst* (Working on that template) Should be a drop down of all users? CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *{color:#d04437}EDI Analyst* (Working on that template) Should be a drop down of all users?{color} {color:#d04437}<< Keep on hold as this is too dynamic. During OE this changes a lot.{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *{color:#d04437}EDI Analyst* (Working on that template) Should be a drop down of all users?{color} {color:#d04437}<< Keep on hold as this is too dynamic. During OE this changes a lot.{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *{color:#d04437}EDI Analyst* (Working on that template) Should be a drop down of all users?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *{color:#d04437}EDI Analyst* (Working on that template) Should be a drop down of all users?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). ** Scheduler Stop Date (Template Delivery/ Expoer Scheduler/ Stop Date). We need this as there is no way one can program the scheduler stop exporting the file. Currently we have to manually change the frequency to calendar date or one time.* * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). ** Scheduler Stop Date (Template Delivery/ Expoer Scheduler/ Stop Date). We need this as there is no way one can program the scheduler stop exporting the file. Currently we have to manually change the frequency to calendar date or one time.* * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *Scheduler Stop Date (Template Delivery/ Expoer Scheduler/ Stop Date). We need this as there is no way one can program the scheduler stop exporting the file. Currently we have to manually change the frequency to calendar date or one time.* * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Summary | File Upload for Templates | Templates - Additional Attributes |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *Scheduler Stop Date (Template Delivery/ Expoer Scheduler/ Stop Date). We need this as there is no way one can program the scheduler stop exporting the file. Currently we have to manually change the frequency to calendar date or one time.* * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *-Scheduler Stop Date (Template Delivery/ Expoer Scheduler/ Stop Date). We need this as there is no way one can program the scheduler stop exporting the file. Currently we have to manually change the frequency to calendar date or one time.*- * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Description |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *-Scheduler Stop Date (Template Delivery/ Expoer Scheduler/ Stop Date). We need this as there is no way one can program the scheduler stop exporting the file. Currently we have to manually change the frequency to calendar date or one time.*- * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
Currently we have a "notes" section for templates which can be used to store information like carrier contacts. However, it is not sufficient. Following is the requirement to store key information with the template. * *Carrier contact* (name and contact details - text area) * *File upload, with category* (text area) - These will be the structure specifications as well as discrepancies. Currently these are stored somewhere else, which is not convenient. It is important to couple it tightly with the template. * *JIRA ID for discrepancy* (text area) - A company+ carrier combination's discrepancies are handled under one JIRA ticket. It will be good to store that ID at template level (if applicable). * *-Scheduler Stop Date (Template Delivery/ Expoer Scheduler/ Stop Date). We need this as there is no way one can program the scheduler stop exporting the file. Currently we have to manually change the frequency to calendar date or one time.*- Instead a flag blackout=y/n is suggested. * *{color:#d04437}-EDI Analyst* (Working on that template) Should be a drop down of all users-?{color} {color:#d04437}<< *Keep on hold as this is too dynamic. During OE this changes a lot.*{color} CC [~Cindy.Wibbing] [~Van.Nguyen] [~amitthorve] [~samir] |
| Assignee | Vinayak Kulkarni [ vinayak.kulkarni ] | Prajakta Belhe [ prajakta.belhe ] |
| Dev Due Date | 23/Aug/2017 | |
| Dev Estimates | 50 |
| Status | New Request [ 10029 ] | Pending for Approval [ 10002 ] |
| Status | Pending for Approval [ 10002 ] | Approved for Development [ 10003 ] |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) |
| Status | Approved for Development [ 10003 ] | In Development [ 10007 ] |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | Parent values: Development(10200)Level 1 values: In Progress(10206) |
| Dev Due Date | 23/Aug/2017 | 23/Aug/2017 |
| Remaining Estimate | 64h [ 230400 ] | |
| Original Estimate | 64h [ 230400 ] |
| Remaining Estimate | 64h [ 230400 ] | 63h [ 226800 ] |
| Time Spent | 1h [ 3600 ] | |
| Worklog Id | 74527 [ 74527 ] |
| Remaining Estimate | 63h [ 226800 ] | 56h [ 201600 ] |
| Time Spent | 1h [ 3600 ] | 8h [ 28800 ] |
| Worklog Id | 74575 [ 74575 ] |
| Remaining Estimate | 56h [ 201600 ] | 49h [ 176400 ] |
| Time Spent | 8h [ 28800 ] | 15h [ 54000 ] |
| Worklog Id | 74655 [ 74655 ] |
| Remaining Estimate | 49h [ 176400 ] | 42h [ 151200 ] |
| Time Spent | 15h [ 54000 ] | 22h [ 79200 ] |
| Worklog Id | 74656 [ 74656 ] |
| Remaining Estimate | 42h [ 151200 ] | 35h [ 126000 ] |
| Time Spent | 22h [ 79200 ] | 29h [ 104400 ] |
| Worklog Id | 74657 [ 74657 ] |
| Remaining Estimate | 35h [ 126000 ] | 28h [ 100800 ] |
| Time Spent | 29h [ 104400 ] | 36h [ 129600 ] |
| Worklog Id | 74658 [ 74658 ] |
| Dev Due Date | 23/Aug/2017 | 01/Sep/2017 |
| Dev Estimates | 50 | 80 |
| Remaining Estimate | 28h [ 100800 ] | 21h [ 75600 ] |
| Time Spent | 36h [ 129600 ] | 43h [ 154800 ] |
| Worklog Id | 74700 [ 74700 ] |
| Remaining Estimate | 21h [ 75600 ] | 14h [ 50400 ] |
| Time Spent | 43h [ 154800 ] | 50h [ 180000 ] |
| Worklog Id | 74701 [ 74701 ] |
| Remaining Estimate | 14h [ 50400 ] | 7h [ 25200 ] |
| Time Spent | 50h [ 180000 ] | 57h [ 205200 ] |
| Worklog Id | 74702 [ 74702 ] |
| Remaining Estimate | 7h [ 25200 ] | 0h [ 0 ] |
| Time Spent | 57h [ 205200 ] | 64h [ 230400 ] |
| Worklog Id | 74722 [ 74722 ] |
| Dev Estimates | 80 | 104 |
| Time Spent | 64h [ 230400 ] | 71h [ 255600 ] |
| Worklog Id | 75816 [ 75816 ] |
| Time Spent | 71h [ 255600 ] | 71.5h [ 257400 ] |
| Worklog Id | 76178 [ 76178 ] |
| Time Spent | 71.5h [ 257400 ] | 72h [ 259200 ] |
| Worklog Id | 76342 [ 76342 ] |
| Time Spent | 72h [ 259200 ] | 73h [ 262800 ] |
| Worklog Id | 77516 [ 77516 ] |
Khandu Kshirsagar (Inactive)
made changes -
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
| Code Reviewed By | Ganesh Sadawarte [ 12101 ] |
| Attachment | AffectedFiles_JIRAID.txt [ 61370 ] |
| Attachment | Affected files for 9319.txt [ 61371 ] |
| Time Spent | 73h [ 262800 ] | 75h [ 270000 ] |
| Worklog Id | 78468 [ 78468 ] |
| Time Spent | 75h [ 270000 ] | 82h [ 295200 ] |
| Worklog Id | 78469 [ 78469 ] |
| Time Spent | 82h [ 295200 ] | 87h [ 313200 ] |
| Worklog Id | 78470 [ 78470 ] |
| Time Spent | 87h [ 313200 ] | 94h [ 338400 ] |
| Worklog Id | 78473 [ 78473 ] |
| Time Spent | 94h [ 338400 ] | 101h [ 363600 ] |
| Worklog Id | 78474 [ 78474 ] |
| Time Spent | 101h [ 363600 ] | 107h [ 385200 ] |
| Worklog Id | 78476 [ 78476 ] |
| Assignee | Prajakta Belhe [ prajakta.belhe ] | Aniruddha Dev [ aniruddha.dev ] |
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Swapnil Eksambekar [ swapnil.eksambekar ] |
| Production Due Date | 21/Sep/2017 | |
| Stage Due Date | 20/Sep/17 [ 2017-09-20 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Time Spent | 107h [ 385200 ] | 112h [ 403200 ] |
| Worklog Id | 78715 [ 78715 ] |
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: In Testing(10210) |
| Time Spent | 112h [ 403200 ] | 113h [ 406800 ] |
| Worklog Id | 80810 [ 80810 ] |
| Status | Local Testing [ 10200 ] | Reopen in Local [ 10018 ] |
| Item State | Parent values: LB QA(10201)Level 1 values: In Testing(10210) | Parent values: LB QA(10201)Level 1 values: Re-open(10212) |
| Time Spent | 113h [ 406800 ] | 118h [ 424800 ] |
| Worklog Id | 81276 [ 81276 ] |
| Time Spent | 118h [ 424800 ] | 120h [ 432000 ] |
| Worklog Id | 81277 [ 81277 ] |
| Remaining Estimate | 0h [ 0 ] | 2h [ 7200 ] |
| Time Spent | 120h [ 432000 ] | 118h [ 424800 ] |
| Worklog Id | 81277 [ 81277 ] | |
| Worklog Time Spent | 2h [ 7200 ] |
| Remaining Estimate | 2h [ 7200 ] | 7h [ 25200 ] |
| Time Spent | 118h [ 424800 ] | 113h [ 406800 ] |
| Worklog Id | 81276 [ 81276 ] | |
| Worklog Time Spent | 5h [ 18000 ] |
| Remaining Estimate | 7h [ 25200 ] | 1h [ 3600 ] |
| Time Spent | 113h [ 406800 ] | 119h [ 428400 ] |
| Worklog Id | 81570 [ 81570 ] |
| Remaining Estimate | 1h [ 3600 ] | 0h [ 0 ] |
| Time Spent | 119h [ 428400 ] | 122h [ 439200 ] |
| Worklog Id | 81573 [ 81573 ] |
| Assignee | Swapnil Eksambekar [ swapnil.eksambekar ] | Prajakta Belhe [ prajakta.belhe ] |
| Time Spent | 122h [ 439200 ] | 123.5h [ 444600 ] |
| Worklog Id | 83431 [ 83431 ] |
| Assignee | Prajakta Belhe [ prajakta.belhe ] | Punam Satpute [ punam.satpute ] |
| Status | Reopen in Local [ 10018 ] | In Development [ 10007 ] |
Punam Satpute (Inactive)
made changes -
| Assignee | Punam Satpute [ punam.satpute ] | Swapnil Eksambekar [ swapnil.eksambekar ] |
| Time Spent | 123.5h [ 444600 ] | 125.5h [ 451800 ] |
| Worklog Id | 84330 [ 84330 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Status | Local Testing [ 10200 ] | Reopen in Local [ 10018 ] |
| Assignee | Swapnil Eksambekar [ swapnil.eksambekar ] | Prajakta Belhe [ prajakta.belhe ] |
| Assignee | Prajakta Belhe [ prajakta.belhe ] | Punam Satpute [ punam.satpute ] |
Punam Satpute (Inactive)
made changes -
| Item State | Parent values: LB QA(10201)Level 1 values: Re-open(10212) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
Punam Satpute (Inactive)
made changes -
| Assignee | Punam Satpute [ punam.satpute ] | Swapnil Eksambekar [ swapnil.eksambekar ] |
| Status | Reopen in Local [ 10018 ] | In Development [ 10007 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) |
| Time Spent | 125.5h [ 451800 ] | 126.5h [ 455400 ] |
| Worklog Id | 84877 [ 84877 ] |
| Time Spent | 126.5h [ 455400 ] | 128.5h [ 462600 ] |
| Worklog Id | 84883 [ 84883 ] |
| Developer | Prajakta Belhe [ prajakta.belhe ] |
Khandu Kshirsagar (Inactive)
made changes -
| Item State | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) |
| Attachment | Affected files for 9319 (a61109ef-054e-498b-80f0-573bc1c166f6).txt [ 64589 ] |
| Attachment | Affected files for 9319 (a61109ef-054e-498b-80f0-573bc1c166f6).txt [ 64589 ] |
| Attachment | Affected files for 9319.txt [ 61371 ] |
| Attachment | Affected files for 9319.txt [ 64590 ] |
Khandu Kshirsagar (Inactive)
made changes -
| Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
Khandu Kshirsagar (Inactive)
made changes -
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) |
| Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) |
| Item State | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) | Parent values: Stage QA(10202)Level 1 values: Re-open(10216) |
| Status | Local Testing [ 10200 ] | Pending for Stage Approval [ 10300 ] |
| Status | Pending for Stage Approval [ 10300 ] | Approved for Stage [ 10030 ] |
| Status | Approved for Stage [ 10030 ] | Stage Testing [ 10201 ] |
| Status | Stage Testing [ 10201 ] | Reopen in Stage [ 10023 ] |
| Assignee | Swapnil Eksambekar [ swapnil.eksambekar ] | Prajakta Belhe [ prajakta.belhe ] |
| Time Spent | 128.5h [ 462600 ] | 130h [ 468000 ] |
| Worklog Id | 85388 [ 85388 ] |
| Time Spent | 130h [ 468000 ] | 132.5h [ 477000 ] |
| Worklog Id | 86116 [ 86116 ] |
| Time Spent | 132.5h [ 477000 ] | 133.5h [ 480600 ] |
| Worklog Id | 86119 [ 86119 ] |
| Status | Reopen in Stage [ 10023 ] | In Development [ 10007 ] |
| Time Spent | 133.5h [ 480600 ] | 137.5h [ 495000 ] |
| Worklog Id | 86614 [ 86614 ] |
| Assignee | Prajakta Belhe [ prajakta.belhe ] | Swapnil Eksambekar [ swapnil.eksambekar ] |
| Item State | Parent values: Stage QA(10202)Level 1 values: Re-open(10216) | Parent values: Stage QA(10202)Level 1 values: Production Deployment on Hold(10224) |
| Time Spent | 137.5h [ 495000 ] | 138.5h [ 498600 ] |
| Worklog Id | 86614 [ 86614 ] |
| Time Spent | 138.5h [ 498600 ] | 140.5h [ 505800 ] |
| Worklog Id | 87613 [ 87613 ] |
| Time Spent | 140.5h [ 505800 ] | 142h [ 511200 ] |
| Worklog Id | 88580 [ 88580 ] |
| Attachment | WT-9319.xls [ 66903 ] |
| Time Spent | 142h [ 511200 ] | 143h [ 514800 ] |
| Worklog Id | 89270 [ 89270 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Status | Local Testing [ 10200 ] | Pending for Stage Approval [ 10300 ] |
| Status | Pending for Stage Approval [ 10300 ] | Approved for Stage [ 10030 ] |
| Status | Approved for Stage [ 10030 ] | Stage Testing [ 10201 ] |
| Time Spent | 143h [ 514800 ] | 144h [ 518400 ] |
| Worklog Id | 89270 [ 89270 ] |
| Time Spent | 144h [ 518400 ] | 145h [ 522000 ] |
| Worklog Id | 105612 [ 105612 ] |
| Production Due Date | 21/Sep/2017 | 05/Mar/2018 |
| Labels | Manual_Export |
| Time Spent | 145h [ 522000 ] | 145.5h [ 523800 ] |
| Worklog Id | 106657 [ 106657 ] |
| Status | Stage Testing [ 10201 ] | Pending for Production Approval [ 10301 ] |
| Status | Pending for Production Approval [ 10301 ] | Approved for production [ 10034 ] |
| Status | Approved for production [ 10034 ] | Production Testing [ 10202 ] |
| Resolution | Done [ 10000 ] | |
| Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
| Time Spent | 145.5h [ 523800 ] | 149h [ 536400 ] |
| Worklog Id | 107084 [ 107084 ] |
| Assignee | Swapnil Eksambekar [ swapnil.eksambekar ] | Damion Velasquez [ damion.velasquez ] |
Sachin Hingole (Inactive)
made changes -
| Status | Production Complete [ 10028 ] | Closed [ 6 ] |
