Cybertrax 2.1 Client (project plan)
From UG
About this doc
This wiki provides all Proj Management info for Cybertrax 2.1 Client project.
Intro
This project is very important therefore planning is critical.
Time vs Features vs Quality
Focus of this project is to deploy minimal set of core features ASAP. As a result feature set will be reduced to minimum and quality might be average (but must not fall below reasonable level)
Time allocated and Error margin
Summary of time allocated:
* only 1 week for analysis and requirements gathering
* only 1 week for design
* only 3 weeks for coding, testing, rollout/training planning
* only 1 week for staging/release
-----------------
Total: 6 weeks
NOTE: This is an estimate. Error is -1 week/+2 weeks.
Project documentation
All information is gathered and structured in several wikis under Category:Cybertrax 2.1 Client
Current list of docs:
Cybertrax 2.1 Client (Q and A) Cybertrax 2.1 Client (data dictionary) Cybertrax 2.1 Client (design) Cybertrax 2.1 Client (glossary) Cybertrax 2.1 Client (project plan) Cybertrax 2.1 Client (requirements) Cybertrax 2.1 Client (use cases)
Project communication
All communication is done through:
- mantis
- Skype
- email (everyone must check min 2 times a day and reply or at least confirm e-mail received same day)
- Q and A wiki article: Cybertrax 2.1 Client (Q and A)
All mantis tasks are under this parent: http://mantis.jaguarfreight.com/mantis/view.php?id=2077
Project broadcasts and forum
- Broadcasts / News posted into mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=2127
- Questions / answers about proj planning should be posted there as well
Project update meetings
- who must attend: Andrei, Sasha, Alex, Denise, Tira
- Tuesd, Thursd 10-11am
- Skype chat
- Coordinator on NY side / Host: Alex
- Coordinator on Kiev side: Sasha
Project Team and responsibilities
- Alex - Proj Manager and Solutions Architect; responsible for:
- proj management/coordination
- solution architecture/structure
- helping everyone as required
Requirements and Documentation Team
- Denise - Business Analyst, RFP Lead; responsible for:
- gathering requirements and interfacing stackeholders/clients/module owners
- documenting requirements (#RFP specs)
- must help Sys Analysts to discover info
- proof reading/editing docs (in terms of English lang)
- Tira - Systems analyst, UI/UC Lead; responsible for:
- creating solution based on requirements
- documenting design
- focus on creating user interface mockups, use cases (UC)
- helping Denise in more technical aspects of requirements gathering/analysis
- Andrei - Systems analyst, 3CS lead; responsible for:
- creating solution based on requirements
- documentation (managing #3CS specs)
- focus on analysing all existing docs and making sure nothing is missing
- face to face meetings with dev leads / developers about specs/design in some cases as required
- answer questions from developers/ dev leads about specs
Implementation team
- Kostya - Development Manager
- Sasha - Lead developer
- serving as a communication liaison between Implementation team (Kiev) and Requirements team (NY)
- Andriy - Developer
- Roma - QA and Support
Workflows
Specs workflow
- Sys Arch (Alex) provides high level breakdown into components / wiki sections
- BA (Denise) creating:
- "(requirements) wiki", #RFP specs type
- "business story" for (use case) wiki
- SA1 (Tira) creates use cases (UI mockups+descr) based on "business story" and "(requirements) wiki"
- SA1 (Tira) helps Denise with more technical parts of "(requirements) wiki"
- Tira and Denise review/proof read each other work
- Completed sections get passed to SA2 (Andrei). His goal is:
- a) transform #RFP specs into #3CS specs:
- asking questions (if something is incomplete/incorrect/unclear)
- first reach out to Denise (business req questions) or Tira (if more technical question). If they for some reason can not answer then escalate to Sys Arch (use this option with care - SAs/BAs should be able to make your own decisions)
- rewriting/restructuring spec as required
- asking questions (if something is incomplete/incorrect/unclear)
- b) update them if new info comes in
- c) assigns into Estimation
- answer questions from Developers and Dev Leads (walk them through spec in face to face in some cases as required )
- Note: #Black box design has additional specs of updating spec after Dev is completed
- a) transform #RFP specs into #3CS specs:
- Sys Arch:
- resolves escalations
- reviews final specs (in some cases) and assigns into Estimation if it is good
Dev and QA workflow
As usual
Tasks
It is very important to find a good way to disect an monster into pieces to be able to digest it.
Requirements and Documentation tasks
- 2126 Shipper functionality - Finalize specs/document
- 2128 Planner functionality - Finalize specs/document
- 2129 Jaguar functionality - Finalize specs/document
- 2122 Misc functionality - Finalize specs/document
Support tasks
- 0002140: (Client 2.1) Create User Guide, Rollout Schedule, Training Plan, Support plan
Implementation tasks
week 1
- 2134 (Client 2.1) (implementation) Add Shipper, Planner roles to Non Jag User profile
- 2135 (Client 2.1) Create all new DB fields
week 2
- 2136 (Client 2.1) Code core Shipper functionality (create/edit/delete/list CTs)
- 2137 (Client 2.1) Code core Planner functionality (authorize/list CTs)
week 3
- 2138 (Client 2.1) Code all Jaguar functionality (new fields, constraints, Approval Report)
- 2139 (Client 2.1) Code all misc functionality (notifications, etc)
Weekly Plan Phase One
Note: This plane has been approved!
Important Dates
- 1st date for Release: Thur, July 15
- 2nd date for Release: Thur, July 22
week 1: June 7 Mon - June 11 Fri
Plan
- meetings with clients
- preliminary design sessions
- end of the week targets:
- requirements: 50% done
- design: 30% done
- documentation: 10% done
- coding: 0% done
- QA: 0% done
Actual
Completed as planned!
week 2: June 14 Mon - June 18 Fri
Plan
- analyze requirements
- invent design
- write detailed documentation
- Wed 2pm: send draft to Simon, Marc
- Fri 4pm: send ver 1.0 to Bill
- end of the week targets:
- requirements: 80% done
- design: 70% done
- documentation: 60% done
- coding: 5% done
- QA: 0% done
Actual
Completed as planned!
week 3: June 21 Mon - June 25 Fri
Coding week #1 (Calendar week#26)
Plan
- Mon/Tue tasks for every developer must be defined/assigned, start coding
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- end of the week targets :
- specs:
- 2126 Shipper functionality - Finalize specs/document
- 2128 Planner functionality - Finalize specs/document
- code:
- complete [andriy] 2134 (Client 2.1) (implementation) Add Shipper, Planner roles to Non Jag User profile
- complete [kostya] 2135 (Client 2.1) Create all new DB fields
- start [sasha] 2136 (Client 2.1) Code core Shipper functionality (create/edit/delete/list CTs)
- metrics:
- code: 30% done
- QA: 20% done
- specs:
Actual
TBD
week 4: June 28 Mon - July 2 Fri
Coding week #2 (Calendar week#27)
Plan
- continue coding and QA
- start UC testing
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- end of the week targets
- specs:
- complete: 2129 Jaguar functionality - Finalize specs/document
- complete: 2122 Misc functionality - Finalize specs/document
- code:
- complete: 2136 (Client 2.1) Code core Shipper functionality (create/edit/delete/list CTs)
- start: 2137 (Client 2.1) Code core Planner functionality (authorize/list CTs)
- metrics:
- code: 60% done
- QA: 40% done
- specs:
Actual
TBD
week 5: July 5 Mon - July 9 Fri
Coding week #3 (Calendar week#28)
Plan
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- end of the week targets
- specs:
- complete: 0002140: (Client 2.1) Create User Guide, Rollout Schedule, Training Plan, Support plan
- code:
- completed 2137 (Client 2.1) Code core Planner functionality (authorize/list CTs)
- completed 2138 (Client 2.1) Code all Jaguar functionality (new fields, constraints, Approval Report)
- completed 2139 (Client 2.1) Code all misc functionality (notifications, etc)
- metrics:
- code: 100% done
- QA: 100% done
- specs:
Actual
TBD
week 6: July 12 Mon - July 16 Fri
(Calendar week#29)
Plan
- QA on staging
- Release
- Training users
- Mon 9am: release to Staging
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- Thur 7-8pm: release to Production
Actual
TBD
week 7: July 19 Mon - July 23 Fri
(Calendar week#30)
Plan
- "2nd release date" in case we could not release previous week
- Mon 9am: release to Staging
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- Thur 7-8pm: release to Production
Actual
TBD
Appendix. Two types of specs
Lets introduce the following.
RFP specs
All specs start as informal collection of information. At this stage they could be considered as a Request For Proposal. That is why this type of spec called "RFP type". .
3CS specs
Gradually specs should take shape and finally considered to comply to 3CS:
- complete
- correct
- clear
- structured
These type of specs we call "3CS specs".
Appendix. Two types of Design methodology
Lets introduce the following.
White box design
What we follow now in most cases:
- Requirements doc completed
- Sys analyst creates and documents Design based on Requirements doc
- Design goes through review process
- developer codes based on Design doc
- QA tests based on Design doc
Black box design
Alternative approach:
- Requirements doc completed
- Developer codes based on Requirements doc (creating functional Prototype)
- Sys analyst creates and documents Design based on Prototype
- Design and Prototype go through review process
- QA tests based on Design doc
Project log and Meeting Notes
Meeting Thursday Jul 15
Meeting Major Conclusions
- proj is on schedule
- Tira will be responsible for UAT
- Denis gets pulled into another project and available on as needed basis
- Roma: QA full time. If you have no new tasks pls try to come up with various use cases you did not test. Also pls post into mantis what specifically you tested. And do not forget to test all info in Data Dictionary wiki.
Chat Transcript
[7/15/2010 2:32:33 PM] *** alex dobrovolsky added Alex Pivnyak *** [7/15/2010 2:32:52 PM] *** alex dobrovolsky added Роман Лахно *** [7/15/2010 2:32:57 PM] *** alex dobrovolsky added Montira Rattanavijit *** [7/15/2010 2:33:41 PM] alex dobrovolsky: Hi guys! I created this group chat. Just waiting for Tira to join... [7/15/2010 2:34:09 PM] Alex Pivnyak: Hi all [7/15/2010 2:34:16 PM] Роман Лахно: hi [7/15/2010 2:35:08 PM] alex dobrovolsky: Great, probably in 10-15 min we can start. Let me prepare agenda... [7/15/2010 2:44:54 PM] alex dobrovolsky: Agenda: • Proj Manager update (Alex) a. Yesterday’s client demo b. Denis completed her BA role, now on as needed basis; Tira – main point of contact c. Current Release sched • Dev Manager update (Sasha) a. What tasks are still in Dev and when they will be completed b. Any questions/issues • QA update a. Status of QA tasks b. Any questions/issues • Sys An update (Tira) a. Status of spec (all up to date?) b. Questions, issues [7/15/2010 2:46:05 PM] alex dobrovolsky: Guys, pls meanwhile make sure all Mantises are up to dat - correct status/dfolder [7/15/2010 2:48:36 PM] Alex Pivnyak: I just now sent 2 my completed tasks to Roma, so hi can start test it tomorrow morning [7/15/2010 2:52:42 PM | Removed 2:52:48 PM] Alex Pivnyak: This message has been removed. [7/15/2010 2:59:28 PM] Montira Rattanavijit: Hi all [7/15/2010 2:59:34 PM] Роман Лахно: hi [7/15/2010 3:02:47 PM] alex dobrovolsky: Ok, Let's start [7/15/2010 3:03:11 PM] alex dobrovolsky: 1) PM's update [7/15/2010 3:04:00 PM] alex dobrovolsky: a) Marc demonstrated system on Demo server to the Client and as he said "everything went very well" [7/15/2010 3:04:18 PM] alex dobrovolsky: No additional details has benn provided. [7/15/2010 3:04:47 PM] alex dobrovolsky: But I would like to thank everyone - we passed important milestone! [7/15/2010 3:05:07 PM] Alex Pivnyak: thank you :) [7/15/2010 3:05:13 PM] Montira Rattanavijit: Thank you [7/15/2010 3:05:25 PM] Роман Лахно: and one from me ^) thank you ) [7/15/2010 3:05:55 PM] alex dobrovolsky: b) [7/15/2010 3:07:49 PM] alex dobrovolsky: I consider that most of Biz Req has been completed for this so I am pooling he out this project into another "TMS EDI" project. She is still available on as needed project but Tira now becomes main resource here in NY for Client 2.1 [7/15/2010 3:08:34 PM] alex dobrovolsky: So pls coordinate daily Specs/QA with her. [7/15/2010 3:08:59 PM] alex dobrovolsky: c. current release sched: [7/15/2010 3:09:10 PM] alex dobrovolsky: dev until end of next week [7/15/2010 3:09:36 PM] alex dobrovolsky: staging Mon July 26 [7/15/2010 3:09:46 PM] Montira Rattanavijit: Noted. [7/15/2010 3:09:48 PM] alex dobrovolsky: release Thur Jul 29 [7/15/2010 3:10:22 PM] alex dobrovolsky: OK, I finished my part. Any questions? [7/15/2010 3:10:34 PM] Alex Pivnyak: no questions [7/15/2010 3:10:39 PM] Montira Rattanavijit: no questions [7/15/2010 3:10:44 PM] Роман Лахно: no [7/15/2010 3:11:34 PM] Montira Rattanavijit: Thank you [7/15/2010 3:12:11 PM] alex dobrovolsky: Just one more point - Tira will be responsible for UAT. [7/15/2010 3:12:24 PM] alex dobrovolsky: Now, Sasha it is your turn. [7/15/2010 3:12:37 PM] Alex Pivnyak: Ok. [7/15/2010 3:15:06 PM] Alex Pivnyak: I planning to finish main part core shipper-planner functionality bugs fixing + [Client 2.1] (Misc Functionality) 6.1 - 6.6 except 6.4 NPA today - tomorrow. There are some minor issues left. And start to develop (Misc Functionality) 6.4 New Pending Address (NPA) Feature [7/15/2010 3:16:06 PM] Alex Pivnyak: Kostya and Andrey are working on TDS panel functionality [7/15/2010 3:16:06 PM] Montira Rattanavijit: I am reviewing and doing UAT at the moment for the tasks that Sasha finished. [7/15/2010 3:16:56 PM] alex dobrovolsky: So do you think our current sched looks fine (finish dev by the end of next week)? [7/15/2010 3:17:04 PM] alex dobrovolsky: realistik? [7/15/2010 3:17:24 PM] Alex Pivnyak: I think yes [7/15/2010 3:17:45 PM] alex dobrovolsky: Sasha, you done? [7/15/2010 3:17:51 PM] Alex Pivnyak: yes [7/15/2010 3:17:57 PM] alex dobrovolsky: Roma, you turn [7/15/2010 3:18:09 PM] alex dobrovolsky: • QA update a. Status of QA tasks b. Any questions/issues [7/15/2010 3:18:33 PM] Роман Лахно: two task on me now from Shasha for tomorow work [7/15/2010 3:18:44 PM] alex dobrovolsky: #? [7/15/2010 3:18:52 PM] Роман Лахно: 2218 [7/15/2010 3:18:55 PM] Роман Лахно: 2220 [7/15/2010 3:19:08 PM] Роман Лахно: and TDS panel for tomorow [7/15/2010 3:19:29 PM] Alex Pivnyak: Andrey's part of work is almost done [7/15/2010 3:20:09 PM] Роман Лахно: whithout * 5.2.5 TDS Action Panel [7/15/2010 3:20:22 PM] Alex Pivnyak: Kostya is working on filters (Action panel) [7/15/2010 3:20:34 PM] alex dobrovolsky: When do you think he will complete? [7/15/2010 3:20:49 PM] Alex Pivnyak: Kostya? [7/15/2010 3:21:08 PM] Alex Pivnyak: I think at beginning of next week [7/15/2010 3:21:21 PM] alex dobrovolsky: right, pls ask him to estimate so we have approx idea of size. Thx. [7/15/2010 3:21:26 PM] Alex Pivnyak: ok [7/15/2010 3:23:07 PM] alex dobrovolsky: Roma, I would like to ask you to QA full time. If you have no new tasks pls try to come up with various use cases you did not test. Also pls post into mantis what specifically you tested. And do not forget to test all info in Data Dictionary wiki. [7/15/2010 3:23:27 PM] alex dobrovolsky: ok? [7/15/2010 3:23:29 PM] Роман Лахно: Ok [7/15/2010 3:23:37 PM] alex dobrovolsky: Roma, anything else from you? [7/15/2010 3:23:45 PM] Роман Лахно: yes [7/15/2010 3:23:58 PM] Alex Pivnyak: or maybe here? http://mantis.jaguarfreight.com/wiki/Cybertrax_2.1_Client_%28UAT%29 [7/15/2010 3:24:01 PM] Роман Лахно: QA and UAT is merged now ? [7/15/2010 3:24:20 PM] Роман Лахно: no need to move task to demo or somwere ? [7/15/2010 3:24:34 PM] alex dobrovolsky: mantis folder? yes [7/15/2010 3:25:45 PM] Alex Pivnyak: Roma asking where hi would move completed tasks since Demo folder is absent now [7/15/2010 3:26:02 PM] alex dobrovolsky: Let me think [7/15/2010 3:31:28 PM] alex dobrovolsky: Ok, I am going to have QA, UAT and Demo as separate folders [7/15/2010 3:32:28 PM] alex dobrovolsky: Roma, pls move completed (passed QA) tasks to UAT. Tira will pick thm up from there, review and what is passed move to Demo [7/15/2010 3:32:36 PM] Роман Лахно: ok [7/15/2010 3:33:00 PM] alex dobrovolsky: OK, do you guys have any outstanding questions about specs? [7/15/2010 3:33:14 PM] Montira Rattanavijit: no [7/15/2010 3:33:21 PM] Роман Лахно: no [7/15/2010 3:33:26 PM] alex dobrovolsky: Sasha? [7/15/2010 3:33:35 PM] Alex Pivnyak: no questions [7/15/2010 3:33:57 PM] alex dobrovolsky: Ok, now Tira is your turn [7/15/2010 3:34:21 PM] Montira Rattanavijit: I am reviewing some requirement [7/15/2010 3:34:38 PM] Montira Rattanavijit: and there may be some slightly changes. [7/15/2010 3:34:50 PM] Alex Pivnyak: not again... [7/15/2010 3:34:52 PM] Montira Rattanavijit: for what it didn't make sense [7/15/2010 3:35:15 PM] Montira Rattanavijit: but the one that changed, Sasha is already notified [7/15/2010 3:35:32 PM] Montira Rattanavijit: one thing that I am looking at it now it is about the notification [7/15/2010 3:35:53 PM] Montira Rattanavijit: core functionality, we already discussed and Sasha understood [7/15/2010 3:36:19 PM] Montira Rattanavijit: Only the format of the message, it might be changed. [7/15/2010 3:36:29 PM] Montira Rattanavijit: not much just add some space... [7/15/2010 3:36:29 PM] Alex Pivnyak: ok [7/15/2010 3:37:04 PM] Montira Rattanavijit: created shipment has no signature...I have to find out what we would need for that [7/15/2010 3:37:34 PM] Montira Rattanavijit: and also the Jaguar disclaimer thing, not sure whether we would like to show that or not. [7/15/2010 3:37:40 PM] Montira Rattanavijit: I have to find that out [7/15/2010 3:38:17 PM] Montira Rattanavijit: other than that, I am doing some UAT for the tasks that Sasha has finished and deployed. [7/15/2010 3:38:44 PM] Montira Rattanavijit: that's pretty much it. [7/15/2010 3:40:49 PM] alex dobrovolsky: OK, Thanks. I would like to remind that if there is a change or additiona to requirements then wiki spec must be updated (so it is up to date) and mantis created (so that QA will not miss it). As a shortcut, One mantis could be created covering several tweaks. [7/15/2010 3:41:29 PM] Montira Rattanavijit: noted [7/15/2010 3:42:55 PM] alex dobrovolsky: I have only one more thing - we dicussed with Sasha how to automate new user accounts.addresses creating , I will discuss this with Tira off line and create Mantis for this. [7/15/2010 3:43:36 PM] Montira Rattanavijit: ok [7/15/2010 3:43:52 PM] Alex Pivnyak: ok. new mantis for this will be good idea [7/15/2010 3:44:46 PM] alex dobrovolsky: That is all from me. Anyone has any more questions for this meeting? [7/15/2010 3:44:54 PM] Montira Rattanavijit: no [7/15/2010 3:44:55 PM] Роман Лахно: no [7/15/2010 3:44:57 PM] Alex Pivnyak: no [7/15/2010 3:46:18 PM] alex dobrovolsky: 42 min total, not too bad ))) See you all next time Tuesd 10:30. Just to remind you - we have proj updates 2 times a week: Tuesdays, Thursdays [7/15/2010 3:46:29 PM] alex dobrovolsky: Thanks you all! Bye! [7/15/2010 3:46:35 PM] Роман Лахно: tnx. bb [7/15/2010 3:46:41 PM] Alex Pivnyak: Thank you, see you soon [7/15/2010 3:46:42 PM] Montira Rattanavijit: bye
Meeting Tuesday Jul 20
Meeting Major Conclusions
- Discuss about diabling an access to unapproved/new/reject/hold with out date shipments:
- Quicklink
- Shipment List (Live tab)
- Virtual group
- Mantis and spec should be created and up to date
- Discuss about re-working on TDS design
- Discuss with Alex for Kostya's other high priority tasks(Acc reports) since TDS is higher priority in order to make it on schedule.
- NPA
- Roma: wait to test new TDS from Kostya, please come up with various use cases.
Chat Transcript
[9:55:15 AM] alex dobrovolsky: Hi all, [9:55:47 AM] alex dobrovolsky: Tira will play a role of a Project Manager on this project starting from today. [9:56:00 AM] Alex Pivnyak: hello everybody [9:56:09 AM] alex dobrovolsky: But I will be part of the meeting. [9:57:58 AM] Роман Лахно: hello [9:57:59 AM] Montira Rattanavijit: Hi everybody. [9:58:29 AM] Montira Rattanavijit: Let me prepare agenda [9:59:32 AM] Montira Rattanavijit: probably 10 mins before we start [10:13:47 AM] Montira Rattanavijit: Lets start [10:13:51 AM] Montira Rattanavijit: hi again [10:13:54 AM] Montira Rattanavijit: - PM update (Tira) a) Shipper Interface b) Planner Interface c) Notifications d) TDS (JG) - Dev manager update (sasha) a) what tasks are still in Dev and when they will be completed? b) Any question/issues - QA update a) Status of QA tasks b) Any question/issues - conclusion [10:14:04 AM] Montira Rattanavijit: this is an agenda for today [10:15:15 AM] Montira Rattanavijit: Since the last meeting, there is not much updated info from MO [10:15:44 AM] Montira Rattanavijit: only plans for moving forward on phase 2 [10:16:03 AM] Montira Rattanavijit: so I won't include those topics today. [10:17:07 AM] Montira Rattanavijit: As I have been doing UAT for shipper, and planner are looking impressive. [10:17:41 AM] Montira Rattanavijit: Notifications, so far they also look good. [10:18:34 AM] Montira Rattanavijit: Roma brought up some issue about notification for Trucker name assigned on the unapproved shipment - This is very good catch. [10:18:54 AM] Montira Rattanavijit: I checked the requirement, and this part is missing. [10:19:35 AM] Montira Rattanavijit: This task will need to be created [10:20:28 AM] Montira Rattanavijit: The only approved CT should be showing on the live tab on INternal app [10:20:57 AM] Montira Rattanavijit: What do you think the fastest way of implementing this kind of block? Sasha? [10:21:34 AM | Edited 10:21:48 AM] Alex Pivnyak: don't forget to disable about access to such shipments from quicklink [10:23:10 AM] Alex Pivnyak: It's not difficult to hide these shipments from lists, but much harder is rework all reports to hide not approved shipments [10:24:19 AM] Alex Pivnyak: The simpliest way is not hide shipments but just disable open edit window [10:24:27 AM] Montira Rattanavijit: Alex and I were just discussing about that problem for the reports. [10:25:12 AM] Montira Rattanavijit: and we think the disable or block unapproved CT for edit is a good idea for now [10:25:42 AM] Montira Rattanavijit: so it should disable for both quicklink and shipment list [10:26:07 AM] Montira Rattanavijit: how long it would take to implement this solution? [10:27:25 AM] Alex Pivnyak: disable for editing - 0.5 - 1 hr. but hiding from lists some more. I think not less then 3 hr [10:27:48 AM] Montira Rattanavijit: This will solve the problem for notification - case of JG assign the trucker on unapproved shipment. [10:27:50 AM] Montira Rattanavijit: ok. [10:29:16 AM] Alex Pivnyak: not all problems. These ct's should be excluded from virtual groups also - to prevent changing their fields via group edition [10:29:37 AM] Montira Rattanavijit: yes. That's right [10:30:04 AM] Montira Rattanavijit: how much time to implement this part to exclude from the vt group? [10:31:02 AM] Alex Pivnyak: not sure, think all this task can take working day or more. hr 8-10 with risk [10:31:24 AM] Montira Rattanavijit: ok. [10:31:51 AM] Montira Rattanavijit: anything else for this topic? [10:32:10 AM] Montira Rattanavijit: next, TDS panel. [10:32:49 AM] Montira Rattanavijit: I reviewed some of it yesterday afternoon, and realized that it doesn't look the same concept as the design spec [10:33:27 AM] Montira Rattanavijit: Is it the fastest way? and should it be this way? or it is a temporary design? [10:33:48 AM] Alex Pivnyak: yes, I know. It's some complicated to make it work with virtual groups together. [10:34:09 AM] Montira Rattanavijit: What is your suggestion? [10:34:51 AM] Alex Pivnyak: It's possible to rework this. [10:37:56 AM | Edited 10:38:06 AM] Alex Pivnyak: Kostya have to work on this task with high priority. Now he have other tasks with ASAP priority too. Have he abandon working on those tasks and switch to current one? [10:38:37 AM] Montira Rattanavijit: That'd be great. Since from the user's stand point, it should be user friendly enough for them to use. What is the idea of rework this for moving forward? and how long it would take to implement? [10:39:19 AM] Montira Rattanavijit: Lets me check Kostya's task. [10:42:18 AM] Montira Rattanavijit: I talked to Alex, he said 2 acc reports of Kostya, seem to be very high, but he would try to postpone the second one. [10:42:32 AM] Montira Rattanavijit: how much time Kostya would need to re-work TDS? [10:44:23 AM] Alex Pivnyak: the idea is in the following 1. Links from TDS panel (portlet) will lead directly to the list of selected shipments. 2. In the virtual groups - combine filters page with selected shipments page to the one single page (filters above selected shipments list which will be dinamically refreshed after user press button ApplyFilters) - so no button next-prev needed between filters and CT list These modifications will unify the user interface of currently existing virtual groups with new specification for TDS action panel. [10:45:53 AM] Montira Rattanavijit: that sounds better than the current one. it makes sense for the user. [10:46:42 AM] Montira Rattanavijit: I will discuss this with Alex and MO for the rest of the tasks for KOstya. And let you know asap. TDS is needed asap. [10:47:20 AM] Montira Rattanavijit: Sasha, do you how many hrs does he need for TDS proj? [10:47:28 AM] Montira Rattanavijit: and Acc reports? [10:47:56 AM] Montira Rattanavijit: look like he estimate 20 for 2 acc reports. [10:48:13 AM] Montira Rattanavijit: I am trying to see whether he would have enough time for TDS ? [10:48:24 AM | Edited 10:48:47 AM] Alex Pivnyak: I do not know even. Should we include Kostya to our meeting? [10:49:05 AM] Montira Rattanavijit: Sure. [10:49:17 AM] *** Montira Rattanavijit added konstantin.ushakov *** [10:49:27 AM] Montira Rattanavijit: Hello Kostya, [10:49:43 AM] Montira Rattanavijit: Sorry for the interruption. [10:50:06 AM] Montira Rattanavijit: We need to ask you about the TDS feature. [10:50:48 AM] Montira Rattanavijit: for the rework TDS, do you have any idea how much time you will need to implement? [10:51:22 AM] Montira Rattanavijit: I talked to Alex about the rest of your tasks. He said only ACC reports are high. [10:51:41 AM] Montira Rattanavijit: But he would try to negotiate with Karen MO to postpone one of them [10:51:45 AM] konstantin.ushakov: i need several hours [10:51:48 AM] konstantin.ushakov: 3-4 [10:52:32 AM] Montira Rattanavijit: umm...so do you think you can finish TDS and 2 ACC reports all together for this release? [10:52:41 AM] konstantin.ushakov: i hope [10:53:16 AM] Montira Rattanavijit: So lets do that then. [10:53:32 AM] konstantin.ushakov: ok [10:54:00 AM] Montira Rattanavijit: Alex will try to talk to Karen to postpone acc reports if possible.. [10:54:16 AM] Montira Rattanavijit: we will let you know for that. So lets do TDS first. [10:54:22 AM] Montira Rattanavijit: then acc reports. [10:54:30 AM] konstantin.ushakov: okay [10:54:38 AM] Montira Rattanavijit: Any questions? [10:54:49 AM] konstantin.ushakov: nothing [10:54:56 AM] Montira Rattanavijit: thank you Kostya. [10:55:01 AM] konstantin.ushakov: welcome [10:56:18 AM] Alex Pivnyak: ok, then I will continue working on New PendingAddresses [10:56:19 AM] Montira Rattanavijit: - Dev manager update (sasha) a) what tasks are still in Dev and when they will be completed? [10:56:31 AM] Alex Pivnyak: NPA [10:56:31 AM] Montira Rattanavijit: Just NPA? [10:56:43 AM] Montira Rattanavijit: ok...when it will be completed? [10:56:48 AM] Alex Pivnyak: yes... so far [10:57:36 AM] Alex Pivnyak: Nearly to the of thursday - friday [10:57:52 AM] Montira Rattanavijit: ok. any questions so far? [10:58:07 AM] Alex Pivnyak: no questins [10:58:20 AM] Montira Rattanavijit: thank you. Next - Roma [10:58:26 AM] Роман Лахно: i'm here ) [10:58:28 AM] Montira Rattanavijit: QA update? [10:58:49 AM] Роман Лахно: on me only TDS panel now [10:59:14 AM] Montira Rattanavijit: ok. All other tasks are done and moved to UAT? [10:59:20 AM] Роман Лахно: yes [10:59:24 AM] Montira Rattanavijit: thank you. [10:59:29 AM] Роман Лахно: urw [10:59:38 AM] Montira Rattanavijit: any questions? [10:59:41 AM] Роман Лахно: no [10:59:51 AM] Роман Лахно: yes [10:59:54 AM] Роман Лахно: sorry ) [10:59:59 AM] Montira Rattanavijit: that's ok [11:00:19 AM] Роман Лахно: need to test this variation of TDS panel, or wait another ? [11:00:43 AM] Montira Rattanavijit: Wait for another. [11:00:48 AM] Роман Лахно: ok [11:00:55 AM] Роман Лахно: thank you [11:01:00 AM] Montira Rattanavijit: Thank you, so you don't have to do double work. [11:01:10 AM] Montira Rattanavijit: conclusion [11:02:44 AM] Montira Rattanavijit: sasha - disable access quicklink, shipment list, update VT for unapproved/reject/new/ hold without date. - For the hold with Date, we will need it...but there is some constrain - I will update the spec and notify you asap. and NPA tasks. [11:03:34 AM] Montira Rattanavijit: Kostya - TDS - urgent priority then acc reports - high. We will keep you posted about how much we can negotiate for the acc tasks. [11:04:01 AM] Montira Rattanavijit: Roma - wait to qa the new TDS from Kostya [11:04:08 AM] Роман Лахно: ok [11:04:19 AM] Montira Rattanavijit: any questions? [11:04:41 AM] Alex Pivnyak: ok, no questions [11:04:44 AM] Роман Лахно: no [11:05:18 AM] Montira Rattanavijit: ok...thank you for your corporation [11:05:24 AM] Роман Лахно: thank you [11:05:34 AM] Alex Pivnyak: thank you [11:05:43 AM] Montira Rattanavijit: See you on Thursday about the same time. [11:05:47 AM] Montira Rattanavijit: bye [11:05:50 AM] Роман Лахно: bye [11:05:51 AM] Alex Pivnyak: bye [11:06:09 AM] konstantin.ushakov: bye [11:06:48 AM] Montira Rattanavijit: one last thing, please look at this: http://mantis.jaguarfreight.com/mantis/view.php?id=2077 [11:07:05 AM] Montira Rattanavijit: for the schedules... [11:07:07 AM] Montira Rattanavijit: thank you again. [11:07:10 AM] Montira Rattanavijit: BYe
Meeting Thursday Jul 22
Meeting Major Conclusions
- Update statuses from the last meeting.
- diabling an access to unapproved/new/reject/hold with out date shipments:
- Sasha plans to implement these on Friday Jul 23
- TDS re-design
- It is ready for Roma to start QA
- NPA
- In progress: slightly change for the design, for the company- city field
- Spec will need to change a little for the design
- Create user account on dev before release to production
- Sasha will finish in an hr. Then he will let Tira know in order to proceed to the next step
- diabling an access to unapproved/new/reject/hold with out date shipments:
[9:54:59 AM] Alex Pivnyak: hello
[10:02:39 AM] Montira Rattanavijit: Hi everyone,
[10:02:46 AM] Роман Лахно: hello
[10:02:50 AM] Montira Rattanavijit: - PM
a) Disable access through quicklink, shipment list, virtual group
b) TDS
c) NPA
d) createing all users (including their addresses) before release
- QA update
a) Status of QA tasks
b) Any question/issues
- Dev manager update (sasha)
a) what tasks are still in Dev and when they will be completed?
b) Any question/issues
c) on schedule for release
- conclusion
[10:03:24 AM] Montira Rattanavijit: Agenda for today: touch up from the last meeting with status update, and questions.
[10:04:01 AM] Montira Rattanavijit: From the last time, we have 4 main tasks that we need to get done
[10:07:10 AM] Alex Pivnyak: well, here is my report
-PM
a) not implemented. planned for tomorrow
b) TDS - it's ready. Roma can start to test in CyberTrax Demo
c) NPA - still in progress. There was some problems with Company-City This object has to be created by shipper as well as Address.
d) - It's almost done. I will prepare database and application in the nearest hour.
[10:07:47 AM] Montira Rattanavijit: ok.
[10:07:57 AM] Montira Rattanavijit: - QA update
[10:08:12 AM] Montira Rattanavijit: Roma? How is everything so far?
[10:09:07 AM] Роман Лахно: today i test TDS dash boar for "shows the correct numbers for each status and columns"
[10:09:07 AM] Montira Rattanavijit: Will you be able to estimate how long will you take to qa?
[10:09:23 AM] Роман Лахно: i think few houre minimum
[10:09:28 AM] Montira Rattanavijit: ok.
[10:10:25 AM] Montira Rattanavijit: and you think the rest of tasks from Dev, will it be possible to finish before we release to Staging?
[10:10:33 AM] Montira Rattanavijit: on Monday
[10:12:21 AM] Роман Лахно: i think if it's will be ready for tomorow it's possible
[10:12:34 AM] Montira Rattanavijit: Thank you.
[10:12:52 AM] Montira Rattanavijit: I will do UAT at the same time as well.
[10:12:54 AM | Edited 10:13:05 AM] Роман Лахно: if will not any big bug's
[10:13:03 AM] Montira Rattanavijit: ok.
[10:13:48 AM] Montira Rattanavijit: any questions for you Roma?
[10:13:57 AM] Роман Лахно: yes
[10:14:48 AM | Edited 10:15:22 AM] Роман Лахно: can we set "Actual export pickup date" for CT which have empty "pickup trucker" ?
[10:16:48 AM] Роман Лахно: becase by spec, if "Actual export pickup date" filled and "pickup trucker" not filled then this CT dissapear from TDS board.
[10:17:07 AM] Montira Rattanavijit: let me think
[10:18:27 AM] Montira Rattanavijit: could you send me the link?
[10:19:00 AM] Роман Лахно: http://mantis.jaguarfreight.com/wiki/Cybertrax_2.1_Client_%28requirements%29#Truck_Domestic_Stats_TDS_feature
[10:19:16 AM] Роман Лахно: Approved status
*
o Approved on date = set AND
o Pick up trucker = empty AND
o Actual Pick up Date = empty AND
o Actual Delivery date = empty
Routed status
! This is #Phase Two
*
o Approved on date = set AND
o Pick up trucker = set AND
o Actual Pick up Date = empty AND
o Actual Delivery date = empty
Picked Up status
! This is #Phase Two
*
o Approved on date = set AND
o Pick up trucker = set AND
o Actual Pick up Date = set AND
o Actual Delivery date = empty
[10:19:44 AM] Montira Rattanavijit: Regarding on Spec: Pick up trucker must be assigned
[10:20:31 AM] Роман Лахно: but system allows set "Actual Pick up Dat" without "Pick up trucker"
[10:20:33 AM] Montira Rattanavijit: for domestic trucking only
[10:21:09 AM] Montira Rattanavijit: system allows, correct.
[10:23:27 AM] Montira Rattanavijit: for now, user can set the act pick up date before assigning ocean, air, and even truck.
[10:24:13 AM] Montira Rattanavijit: but for Truck only, that user has to assign act pick up date with pick up trucker together...
[10:24:20 AM] Montira Rattanavijit: that is always a must in JG.
[10:24:43 AM] Montira Rattanavijit: but not for other modes...but we don't have a logic for this yet.
[10:24:49 AM] Montira Rattanavijit: It will be in the future.
[10:24:53 AM] Роман Лахно: ok
[10:24:56 AM] Роман Лахно: thank you
[10:25:08 AM] Montira Rattanavijit: right now we just have to depend on user, hope they don't make a mistake.
[10:25:12 AM] Montira Rattanavijit: anything else?
[10:25:21 AM] Роман Лахно: no
[10:25:25 AM] Montira Rattanavijit: ok.
[10:26:21 AM] Montira Rattanavijit: now, we come back to Sasha.
[10:26:24 AM] Montira Rattanavijit: c) NPA - still in progress. There was some problems with Company-City This object has to be created by shipper as well as Address.
[10:26:38 AM] Alex Pivnyak: yes
[10:27:03 AM] Montira Rattanavijit: is this something that required spec changes?
[10:27:25 AM] Alex Pivnyak: Slightly..
[10:27:41 AM] Montira Rattanavijit: what is the problem?
[10:29:35 AM] Alex Pivnyak: no problem, just in address creation dialog Company Name and City Name should be dropdown with existinging Company-City. Shipper can select it from existing or just enter new. If So then new Company City will be created with new address. I will send you screenshot
[10:30:10 AM] Montira Rattanavijit: ok.
[10:30:59 AM] Montira Rattanavijit: but what happen, if there is a new company-city?
[10:31:28 AM] Montira Rattanavijit: there is no new company-city
[10:32:18 AM] Montira Rattanavijit: this fields, you would like to have it more like an option to choose from existing, or create a new one, correct?
[10:34:44 AM] Alex Pivnyak: No, it will be created automatically if entered CompanyName and City will not match to any existing one.
it will be stored in database and should be approved by operator as well.
[10:35:37 AM] Montira Rattanavijit: ok. Please send me the screen shot after the meeting. I will take a look at it.
[10:35:45 AM] Montira Rattanavijit: thank you.
[10:36:32 AM] Montira Rattanavijit: any other concern?
[10:37:35 AM] Alex Pivnyak: Ok. Tira, I have one more question. In the spec is written what jag. user approving new addresses has a SuperUser access rights. Does it means Super Accounting operator?
[10:37:55 AM] Montira Rattanavijit: no. Super Ops
[10:38:05 AM] Alex Pivnyak: Ok
[10:38:15 AM] Montira Rattanavijit: any thing else?
[10:38:34 AM] Alex Pivnyak: no
[10:38:50 AM] Montira Rattanavijit: so that mean we are still on schedule right?
[10:39:02 AM] Montira Rattanavijit: I hope :)
[10:39:08 AM] Alex Pivnyak: me too :)
[10:39:16 AM] Роман Лахно: )yes
[10:39:22 AM] Montira Rattanavijit: ok. That's great.
[10:40:05 AM] Montira Rattanavijit: conclusion
[10:40:33 AM] Montira Rattanavijit: a) it will be implemented tomorrow.
[10:41:12 AM] Montira Rattanavijit: b) Roma can start qa. AND if you have any questions, please let me know right away.
[10:41:48 AM] Montira Rattanavijit: c) NPA - Sasha will send me the screen shot, so I can understand it correctly and update the spec
[10:42:02 AM] Montira Rattanavijit: d) sasha will notify me once it is done.
[10:42:12 AM] Alex Pivnyak: ok
[10:42:20 AM] Montira Rattanavijit: thank you everyone.
[10:42:32 AM] Роман Лахно: ok, than you.
[10:42:49 AM] Montira Rattanavijit: bye.
[10:42:52 AM] Роман Лахно: bye
Meeting Major Conclusions
- Update statuses from the last meeting.
- disbling an access to unapproved/new/reject/hold with out date shipments: Through shipment list(live tab), quicklink, update fields for VT group, NPA address viewing CT links
- Spec needs to be updated
- TDS - Auto checkbox, back button- chg to window pop-up, deleted CTs, More info for "Trucker" and etc.
- Spec needs to be updated
- Kostya won't be able to do the back button - chg to window pop-up today
- NPA
- New automatically functions implemented and almost completed
- Delete button is added for the address that has no CTs referred to
- Hide all the new unapproved address from a dropdown list: Replace from address book button, any other editors such as Shipment editor (Gen Imp/Exp tabs) and so on
- JG operator will open NPA view Address panel - list of all referenced CT's will be displayed there. And each CT will display the autorization status - Approved/Rejected and so on
- Spec needs to be updated
- Bugs found
- On time for Staging release on Tuesday(moved from Monday)
- disbling an access to unapproved/new/reject/hold with out date shipments: Through shipment list(live tab), quicklink, update fields for VT group, NPA address viewing CT links
[9:45:24 AM] alex dobrovolsky: Hi, All! This is a reminder for 10 am Status Update meeting for Client 2.1 today. [9:45:39 AM] Montira Rattanavijit: Hello Everyone: Reminder: Meeting at 10:00 AM for status updates [9:45:58 AM] Alex Pivnyak: Hello [9:50:18 AM] Роман Лахно: hello. in 20 min i have to go English classes. [9:51:21 AM] Montira Rattanavijit: Lets start now then since Roma has to go in 20 mins [9:51:40 AM] Alex Pivnyak: ok [9:51:45 AM] Роман Лахно: ok [9:52:13 AM] Montira Rattanavijit: 1) Disable JG Access through unapproved shipments by planner [9:53:18 AM] Montira Rattanavijit: 2) TDS: Update fields[Kostya said he would implement this page to be a window popup - solution for back button - which allows users to return to the shipment list anytime [9:53:46 AM] Montira Rattanavijit: 3) Deleted shipments still show on TDS (Internal) [9:54:02 AM] Montira Rattanavijit: 4) NPA - JG Action [9:54:17 AM] Montira Rattanavijit: 5) Bugs found for NPA [9:55:05 AM] Montira Rattanavijit: Lets start with Roma. [9:55:27 AM] Montira Rattanavijit: QA update - how is the status of QA tasks? [9:57:03 AM] Роман Лахно: the last deploy was only 10 minuts ago [9:57:49 AM] Роман Лахно: so i had no time [9:58:01 AM] Montira Rattanavijit: How long will QA tasks be completed and are there any tasks that you are still waiting to QA? [9:58:17 AM] Montira Rattanavijit: Will you be able to do it after class? [9:58:22 AM] Роман Лахно: still waiting only NPA [9:58:39 AM] Роман Лахно: yes i can work little later [9:58:43 AM] Montira Rattanavijit: ok. Do you know how much time you need to QA NPA? [9:59:06 AM] Роман Лахно: minimum few hours [9:59:11 AM] Роман Лахно: 2 [9:59:24 AM] Montira Rattanavijit: any questions/issues so far? [9:59:28 AM] Montira Rattanavijit: ok. [10:00:00 AM] Роман Лахно: 1) not full, Sasha will explane [10:00:10 AM] Montira Rattanavijit: ok [10:00:21 AM] Роман Лахно: 3) need to update spec [10:00:49 AM] Montira Rattanavijit: regarding design changed, correct? [10:01:38 AM] Alex Pivnyak: 3) is almost done. TDS panel and TDS list will not show deleted shipments today [10:02:08 AM] Montira Rattanavijit: ok. [10:02:29 AM] Montira Rattanavijit: how about 2) does any one know anything about it? [10:03:10 AM] Alex Pivnyak: minute please, I will ask Kostya [10:03:23 AM] Montira Rattanavijit: ok [10:07:38 AM] Montira Rattanavijit: So Roma, TDS is done? [10:08:28 AM] Роман Лахно: no [10:08:39 AM] Montira Rattanavijit: what is left for TDS? [10:08:42 AM] Роман Лахно: deleted CT [10:08:45 AM] Montira Rattanavijit: ok. [10:08:50 AM] Montira Rattanavijit: other than that? [10:08:57 AM] Роман Лахно: auto checkbox when select date [10:09:07 AM] Роман Лахно: back button [10:09:11 AM] Montira Rattanavijit: ok. [10:09:27 AM] Роман Лахно: and more info for "truckers" in CT list [10:09:33 AM] Montira Rattanavijit: ok [10:11:16 AM] Montira Rattanavijit: anything else? [10:11:56 AM] Роман Лахно: the specs for NPA not details [10:12:06 AM] Montira Rattanavijit: yes - that needs to be updated [10:12:52 AM] Montira Rattanavijit: the design has changed - so I will have to re-do the whole thing for NPA [10:13:15 AM] Montira Rattanavijit: I will start updating after the meeting [10:13:31 AM] Роман Лахно: ok, tnx [10:14:18 AM] Montira Rattanavijit: And I have to also ask Sasha for the part that he has not deployed. [10:14:26 AM] Montira Rattanavijit: so I will try to get that done for you asap. [10:14:40 AM] Montira Rattanavijit: Anything else for you? [10:14:45 AM] Montira Rattanavijit: or any questions? [10:14:51 AM] Роман Лахно: no, tnx [10:15:01 AM] Montira Rattanavijit: Ok...is Sasha back? [10:15:07 AM] Роман Лахно: not yet [10:15:29 AM] Montira Rattanavijit: umm...so if you have to leave, you can. I will update you all info afterward. [10:16:11 AM] Montira Rattanavijit: or you can read all of our conversation for the meeting after. [10:16:29 AM] Montira Rattanavijit: I always keep the logs of our conversation. [10:16:43 AM] Роман Лахно: ok, thank you, i'l be online later [10:16:48 AM] Montira Rattanavijit: ok. [10:17:00 AM] Montira Rattanavijit: Sasha, please let me know when you are back [10:33:01 AM] Alex Pivnyak: Tira, I'm sorry. I'm back. There was problems with Kostya's work, Was needed my presence urgently [10:33:55 AM] Montira Rattanavijit: is everything ok now? [10:34:28 AM] Alex Pivnyak: yes. I'm sorry [10:34:32 AM] Montira Rattanavijit: that's ok. [10:34:54 AM] Montira Rattanavijit: Did you ask Kostya about the update field window pop up? [10:35:04 AM] Montira Rattanavijit: solution for back button [10:35:43 AM] Alex Pivnyak: yes, he said he will do popup window, but after he will finish urgent task about report. [10:36:19 AM] Montira Rattanavijit: ok. [10:36:53 AM] Montira Rattanavijit: Dev update NPA - Edit a saved CT's address for a new address create: Bug display "--" - User would like to replace the new address with another new address that was created before, but still did not get approved - Need to block this. Problem: there are 2 same addresses on MPA, one on the new tab, the other on Closed tab - Edit button - After clicking "OK", info doesn't update right away, user has to refresh the window - Still wait for more testing after it is deployed. - Anything else? [10:37:35 AM] Alex Pivnyak: - Edit a saved CT's address for a new address create: Bug display "--"fixed [10:38:07 AM] Alex Pivnyak: - User would like to replace the new address with another new address that was created before, but still did not get approved - Need to block this.fixed. I hide all not approved addresses from any drop-down lists [10:38:37 AM] Montira Rattanavijit: for the replace from address book right? [10:38:51 AM] Alex Pivnyak: yes [10:38:52 AM] Montira Rattanavijit: good. [10:39:36 AM] Alex Pivnyak: and from any other editors such as Shipment editor (Gen Imp/Exp tabs) and so on [10:40:01 AM] Montira Rattanavijit: ok [10:40:03 AM] Montira Rattanavijit: good [10:40:13 AM] Montira Rattanavijit: Edit button - After clicking "OK", info doesn't update right away, user has to refresh the window? [10:41:10 AM] Alex Pivnyak: fixed. After Ok button address becomes closed as well as after "Set Closed" button [10:41:31 AM] Alex Pivnyak: and on the view panel will display next address from list [10:41:42 AM] Montira Rattanavijit: ok [10:41:58 AM] Montira Rattanavijit: I meant the Edit button [10:42:13 AM] Montira Rattanavijit: for ex, when user view and edit address and press ok [10:42:18 AM] Montira Rattanavijit: without set closed [10:42:35 AM] Montira Rattanavijit: the address list doesn't update. [10:42:45 AM] Montira Rattanavijit: I had to refresh the page [10:42:56 AM] Montira Rattanavijit: in order to get the updated info [10:43:30 AM] Alex Pivnyak: Do you mean you have to close and open the view panel to refresh? [10:43:44 AM] Montira Rattanavijit: yes [10:43:49 AM] Montira Rattanavijit: no [10:44:06 AM] Montira Rattanavijit: I will send the screen shot to you after the meeting [10:44:36 AM] Montira Rattanavijit: what tasks are still in Dev? [10:47:12 AM] Alex Pivnyak: The problem is still existing is that NPA dashboard will display count of all addresses, not only for approved CT's. I can't change this now because of multiple CT's can have one new created address and some of that CT can be approved and some of them - rejected e.t.c [10:48:13 AM] Montira Rattanavijit: ok [10:48:27 AM] Alex Pivnyak: After JG operator will open NPA view Address panel - list of all referenced CT's will be displayed there. [10:48:42 AM] Montira Rattanavijit: yes [10:48:54 AM] Montira Rattanavijit: I saw it this morning. Looks good. [10:49:05 AM] Alex Pivnyak: And each CT will display hes autorization status (- Approved/Rejected...) [10:49:09 AM] Montira Rattanavijit: so in this case, NPA shows for all CTs [10:50:07 AM] Montira Rattanavijit: did you make sure those rejected CT not allow to access? [10:50:14 AM] Montira Rattanavijit: will that cause the reports? [10:50:20 AM] Montira Rattanavijit: any reports? [10:51:48 AM] Montira Rattanavijit: look like the ones that is pending for approved - still allow JG to access [10:52:09 AM] Alex Pivnyak: I removed not approved CT's from live CT's tab list [10:52:47 AM] Montira Rattanavijit: and the rejected ones as well [10:53:07 AM] Alex Pivnyak: yes, only approved should be shown [10:53:35 AM] Montira Rattanavijit: did you deploy? [10:53:44 AM] Montira Rattanavijit: It doesn't work for me at the moment [10:57:05 AM] Alex Pivnyak: CT300402 is pending for approval. It does not displaying in CT list for the Live Trucking CT's [10:59:30 AM] Montira Rattanavijit: but still able to access through quicklink? [11:00:55 AM] Alex Pivnyak: yep.. qucklink is working. :( I have to look [11:02:04 AM] Alex Pivnyak: Ok, I will fix this today also. [11:02:14 AM] Montira Rattanavijit: yes. [11:04:36 AM] Alex Pivnyak: And one more thing. I making a "Delete" button for those new addresses what don't have anymore referenced CT's It could be happened if Shipper will create CT with new created address and then - will edit created CT and replace new created address with another. In this case - previously created address should be deleted. [11:05:33 AM] Montira Rattanavijit: is this deployed? [11:05:41 AM] Montira Rattanavijit: will it be deployed soon? [11:06:33 AM] Alex Pivnyak: After this, I think, all the JG operator functionality will be completed. And operator will have full control on the created addresses. Yes, I deploy this soon. [11:06:56 AM] Montira Rattanavijit: Is the delete button - manually delete by operator correct? [11:07:03 AM] Montira Rattanavijit: I can't wait to see this. [11:08:17 AM] Alex Pivnyak: yes, manually. The button will be shown only if new created address without referenced CT's will be currently opened on the panel [11:08:26 AM] Montira Rattanavijit: THat's great! [11:08:45 AM] Montira Rattanavijit: Anything else in Dev? [11:09:03 AM] Alex Pivnyak: no, only bug fixes and this button [11:09:12 AM] Montira Rattanavijit: ok. [11:09:34 AM] Montira Rattanavijit: when it will be ready for QA? [11:09:43 AM] Montira Rattanavijit: should not take much time right? [11:09:56 AM] Alex Pivnyak: I hope, 2 hours [11:10:17 AM] Montira Rattanavijit: So are we on schedule for realistic for staging tonight? [11:10:26 AM] Alex Pivnyak: I think yes [11:10:35 AM] Montira Rattanavijit: include Kostya task as well [11:10:47 AM] Alex Pivnyak: one moment, I not sure about Kostya's back button :( [11:16:45 AM] Alex Pivnyak: I think, back button will not ready today [11:17:04 AM] Montira Rattanavijit: ok. That's fine. At least I know. [11:17:43 AM] Montira Rattanavijit: any thing else? [11:17:48 AM] Alex Pivnyak: no [11:17:51 AM] Montira Rattanavijit: ok. Thank you. [11:18:30 AM] Montira Rattanavijit: I will update spec for NPA - is it ok for you to review whether I create spec follow your design later on? [11:19:06 AM] Montira Rattanavijit: I would like to make sure I write all the functionality correctly. [11:20:44 AM] Alex Pivnyak: Ok, you can begin updating with existing features. I will let you know when I will deploy the rest. [11:20:54 AM] Montira Rattanavijit: ok. Thank you. [11:21:21 AM] Montira Rattanavijit: bye. See you online later on. [11:21:34 AM] Alex Pivnyak: Ok, bye
