-
Type:
Enhancement
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Export
-
Reported by:Support
-
Item State:Development - On Hold
-
Sprint:WT Sprint 31 - Enhancement, WT Sprint 32 - Enhancement
-
Feature Category:New
-
Severity:Medium
Requirements are documented in the attached specs. It is kept in sync with Confluence page as of July 11, 2017.
- causes
-
WT-10650 OE dashboard -> Oe dashboard is getting Server Error
-
- Closed
-
-
-
- Resolution Setting
-
- relates to
-
-
- Resolution Setting
-
-
-
- Resolution Setting
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
WT-10493 Changes in OE dashboard export feature
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
(16 relates to)
| Field | Original Value | New Value |
|---|---|---|
| Module | Parent values: BenAdmin(10100) | Parent values: BenAdmin(10100)Level 1 values: Export(10110) |
| Assignee | Vijay Siddha [ vijays ] | Vinayak Kulkarni [ vinayak.kulkarni ] |
| Description |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are 400+ feeds at the time of OE. People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, we many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would maintain, along with feed details, resources allocated to ithem and also the critical dates. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. [~Yamilka.Coca] [~jackie.sivigny] [~Cindy.Wibbing] [~nick] |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are 400+ feeds at the time of OE. People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would maintain, along with feed details, people allocated to them and also the critical dates. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? [~Yamilka.Coca] [~jackie.sivigny] [~Cindy.Wibbing] [~nick] |
| Attachment | Open Enrollment.xlsx [ 46358 ] |
| Description |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are 400+ feeds at the time of OE. People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would maintain, along with feed details, people allocated to them and also the critical dates. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? [~Yamilka.Coca] [~jackie.sivigny] [~Cindy.Wibbing] [~nick] |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are *400+ feeds at the time of OE.* People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would *maintain, along with feed details, people allocated to them and also the critical dates*. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? Briefly, so far the following requirements have emerged. * Ability to export Excel file, which can be edited outside and imported back. * Maintain all important dates (OE start, OE end, Scheduled OE file sending, Year start) and automation of associated tasks (flipping flags and back, turning scheduler on/off). * History of changes? [~Yamilka.Coca] [~jackie.sivigny] [~Cindy.Wibbing] [~nick] |
| Attachment | Open Enrollment.xlsx [ 46358 ] |
| Attachment | Dashboard Field List.xlsx [ 46465 ] |
| Description |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are *400+ feeds at the time of OE.* People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would *maintain, along with feed details, people allocated to them and also the critical dates*. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? Briefly, so far the following requirements have emerged. * Ability to export Excel file, which can be edited outside and imported back. * Maintain all important dates (OE start, OE end, Scheduled OE file sending, Year start) and automation of associated tasks (flipping flags and back, turning scheduler on/off). * History of changes? [~Yamilka.Coca] [~jackie.sivigny] [~Cindy.Wibbing] [~nick] |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are *400+ feeds at the time of OE.* People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would *maintain, along with feed details, people allocated to them and also the critical dates*. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? Briefly, so far the following requirements have emerged. * Ability to export Excel file, which can be edited outside and imported back. * Maintain all important dates (OE start, OE end, Scheduled OE file sending, Year start) and automation of associated tasks (flipping flags and back, turning scheduler on/off). * History of changes? [^Dashboard Field List.xlsx] [~Yamilka.Coca] [~jackie.sivigny] [~Cindy.Wibbing] [~nick] |
| Attachment | Dashboard Field List.xlsx [ 46465 ] |
| Attachment | OE Dashboard Field List.xlsx [ 47481 ] |
| Description |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are *400+ feeds at the time of OE.* People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would *maintain, along with feed details, people allocated to them and also the critical dates*. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? Briefly, so far the following requirements have emerged. * Ability to export Excel file, which can be edited outside and imported back. * Maintain all important dates (OE start, OE end, Scheduled OE file sending, Year start) and automation of associated tasks (flipping flags and back, turning scheduler on/off). * History of changes? [^Dashboard Field List.xlsx] [~Yamilka.Coca] [~jackie.sivigny] [~Cindy.Wibbing] [~nick] |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are *400+ feeds at the time of OE.* People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would *maintain, along with feed details, people allocated to them and also the critical dates*. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? Briefly, so far the following requirements have emerged. * Ability to export Excel file, which can be edited outside and imported back. * Maintain all important dates (OE start, OE end, Scheduled OE file sending, Year start) and automation of associated tasks (flipping flags and back, turning scheduler on/off). * History of changes? [^OE Dashboard Field List.xlsx] ivigny] [~Cindy.Wibbing] [~nick] |
| Description |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are *400+ feeds at the time of OE.* People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would *maintain, along with feed details, people allocated to them and also the critical dates*. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? Briefly, so far the following requirements have emerged. * Ability to export Excel file, which can be edited outside and imported back. * Maintain all important dates (OE start, OE end, Scheduled OE file sending, Year start) and automation of associated tasks (flipping flags and back, turning scheduler on/off). * History of changes? [^OE Dashboard Field List.xlsx] ivigny] [~Cindy.Wibbing] [~nick] |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are *400+ feeds at the time of OE.* People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would *maintain, along with feed details, people allocated to them and also the critical dates*. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? Briefly, so far the following requirements have emerged. * Ability to export Excel file, which can be edited outside and imported back. * Maintain all important dates (OE start, OE end, Scheduled OE file sending, Year start) and automation of associated tasks (flipping flags and back, turning scheduler on/off). * History of changes? [^OE Dashboard Field List.xlsx] [~Cindy.Wibbing] |
| Attachment | OE-Dashboard-Requirements.docx [ 47632 ] |
| Attachment | OE Dashboard Field List.xlsx [ 47481 ] |
| Remaining Estimate | 60h [ 216000 ] | |
| Original Estimate | 60h [ 216000 ] |
| Remaining Estimate | 60h [ 216000 ] | 59h [ 212400 ] |
| Time Spent | 1h [ 3600 ] | |
| Worklog Id | 44836 [ 44836 ] |
| Attachment | OE-Dashboard-Requirements.docx [ 47632 ] |
| Attachment | OE-Dashboard-RequirementsV2.0.docx [ 47778 ] |
| Description |
Open Enrollment is the most busy time of the year and need to have a dashboard was discussed and agreed upon in a meeting between EDI Team with [~samir] and [~amitthorve]. Here is the problem statement and an outline of requirements. There are *400+ feeds at the time of OE.* People get assigned to feeds - and assignments are dynamic. Similarly the dates change. Typically the feed details are exported from WT and the Excel files are maintained with additional information. However, with many stake holders it is impossible to keep the information in sync. This breaks coordination and results in wastage of time and effort. We need a OE dashboard that would *maintain, along with feed details, people allocated to them and also the critical dates*. This will allow everyone to go to one place for information. The detailed requirement needs to be spelled out. We have also seen another communication gap. Client Executives share requirements with EDI team re the renewal details. Later at the time of Stage to Production move, Client Executives communicate with Development. On some occasions the communication with development differs from the information shared with EDI analysts earlier. We need to discuss and avoid this from happening. Will OE dashboard be the solution? Briefly, so far the following requirements have emerged. * Ability to export Excel file, which can be edited outside and imported back. * Maintain all important dates (OE start, OE end, Scheduled OE file sending, Year start) and automation of associated tasks (flipping flags and back, turning scheduler on/off). * History of changes? [^OE Dashboard Field List.xlsx] [~Cindy.Wibbing] |
Requirements are documented in the attached specs. [^OE-Dashboard-RequirementsV2.0.docx] |
| Comment |
[ I have replaced the dashboard field list with updates by Amit. Following are my notes. There may be some ambiguities due to my limited understanding. * There will be two types of fields (a) those extracted from WT (and are thus read-only) and (b) input by user (read-write). The user fields are highlighted in the spreadsheet. * We need to have some basic data integrity check in the dashboard. (E.g. OE end date > start date) * When there are multiple OE dates for a company, all the templates for that company will be marked with the earliest OE start and end dates. This is not supposed to hurt as flipping flag before start date is fine. End date doesn't drive anything. What matters is when the files are sent and when the new year begins. ({color:#d04437}What if the file send dates are different for different templates{color}?) * The templates will feature on dashboard ONLY IF they are on the scheduler. Therefore no active template should be made inactive or taken off the scheduler - e.g. after file is sent after OE. Instead the date should be set to beginning of the next plan year. (THis step could be automated.) For manual files - put it on the scheduler and send them to yourself (EDI analyst) via email. New feeds should be on the scheduler with beginning of the next year as the date. * Dashboard can be exported to Excel file, which can be edited outside and imported back. NOTE that when being imported, it SHOULD UPDATE the records and not OVERWRITE. In other words, each row in imported file should identify corresponding dashboard record (i.e. template) and update it. It SHOULD NOT wipe out entire dashboard and replace it with file. This is necessary as when a user exports file, they will export only those rows that they have permission to access. This is a note for the development. * A global template may span multiple companies. In case of global template, the dashboard should explode it to show all child templates. Notes: * Carrier contacts should be recorded in the notes section for the templates. * {color:#d04437}Handling termed plans - there was some issue about them. Need elaboration.{color} ] |
| Remaining Estimate | 59h [ 212400 ] | 56.75h [ 204300 ] |
| Time Spent | 1h [ 3600 ] | 3.25h [ 11700 ] |
| Worklog Id | 45329 [ 45329 ] |
| Remaining Estimate | 56.75h [ 204300 ] | 56.25h [ 202500 ] |
| Time Spent | 3.25h [ 11700 ] | 3.75h [ 13500 ] |
| Worklog Id | 45330 [ 45330 ] |
| Worklog Id | 45329 [ 45329 ] |
Lalit Kumar (Inactive)
made changes -
| Remaining Estimate | 56.25h [ 202500 ] | 55.25h [ 198900 ] |
| Time Spent | 3.75h [ 13500 ] | 4.75h [ 17100 ] |
| Worklog Id | 48670 [ 48670 ] |
Lalit Kumar (Inactive)
made changes -
| Remaining Estimate | 55.25h [ 198900 ] | 53.75h [ 193500 ] |
| Time Spent | 4.75h [ 17100 ] | 6.25h [ 22500 ] |
| Worklog Id | 48671 [ 48671 ] |
| Remaining Estimate | 53.75h [ 193500 ] | 52.25h [ 188100 ] |
| Time Spent | 6.25h [ 22500 ] | 7.75h [ 27900 ] |
| Worklog Id | 48808 [ 48808 ] |
Lalit Kumar (Inactive)
made changes -
| Remaining Estimate | 52.25h [ 188100 ] | 51.75h [ 186300 ] |
| Time Spent | 7.75h [ 27900 ] | 8.25h [ 29700 ] |
| Worklog Id | 49011 [ 49011 ] |
| Remaining Estimate | 51.75h [ 186300 ] | 50.5h [ 181800 ] |
| Time Spent | 8.25h [ 29700 ] | 9.5h [ 34200 ] |
| Worklog Id | 50641 [ 50641 ] |
| Attachment | OE-Dashboard-RequirementsV2.0.docx [ 47778 ] |
| Attachment | OE-Dashboard-RequirementsV2.1.docx [ 49915 ] |
| Attachment | OE-Dashboard-RequirementsV2.1.docx [ 49915 ] |
| Attachment | OE-Dashboard-RequirementsV2.1.docx [ 49916 ] |
| Remaining Estimate | 50.5h [ 181800 ] | 46.5h [ 167400 ] |
| Time Spent | 9.5h [ 34200 ] | 13.5h [ 48600 ] |
| Worklog Id | 50924 [ 50924 ] |
| Remaining Estimate | 46.5h [ 167400 ] | 44.5h [ 160200 ] |
| Time Spent | 13.5h [ 48600 ] | 15.5h [ 55800 ] |
| Worklog Id | 50947 [ 50947 ] |
| Worklog Id | 50947 [ 50947 ] |
| Remaining Estimate | 44.5h [ 160200 ] | 42.5h [ 153000 ] |
| Time Spent | 15.5h [ 55800 ] | 17.5h [ 63000 ] |
| Worklog Id | 51734 [ 51734 ] |
| Worklog Id | 51734 [ 51734 ] |
| Remaining Estimate | 42.5h [ 153000 ] | 41.75h [ 150300 ] |
| Time Spent | 17.5h [ 63000 ] | 18.25h [ 65700 ] |
| Worklog Id | 51804 [ 51804 ] |
| Attachment | OE Dashboard.zip [ 50394 ] |
| Attachment | OE-Dashboard.jpg [ 50395 ] | |
| Attachment | OE-Dashboard-column-open.jpg [ 50396 ] | |
| Attachment | OE-Dashboard-Group Template.jpg [ 50397 ] | |
| Attachment | OE-Dashboard-opt0.jpg [ 50398 ] | |
| Attachment | OE-Dashboard-opt1.jpg [ 50399 ] | |
| Attachment | OE-Dashboard-opt2.jpg [ 50400 ] |
| Attachment | OE-Dashboard.jpg [ 50395 ] |
| Attachment | OE-Dashboard-column-open.jpg [ 50396 ] |
| Attachment | OE-Dashboard-Group Template.jpg [ 50397 ] |
| Attachment | OE-Dashboard-opt0.jpg [ 50398 ] |
| Attachment | OE-Dashboard-opt1.jpg [ 50399 ] |
| Attachment | OE-Dashboard-opt2.jpg [ 50400 ] |
| Attachment | OE-Dashboard-RequirementsV2.1.docx [ 49916 ] |
| Attachment | OE-Dashboard-RequirementsV3.0.docx [ 50488 ] |
| Remaining Estimate | 41.75h [ 150300 ] | 39.75h [ 143100 ] |
| Time Spent | 18.25h [ 65700 ] | 20.25h [ 72900 ] |
| Worklog Id | 52141 [ 52141 ] |
| Remaining Estimate | 39.75h [ 143100 ] | 38.75h [ 139500 ] |
| Time Spent | 20.25h [ 72900 ] | 21.25h [ 76500 ] |
| Worklog Id | 52160 [ 52160 ] |
| Attachment | OE-Dashboard.jpg [ 50611 ] | |
| Attachment | OE-Dashboard-column-open.jpg [ 50612 ] |
| Attachment | OE-Dashboard-RequirementsV3.0.docx [ 50488 ] |
| Attachment | OE-Dashboard-RequirementsV3.1.docx [ 50686 ] |
| Remaining Estimate | 38.75h [ 139500 ] | 38.25h [ 137700 ] |
| Time Spent | 21.25h [ 76500 ] | 21.75h [ 78300 ] |
| Worklog Id | 52433 [ 52433 ] |
| Remaining Estimate | 38.25h [ 137700 ] | 35.25h [ 126900 ] |
| Time Spent | 21.75h [ 78300 ] | 24.75h [ 89100 ] |
| Worklog Id | 52641 [ 52641 ] |
| Remaining Estimate | 35.25h [ 126900 ] | 34.75h [ 125100 ] |
| Time Spent | 24.75h [ 89100 ] | 25.25h [ 90900 ] |
| Worklog Id | 52750 [ 52750 ] |
| Remaining Estimate | 34.75h [ 125100 ] | 29.25h [ 105300 ] |
| Time Spent | 25.25h [ 90900 ] | 30.75h [ 110700 ] |
| Worklog Id | 53021 [ 53021 ] |
| Remaining Estimate | 29.25h [ 105300 ] | 29.5h [ 106200 ] |
| Time Spent | 30.75h [ 110700 ] | 30.5h [ 109800 ] |
| Worklog Id | 53021 [ 53021 ] |
| Remaining Estimate | 29.5h [ 106200 ] | 25h [ 90000 ] |
| Time Spent | 30.5h [ 109800 ] | 35h [ 126000 ] |
| Worklog Id | 53503 [ 53503 ] |
| Assignee | Vinayak Kulkarni [ vinayak.kulkarni ] | Ganesh Sadawarte [ ganesh.sadawarte ] |
| Item State | Parent values: Development(10200) | Parent values: Development(10200)Level 1 values: In Analysis(10204) |
| Status | New Request [ 10029 ] | Pending for Approval [ 10002 ] |
| Status | Pending for Approval [ 10002 ] | Approved for Development [ 10003 ] |
| Remaining Estimate | 25h [ 90000 ] | 23.5h [ 84600 ] |
| Time Spent | 35h [ 126000 ] | 36.5h [ 131400 ] |
| Worklog Id | 53898 [ 53898 ] |
| Remaining Estimate | 23.5h [ 84600 ] | 18h [ 64800 ] |
| Time Spent | 36.5h [ 131400 ] | 42h [ 151200 ] |
| Worklog Id | 54020 [ 54020 ] |
Punam Satpute (Inactive)
made changes -
| Remaining Estimate | 18h [ 64800 ] | 17h [ 61200 ] |
| Time Spent | 42h [ 151200 ] | 43h [ 154800 ] |
| Worklog Id | 54026 [ 54026 ] |
| Remaining Estimate | 17h [ 61200 ] | 14h [ 50400 ] |
| Time Spent | 43h [ 154800 ] | 46h [ 165600 ] |
| Worklog Id | 54259 [ 54259 ] |
| Remaining Estimate | 14h [ 50400 ] | 12h [ 43200 ] |
| Time Spent | 46h [ 165600 ] | 48h [ 172800 ] |
| Worklog Id | 54268 [ 54268 ] |
| Remaining Estimate | 12h [ 43200 ] | 10h [ 36000 ] |
| Time Spent | 48h [ 172800 ] | 50h [ 180000 ] |
| Worklog Id | 54280 [ 54280 ] |
| Remaining Estimate | 10h [ 36000 ] | 2h [ 7200 ] |
| Time Spent | 50h [ 180000 ] | 58h [ 208800 ] |
| Worklog Id | 54671 [ 54671 ] |
| Remaining Estimate | 2h [ 7200 ] | 0h [ 0 ] |
| Time Spent | 58h [ 208800 ] | 64h [ 230400 ] |
| Worklog Id | 54676 [ 54676 ] |
| Status | Approved for Development [ 10003 ] | In Development [ 10007 ] |
| Time Spent | 64h [ 230400 ] | 68h [ 244800 ] |
| Worklog Id | 55003 [ 55003 ] |
| Time Spent | 68h [ 244800 ] | 71h [ 255600 ] |
| Worklog Id | 55459 [ 55459 ] |
| Sprint | WT Sprint 31 - Enhancement [ 64 ] |
| Time Spent | 71h [ 255600 ] | 72h [ 259200 ] |
| Worklog Id | 56439 [ 56439 ] |
| Time Spent | 72h [ 259200 ] | 73.5h [ 264600 ] |
| Worklog Id | 56455 [ 56455 ] |
| Time Spent | 73.5h [ 264600 ] | 74.5h [ 268200 ] |
| Worklog Id | 56468 [ 56468 ] |
| Time Spent | 74.5h [ 268200 ] | 76.5h [ 275400 ] |
| Worklog Id | 56473 [ 56473 ] |
| Time Spent | 76.5h [ 275400 ] | 78.5h [ 282600 ] |
| Worklog Id | 56482 [ 56482 ] |
| Time Spent | 78.5h [ 282600 ] | 79.5h [ 286200 ] |
| Worklog Id | 56482 [ 56482 ] |
| Time Spent | 79.5h [ 286200 ] | 80.5h [ 289800 ] |
| Worklog Id | 56491 [ 56491 ] |
| Time Spent | 80.5h [ 289800 ] | 81.5h [ 293400 ] |
| Worklog Id | 56622 [ 56622 ] |
| Time Spent | 81.5h [ 293400 ] | 83.5h [ 300600 ] |
| Worklog Id | 56889 [ 56889 ] |
| Time Spent | 83.5h [ 300600 ] | 86.5h [ 311400 ] |
| Worklog Id | 56893 [ 56893 ] |
| Time Spent | 86.5h [ 311400 ] | 88.5h [ 318600 ] |
| Worklog Id | 57927 [ 57927 ] |
| Time Spent | 88.5h [ 318600 ] | 119.5h [ 430200 ] |
| Worklog Id | 57931 [ 57931 ] |
| Remaining Estimate | 0h [ 0 ] | 28h [ 100800 ] |
| Time Spent | 119.5h [ 430200 ] | 91.5h [ 329400 ] |
| Worklog Id | 57931 [ 57931 ] |
| Remaining Estimate | 28h [ 100800 ] | 29h [ 104400 ] |
| Time Spent | 91.5h [ 329400 ] | 90.5h [ 325800 ] |
| Worklog Id | 57931 [ 57931 ] |
| Description | Requirements are documented in the attached specs. [^OE-Dashboard-RequirementsV2.0.docx] | Requirements are documented in the attached specs. (Attached here [^OE-Dashboard-RequirementsV3.1.docx] is in sync with [Confluence page|https://careerbuilder.atlassian.net/wiki/display/WTEDIDOC/OE+Dashboard+Requirements] as of June 26, 2017. |
Punam Satpute (Inactive)
made changes -
| Remaining Estimate | 29h [ 104400 ] | 25h [ 90000 ] |
| Time Spent | 90.5h [ 325800 ] | 94.5h [ 340200 ] |
| Worklog Id | 58436 [ 58436 ] |
Punam Satpute (Inactive)
made changes -
| Remaining Estimate | 25h [ 90000 ] | 21h [ 75600 ] |
| Time Spent | 94.5h [ 340200 ] | 98.5h [ 354600 ] |
| Worklog Id | 58437 [ 58437 ] |
| Remaining Estimate | 21h [ 75600 ] | 19h [ 68400 ] |
| Time Spent | 98.5h [ 354600 ] | 100.5h [ 361800 ] |
| Worklog Id | 58470 [ 58470 ] |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | Parent values: Development(10200)Level 1 values: In Progress(10206) |
| Remaining Estimate | 19h [ 68400 ] | 17h [ 61200 ] |
| Time Spent | 100.5h [ 361800 ] | 102.5h [ 369000 ] |
| Worklog Id | 58737 [ 58737 ] |
| Remaining Estimate | 17h [ 61200 ] | 15.5h [ 55800 ] |
| Time Spent | 102.5h [ 369000 ] | 104h [ 374400 ] |
| Worklog Id | 59420 [ 59420 ] |
| Remaining Estimate | 15.5h [ 55800 ] | 15h [ 54000 ] |
| Time Spent | 104h [ 374400 ] | 104.5h [ 376200 ] |
| Worklog Id | 59895 [ 59895 ] |
| Worklog Id | 59895 [ 59895 ] |
| Remaining Estimate | 15h [ 54000 ] | 14h [ 50400 ] |
| Time Spent | 104.5h [ 376200 ] | 105.5h [ 379800 ] |
| Worklog Id | 60039 [ 60039 ] |
| Remaining Estimate | 14h [ 50400 ] | 13h [ 46800 ] |
| Time Spent | 105.5h [ 379800 ] | 106.5h [ 383400 ] |
| Worklog Id | 60205 [ 60205 ] |
| Worklog Id | 60205 [ 60205 ] |
| Sprint | WT Sprint 31 - Enhancement [ 64 ] | WT Sprint 31 - Enhancement, WT Sprint 32 - Enhancement [ 64, 75 ] |
| Attachment | screenshot-1.png [ 54403 ] |
| Attachment | OE-Dashboard-RequirementsV3.1.docx [ 50686 ] |
| Attachment | OE+Dashboard+Requirements.doc [ 54807 ] |
| Attachment | OE+Dashboard+Requirements.doc [ 54807 ] |
| Attachment | OE+Dashboard+Requirements.doc [ 54808 ] |
| Remaining Estimate | 13h [ 46800 ] | 12h [ 43200 ] |
| Time Spent | 106.5h [ 383400 ] | 107.5h [ 387000 ] |
| Worklog Id | 62465 [ 62465 ] |
| Attachment | OE+Dashboard+Requirements.doc [ 54808 ] |
| Attachment | OE+Dashboard+Requirements.docx [ 54991 ] |
| Description | Requirements are documented in the attached specs. (Attached here [^OE-Dashboard-RequirementsV3.1.docx] is in sync with [Confluence page|https://careerbuilder.atlassian.net/wiki/display/WTEDIDOC/OE+Dashboard+Requirements] as of June 26, 2017. | Requirements are documented in the attached specs. It is kept in sync with [Confluence page|https://careerbuilder.atlassian.net/wiki/display/WTEDIDOC/OE+Dashboard+Requirements] as of July 11, 2017. |
| Attachment | OE+Dashboard+Requirements.mht [ 56080 ] |
| Attachment | OE+Dashboard+Requirements.mht [ 56080 ] |
| Attachment | OE+Dashboard+Requirements.docx [ 56081 ] |
| Attachment | OE+Dashboard+Requirements.docx [ 54991 ] |
| Remaining Estimate | 12h [ 43200 ] | 11h [ 39600 ] |
| Time Spent | 107.5h [ 387000 ] | 108.5h [ 390600 ] |
| Worklog Id | 65984 [ 65984 ] |
| Attachment | OE+Dashboard+Requirements.docx [ 56718 ] |
| Attachment | OE+Dashboard+Requirements.docx [ 56081 ] |
| Attachment | screenshot-2.png [ 56734 ] |
| Remaining Estimate | 11h [ 39600 ] | 9.5h [ 34200 ] |
| Time Spent | 108.5h [ 390600 ] | 110h [ 396000 ] |
| Worklog Id | 66913 [ 66913 ] |
| Remaining Estimate | 9.5h [ 34200 ] | 9h [ 32400 ] |
| Time Spent | 110h [ 396000 ] | 110.5h [ 397800 ] |
| Worklog Id | 66990 [ 66990 ] |
| Remaining Estimate | 9h [ 32400 ] | 8h [ 28800 ] |
| Time Spent | 110.5h [ 397800 ] | 111.5h [ 401400 ] |
| Worklog Id | 67033 [ 67033 ] |
| Remaining Estimate | 8h [ 28800 ] | 7.5h [ 27000 ] |
| Time Spent | 111.5h [ 401400 ] | 112h [ 403200 ] |
| Worklog Id | 67177 [ 67177 ] |
| Remaining Estimate | 7.5h [ 27000 ] | 7h [ 25200 ] |
| Time Spent | 112h [ 403200 ] | 112.5h [ 405000 ] |
| Worklog Id | 67483 [ 67483 ] |
| Remaining Estimate | 7h [ 25200 ] | 2.5h [ 9000 ] |
| Time Spent | 112.5h [ 405000 ] | 117h [ 421200 ] |
| Worklog Id | 67516 [ 67516 ] |
| Worklog Id | 67516 [ 67516 ] |
| Remaining Estimate | 2.5h [ 9000 ] | 2h [ 7200 ] |
| Time Spent | 117h [ 421200 ] | 117.5h [ 423000 ] |
| Worklog Id | 67516 [ 67516 ] |
Gaurav Sodani (Inactive)
made changes -
| Assignee | Ganesh Sadawarte [ ganesh.sadawarte ] | Swapnil Eksambekar [ swapnil.eksambekar ] |
| Remaining Estimate | 2h [ 7200 ] | 0h [ 0 ] |
| Time Spent | 117.5h [ 423000 ] | 121.5h [ 437400 ] |
| Worklog Id | 74110 [ 74110 ] |
| Worklog Id | 74110 [ 74110 ] |
| Time Spent | 121.5h [ 437400 ] | 123.5h [ 444600 ] |
| Worklog Id | 74138 [ 74138 ] |
| Time Spent | 123.5h [ 444600 ] | 126h [ 453600 ] |
| Worklog Id | 75009 [ 75009 ] |
Gaurav Sodani (Inactive)
made changes -
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: Development(10200)Level 1 values: On Hold(10207) |
| Time Spent | 126h [ 453600 ] | 127h [ 457200 ] |
| Worklog Id | 76281 [ 76281 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Attachment | Observation.png [ 61273 ] |
| Time Spent | 127h [ 457200 ] | 131h [ 471600 ] |
| Worklog Id | 78297 [ 78297 ] |
| Time Spent | 131h [ 471600 ] | 132h [ 475200 ] |
| Worklog Id | 80141 [ 80141 ] |
| Assignee | Swapnil Eksambekar [ swapnil.eksambekar ] | Ganesh Sadawarte [ ganesh.sadawarte ] |
| Status | Local Testing [ 10200 ] | Reopen in Local [ 10018 ] |
| Status | Reopen in Local [ 10018 ] | In Development [ 10007 ] |
| Assignee | Ganesh Sadawarte [ ganesh.sadawarte ] | Swapnil Eksambekar [ swapnil.eksambekar ] |
| Assignee | Swapnil Eksambekar [ swapnil.eksambekar ] | Ganesh Sadawarte [ ganesh.sadawarte ] |
| Time Spent | 132h [ 475200 ] | 133h [ 478800 ] |
| Worklog Id | 82246 [ 82246 ] |
| Assignee | Ganesh Sadawarte [ ganesh.sadawarte ] | Swapnil Eksambekar [ swapnil.eksambekar ] |
| Attachment | OE+Dashboard+Requirements.docx [ 56718 ] |
| Attachment | OE+Dashboard+Requirements.doc [ 63631 ] |
| Status | In Development [ 10007 ] | Mockup Approval [ 10010 ] |
| Status | Mockup Approval [ 10010 ] | Mockup Approved [ 10012 ] |
| Status | Mockup Approved [ 10012 ] | In Development [ 10007 ] |
| 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 ] |
| 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 ] |
| Resolution | Done [ 10000 ] | Fixed [ 1 ] |
| Status | Production Complete [ 10028 ] | Closed [ 6 ] |
| Time Spent | 133h [ 478800 ] | 133.5h [ 480600 ] |
| Worklog Id | 84597 [ 84597 ] |
| Time Spent | 133.5h [ 480600 ] | 135.5h [ 487800 ] |
| Worklog Id | 87768 [ 87768 ] |
