Company: Link Technologies
Case No: L08676. Project: 08.20: LinkSOFT Version 8.2
Logged By: Rashna (Edge Business Solutions) on 14 Jul 2017 08:39AM
Priority: High
Product: Payroll & HR
Group: Software Defect
Time Taken: 3.50 (Weight: 3.50)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna
Resolve By: Saturday, 15 July 2017 12:00 AM [2479 days since logged date]
Status: Closed
Subject: Unable to generate Leave Transaction Report
Summary:    

Hi Sanjay, 

The setup for the case is in QA4.

Generating the Leave Transaction Report for Company 1001 in a customer database, with dates 01/06/2017 to 30/06/2017, Employee Status as Active and Leave Status as Taken, the system displays the report with the below result.

The client is on version 8.13.


Audit Notes:
14 Jul 201708:40AM Comment 1 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 14-07-2017 08:40 AM Time Taken: 1.00

Hi Alvis, 

Can you please attend to this case, we need a urgent fix.

Thanks


14 Jul 201711:36AM Comment 2 by Alvis (Link Technologies) Case 8676 added to project 8.14
14 Jul 201711:41AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-07-2017 11:41 AM Time Taken: 1.00
Development work for this case has been completed.
The change will be available in version: 8.14
Documentation update required(Yes/No. Add change details below)
QA required(Yes/No.Include areas that require testing): Yes

The following changes were made(Include Database object names, Program classes and any other relevant information):|

  1. Resolved issue with leave report. This was caused by large description entered in branch maintenance.

14 Jul 201703:01PM Comment 4 by Aarti Pooja Gayaneshwar (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 14-07-2017 03:01 PM Time Taken: 1.50
QA for product and Patch Releases

Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test
Step 2 - Product expert allocated by Consulting Manager for Product QA.
               Consulting Manager to allocate resource
               Consulting Manager to sign off on UAT and Generic Test

Step 3 - Sanjay to release patch only after steps 1 and 2 are completed successfully.

STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below.

Table 1 - Summarised list of issues

NoIssue Description Resolved? 
1 Unfiltered by DatesLeave Transaction report is generating
2 Filtered by DatesLeave Transaction report is generating 
3 Filtered by Employee StatusLeave Transaction report is generating 
4Unfiltered by Employee StatusLeave Transaction report is generating 
5Filtered by Leave StatusLeave Transaction report is generating
6Unfiltered by Leave StatusLeave Transaction report is generating 
7  
8  
9  
10  
11  
12  

WORKFLOW:

  1. Original case assigned to Development
  2. When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
  3. If system test passes, assign case to Consulting Manager for UAT
  4. If UAT Passes, Assign case to MD to release patch

    If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L08676 in the subject line of all emails regarding this issue.

    Document size: 11.1 KB
    For call complaints, please contact the Managing Director of the company using this form