| |
Table Name: |
Work Break
Down With Task Grouping |
|
|
|
|
|
|
|
|
|
| |
Client
Name: |
EBL |
|
|
|
|
|
|
|
|
|
|
BankOnApp |
|
| Task Grouping From
Work Break Down Of CR after Impact analysis |
|
| Task ID |
Task
Name |
Description |
Remark |
Completed
(%) |
Remaining
Time (Man Hour) |
Status |
Estimated
Time (Man Hour) |
Sub
Project Type |
Priority |
Task
Group Name |
Assign |
| BankOnApp Admin
Panel |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-1 |
Password
Policy configuration |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-1.1 |
Add
Password Policy configuration(Maker) |
Pre-requiste
task: i)Add perticular module during Create,Edit,Detail in Admin user
group(Maker). ii)Add perticular report module to Authorozation(Checker).
iii)Customize Login, Them1 and Them2 because impact on Session data after Log
in.Pre-requiste TaskID: BOA-API-1.1, BOA-API-1.2, BOA-API-1.3, BOA-API-1.5.1,
BOA-API-1.5.2 |
Need
some clearification of business logic. |
60% |
9.6 |
On going |
24 |
BOA-AP |
2 |
Password
Policy |
Shahin |
| BOA-AP-1.2 |
Add
Password Policy configuration(Checker) |
Pre-requiste
task: i)Add perticular module during Create,Edit,Detail in Admin user
group(Maker). ii)Add perticular module to Authorozation(Checker).
iii)Customize Login, Them1 and Them2 because impact on Session data after Log
in.Pre-requiste TaskID: BOA-API-1.1, BOA-API-1.2, BOA-API-1.3, BOA-API-1.5.1,
BOA-API-1.5.2 |
Need
some clearification of business logic. |
60% |
9.6 |
On going |
24 |
BOA-AP |
2 |
Password
Policy |
Shahin |
| BOA-API-1.1 |
Key
Exchange API(Password Policy configuration Impact[BOA-AP-1.1,BOA-AP-1.2]) |
customize
this api as per password policy configure by admin panel Pre-requiste TaskID:
BOA-AP-1.1,BOA-AP-1.2 |
|
0% |
4 |
Pending |
4 |
BOA-API |
2 |
Password
Policy |
Sakib |
| BOA-API-1.2 |
Device
Activation API(Password Policy configuration Impact[BOA-AP-1.1,BOA-AP-1.2]) |
customize
this api as per password policy configure by admin panel Pre-requiste TaskID:
BOA-AP-1.1,BOA-AP-1.2 |
|
0% |
8 |
Pending |
8 |
BOA-API |
2 |
Password
Policy |
Sakib |
| BOA-API-1.3 |
LogIn
API(Password Policy configuration Impact[BOA-AP-1.1,BOA-AP-1.2]) |
customize this api as per password policy configure by admin panel
Pre-requiste TaskID: BOA-AP-1.1,BOA-AP-1.2 Note to developer: i) functional
impact analysis report: Key Exchange, Token generate, Session Handling,
Password change alert or Forcedly Password Change as per password policy set
by Admin panel, Validation and verification alert (Lock, Inactive for account
and device)
|
|
0% |
24 |
Pending |
24 |
BOA-API |
2 |
Password
Policy |
Sakib |
| BOA-API-1.5.1 |
Get Password Policy API(Password Policy configuration
Impact[BOA-AP-1.1,BOA-AP-1.2])
|
customize
this api as per password policy configure by admin panel Pre-requiste TaskID:
BOA-AP-1.1,BOA-AP-1.2 |
Need
some clearification of business logic. |
0% |
3 |
Pending |
3 |
BOA-API |
2 |
Password
Policy |
Sakib |
| BOA-API-1.5.2 |
Change Password API(Password Policy configuration
Impact[BOA-AP-1.1,BOA-AP-1.2])
|
customize
this api as per password policy configure by admin panel Pre-requiste TaskID:
BOA-AP-1.1,BOA-AP-1.2 |
Need
some clearification of business logic. |
0% |
5 |
Pending |
5 |
BOA-API |
2 |
Password
Policy |
Sakib |
| |
|
|
|
|
|
|
|
|
|
|
|
| BOA-AP-2 |
Limit
Package |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-2.1 |
Limit
Package List View populate as order by Limit Package name(maker and checker)
and accordingly also reflect Add,Edit and Detail view. |
|
|
100% |
0 |
Done |
5 |
BOA-AP |
3 |
Limit
Package ordering |
Shahin |
| BOA-AP-2.2 |
All
Limit Package dropdown controll
populate as order by Limit Package name(maker and checker) |
|
|
100% |
0 |
Done |
3 |
BOA-AP |
3 |
Limit
Package ordering |
Shahin |
| BOA-AP-3 |
Service
Request Process |
|
|
|
|
|
0 |
|
|
|
|
| BOA-AP-3.1 |
Add
new field "cc" in Send Mail Form of Product Service Request and
accordingly customize the send mail function for further create audit trail
report. |
Impact
on "Product Service request process List View","Send Mail
Form" and Database |
|
100% |
0 |
Done |
5 |
BOA-AP |
9 |
Product
Service Request Mail |
Sakib |
| BOA-AP-3.2 |
Add
new field "cc" in Send Mail Form of Priority Service Request and
accordingly customize the send mail function for further create audit trail
report. |
Impact
on "Priority Service request process List View","Send Mail
Form" and Database |
|
100% |
0 |
Done |
5 |
BOA-AP |
10 |
Priority
Service Request Mail |
Sakib |
| BOA-AP-3.3 |
Add
new field "cc" in Send Mail Form of Banking Service Request and
accordingly customize the send mail function for further create audit trail
report. |
Impact
on "Banking Service request process List View","Send Mail
Form" and Database |
|
100% |
0 |
Done |
5 |
BOA-AP |
11 |
Banking
Service Request Mail |
Sakib |
| BOA-AP-3.4 |
Add
new field "Client ID" in Body of the "Send mail form
view" against all Card related service type |
Impact
on "API","Apps","Send Mail Form" and
Database.Pre-requiste TaskID: BOA-MA-4,BOA-API-2.1.6.3 |
|
100% |
0 |
Done |
4 |
BOA-AP |
13 |
ClientID
within Card Related Service request |
Shahin |
| BOA-API-2.1.6.3 |
Banking
Service Request API(Client ID Add Impact[BOA-MA-4]) |
customize the "Banking Service Request API" as per Add internal
extra field "ClientID" of the Card during card releted service
request By Apps.Pre-requiste TaskID: BOA-MA-4,BOA-AP-3.4
|
|
100% |
0 |
Done |
2 |
BOA-API |
12 |
ClientID
within Card Related Service request |
Sakib |
| BOA-MA-4 |
Add
internal extra field "ClientID" of the Card will send during card
releted service request. |
Add
new field "Client ID" in Body of the "Send mail form
view" against all Card related service type during Card related service
request process.Pre-requiste TaskID: BOA-AP-3.4,BOA-API-2.1.6.3 |
|
100% |
0 |
Done |
3 |
BOA-MA |
12 |
ClientID
within Card Related Service request |
Rajesh |
| |
|
|
|
|
|
|
|
|
|
|
|
| BOA-AP-4 |
Other |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-4.2 |
Remove
"Select All" button from all List View Column Header |
|
|
100% |
0 |
Done |
4 |
BOA-AP |
4 |
Remove
"Select All" Button |
Shahin |
| BOA-AP-4.4 |
In
all Authorization module Button order as: Approve->Back->Reject. |
|
|
100% |
0 |
Done |
2 |
BOA-AP |
5 |
Authorization
Action Button Ordering |
Shahin |
| BOA-AP-4.8 |
Shift
All Acction Buttons of all List view because of scorolling problem |
1. All right most action button shift to Left most in all List view
controll(All module).
2. Only Add/Create button shift between "Select Action dropdown
controll" and "List View controll" of all List
view(Maker-Checker)
|
|
100% |
0 |
Done |
24 |
BOA-AP |
6 |
Shift
All Action Button within all List View |
Shahin |
| BOA-AP-4.6 |
Mail
sent to apps user |
1)Mail sent during 1st device add action approved by Checker from Admin
panel. 2)Mail sent during reset action approved by Checker from admin
panel.
|
|
100% |
0 |
Done |
3 |
BOA-AP |
7 |
Mail
Send During Approved |
Shahin |
| BOA-AP-4.7 |
SMS
sent to apps user |
SMS sent during 1st device add action approved by Checker from Admin
panel. 2)SMS sent during reset action
approved by Checker from admin panel.
|
|
100% |
0 |
Done |
3 |
BOA-AP |
7 |
SMS
Send During Approved |
Shahin |
| BOA-AP-4.10 |
Tracking
of changes in Admin Panel View |
Currently during checker approve/Reject, checker can view both published
and changed data. Tracking of changes in admin panel view should be there for
audit purpose, so that Checker can
view difference between published and changed data by hilighted
colour.Task:Create a analysis scanner engine with javascript to do this type
job then deploy in all checker modules.
|
|
70% |
108 |
Resolved |
360 |
BOA-AP |
30 |
Change
Tracking within View |
Shahin |
| BOA-AP-5 |
Content
Setup |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-5.1 |
Add
New Module EBL Complaint Cell Setup(Complaint Cell activity dynamic
Impact[BOA-MA-6]) |
Impact on "Apps","API","Admin User
Group(Maker,Checker)" and Database.Pre-requiste task: i)Add the module
during Create,Edit,Detail in Admin user group(Maker). ii)Add the module to
Authorozation(Checker). iii)Customize Login, Them1 and Them2 because impact
on Session data after Log in.Pre-requiste TaskID:
BOA-API-3.1.1,BOA-MA-6
|
|
0% |
16 |
Pending |
16 |
BOA-AP |
8 |
Complaint
Cell Dynamic |
Sakib |
| BOA-API-3.1.1 |
Off
line api(Complaint Cell activity dynamic Impact[BOA-MA-6]) |
Add New Public function in this API to get Complain Cell information.
Pre-requiste TaskID: BOA-MA-6,BOA-AP-5.1
|
|
0% |
1 |
Pending |
1 |
BOA-API |
8 |
Complaint
Cell Dynamic |
Sakib |
| BOA-MA-6 |
EBL Complaint Cell activity dynamic which will be configurable by Admin
Panel
|
Should
be followed as Address Book style.Pre-requiste TaskID:
BOA-AP-5.1,BOA-API-3.1.1 |
|
0% |
8 |
Pending |
8 |
BOA-MA |
8 |
Complaint
Cell Dynamic |
Rajesh |
| BOA-AP-6 |
REPORT |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-6.2 |
Service
Request Report |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-6.2.1 |
Product
Service Request Report |
Create Date wise Product Service Request Report populate which will be pdf
or exel. Pre-requiste task: i)Add this report module during
Create,Edit,Detail in Admin user group(Maker). ii)Add this report module to
Authorozation(Checker). iii)Customize Login, Them1 and Them2 because impact
on Session data after Log in.
|
|
100% |
0 |
Done |
24 |
BOA-AP |
14 |
Product
Service Request Report |
Shahin |
| BOA-AP-5.2.2 |
Priority
Service Request Report |
Create Date,Service Type wise Priority Service Request Report populate
which will be pdf or exel. Pre-requiste task: i)Add this report module during
Create,Edit,Detail in Admin user group(Maker). ii)Add this report module to
Authorozation(Checker). iii)Customize Login, Them1 and Them2 because impact
on Session data after Log in.
|
|
100% |
0 |
Done |
24 |
BOA-AP |
15 |
Priority
Service Request Report |
Shahin |
| BOA-AP-6.2.3 |
Banking
Service Request Report |
Create Date,Service Type,Sub Service Type wise Banking Service Request
Report populate which will be pdf or exel. Pre-requiste task: i)Add this
report module during Create,Edit,Detail in Admin user group(Maker). ii)Add
this report module to Authorozation(Checker). iii)Customize Login, Them1 and
Them2 because impact on Session data after Log in.
|
|
100% |
0 |
Done |
24 |
BOA-AP |
16 |
Banking
Service Request Report |
Shahin |
| BOA-AP-6.3 |
Service
Request Process Report |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-6.3.1 |
Product
Service Request Mail Process Report |
Create Date wise Product Service Request Mail Process Report populate which
will be pdf or exel. Pre-requiste task: i)Add this report module during
Create,Edit,Detail in Admin user group(Maker). ii)Add this report module to
Authorozation(Checker). iii)Customize Login, Them1 and Them2 because impact
on Session data after Log in.
|
Need
Report format from EBL |
100% |
0 |
Done |
24 |
BOA-AP |
17 |
Product
Service Request Mail Report |
Shahin |
| BOA-AP-6.3.2 |
Priority
Service Request Mail process Report |
Create Date,Service Type wise Priority Service Request Report populate
which will be pdf or exel. Pre-requiste task: i)Add this report module during
Create,Edit,Detail in Admin user group(Maker). ii)Add this report module to
Authorozation(Checker). iii)Customize Login, Them1 and Them2 because impact
on Session data after Log in.
|
Need
Report format from EBL |
100% |
0 |
Done |
24 |
BOA-AP |
18 |
Priority
Service Request Mail Report |
Shahin |
| BOA-AP-6.3.3 |
Banking
Service Request Mail Process Report |
Create
Date,Service Type,Sub Service Type wise Banking Service Request Report
populate which will be pdf or exel. Pre-requiste task: i)Add this report
module during Create,Edit,Detail in Admin user group(Maker). ii)Add this
report module to Authorozation(Checker). iii)Customize Login, Them1 and Them2
because impact on Session data after Log in. |
Need
Report format from EBL |
100% |
0 |
Done |
24 |
BOA-AP |
19 |
Banking
Service Request Mail Report |
Shahin |
| BOA-AP-7 |
Dashboard |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-7.1 |
Real
time List View Transaction dashboard |
This is the real time transaction related List View dashboard which should
be following features: i)Real time last "n-transaction" List View
populate. ii)Transaction Status wise row colour.Pre-requiste task: i)Add the
module during Create,Edit,Detail in Admin user group(Maker). ii)Add the
module to Authorozation(Checker). iii)Customize Login, Them1 and Them2
because impact on Session data after Log in.Pre-requiste TaskID:
BOA-API-2.1.3.1, BOA-API-2.1.3.2, BOA-API-2.1.3.3
|
|
0% |
24 |
Pending |
24 |
BOA-AP |
26 |
Real
Time Transaction Dashboard |
Shahin |
| BOA-API-2.1.3.1 |
Own
Account Transfer(Real time List View Transaction dashboard
Impact[BOA-AP-7.1]) |
customize this api as per Real time List View Transaction
dashboard.customize this api as per Real time List View Bill Payment
dashboard.(insert dash board related data in DB) Pre-requiste TaskID:
BOA-AP-7.1
|
|
0% |
4 |
Pending |
4 |
BOA-API |
26 |
Real
Time Transaction Dashboard |
Shahin |
| BOA-API-2.1.3.2 |
Another
Account Transfer(Real time List View Transaction dashboard
Impact[BOA-AP-7.1]) |
customize this api as per Real time List View Transaction
dashboard.customize this api as per Real time List View Bill Payment
dashboard.(insert dash board related data in DB) Pre-requiste TaskID:
BOA-AP-7.1
|
|
0% |
4 |
Pending |
4 |
BOA-API |
26 |
Real
Time Transaction Dashboard |
Shahin |
| BOA-API-2.1.3.3 |
Other
Bank Account Transfer(Real time List View Transaction dashboard
Impact[BOA-AP-7.1]) |
customize this api as per Real time List View Transaction
dashboard.customize this api as per Real time List View Bill Payment
dashboard.(insert dash board related data in DB) Pre-requiste TaskID:
BOA-AP-7.1
|
|
0% |
4 |
Pending |
4 |
BOA-API |
26 |
Real
Time Transaction Dashboard |
Shahin |
| BOA-AP-7.2 |
Real
time List View Bill Payment dashboard |
This is the real time Bill Payment related List View dashboard which should
be following features: i)Real time last "n-bill payment" List View
populate. ii)Bill payment Status wise row colour.Pre-requiste task: i)Add the
module during Create,Edit,Detail in Admin user group(Maker). ii)Add the
module to Authorozation(Checker). iii)Customize Login, Them1 and Them2
because impact on Session data after Log in.Pre-requiste TaskID:
BOA-API-2.1.4.1
|
|
0% |
24 |
Pending |
24 |
BOA-AP |
27 |
Real
Time Bill Payment Dashboard |
Shahin |
| BOA-API-2.1.4.1 |
Pay
Bill(Real time List View Bill Payment dashboard Impact[BOA-AP-7.2]) |
customize this api as per Real time List View Bill Payment
dashboard.(insert dash board related data in DB) Pre-requiste TaskID:
BOA-AP-7.2
|
|
0% |
6 |
Pending |
6 |
BOA-API |
27 |
Real
Time Bill Payment Dashboard |
Shahin |
| BOA-AP-10 |
Products |
|
|
|
|
|
|
|
|
|
|
| BOA-AP-10.1 |
Ordaring
of all dynamic Item of the Products as per configure by Back end admin user
which make sure apps data ordering. |
EBL Requirment:Ordering Should be possible in Products as like as present
biller system in back end admin panel so that we can order the product as our
own from time to time.
Note to Developer:Add new field "Order" in db table and
accordingly change of all View in admin panel.Impact on Add,Edit and detail
view in admin panel and also API "Get Product".Pre-requiste TaskID:
BOA-API-5.1 |
|
60% |
2.4 |
On going |
6 |
BOA-AP |
20 |
Product
Ordering |
Shahin |
| BOA-API-5.1 |
Get
Product API(Ordaring of all dynamic Item of the Products as per configure by
Back end admin user Impact[BOA-AP-10.1]) |
customize
this api as per Ordaring of all dynamic Item of the Products as per configure
by Back end admin user.
Note to Developer:Add new field "Order" in db table and
accordingly change of all View in admin panel.Impact on Add,Edit and detail
view in admin panel and also API "Get Product".Pre-requiste TaskID:
BOA-AP-10.1 |
|
60% |
0.8 |
On going |
2 |
BOA-API |
20 |
Product
Ordering |
Shahin |
| |
|
|
|
|
|
|
|
|
|
|
|
| BOA-API-2.1.3.5 |
Beneficiary |
|
|
|
|
|
|
|
|
|
|
| BOA-API-2.1.3.5.1 |
Add
Beneficary Inter Bank Account Impact[BOA-MA-15.1]) |
During inter bank account (EBL account) fund transfer by apps, user should
be set value of "To Account/Destination Account" from dropdown
list.To create this dropdown list value as alias/template, user will use the
mobile apps feature "Add Beneficiary Account".Apps will complete
the fullcycle through this API.
Pre-requiste TaskID:
BOA-MA-15.1,BOA-MA-15.2,BOA-MA-15.3,BOA-API-2.1.3.5.2,BOA-API-2.1.3.5.3,BOA-API-2.1.3.5.4,BOA-API-2.1.3.5.5,BOA-API-2.1.3.5.6
Note to developer:
i)create new table "beneficaryIBAccount" in DB (unique
field:AppsUserID+accountNo).
ii)create new controller "beneficiaryAccount"(if not exist) in
API project.
iii)create new public function "add_beneficary_ib_account"
in "beneficiaryAccount"
controller which will controll Apps request during save the "inter bank
account" as alias/template by apps user.
|
|
70% |
1.8 |
Resolved |
6 |
BOA-API |
21 |
Beneficiary
for Transaction |
Sakib |
| BOA-API-2.1.3.5.2 |
Add
Beneficary Other Bank Account Impact[BOA-MA-15.1]) |
During other bank account fund transfer by apps, user should be set value
of "To Account/Destination Account" from dropdown list.To create
this dropdown list value as alias/template, user will use the mobile apps
feature "Add Beneficiary Account".Apps will complete the fullcycle
through this API.
Pre-requiste TaskID:
BOA-MA-15.1,BOA-MA-15.2,BOA-MA-15.3,BOA-API-2.1.3.5.1,BOA-API-2.1.3.5.3,BOA-API-2.1.3.5.4,BOA-API-2.1.3.5.5,BOA-API-2.1.3.5.6
Note to developer:
i)create new table "beneficaryOBAccount" in DB(unique
field:AppsUserID+accountNo)
ii)create new controller "beneficiaryAccount"(if not exist) in
API project.
iii)create new public function "add_beneficary_ob_account"
in "beneficiaryAccount"
controller which will controll Apps request during save the "other bank
account" as alias/template by apps user.
|
|
70% |
1.8 |
Resolved |
6 |
BOA-API |
21 |
Beneficiary
for Transaction |
Sakib |
| BOA-API-2.1.3.5.3 |
Delete
Beneficary Inter Bank Account
(Impact[BOA-MA-15.2]) |
During inter bank account fund transfer by apps, user should be set value
of "To Account/Destination Account" from dropdown list.To create
this dropdown list value as alias/template, user will use the mobile apps
feature "Add Beneficiary Account" and also apps user can delete the
previous added beneficary account using the mobile apps feature "Delete
Beneficary Account".Apps will complete the fullcycle for delete through
this API.
Pre-requiste TaskID: BOA-MA-15.1,BOA-MA-15.2,BOA-MA-15.3,BOA-API-2.1.3.5.1,BOA-API-2.1.3.5.2,BOA-API-2.1.3.5.4,BOA-API-2.1.3.5.5,BOA-API-2.1.3.5.6
Note to developer:
i)create new controller "beneficiaryAccount"(if not exist) in API
project.
ii)create new public function "inactive_beneficary_ib_account"
in "beneficiaryAccount"
controller which will controll Apps request during delete the "inter
bank account".
DB table: beneficaryIBAccount |
|
70% |
0.9 |
Resolved |
3 |
BOA-API |
21 |
Beneficiary
for Transaction |
Sakib |
| BOA-API-2.1.3.5.4 |
Delete
Beneficary Other Bank Account (Impact[BOA-MA-15.2]) |
During other bank account fund transfer by apps, user should be set value
of "To Account/Destination Account" from dropdown list.To create
this dropdown list value as alias/template, user will use the mobile apps
feature "Add Beneficiary Account" and also apps user can delete the
previous added beneficary account using the mobile apps feature "Delete
Beneficary Account".Apps will complete the fullcycle for delete through
this API.
Pre-requiste TaskID: BOA-MA-15.1,BOA-MA-15.2,BOA-MA-15.3,BOA-API-2.1.3.5.1,BOA-API-2.1.3.5.2,BOA-API-2.1.3.5.3,BOA-API-2.1.3.5.5,BOA-API-2.1.3.5.6
Note to developer:
i)create new controller "beneficiaryAccount"(if not exist) in API
project.
ii)create new public function "inactive_beneficary_ob_account"
in "beneficiaryAccount"
controller which will controll Apps request during delete the "other
bank account".
DB table: beneficaryOBAccount |
|
70% |
0.9 |
Resolved |
3 |
BOA-API |
21 |
Beneficiary
for Transaction |
Sakib |
| BOA-API-2.1.3.5.5 |
Get
Beneficary Inter Bank Added Account (Impact[BOA-MA-15.2]) |
During inter bank account fund transfer and delete the previous added
beneficary inter bank account by apps, mobile apps need to populate "To
Account/Destination Account" dropdown list and beneficary template list
activaty.To do this type job,apps will consume this API.
Pre-requiste TaskID:
BOA-MA-15.1,BOA-MA-15.2,BOA-MA-15.3,BOA-API-2.1.3.5.1,BOA-API-2.1.3.5.2,BOA-API-2.1.3.5.3,BOA-API-2.1.3.5.4,BOA-API-2.1.3.5.6
Note to developer:
i)create new controller "beneficiaryAccount"(if not exist) in API
project.
ii)create new public function "get_beneficary_ib_account" in "beneficiaryAccount" controller
which will ensure Apps to get the previous aded beneficary inter bank
account.
DB table: beneficaryIBAccount
|
|
70% |
0.9 |
Resolved |
3 |
BOA-API |
21 |
Beneficiary
for Transaction |
Sakib |
| BOA-API-2.1.3.5.6 |
Get
Beneficary Other Bank Added Account (Impact[BOA-MA-15.2]) |
During other bank account fund transfer and delete the previous added
beneficary other bank account by apps, mobile apps need to populate "To
Account/Destination Account" dropdown list and beneficary template list
activaty.To do this type job,apps will consume this API.
Pre-requiste TaskID:
BOA-MA-15.1,BOA-MA-15.2,BOA-MA-15.3,BOA-API-2.1.3.5.1,BOA-API-2.1.3.5.2,BOA-API-2.1.3.5.3,BOA-API-2.1.3.5.4,BOA-API-2.1.3.5.5
Note to developer:
i)create new controller "beneficiaryAccount"(if not exist) in API
project.
ii)create new public function "get_beneficary_ob_account" in "beneficiaryAccount" controller
which will ensure Apps to get the previous aded beneficary other bank
account.
DB table: beneficaryOBAccount |
|
70% |
0.9 |
Resolved |
3 |
BOA-API |
21 |
Beneficiary
for Transaction |
Sakib |
| BOA-MA-15.1 |
Add
Beneficary Account |
During
fund transfer, user should be set value of "To Account/Destination
Account" from dropdown list.To create this dropdown list value as
alias/template, user will use this feature (Add Beneficiary Account).
Pre-requiste TaskID: BOA-MA-15.2,BOA-MA-15.3,BOA-API-2.1.3.5.1,BOA-API-2.1.3.5.2,BOA-API-2.1.3.5.3,BOA-API-2.1.3.5.4,BOA-API-2.1.3.5.5,BOA-API-2.1.3.5.6
Not to developer:
1. Add one Item "Add Beneficary" in Fund transfer Activity.
2. Create new Activity "BeneficiaryAccountCategoryList" with
Items(Inter Bank Account,Other Bank Account).
3. Create new two more Activity "AddBeneficiaryInterBankAccount"
and "AddBeneficiaryOtherBankAccount" with bottons Save and
Cancel.
Full cycle navigation and process flow with
Business logic:
1. Click the Item "Add Beneficary" from Fund transfer Activity.
2. Nevigate to "BeneficiaryAccountCategoryList" Activity.
3. Click the Item from "BeneficiaryAccountCategoryList" Activity. |
|
70% |
3.6 |
Resolved |
12 |
BOA-MA |
21 |
Beneficiary
for Transaction |
Rajesh |
| |
|
3.1.
If(Click the Item ="Inter Bank Account")
3.1.1. Nevigate to "AddBeneficiaryInterBankAccount"
Activity.
3.1.2 Fill up the Activity form.
3.1.3 Click the button from "AddBeneficiaryInterBankAccount" Activity.
3.1.3.1. If(Click the Button ="Save")
3.1.3.1.1. Show confirmation Activity as modal.
3.1.3.1.2. Click the Button "Confirm".
3.1.3.1.3. Consume the API "Add Beneficary Inter Bank Account".
3.1.3.1.4. Message show and nevigate as per API response.
3.1.3.2 Else If(Click the Button ="Cancel")
3.1.3.2.1 Get back previous activity.
3.2. Else If(Click the Item ="Other Bank Account")
3.2.1. Nevigate to "AddBeneficiaryOtherBankAccount"
Activity.
3.2.2 Fill up the Activity form.
3.2.3 Click the button from "AddBeneficiaryOtherBankAccount"
Activity.
3.2.3.1. If(Click the Button ="Save")
3.2.3.1.1. Show confirmation Activity as modal.
3.2.3.1.2. Click the Button "Confirm".
3.2.3.1.3. Consume the API "Add Beneficary Other Bank
Account".
3.2.3.1.4. Message show and nevigate as per API response.
3.2.3.2 Else If(Click the Button ="Cancel")
3.2.3.2.1 Get back previous activity.
|
|
70% |
0 |
Resolved |
|
BOA-MA |
21 |
Beneficiary
for Transaction |
Rajesh |
| BOA-MA-15.2 |
Delete
Beneficary Account |
Apps user can delete the previous added beneficary account using this
mobile apps feature "Delete Beneficary Account". Pre-requiste
TaskID:
BOA-MA-15.1,BOA-MA-15.3,BOA-API-2.1.3.5.1,BOA-API-2.1.3.5.2,BOA-API-2.1.3.5.3,BOA-API-2.1.3.5.4,BOA-API-2.1.3.5.5,BOA-API-2.1.3.5.6
Not to developer:
1. Add one Item "Delete Beneficary" in Fund transfer
Activity.
2. Create new Activity "BeneficiaryAccountCategoryList" (if not
exist) with Items(Inter Bank Account,Other Bank Account).
3. Create new one more List Activity
"BeneficiaryAccountList".
|
|
70% |
4.8 |
Resolved |
16 |
BOA-MA |
21 |
Beneficiary
for Transaction |
Rajesh |
| |
|
Full cycle navigation and process flow with Business logic:
1. Click the Item "Delete Beneficary" from Fund transfer Activity .
2. Nevigate to "BeneficiaryAccountCategoryList" Activity.
3. Click the Item from "BeneficiaryAccountCategoryList"
Activity.
3.1 If(Click the Item ="Inter Bank Account")
3.1.1 Nevigate to "BeneficiaryAccountList" Activity and populate
this list with previous added beneficary inter bank account data through the
API "get_beneficary_ib_account".
3.1.2 Click the list item or right most delete button.
3.1.3 Show confirmation Activity as modal.
3.1.4 Click the Button "Confirm".
3.1.5 Consume the API "Delete Beneficary Inter Bank
Account".
3.1.6 Message show and nevigate as per API response.
3.2 Else If(Click the Item ="Other Bank Account")
3.2.1 Nevigate to "BeneficiaryAccountList" Activity and populate
this list with previous added beneficary other bank account data through the
API "get_beneficary_ob_account".
3.2.2 Click the list item or right most delete button.
3.2.3 Show confirmation Activity as modal.
3.2.4 Click the Button "Confirm".
3.2.5 Consume the API "Delete Beneficary other Bank
Account".
3.2.6 Message show and nevigate as per API response.
|
|
70% |
0 |
Resolved |
|
BOA-MA |
21 |
Beneficiary
for Transaction |
Rajesh |
| BOA-MA-15.3 |
Inter
bank and other bank Fund Transfer User input Activity
changed(Impact[BOA-MA-15.1]) |
During
fund transfer(Inter bank and other bank fund transfer), user should be set
value of "To Account/Destination Account" from dropdown list.To
populate this dropdown list value as alias/template, Apps will consume the
API "get_beneficary_ib_account" (for inter bank fund transfer) or
"get_beneficary_ob_account" (for other bank fund transfer).
Pre-requiste TaskID:
BOA-MA-15.1,BOA-MA-15.2,BOA-API-2.1.3.5.1,BOA-API-2.1.3.5.2,BOA-API-2.1.3.5.3,BOA-API-2.1.3.5.4,BOA-API-2.1.3.5.5,BOA-API-2.1.3.5.6
|
|
70% |
3.6 |
Resolved |
12 |
BOA-MA |
22 |
Beneficiary
Impact during Transaction |
Rajesh |
| |
|
|
|
|
|
|
|
|
|
|
|
| BOA-API-2.1.4 |
BILLS
PAY |
|
|
|
|
|
|
|
|
|
|
| BOA-API-2.1.4.4 |
Delete
Biller Registration(Delete Registred Biller Activity[BOA-MA-8]) |
Create the new API to delete a registered biller.Please check the
dependency table before delete.Pre-requiste TaskID: BOA-MA-8
|
|
70% |
2.4 |
Resolved |
8 |
BOA-API |
23 |
Beneficiary for Bill Payment |
Sakib |
| BOA-MA-8 |
Delete
Registered Biller Activity |
Need a new activity "Delete registered Biller" to delete a
registered biller.Pre-requiste TaskID: BOA-API-2.1.4.4
|
|
70% |
3.6 |
Resolved |
12 |
BOA-MA |
23 |
Beneficiary for Bill Payment |
Rajesh |
| |
|
|
|
|
|
|
|
|
|
|
|
| BOA-API-4 |
Activity
Log |
|
|
|
|
|
|
|
|
|
|
| BOA-API-4.1 |
Apps
User Activity log in flat file |
Currently storing the activity log in Database after login. Apart from
this, activity log should generate in flat file for customer initiated
actions which should be stored in the file system.Only file system activity
log should be generate for both before and after login because there could be
a risk if non-registered customer hit the application and database very
frequently. Access log should generate in flat file for unregistered customer
which should be stored in the file system.Impact on all entry lavel functions
of all API.
|
Does
the apps read IMEI NO,MOB NO,Model no
etc for further analysis? |
0% |
56 |
Pending |
56 |
BOA-API |
29 |
Apps
User Activity Log within Flat File |
Sakib |
| BOA-API-5 |
Zip |
|
|
|
|
|
|
|
|
|
|
| BOA-API-5.1 |
Get Zip API(Ordaring
"Name" as ascending )
|
customize
this api as per Ordaring
"Name" as ascending.
|
|
100% |
0 |
Done |
2 |
BOA-API |
24 |
Zip
Ordering |
Shahin |
| BOA-API-6 |
Benefit |
|
|
|
|
|
|
|
|
|
|
| BOA-API-6.1 |
Get Benifit API(Ordaring
"Name" as ascending )
|
customize
this api as per Ordaring
"Name" as ascending. |
|
100% |
0 |
Done |
2 |
BOA-API |
25 |
Benifit
Ordering |
Shahin |
| BOA-MA-5 |
Run time permission impliment in MarshMallow
|
|
|
100% |
0 |
Done |
32 |
BOA-MA |
-1 |
Run
Time Permission in MarshMallow |
Rajesh |
| BOA-MA-11 |
Locate
EBL |
|
|
|
|
|
|
|
|
|
|
| BOA-MA-11.1 |
Search
option in Locate Branch |
EBL Requirment:Search option should be there so that customer could find
any branch by writing name.
Note to developer:
1. create new activity with search input field which will be auto
complete.
2. Create new list as per aut0 complete Item selection.
3. Populate map as per list Item selection.
|
|
100% |
0 |
Done |
24 |
BOA-MA |
-1 |
Search
Bank |
Rajesh |
| BOA-MA-11.2 |
Search
option in Locate EBL 365 |
EBL Requirment:Search option should be there so that customer could find
any ATM by writing name.
Note to developer:
1. create new activity with search input field which will be auto
complete.
2. Create new list as per auto complete Item selection
3. Populate map as per list Item selection.
|
|
100% |
0 |
Done |
24 |
BOA-MA |
-1 |
Search
Bank |
Rajesh |
| BOA-MA-11.3 |
Search
option in Locate EBL Dropbox |
EBL Requirment:Search option should be there so that customer could find
any dropbox by writing name.
Note to developer:
1. create new activity with search input field which is auto
complete.
2. Create new list as per auto complete Item selection
3. Populate map as per list Item selection.
|
|
100% |
0 |
Done |
24 |
BOA-MA |
-1 |
Search
Bank |
Rajesh |
| BOA-MA-12 |
Biller
name to be shown at confirmation page |
At confirmation page, the biller name/ mobile number/ account number should
be shown so that customer can confirm that he/she is sending fund to the
right person or recharging the right mobile number.
[Impact on 3-type transaction,Bill payment and these related all
confirmation activity]
|
|
100% |
0 |
Done |
5 |
BOA-MA |
-1 |
Change
Confirmation page during Bill Payment |
Rajesh |
| BOA-MA-13 |
A
new category “What’s New” add in Benefit and Zip |
When any new ZIP or Benefit partner gets added in the list, it will be
shown in a new category: “What’s New” along with its own category. This
category will be at the top of other categories. Even when any merchant’s
info is updated at the back end it will be shown in these categories
too.
Example:
Suppose in “Airline” category under “Benefits”, a new merchant ‘US Bangla
airlines’ gets added at the back end, it will be shown in the new category
“What’s New”. It will also be shown under “Airline” category.
Its similar to TaskId:BOA-MA-10
|
|
0% |
24 |
Pending |
24 |
BOA-MA |
28 |
Category
"What's New" within Zip & Benefit |
Rajesh |
| BOA-MA-16 |
Displaying
Multiple Credit Card Information In the App |
Impact
on:Maker Apps User ADD/EDIT(registration process), Checker Apps User
Authorization,General Card Information activity,Card Transaction Statement
activity,Card Service Request activity in Apps and also General Card
Information API,Card Transaction Statement API,Card Service Request API,
cardNumber API in TAE and accordingly
also should be optimised card service return data. |
|
|
|
|
|
|
|
|
|
| BOA-AP-4.11 |
Customize
Maker Apps user Add and Edit as per multi card information view in Back
Office Admin Panel (Impact[BOA-MA-16]) |
Customize
Maker Apps user Add and Edit as per multi card information view in Back
Office Admin Panel. Pre-requiste TaskID: BOA-AP-4.12, BOA-MA-6.1,BOA-MA-6.2,
BOA-MA-6.3 |
|
100% |
0 |
Done |
16 |
BOA-AP |
1 |
Displaying
Multiple Credit Card Information In the App |
Shahin |
| BOA-AP-4.12 |
Customize
Checker Apps user Authorization as per multi card information view in Back
Office Admin Panel (Impact[BOA-MA-16]) |
Customize
Checker Apps user Authorization as per multi card information view in Back
Office Admin Panel. Pre-requiste TaskID: BOA-AP-4.11, BOA-MA-6.1,BOA-MA-6.2,
BOA-MA-6.3 |
|
100% |
0 |
Done |
16 |
BOA-AP |
1 |
Displaying
Multiple Credit Card Information In the App |
Shahin |
| BOA-MA-16.1 |
General
Card Information Activity changed with Multiple Credit Card Information |
General
Card Information Activity changed with
Multiple Credit Card Information and if need more activity add. Pre-requiste
TaskID: BOA-API-2.1.5.1 |
|
100% |
0 |
Done |
28 |
BOA-MA |
1 |
Displaying
Multiple Credit Card Information In the App |
Rajesh |
| BOA-MA-16.2 |
Card
transaction activity customized as per Multiple Credit Card Information |
Card
Transaction View Activity changed with
Multiple Credit Card Information and if need more activity add. Pre-requiste
TaskID: BOA-API-2.1.5.2 |
|
100% |
0 |
Done |
16 |
BOA-MA |
1 |
Displaying
Multiple Credit Card Information In the App |
Rajesh |
| BOA-MA-16.3 |
Card
related service request activity customized as per Multiple Credit Card
Information |
Card
Related Service Request Activity changed
with Multiple Credit Card Information and if need more activity add.
Pre-requiste TaskID: BOA-API-2.1.5.3 |
|
100% |
0 |
Done |
24 |
BOA-MA |
1 |
Displaying
Multiple Credit Card Information In the App |
Rajesh |
| BOA-API-2.1.5 |
CARD |
|
|
|
|
|
|
|
|
|
|
| BOA-API-2.1.5.1 |
General
Information of card (Impact[BOA-MA-16]) |
This
API should be full customized as per Multiple Credit Card Information and
also should be optimised card service return data. Pre-requiste TaskID:
BOA-MA-16.1 |
|
100% |
0 |
Done |
24 |
BOA-API |
1 |
Displaying
Multiple Credit Card Information In the App |
Shahin |
| BOA-API-2.1.5.2 |
Last
3 Transection of card (Impact[BOA-MA-16]) |
This
API should be full customized as per Multiple Credit Card Information and
also should be optimised card service return data. Pre-requiste TaskID:
BOA-MA-16.2 |
|
100% |
0 |
Done |
24 |
BOA-API |
1 |
Displaying
Multiple Credit Card Information In the App |
Shahin |
| BOA-API-2.1.5.3 |
Get
Card No (Impact[BOA-MA-16]) |
This
API should be full customized as per Multiple Credit Card Information.
Pre-requiste TaskID: BOA-MA-16.3 |
|
100% |
0 |
Done |
16 |
BOA-API |
1 |
Displaying
Multiple Credit Card Information In the App |
Shahin |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
| BankOnApp Priority
Plus |
|
|
|
|
|
|
|
|
|
|
| BOA-PP-1 |
New
APK Project and Versioning |
|
|
|
|
|
|
|
|
|
|
| BOA-PP-1.1 |
Separate
from existing Android SKY BANKING Apps as new project |
For priority customer,separate from existing Android SKY
BANKING Apps as a new project and also version controll for google play
store.This Apps will consume all existing API of SKY BANKING Apps.
Note to developer:
1. Separate from existing Android SKY BANKING Apps as new project
2.Customise the Key Exchange API
3.Create new table in DB "priorityPlusImeiNo".
4.Create new module in BOA Admin panel which will ensure add,edit and
delete view to DB table "priorityPlusImeiNo". (without
maker-checker facility)
5.Add the module during
Create,Edit,Detail in Admin user group(Maker).
6.Add the module to Authorozation(Checker).
7.Customize Login, Them1 and Them2 because impact on Session data after Log
in
|
|
100% |
0 |
Done |
40 |
BOA-PP |
-1 |
APK
Project Versioning & Branding for BOA-PP |
Rajesh |
| BOA-PP-2 |
New
APK Project and Branding |
|
|
|
|
|
|
|
|
|
|
| BOA-PP-2.1 |
Design
customization and branding as per EBL provided image |
Note to developer:
1.AI to Image conversion
2.All background logo change
3.Create new Header for all screen.
4.All static text colour change as per EBL suggestion.
|
|
100% |
0 |
Done |
32 |
BOA-PP |
-1 |
APK
Project Versioning & Branding for BOA-PP |
Rajesh |
| BOA-PP-3 |
All
Changes Under BOA-MA Reflect |
|
|
|
|
|
|
|
|
|
|
| BOA-PP-3.1 |
All
Changes Under BOA-MA should be incorporate in BankOnApp Priority Plus. |
Estimated
time (Man Hour) should be calculated of this type of job followed as per the
following rules
1) Estimated Time (Man Hour) = ROUND(10% of Total Man Hour (BOA-MA)) |
|
0% |
26 |
Pending |
26 |
BOA-PP |
30 |
All
Changes Under BOA-MA Reflect for BOA-PP |
Rajesh |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Table Name: |
Milestone As
Per Task Grouping |
|
|
|
|
|
|
|
|
|
| |
Client
Name: |
EBL |
|
|
|
|
|
|
|
|
|
| SL |
Task
Group Name |
Total
(Man Hour) |
Remaining Time
(Man Hour) |
Completed (%) |
Remark |
BOA-AP |
BOA-API |
BOA-MA |
BOA-PP |
Total |
|
| 1 |
Password
Policy |
92 |
63.2 |
31.30435 |
|
48 |
44 |
0 |
0 |
92 |
|
| 2 |
Limit
Package ordering |
8 |
0 |
100 |
|
8 |
0 |
0 |
0 |
8 |
|
| 3 |
Product
Service Request Mail |
5 |
0 |
100 |
|
5 |
0 |
0 |
0 |
5 |
|
| 4 |
Priority
Service Request Mail |
5 |
0 |
100 |
|
5 |
0 |
0 |
0 |
5 |
|
| 5 |
Banking
Service Request Mail |
5 |
0 |
100 |
|
5 |
0 |
0 |
0 |
5 |
|
| 6 |
ClientID
within Card Related Service request |
9 |
0 |
100 |
|
4 |
2 |
3 |
0 |
9 |
|
| 7 |
Remove
"Select All" Button |
4 |
0 |
100 |
|
4 |
0 |
0 |
0 |
4 |
|
| 8 |
Authorization
Action Button Ordering |
2 |
0 |
100 |
|
2 |
0 |
0 |
0 |
2 |
|
| 9 |
Shift
All Action Button within all List View |
24 |
0 |
100 |
|
24 |
0 |
0 |
0 |
24 |
|
| 10 |
Mail
Send During Approved |
3 |
0 |
100 |
|
3 |
0 |
0 |
0 |
3 |
|
| 11 |
SMS
Send During Approved |
3 |
0 |
100 |
|
3 |
0 |
0 |
0 |
3 |
|
| 12 |
Complaint
Cell Dynamic |
25 |
25 |
0 |
|
16 |
1 |
8 |
0 |
25 |
|
| 13 |
Product
Service Request Report |
24 |
0 |
100 |
|
24 |
0 |
0 |
0 |
24 |
|
| 14 |
Priority
Service Request Report |
24 |
0 |
100 |
|
24 |
0 |
0 |
0 |
24 |
|
| 15 |
Banking
Service Request Report |
24 |
0 |
100 |
|
24 |
0 |
0 |
0 |
24 |
|
| 16 |
Product
Service Request Mail Report |
24 |
0 |
100 |
|
24 |
0 |
0 |
0 |
24 |
|
| 17 |
Priority
Service Request Mail Report |
24 |
0 |
100 |
|
24 |
0 |
0 |
0 |
24 |
|
| 18 |
Banking
Service Request Mail Report |
24 |
0 |
100 |
|
24 |
0 |
0 |
0 |
24 |
|
| 19 |
Real
Time Transaction Dashboard |
36 |
36 |
0 |
|
24 |
12 |
0 |
0 |
36 |
|
| 20 |
Real
Time Bill Payment Dashboard |
30 |
30 |
0 |
|
24 |
6 |
0 |
0 |
30 |
|
| 21 |
Product
Ordering |
8 |
3.2 |
60 |
|
6 |
2 |
0 |
0 |
8 |
|
| 22 |
Beneficiary
for Transaction |
52 |
15.6 |
70 |
|
0 |
24 |
28 |
0 |
52 |
|
| 23 |
Beneficiary
Impact during Transaction |
12 |
3.6 |
70 |
|
0 |
0 |
12 |
0 |
12 |
|
| 24 |
Beneficiary for Bill Payment |
20 |
6 |
70 |
|
0 |
8 |
12 |
0 |
20 |
|
| 25 |
Apps
User Activity Log within Flat File |
56 |
56 |
0 |
|
0 |
56 |
0 |
0 |
56 |
|
| 26 |
Zip
Ordering |
2 |
0 |
100 |
|
0 |
2 |
0 |
0 |
2 |
|
| 27 |
Benifit
Ordering |
2 |
0 |
100 |
|
0 |
2 |
0 |
0 |
2 |
|
| 28 |
Run
Time Permission in MarshMallow |
32 |
0 |
100 |
|
0 |
0 |
32 |
0 |
32 |
|
| 29 |
Search
Bank |
72 |
0 |
100 |
|
0 |
0 |
72 |
0 |
72 |
|
| 30 |
Change
Confirmation page during Bill Payment |
5 |
0 |
100 |
|
0 |
0 |
5 |
0 |
5 |
|
| 31 |
Category
"What's New" within Zip & Benefit |
24 |
24 |
0 |
|
0 |
0 |
24 |
0 |
24 |
|
| 32 |
APK
Project Versioning & Branding for BOA-PP |
72 |
0 |
100 |
|
0 |
0 |
0 |
72 |
72 |
|
| 33 |
Change
Tracking within View |
360 |
108 |
70 |
|
360 |
0 |
0 |
0 |
360 |
|
| 34 |
Displaying
Multiple Credit Card Information In the App |
164 |
0 |
100 |
|
32 |
64 |
68 |
0 |
164 |
|
| 35 |
All
Changes Under BOA-MA Reflect for BOA-PP |
26 |
26 |
0 |
|
0 |
0 |
0 |
26 |
26 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Total Man Hour
Without ios |
1302 |
396.6 |
69.53917 |
|
717 |
223 |
264 |
98 |
1302 |
|
| |
Total
Man Hour BOA-MA (ios) |
264 |
|
|
|
|
|
|
|
|
|
| |
Total
Man Hour BOA-PP (ios) |
98 |
|
|
|
|
|
|
|
|
|
| |
Total
Man Hour (Development) |
1664 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Table Name: |
Total Time
Estimation |
|
|
|
|
|
|
|
|
|
| |
Client
Name: |
EBL |
|
|
|
|
|
|
|
|
|
|
BankOnApp |
|
|
|
|
|
|
|
|
|
| Time Estimation of CR |
|
|
|
|
|
|
|
|
| SLNO |
Description |
Estimation
Time(Man Hour) |
%
of Development |
|
|
|
|
|
|
|
|
| 1 |
Development |
1664 |
|
|
| 2 |
Analysis
and Design |
249.6 |
15 |
|
| 3 |
Testing |
499.2 |
30 |
|
| 4 |
Documentation |
166.4 |
10 |
|
| 5 |
Deployment
on EBL Test server and Testing |
41.6 |
2.5 |
|
| 6 |
Deployment
on EBL Production server and testing |
41.6 |
2.5 |
|
| 7 |
Project
Management |
83.2 |
5 |
|
|
|
|
|
|
| |
Total Man Hour |
2745.6 |
|
|
| |
Total
Man Day |
343.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Table Name: |
Status Type |
|
|
| |
Client
Name: |
EBL |
|
|
| SL |
Status |
Description |
Estimated Time
(Man Hour) |
|
| 1 |
Pending |
Issue
raised but not initiate from CIBL |
241 |
|
| 2 |
On
going |
Development/Bug
fixing/Analysis/R&d running |
56 |
|
|
|
| 3 |
Resolved |
Fix
the issue but not impliment to Client Side |
444 |
|
|
|
| 4 |
Done |
Fix
the issue and impliment to Client Side |
561 |
|
|
|
|
|
|
|
|
|
|
| |
|
Total Man Hour
Without ios |
1302 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Table Name: |
Rule Of
Formated Colour |
|
|
|
|
| |
|
|
|
|
|
|
| SL |
Table
Name |
CVBR
apply on "Column Name" |
Cell Velue
Between Renge (CVBR) |
Back Ground
Formated Colour |
Font Formated
Colour |
|
| 1 |
Milestone
AS Per Task Grouping |
Completed
(%) |
0-0 |
|
N/A |
|
| 2 |
Milestone
AS Per Task Grouping |
Completed
(%) |
0.01-25 |
|
N/A |
|
| 3 |
Milestone
AS Per Task Grouping |
Completed
(%) |
25.01-50 |
|
N/A |
|
| 4 |
Milestone
AS Per Task Grouping |
Completed
(%) |
50.01-75 |
|
N/A |
|
| 5 |
Milestone
AS Per Task Grouping |
Completed
(%) |
75.01-100 |
|
N/A |
|
| 6 |
Work
Break Down With Task Grouping |
Completed
(%) |
0%-0% |
|
N/A |
|
| 7 |
Work
Break Down With Task Grouping |
Completed
(%) |
0.01%-25% |
|
N/A |
|
| 8 |
Work
Break Down With Task Grouping |
Completed
(%) |
25.01%-50% |
|
N/A |
|
| 9 |
Work
Break Down With Task Grouping |
Completed
(%) |
50.01%-75% |
|
N/A |
|
| 10 |
Work
Break Down With Task Grouping |
Completed
(%) |
75.01%-100% |
|
N/A |
|
|
|
|
|
|
|
|
|
|
|
|
|