S No# Module Task Type Priority

1 KM Bug
2 KM Bug
3 KM Bug
4 KM Bug
5 KM Bug
6 KM Bug
7 KM Bug
8 KM Bug
9 KM Bug
10 KM Bug
11 KM Bug
12 KM Bug
13 KM Bug
14 KM Bug
15 KM Bug
16 KM Bug
17 KM Bug
18 KM Bug
19 KM Bug
20 KM Bug
21 KM Bug
22 KM Bug
23 KM Bug
24 KM Bug
25 KM Bug
26 KM Bug
27 KM Bug
28 KM Bug
29 KM Bug
30 KM Bug
31 KM Bug
32 KM Bug
33 KM Bug
34 KM Bug
35 KM Bug
36 KM Bug
37 KM Bug
38 KM Bug
39 KM Bug
40 KM Bug
41 KM Bug
42 KM Bug
43 KM Bug
44 KM Bug
45 KM Bug
46 KM Bug
47 KM Bug
48 KM Bug
49 KM Bug
50 KM Bug
51 KM Bug
52 KM Bug
53 KM Bug
54 KM Bug
55 KM Bug
56 KM Bug
57 KM Bug
58 KM Bug
59 KM Bug
60 KM Bug
61 KM Bug
62 KM Bug
63 KM Bug
64 KM Bug
65 KM Bug
66 KM Bug
67 KM Bug
68 KM Bug
69 KM Bug
70 KM Bug
71 KM Bug
72 KM Bug
73 KM Bug
74 KM Bug
75 KM Bug
78 KM Bug
79 KM Bug
80 KM Bug
Point of Discussion / Action Item Owner (s)
On linking knowledge articke as mark as solution from incident management console, the
article is not related to the incident.
Divya
article type: general : subject and details field editable after the article is published: make
it read only
Divya
view count is automatically set to 2 when knowledge article Is cancelled at draft
status(KBA3877)
Divya
when published article is copied through copy button, valid till date is not right for the
child article(KBA 3876, KBA 3880)
Divya
knowledge feedback related list should only be visible in published status Divya
optional fields has to be read only after published status Divya
On clicking on the new knowledge feedback button in Knowledge feedback related list , a
new feedback page opens up. On saving the required fields , submit for approval button
should be removed.Introduce Back to article button .
Divya
remove clone, edit, submit for approval buttons from ew feedback page and introduce
back to article button.
Divya
Hide Is Client feedback and User field from knowledge feedback page Divya
when knowledge article is marked as solution it is not copying the resolution notes (refer
incident : INC00015737)
Divya
resolution through knowledge article checkbox should be locked and get auto populated
only.
Divya
rename 'create knowledge article button to propose knowledge article Divya
Knowlede ID should get populated in work info notes when the user marks as solution for
the knowledge article.
Divya
hide submit for approval button from approval history section Divya
remove edit button in knowledge feedback related list entries Divya
Available for group : added a group but still article was visible to all. In published status Divya
when bulider refer backs the article , it goes to draft status, and if he submit for build , it
still stays in draft but the page gets refreshed, instead the builder should get an error
message on button click .
Divya
When article is closed rejected(rejected at build status), after being closed, the form
should be locked for any modifications. But affected CI/service, and other Article details
section fields are editable.
Divya
when article is published, only published date is populated, and then the page has to be
refreshed again to get the Valid till field populated. Valid till and Published date should
get populated together
Divya
Inlcude notification logs related list Divya
After creating a knowledge article in draft status , the creator is not able to submit the
article for build, so knowledge cycle cannot be run
Divya
change the error message if the approver does not fill the refer back comments ' Refer
back reason is mandatory to fill'
Divya
Propose a knowledge article checkbox from change form is not working Divya
remove private checkbox from new note option.
Remove edit delete links beside the notes and attachment related list entries.
Divya
on clicking the knowledge search button when incident is in resolved status, a window
pops up, the search box displays KBA and Incidents , incident searched have their ticket
number missing,and in knowledge articles, change z_article type to article type and
category~ to category
Divya
move approval history related list to be the first related list Divya
remove new knowledge action history button from the related list knowledge action
history
Divya
new notes and attachments should not be added after an article is closed Divya
when 'copy and replace' button is clicked, some pop up with the new KBA number should
be visible or related in related list as user couldnt find out which article he created
Divya
email notification : When the Knowledge article is submit for Approval phase:after dear
builder's name should be there and not user.
Divya
email notification : When the Knowledge article is rejected by the approver in Build phase
: reason of rejection in body is blank as reason for rejection is not mandatory in tool.
Divya
email notification : When the Knowledge article is referred back to the contributor from
Build phase: after dear contibutor comma should be there , reason for refrring back is not
populated and is blank
Divya
notifications are not getting updated in notification logs Divya
email notification : When the Knowledge article is published: dear contributor name
should be there
Divya
Email notification : When the Knowledge article is pending for Builders approval in build
phase for more than 10 calendar days : triggered twice, comma after dear application
support group.
Divya
Email notification : When the article comes in Closed-Auto Reject due to no approvals
for more than 30 calendar days : triggered twice
Divya
When the Knowledge article is pending for Builders approval in build phase for more
than 15 calendar days: not triggered
Divya
Email notification :When the Knowledge article is pending for Builders approval in build
phase for more than 25 calendar days: not triggered
Divya
Email notification :When the Knowledge article is pending for Builders approval in build
phase for more than 29 calendar days: not triggered
Divya
Email notification: 30 calendar days before the Validity of a Knowledge article expires:
triggered twice
Divya
Email notification : 15 days before the Validity of Knowledge article expires: in body of
email make it 15 days and this mail is triggered twice
Divya
Email notification : 7 days before the Validity of a Knowledge ticket expires: in body make
it 7 days. Mail triggered twice
Divya
Email notification : When any article is rated as 'Needs Update': not going to builder and
not going to few members of knowledgement group
Divya
Email notification : 1 days before the Validity of a Knowledge ticket expires: triggered
twice.
Divya
Email notification :When the article comes in Retired Validity Expired: did not trigger Divya
create new custom field for rich text fields and map the fields accordingly for self service
view.
Divya
when a new knowledge article is created and saved ,its in draft status, valid till is an
editable field and contributor is able to fill in the vatil till date
Divya
In symptoms text helptext, created word at the end is missing. Divya
Move knowledge action history above the knowledge article history related list Divya
Articles to be Retired report not present Divya
blank search in knowledge search in incident module Divya
when article is searched during knowldedge saerch and opened, fields which are visible at
top has just labels and no values
Divya
Views In Knowledge Articles tab: Divya
when clicking on new button , the article page selection which comes up, default article
should be General
Divya
when clicking on 'Serach for Duplicate button' , a page pops up 'Page search for duplicate
does not exist.'
Divya
Remove KA available for groups related list Divya
KBA 388, after the kBA was published , only publish notification triggered, and KBA needs
update mail also triggered.
Divya
On clicking on 'Download' button error comes up as 'Unable to retrieve object'. Divya
when clicking on 'Copy and Replace ' button, new knowledge article should be of same
article type , in tool it is created 'Error' article type for all copy and replace.
Divya
when KBA is proposed through incident , summary of incident didnt populate In subject
of KBA. Incident 5196
Divya
when KBA is proposed through incident, KBA is related in Linked Knowledge Articles
related list, shift Article # column to left and include Article type and created date in
columns of related list.
Divya
refer back functionality is not working Divya
Available for group : added a group but still article was visible to all. In published status Divya
Valid Till' date is not exact 15 months to the Published date Divya
when an article is closed cancelled at Draft status, notes and attachments section should
be non editable
Divya
Valid till' date should not be editable by the contributor at Draft status. It should get auto
populated at Published status only . And after that can be edited by builder and
knowledge manager
Divya
Assigned to should be filled by Knowledge manager only ie members of knowledgement
group only
Divya
closed articles should not be searchable through global search Divya
view count should increase only for published articles Divya
attachment is mandatory for article type 'Patch Review' to be submitted for build Divya
when an article is marked as solution, and ticket is resolved , resolution code entry is
done twice in action history
Divya
in action history , Knowledge Article History Name can be configured as in incident
history rather than a random number
Divya
when a KBA is referred back , then buttons are not visible at Draft status Divya
When the Knowledge article is submit for Approval phase- please put a comma after Dear
Approver.
Divya
On creating Known error KBA, after it gets published, subject field becomes blank, Divya
notifications are not getting triggered Divya
buttons in related list Divya
when clicking on download button of a published article, if rich text is there in fields , it
gives complete coding in the document which is popped up on download button. Refer
KBA498
Divya
Reported Dated Status ETA
15-Apr-14
Closed - Passed
16-Apr-14
Closed - Passed
16-Apr-14
Closed - Passed
16-Apr-14
Closed - Passed
16-Apr-14 Closed - Passed
16-Apr-14 Closed - Passed
16-Apr-14
Closed - Passed
16-Apr-14
Closed - Passed
16-Apr-14
Closed - Passed
16-Apr-14
Closed - Passed
17-Apr-14
Closed - Passed
17-Apr-14
Closed - Passed
17-Apr-14
Closed - Passed
17-Apr-14
Closed - Passed
17-Apr-14 Closed - Passed
18-Apr-14
Closed - Passed
18-Apr-14
Closed - Passed
21-Apr-14
Closed - Passed
21-Apr-14
Closed - Passed
21-Apr-14 Closed - Passed
21-Apr-14
Closed - Passed
21-Apr-14
Closed - Passed
21-Apr-14 Pending
21-Apr-14
Closed - Passed
21-Apr-14
Closed - Passed
22-Apr-14 Closed - Passed
22-Apr-14 Closed - Passed
22-Apr-14 Closed - Passed
22-Apr-14 Closed - Passed
22-Apr-14 Closed - Passed
22-Apr-14 Pending
22-Apr-14 Closed - Passed
22-Apr-14 Closed - Passed
22-Apr-14 Closed - Passed
23-Apr-14
Closed - Passed
KBA4053
23-Apr-14
Closed - Passed
23-Apr-14
Closed - Passed
KBA4053
23-Apr-14
Closed - Passed
KBA4053
23-Apr-14
Closed - Passed
KBA4053
23-Apr-14
Closed - Passed
KBA4052
23-Apr-14
Closed - Passed
KBA4052
23-Apr-14
Closed - Passed
KBA4052
23-Apr-14
Pending
23-Apr-14
Closed - Passed
KBA4052
to be
checked
24-Apr-14
Closed - Passed
24-Apr-14
Closed - Passed
24-Apr-14
Closed - Passed
24-Apr-14 Closed - Passed
24-Apr-14
Closed - Passed
24-Apr-14 Closed - Passed
24-Apr-14
Closed - Passed
24-Apr-14
Closed - Passed
6-May-14 Closed - Passed
6-May-14
Closed - Passed
6-May-14
Closed - Passed
6-May-14 Closed - Passed
6-May-14
Closed - Passed
6-May-14 Closed - Passed
6-May-14
Closed - Passed
7-May-14
Open
7-May-14
Open
7-May-14
Closed - Passed
7-May-14
Closed - Passed
7-May-14
Closed - Passed
7-May-14
Closed - Passed
7-May-14
Closed - Passed
7-May-14
Closed - Passed
7-May-14 Closed - Passed
7-May-14
Closed - Passed
7-May-14
Closed - Passed
8-May-14
Closed - Passed
8-May-14
Open
8-May-14 Closed - Passed
12-May-14 Open
12-May-14 Open
13-May-14 Open
13-May-14 Open
13-May-14 Open
Comments
working fine now
Same as point 6.All the optional fields are read-only in Published layout
working fine now
working fine now
working fine now
working fine now
working fine now
working fine now
is client feedback field is removed from Knowledge Feedback form,not
from related list.
working fine now
working fine now
working fine now
working fine now
working fine now
working fine now
working fine .
Working fine already .
working fine
working fine now
Notification logs configured.Use the link to test
resolved
Done.Error message is changed.
Working fine already.
Private checkbox cant be removed(platform limitation).Edit and Delete
links work according to the permission of Knowledge Article.Notes and
Attachment cannot be added whn the status is 'Closed - Cancelled' or
'Closed - Auto Rejected' or 'Closed - Rejected' or 'Retired - Validity
Expired'
Fixed.
Done.
Done.
Done.User gets an error message while attaching .
A popup page for newly created article is not mentioned in FRS .
Name changed to Approver instead of User
Platform limitation.We can only give a note to fill rejection
comments.Same as other modules
Done.Comma is added and refer back reason is not blank
Notification logs configured.Use the link to test
Done
Comma has been added .Triggered only once.Please refer KBA4035
Triggered only once .Refer KBA4035
Triggered.Refer KBA4035
Triggered but body of email content was not correct, 15 days was
written there instead of 25 days.Please update the FRS also
Triggered.Refer KBA4035
Triggered only once .Refer KBA4036
Content is changed. Triggered only once.
Content is changed. Triggered only once.
Done .KBA 388, after the kBA was published , only publish notification
triggered, and KBA needs update mail also triggered.
Triggered only once.
Fixed.
Content of rich text fields are converted to plain text .
Fixed.Only Knowledge Management Group member can fill valid till
date
Added created word
Done
Configured.
Already working fine
Already working fine
Done .
Done .Default KA is set as General .
Fixed
Done .This related list was added in the layout at that time for testing .
Working fine already.Feedback is also given for this KA
Working fine already
Working fine already
Replicated to QA
Replicated to QA
Fixed already on QA
Its working fine.Please recheck
Valid till date is set as 450 days from published days(approx 15months)
Fixed on QA
As per Sachin this doesnot need to be done.So undone on master
As per Sachin this doesnot need to be done.So undone on master
Not possible.
Fixed.View count for process and policy only on closed-rejected statis
as ViewCount page was added in the layout
Done on QA
Fixed
Please move it to QA
Done on master.Please check
fixed on QA
Draft
Open
Pending
ORT
Reject
Closed - Passed
Closed - Working as Desired
Closed - Duplicate
Bug/Issue is in discussion phase & FRS need to be shared with Dev Team
Bug/Issue opened and/or actioned by dev team.
Bug/Issue being worked by respective team
testing by FC team
Not required
Testing done by QA and passed.
issue closed by development for points which are incorrectly classified as bugs. If it is a potential enhancement
candidate, then it is reclassified and put to open status.
Issue closed because a duplicate task already exists
1 When the Knowledge article is submit for
Approval phase
Builder
2 When the Knowledge article is rejected by the
approver in Build phase
Contributor
3 When the Knowledge article is referred back to
the contributor from Build phase
Contributor
4 When the Knowledge article comes to Editorial
Review stage
Knowledge
Management Group
5 When the Knowledge article is published Contributor Builder
6 30 calendar days before the Validity of a
Knowledge article expires
KM
KBA4003
Builder
7 15 days before the Validity of Knowledge article
expires
KM
KBA4003
Builder
8 7 days before the Validity of a Knowledge ticket
expires
KM
KBA4003
Builder
9 1 days before the Validity of a Knowledge ticket
expires
KM
KBA4003
Builder
10 When the article comes in Closed-Auto Reject
due to no approvals for more than 30 calendar
days
Contributor
KBA3999
Builder
11 When the Knowledge article is pending for
Builders approval in build phase for more than
10 calendar days
Builder
KBA3999
S No Email Notification Notification To Notification cc
12 When the Knowledge article is pending for
Builders approval in build phase for more than
15 calendar days
Builder
KBA3999
13 When the Knowledge article is pending for
Builders approval in build phase for more than
25 calendar days
Builder
14 When the Knowledge article is pending for
Builders approval in build phase for more than
29 calendar days
Builder
KBA3999
15 When the article comes in Retired Validity
Expired
Knowledge
Management Group,
Builder
KBA4003
16 When any article is rated as 'Needs Update' Builder Knowledge
Management Group
Reminder mail
frequency/
Time Frame
As soon as the contributor clicks on
'Submit for Approval' button
Template 1
As soon as the Builder clicks on the
'Reject' button, and the status of the
article during this time is 'Build'
Template 2
As soon as the Builder clicks on
'Submit' button on Reason for
Referring back page after
mentioning the Reason for
Referring back the article
Template 3
As soon as the Builder clicks on
approve button in 'Build' status of
Article
Template 4
As soon as the Knowledge Manager
clicks on 'Publish' button
Template 5
30 Calendar Days When the difference between the
Current date and the Valid Till date
is 30 days and the article status is
'Published'
Template 6
15 Calendar Days When the difference between the
Current date and the Valid Till date
is 15 days and the article status is
'Published'
Template 7
7 Calendar Days When the difference between the
Current date and the Valid Till date
is 7 days and the article status is
'Published'
Template 8
1 Calendar Day When the difference between the
Current date and the Valid Till date
is 1 day and the article status is
'Published'
Template 9
30 Calendar Days When the difference between the
Current date and the date when the
article was submitted for 'Build'
phase is 30 days, the article status
at this time would be 'Build'
Template 10
10 Calendar Days When the difference between the
Current date and the date when the
article was submitted for 'Build'
phase is 10 days, the article status
at this time would be 'Build'
Template 11
Comments When to trigger Template no
15 Calendar Days When the difference between the
Current date and the date when the
article was submitted for 'Build'
phase is 15 days, the article status
at this time would be 'Build'
Template 12
25 Calendar Days When the difference between the
Current date and the date when the
article was submitted for 'Build'
phase is 25 days, the article status
at this time would be 'Build'
Template 13
29 Calendar Days When the difference between the
Current date and the date when the
article was submitted for 'Build'
phase is 29 days, the article status
at this time would be 'Build'
Template 14
When the Status/Sub Status of an
article changes to Retired- Validity
Expired
Template 15
As soon as the User clicks on
Submit button on Knowledge
Feedback form after choosing the
'Needs Update' rating
Template 16
triggered
not triggered
triggered but should
be in cc(tool
limitation)
1. When the Knowledge article is pending for Builders approval in build phase for more than 10 calendar days : 1 hour after pending for approval
2. When the Knowledge article is pending for Builders approval in build phase for more than 15 calendar days : 2 hours after pending for approval
3. When the Knowledge article is pending for Builders approval in build phase for more than 25 calendar days : 3 hours after pending for approval
4. When the Knowledge article is pending for Builders approval in build phase for more than 29 calendar days : 4 days after pending for approval
5. 30 calendar days before the Validity of a Knowledge article expires : 4 hours before valid till date
6. 15 days before the Validity of Knowledge Article expires : 3 hours before valid till date
7. 7 days before the Validity of a Knowledge Article expires : 2 hours before valid till date
8. 1 Day before the Validity of a Knowledge Article expires : 1 hour after valid till date
1. When the Knowledge article is pending for Builders approval in build phase for more than 10 calendar days : 1 hour after pending for approval
2. When the Knowledge article is pending for Builders approval in build phase for more than 15 calendar days : 2 hours after pending for approval
3. When the Knowledge article is pending for Builders approval in build phase for more than 25 calendar days : 3 hours after pending for approval
4. When the Knowledge article is pending for Builders approval in build phase for more than 29 calendar days : 4 days after pending for approval