Testing bugs for 1597

[Sanam-07]

• Issue 1 : Check the completeness of the activity while importing from the XML File.

Pre-condition :

1. The user should be logged-In.
2. The XML should contain all the activity element filled.
3. The XML file should not contain already existing activity.

Steps to reproduce :

1. Click on the add activity button.
2. Click on the Import Activities by XML/CSV.
3. Upload the XML File and import activity.

Expected Result : The activity should be successfully imported and all the element in the activity should be filled.
Actual Result : The activity is successfully imported but the sector and transaction element is marked as incomplete.

• Issue 2 : Check the completeness of the activity while importing from the CSV File.

Pre-condition :

1. The user should be logged-In.
2. The CSV should contain all the activity element filled.
3. The CSV file should not contain already existing activity.

Steps to reproduce :

1. Click on the add activity button.
2. Click on the Import Activities by XML/CSV.
3. Upload the CSV File and import activity.

Expected Result : The activity should be successfully imported and all the element in the activity should be filled.
Actual Result : The activity is successfully imported but the result and transaction element is marked as incomplete.

• Issue 3: The contact-info element must be type + any attribute but while import from the XML file then uploading only the type shows the contact-info as complete.
  

• Issue 4 : In the location element the reference field is not marked as the required field.
  

• Issue 5 : The latitude and the longitude in the location element does not got filled out while importing from the XML File.
  
  

• Issue 6 : When the default aid type with only code field is imported from the XML then the code value is not imported on the activity.
  

• Issue 7 : The error message displayed 2 times when the user does not provide any value in budget element importing from the XML File. ??? 2 budget items provided. Working as intended.
  For Reference :
  
  

• Issue 8 : When the user does not provide the value then the 1st and 2nd error message does not make any sense. Is from validator. Makes sense. Value cannot be empty string. needs to be numeric.
  
  

• Issue 9: When the user filled all the required fields on the XML File for transaction element and import it then the transaction element is marked as incomplete.
  
  

• Issue 10 : Import error while importing the XML file.
  Steps to reproduce.

• Import the XML file where the required field of the transaction are filled.

• Delete the imported activity.

• Remove some required field from the XML and reimport.

• Again try to import the same XML File.

• Add the required field that you have removed and reimport.

Expected Behavior : The XML File should be successfully imported.
Actual Behavior : The error message gets displayed indicating that the XML cannot be imported and if again we try to import then the import in progress is displayed,

• Issue 11 : When the user filled the description from the transaction element then the description is not displayed as required field. Incorrect issue. Transaction description and activity description are not linked.
  

• Issue 12: Need to add the percentage field in the sector section of the transaction element to make the flow similar with the sector element. Incorrect issue. Transaction sector doesnt have percentage in IATI standard.
  
  

• Issue 13: When the user fill the recipient region code field from the transaction element then it is not marked as complete.
  

• Issue 14 : Need to add the percentage in the recipient region field inside the transaction element to make the form consistent and remove the vocabulary as required element to complete the recipient region inside the transaction element. Incorrect issue. Transaction RR RC doesnt have percentage in IATI standard.

• Issue 15 : If the user filled the tied status from the transaction element then the default-tied status should be marked as the completed in the activity detail page.(same for aid type, finance type, flow type ) Incorrect issue. Transaction default-tied-status and activity default-tied-status are not linked.
  

• Issue 16 : The Category Code field of document link gets automatically filled while importing from the XML file.
  

• Issue 17 : When the user only filled the code field in policy marker element and download the XML then the XML file should contain the policy marker element but it doesn't.
  
  

• Issue 18: The country budget item gets imported from the XML file when the percentage is below 100 and marked as completed. I think it should not marked as completed as percentage is not 100 percentage.
  

[PG-Momik]

Take zendesk issue and #1634 into consideration for this issue.

[Sanam-07]

For CSV

• Issue 1 : When the user imported the CSV with all the required filled in tag then the tag element should marked as complete but it is marked as incomplete.
  

• Issue 2 : When a user Download the CSV file filling the required field of policy marker in the form then the CSV should contain the filled data of policy marker but it doesn't.
  
  

• Issue 3 : When a user downloads the CSV file after filling in the "Description" field in the form, the CSV should include the entered "Description" data. However, it currently does not.
  

• Issue 4: When a user downloads the CSV file after filling in the "transaction" field in the form, the CSV should include the entered "transaction" data. However, it currently does not.
  

• Issue 5 : When the user fills in only the "Name" field in the Participation Org element, it does not appear in the CSV file.
  
  

• ~~Issue 6: Assigning 100% to RC even tho RC country_code is not specified should result in RR being complete since RR can no longer be allocated any % .
  
  

• Issue 8 : The description should marked as completed when the description is provided from the transaction. Incorrect issue. Transaction description is not linked to activity description.
  

• Issue 9 : When the user delete the recipient region or recipient country then sector added from the transaction also marked as incomplete.
  Untitled_ Dec 26,2024 10_25 AM.webm

• Issue 10: There is no any column for transaction flow type, finance type, Aid Type, Tied Status , due to which these field are not filled while importing activity from the CSV. Incorrect issue. Intended template.
  

• Issue 11 : An error message occurs when the user provide only the policy marker code and imported it from the CSV. Incorrect issue. Working as intended. Policy marker code is invalid since vocab is not specified.
  

• Issue 12 : Need to make the date format consistent in the CSV and activity element. Incorrect issue. Date format working fine. Date formats in csv files are determined by spreadsheet application. If data is viewed in text editor, date format is fine.
  
  

• Issue 13 : As per my knowledge contact-info should be marked as completed when the user provide type attribute + any attribute but it is getting marked as completed when the user only provide type attribute.
  

[Sanam-07]

For XLS :

• Issue 1: The element Recipient Region and Recipient Country should be marked as completed in activity detail page when the user has filled either of these elements and imported the XLS file.
  

• Issue 2 : The collaboration Type data is not uploaded while importing from the XLS file.
  
  

• Issue 3 : Although the result data, collaboration type element is not completed but the activity marked as 100 percentage while imported from the XLS File. Incorrect issue. Collaboration type and result are not core elements. Only core elements contribute to percentage. Yellow icon = core element.
  
  

• Issue 5: The recipient country and recipient region should be marked as completed when the user have filled all the required fields of any one element .
  

• Issue 7: When the user provide following inputs shown in image then the recipient country is marked as completed which should not be. (Same for recipient region) Incorrect issue. Working as intended. RR and RC completion depend on percentage. since RR is given 100% (50 + 50) but one of the RR doesnt contain code, which makes rr complete but not RC.
  
  

• Issue 8: The user is not able to import the multiple recipient region and recipient country form from the XLS file. Refer image for it.
  

• Issue 10 : An warning message occurs when the user import the XLS file which contain multiple Budget element without type fields. It should not give warning message when the user provide empty type field. Incorrect issue. Intended behaviour.
  
  

• Issue 11: The value of the legacy data should be integer rather than string. Incorrect issue. Value is a string field according to IATI standard.
  

• Issue 12: The user is not able to import the additional sector fields from the XLS File.
  

• Issue 13: The user is not able to import the addition policy marker element filling the required fields.
  
  

• Issue 16: The Green line appears while uploading the XLS File.
  

• Issue 17 : The RC,RR and sector should be marked as complete when the user imported the details from the transaction.
  

• Issue 18: The error message automatically disappear after some time when the user imported indicator only from the XLS File. Incorrect issue. Intended behaviour of toast message.