Filters are not saved in generated report in Issues

Hello there,

I tried it several times and realized, that I can’t save the filters of reports I have generated with the generator in the Issues app.

Any ideas?

Thank you very much.

Hi,

Can you help us with the steps you taken? So we can replicate the issue.

Regards,
Prakash

Of course.

  1. I call the Issues app. https://erp.local/desk#List/Issue

  2. On the left side I click “Reports” and choose “Report Builder”

  3. By default, only the filter “Status = “Open”” is set. I set my filters like I want them. For example I set “Subject” “Not Like” “%Error%”


  4. I choose “Menu” > “Save” and enter the report name “MyReport”. Immediately my filters jump back to this:

Even refreshing or calling the report manually to check if my filters are saved, show only the default filter. So I think, the filters are not saved at all.

you can check this :

Thank you Mohammed, but unfortunately this would change the default behaviour of the Issues doctype, which is not wanted.

We want simply the Report Builder to work as it is meant to be. I think it’s a bug.

Seems to work now. Has anything been changed?

It works since I created Custom Reports for my projects. Now all my issues reports work as well.

After it worked for a while, since the update I pulled today in developer branch, it again stopped to work.

Heres the json of the custom report:

{
  "add_total_row": 0,
  "sort_by": "Issue.subject",
  "add_totals_row": 0,
  "sort_order": "asc",
  "sort_by_next": null,
  "filters": [
    [
      "Issue",
      "subject",
      "not like",
      "%identisch%"
    ],
    [
      "Issue",
      "raised_by",
      "like",
      "%ebay%"
    ],
    [
      "Issue",
      "subject",
      "not like",
      "%massnahmen%"
    ],
    [
      "Issue",
      "subject",
      "not like",
      "%nicht verkauft%"
    ]
  ],
  "sort_order_next": "desc",
  "columns": [
    [
      "name",
      "Issue"
    ],
    [
      "subject",
      "Issue"
    ],
    [
      "status",
      "Issue"
    ],
    [
      "raised_by",
      "Issue"
    ],
    [
      "customer",
      "Issue"
    ],
    [
      "customer_name",
      "Issue"
    ]
  ]
}

It’s weird that the problem only occurs in the Issues-App. I use custom reports for projects as well and it’s working fine.

Again, it stopped to work. Every few updates something breaks the custom reports in the Support / Issues App.

Works again by doing bench update.

Maybe there is a way not always have this problem return every once in a while.