-
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
-
| 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 ] |
Lalit Kumar (Inactive)
logged work - 11/May/17 08:07 AM -
- Time Spent:
- 1h
-
Going through document shared.
-
- Time Spent:
- 1h
-
brainstorming over the concept.
| Remaining Estimate | 60h [ 216000 ] | |
| Original Estimate | 60h [ 216000 ] |
| Remaining Estimate | 60h [ 216000 ] | 59h [ 212400 ] |
| Time Spent | 1h [ 3600 ] | |
| Worklog Id | 44836 [ 44836 ] |
-
- Time Spent:
- 2.25h
-
Call with Abhay and Amit
Pre-call discussion
| 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} ] |
Hi All,
While going through document, We have come up with an suggestion which will avoid need to sync system data with dashboard data.
We will have data structure ( table ) to hold only user input values of OE dashboard and not for the values which are sourced from system data.
While listing templates, we will get templates which are on scheduler with system information like templates flags, group template name, schedule details etc, along with this if there is an information present for particular template in dashboard data structure then will also show those along with system information, if there is nothing in dashboard data structure for a particular template then we'll show only system information along with empty ( blank ) user input values.
We can update OE start date and end date from company information page to dashboard data structure in real time. So whenever OE dates are entered/updated on company information page, we can update same dates including logic of earliest effective date in case of multiple open enrollments to dashboard data structure.
All other logic of background process will remain same on dashboard data. Let us know your views on same.
| 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 ] |
Vinayak Kulkarni - your suggestions are great.
As I understand, you are talking about the implementation detail and there is no change in the functionality (that is exposed to the user) envisaged in the requirement document.
Thanks!
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 ] |
-
- Time Spent:
- 2h
-
OE Dashboard Discussion.
-
- Time Spent:
- 1.25h
-
Discussion on page design & OE dashboard features
| 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 ] |
Vinayak Kulkarni - I have uploaded a slightly revised version. [^OE-Dashboard-RequirementsV2.1.docx]
Have added the following in the requirements.
Note: User update of OE dates needs to be synchronized with all other templates of that company. In other words, when OE dates for a template are edited by the user, OE dates on all templates belonging to that company need to be updated.
CC Amit Thorve Satya
| Attachment | OE-Dashboard-RequirementsV2.1.docx [ 49915 ] |
| Attachment | OE-Dashboard-RequirementsV2.1.docx [ 49916 ] |
Hi Abhay Patil
Noted it.
Actually during analysis and mock-ups discussion, we came up with new idea to have two tables instead of showing everything in one table on screen.
First table would contain only company specific data and OE dates goes there and second table would contain template specific data. By this we need to update OE dates for company which will be considered for all the template on that company.
This might be little confusing to you right now. We are creating two mock-ups, first that we had discussed in call ( single row for every template ) and second one which i mentioned above.
Once we are done with mock-ups then we can have call to discuss both to make everyone on same page.
| 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 ] |
-
- Time Spent:
- 0.75h
-
OE Dashboard Mock-up Review.
| Remaining Estimate | 44.5h [ 160200 ] | 42.5h [ 153000 ] |
| Time Spent | 15.5h [ 55800 ] | 17.5h [ 63000 ] |
| Worklog Id | 51734 [ 51734 ] |
| Worklog Id | 51734 [ 51734 ] |
Hi Abhay Patil and Amit Thorve
We would be done with Mock-ups creation soon,
Can we have call on 06/02/2017 at 10am IST to discuss these mock-ups?
Thanks,
Vinayak
Sure Vinayak Kulkarni - please schedule and send calendar invite for the meeting.
-
- Time Spent:
- 0.5h
-
Discussion with Vinayak G on OE Dashboard and providing Inputs - 0.5 hr
Vinayak Kulkarni I am fine with the time as well.
| 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 ] |
As we discussed, here I have attached OE dashboard mockups, Please go through it and share your feedback.
OE Dashboard.zip
Thanks,
Vinayak G
Attached Mockups as discussed in call.
Abhay Patil, Amit Thorve; Please let us know your feedback on this.
Regards,
Satya Prakash
| 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 ] |
I have uploaded the latest version of the requirement document. I have added a few questions too.
I have not commented on option 1 and 2. As per the meeting, we recommend one row per template where company information is repeated.
| 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 ] |
Hi Amit Thorve,
As per our discussion, I have updated the option one. Where user can manage the column order by using drag and drop and clicking on the icon.
Please check the attached design and confirm.
Thanks,
Vinayak
This looks good to me. Abhay Patil, Cindy Wibbing Please check this.
| Attachment | OE-Dashboard-RequirementsV3.0.docx [ 50488 ] |
| Attachment | OE-Dashboard-RequirementsV3.1.docx [ 50686 ] |
Thanks Vinayak Ghanwat - this is good.
Vinayak Kulkarni, Satya Amit Thorve - please see the updated requirements document, especially for filters, grid management, import/export and data constraints.
| 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 ] |
-
- Time Spent:
- 1h
-
Meeting Regarding OE dashbaord
We have some queries related to how filters would be shown on screen and wanted to discuss to clear those queries, Can we have a call tomorrow 06/08/2017 at 10am IST to discuss this?
If yes, I will send meeting invite for the same. Thanks.
Vinayak Kulkarni I am not available at 10.00am IST. Can we have this meeting at 8.00am IST or 11.00am IST?
-
- Time Spent:
- 5.25h
-
1) Internal Discussion
2) Open enrollment meeting
3) Analysis
4) Queries
11:00am will be fine with us, Abhay Patil is this fine with you?
| 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 ] |
Vinayak Kulkarni Amit Thorve - yes 11 AM IST (i.e. 10:30 PM PST) will be okay for me. Please send me the invite.
Amit Thorve Abhay Patil Gaurav Sodani Ganesh Sadawarte Punam Satpute Pallavi Kulkarni Aniruddha Dev
Hi All,
Thanks for taking out your time. Please find the MoM of our discussion today(06/08/2017).
1. UI:
- The approach shown by Vinayak for Advance filter is good to go with.
- "Blank" or "Empty" option will be shown for each Advance filter which will indicate filter is applied with blank value
- Multiple select as well as Single select will be applicable based on the values the specific filter carries
2. Concurrent usage of dashboard by multiple users
- Team needs to discuss with Amit and finalize the approach on the change control and refresh approach, this is a specific condition when 2 or more concurrent users are working on the OE dashboard at once
3. OE dashboard separate table
- Harbinger team needs to decide whether OE dashboard will be using the system data to pull out filer specific data or maintaining a separate table for OE dashboard. This has been proposed in order to decrease the latency that would be caused because of the huge amount of data which needs to be scanned. However, harbinger team needs to consult the Performance team and understand the current implementation latency
4. Blackout Period:
- The requirement is understood
- Amit to confirm on which date needs to be considered for swapping the Flag from YES to NO and shifting schedule to next enrollment year.
- File due date
- File sent date
Please add if anything is missing here. Thanks.
-
- Time Spent:
- 4.5h
-
1) Call for open enrollment dashboard discussion.
2) Internal discussion
3) Analysis.
Punam Satpute (Inactive)
logged work - 08/Jun/17 12:00 PM -
- Time Spent:
- 1h
-
Call for open enrollment dashboard discussion
-
- Time Spent:
- 1h
-
Call for open enrollment dashboard discussion
| 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 ] |
-
- Time Spent:
- 5.5h
-
1) Design Team Meeting
2) Analysis and documentation.
3) Internal discussion.
| Remaining Estimate | 25h [ 90000 ] | 23.5h [ 84600 ] |
| Time Spent | 35h [ 126000 ] | 36.5h [ 131400 ] |
| Worklog Id | 53898 [ 53898 ] |
-
- Time Spent:
- 1h
-
Design team meeting - Open Enrollment Dashboard Data structure
Abhay Patil,Vinayak Kulkarni,Gaurav Sodani,Pallavi Kulkarni,Punam Satpute
Hi Amit Thorve,
Please check below summary of our discussion.
1) We will update open enrollment dashboard data at same time whenever any field get changed in the system which is referenced in open enrollment dashboard, so we don't need any sync service.
2) We will have another input column on open enrollment dashboard for black out period, which will have default value to 'Yes', if some one don't want to consider as black out period for that specific template then set value to 'No'. The value of this input will determine whether to shift schedule start date to next enrollment year.
3) OE file Due date will consider to set current year flag to 'No' and set schedule start date to next enrollment year.
4) While importing data,keep only those rows which we want to update into open enrollment dashboard and delete other rows from excel file. Also we will show the note on open enrollment dashboard.
5) If user enter open enrollment start date and end date then it will populate for all templates of that same company.
6) Once open enrollment start date and end date are entered into company information and reflected into OE dashboard then user should not be able update again. We will show those fields as non editable.
7) We need to check for new template as well as new company is added in WT. While adding new company will add this point into our check list.
8) Configuration Screen - User access restriction of import/export functionality.
Thanks,
Ganesh
| 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 ] |
Gaurav Sodani (Inactive)
added a comment - Looping Nagini to OE dashboard thread++
CC Nagini Indugula
Regards
Gaurav -
- Time Spent:
- 8h
-
1) Discussion with Amit
2) Internal Discussion
3) Work break down structure/ task identification.
4) Open enrollment JIRA update for summary point.
| 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 ] |
-
- Time Spent:
- 6h
-
1) Work break down structure with estimation
2) Analysis
3) Internal discussion with team for new field implementation.
| Remaining Estimate | 2h [ 7200 ] | 0h [ 0 ] |
| Time Spent | 58h [ 208800 ] | 64h [ 230400 ] |
| Worklog Id | 54676 [ 54676 ] |
| Status | Approved for Development [ 10003 ] | In Development [ 10007 ] |
Amit Thorve,Abhay Patil,Vinayak Kulkarni,Gaurav Sodani,Pallavi Kulkarni,Punam Satpute
Hi All,
There are total 31 fields given in OE dashboard and out below three fields are not exits in system. so we are implementing these fields into system as part of OE dashboard development.
1) Client Executive
2) EDI Executive (for Company) .
3) Carrier Contact.
There is an enhancement WT-9262 which need implementation of Client Executive and EDI Executive (for Company) fields in system. As per requirement document if these fields are implemented in the system then we need to show this as read only on open enrollment dashboard. So we will display it as text as we are implementing those into system, if no value selected then blank will populate on dashboard.
Thanks,
Ganesh
-
- Time Spent:
- 4h
-
1) Call with Amit
2) Internal discussion with satya and team for new field implementation
3) Discussion UI team.
4) Update analysis on JIRA
5) Analysis document creation.
| Time Spent | 64h [ 230400 ] | 68h [ 244800 ] |
| Worklog Id | 55003 [ 55003 ] |
-
- Time Spent:
- 3h
-
- Internal Discussion
- Created Test plan and sent to Rakesh, Vijay, Samir, Satya and Gaurav for review.
| Time Spent | 68h [ 244800 ] | 71h [ 255600 ] |
| Worklog Id | 55459 [ 55459 ] |
-
- Time Spent:
- 1.5h
-
OE Dashboard meeting for preparing test plan along with Hrishikesh and Swapnil
-
- Time Spent:
- 1h
-
Analysis and Discussion about req doc along with Swapnil
-
- Time Spent:
- 3h
-
Discussion with UI team
Internal discussion
-
- Time Spent:
- 2h
-
Continue analysis,Test Scenarios discussion, Revise Test Plan along with Hrishikesh and Swapnil
| Sprint | WT Sprint 31 - Enhancement [ 64 ] |
-
- Time Spent:
- 1h
-
TC writing , Reviewing , Discussion about OE dashboard testing
| 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:
- 3h
-
1) Internal Discussion
2) Discussion with UI team
3) Implementation change possibility for dashboard
| 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:
- 2h
-
Discussion and analysis.
Meeting
-
- Time Spent:
- 0.5h
-
Discussion with Hrishikesh and Gaurav regarding new WBS
| 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 ] |
-
- Time Spent:
- 1.5h
-
Discussion and Review of new WBS shared by Gaurav
| 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 ] |
Attaching screenshot of current developed page.
Note: Development is in progress and few small changes are still pending.
-
- Time Spent:
- 1.5h
-
meeting in Gir Regarding Delayed points and current Status and test planning
Hi Amit Thorve and Abhay Patil
We got one query about shifting Schedule start day to first day of next enrollment year.
Here we are fine with company level template which are on scheduler, we can get next enrollment year's start date from company information.
But, How about group level templates? they can have multiple companies involved and which companies enrollment period should we look for?
Shall we look enrollment period for any one of the group companies or we shall not update schedule for group templates? let us know your views on the same. Thanks.
| 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 ] |
-
- Time Spent:
- 0.5h
-
Discussion and Examining the slowness on OE Dashbaord
| 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. |
Vinayak Kulkarni and Abhay Patil Here is what I feel should happen for Group Level Templates:
1. The Black Out Period flag should be set to YES for all company level feeds under group level (if Black out Period needs to be set).
2. If Black Out period flag is set to NO for any company feed under group level feed then Black Out period is considered as NO for that global level feed.
3. If multiple companies feeds are grouped under Global Level feed and if those companies have different financial year in that case financial year of the first company in the sequence is considered to set the schedule.
*Note: *As per my advice, we should not set black out period for global feeds which consists of multiple company level feeds having different financial year.
CC-Cindy Wibbing, Van Nguyen, Chris Ellenberger, Damion M Velasquez, Kevin Hale, Rochelle Thomas, Nathaniel Cornejo-Walker
-
- Time Spent:
- 1h
-
Integration test planning along with Swapnil
-
- Time Spent:
- 0.5h
-
OE Dashboard weekend test planning along with swapnil
-
- Time Spent:
- 5h
-
Integration and regression testing ,Data creation, Discussion among team, Bug Status Report Creation along with Swapnil, Mock Demo , Demo
| 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 ] |
Amit Thorve
While doing a demo for the CE and CT teams today it was brought to our attention that the values set on the company page for Fiscal Start and Fiscal End dates is not driven by the renewal date for Open Enrollment but can be setup based on such things as life plans for the company. The company may have a renewal date of January 1 but have the Fiscal Settings on the company page set to July 1 because of the way the salary updates need to be addressed.
In light of this information it sounds like we may need to make adjustments to the OE Dashboard to pull the renewal information instead of these fields.
Vinayak Kulkarni We need to check this out. Based on Cindy's above mentioned comment, we might need to keep this field editable. We will populate the values based on Fiscal year settings from Company Info but will allow the user to override the same.
| 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 ] |
-
- Time Spent:
- 4h
-
Stage check in and testing
| 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:
- 2.5h
-
Basic OE Dashboard testing on stage.
Adding testing feedback reported by Van Nguyen.
Error:
Austin: template: TEST VSP Van
“EDI Analyst” field. I tried to overwrite this field with “Van Nguyen,” but I got a message stating “No changes found” after I clicked “Save.”
In “Advanced Filtering,” there’s no option to “Check All” or “Uncheck All”
Success:
“OE Start Date” field. I added 10/01/2017 and it saved successfully.
“OE End Date” field. I added 10/31/2017 and it saved successfully.
“OE File Due Date” field. I added 12/01/2017 and it saved successfully.
“Is New Structure” field. I clicked on the checkbox and it saved successfully.
“OE File Sent Date” field. I added 12/01/2017 and it saved successfully.
“Carrier Confirmation Date” field. I added 12/5/2017 and it saved successfully.
“Data Discrepancies Processed” field. I added 12/6/2017 and it saved successfully.
Hi Abhay Patil,
We have created JIRA WT-10864 for above issue.
Please check and let us know if you have any questions.
Thanks,
Ganesh
| 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:
- 1h
-
Discussion and QA estimates for Prod deployement
| Time Spent | 126h [ 453600 ] | 127h [ 457200 ] |
| Worklog Id | 76281 [ 76281 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
Hi Abhay and Amit,
We need to discuss below one point related to OE dashboard.
Currently, Whenever someone enters OE dates on company information page then those dates gets reflected into dashboard and after that those date cannot be modified from dashboard.
For this year, there won't be any problems with this, However when we go to next year and come closer to next year's OE then these dates will still be there and user cannot modify it as those dates were entered on Company information.
One solution to this could be reset "updated from company" flag ( we use this to determine whether to allow user to modify OE dates ) on a particular date automatically.
This date could be OE end date of respective company. Let us know your views on same. Thanks.
-
- Time Spent:
- 1h
-
Production Dep discussion with Swapnil E
| Attachment | Observation.png [ 61273 ] |
Hi Vinayak Kulkarni and Ganesh Sadawarte,
Take a note of below observations:-
1.As per implementation , During File importing we have to delete rows for the templates which we dont want to change as they are not reflected on OE dashboard,but when we insert any another value in deleted rows,it will create bad file for that with unknown Company ID .
2.All data flushed out after making schedule off for Group / Company level templates,i.e values saved before scheduling off ,it will not persists on Dashboard again.(Editable fields such as EDI analyst,OE start date ,End date)
3.: If OE start date and OE end date are editable from OE dashboard,after exporting it as per implementation ,we can change Dates from exporte file and Insert new dates,But for one company it should reflect one OE start date or end date for all templates ,which is not handled for importing.
For example, If OE start date is 09/06/2017 and OE end date is 09/07/2017 for all templates , when we export it and done changes for only one template as OE start date 06/01/2017 and OE end date 06/06/2017 then it is only reflected for one template as shown in attachment below.
It is causing discrepancy.
CC-Amit ThorveAbhay PatilHrishikesh DeshpandeAniruddha DevGaurav SodaniRakesh Roy
| Time Spent | 127h [ 457200 ] | 131h [ 471600 ] |
| Worklog Id | 78297 [ 78297 ] |
-
- Time Spent:
- 1h
-
OE dashboard production testing and discussion
| 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 ] |
As all linked WT tickets are assigned to QA, assigning parent ticket to QA as well.
| 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:
- 2h
-
Discussion and reply to Queries
-
- Time Spent:
- 0.5h
-
Need to discuss OE Dashboard questions
| Time Spent | 133h [ 478800 ] | 133.5h [ 480600 ] |
| Worklog Id | 84597 [ 84597 ] |
| Time Spent | 133.5h [ 480600 ] | 135.5h [ 487800 ] |
| Worklog Id | 87768 [ 87768 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
51d 7h 33m | 1 |
|
5s | 1 |
|
4d 21h 50m | 1 |
|
25d 17h 30m | 1 |
|
4s | 1 |
|
8d 13h 49m | 1 |
|
8s | 1 |
|
4s | 1 |
|
79d 7h 30m | 2 |
|
8s | 1 |
|
6s | 1 |
|
2s | 1 |
|
3s | 1 |
|
7s | 1 |
|
3s | 1 |
|
16s | 1 |
|
5d 3h 53m | 1 |
I have updated specs based on meeting on 5/11/2017. [^OE-Dashboard-RequirementsV2.0.docx]