Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] case.for_customer Not Populating in Templates #680

Open
WellKnitTech opened this issue Jan 8, 2025 · 0 comments
Open

[BUG] case.for_customer Not Populating in Templates #680

WellKnitTech opened this issue Jan 8, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@WellKnitTech
Copy link

Describe the bug
The variable case.for_customer is not available in the case dictionary during template rendering, resulting in a failure to display the expected customer name in generated reports. Although case.client.customer_name contains the relevant data, case.for_customer is undefined, causing Jinja templates that rely on it to fail or display no output. This means that the documentation in https://docs.dfir-iris.org/operations/reports/ is inaccurate at least on this count.


To Reproduce
Steps to reproduce the behavior:

  1. Create a new report template that includes the {{ case.for_customer }} variable.
  2. Populate the case with valid client information.
  3. Generate a report using the template.
  4. Observe that the case.for_customer variable does not render any output.

Expected behavior
The case.for_customer variable should be populated with the customer_name field from case.client and display the appropriate customer name in the report template.


Screenshots
N/A (This issue is directly related to rendered template output and debugging logs).


Additional context

  • Debugging logs confirm that case.client.customer_name is populated as part of the case dictionary, but case.for_customer is missing.
  • Documentation indicates case.for_customer should exist as a standard tag for templates.
  • A workaround is to access case.client.customer_name directly in the template or modify the Python logic to populate case.for_customer.
@WellKnitTech WellKnitTech added the bug Something isn't working label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant