Closed AndreiIf closed 1 year ago
Hi @AndreiIf ,
Thank you very much for opening your first issue here! Contributions are always welcome.
Since you're reporting a bug, please add some steps to reproduce the issue. Add also some information about your environment. You will get that info by navigating into your Redmine root directory and typing:
bin/rails about
This would help us to investigate your issue.
Best Regards, Liane
Hello @liaham, So , to reproduce the steps: Installed the plugin accordingly , after that I added 1 entry for holidays. As long as the user or group that I want to see the workload for has no active issues between the interval selected, it return no activity. After I add some Issues for the same user it return error 500 with the error mentioned above in production.log Here are some information about the enviroment:
Ruby version 2.7.4-p191 (2021-07-07) [x86_64-linux]
Rails version 5.2.8
Environment production
Database adapter PostgreSQL
List of installed plugins:
additionals
author
default_roles
periodictask
progressive_projects_list
redmine_agile
redmine_announcements
redmine_base_deface
redmine_base_select2
redmine_better_overview
redmine_checklists
redmine_contacts
redmine_contacts_helpdesk
redmine_dmsf
redmine_documents_short
redmine_drive
redmine_excel_connector
redmine_favorite_projects
redmine_issue_dynamic_edit
redmine_issue_evm
redmine_issue_templates
redmine_lightbox2
redmine_more_context
redmine_my_page_paginations
redmine_people
redmine_questions
redmine_reporter
redmine_resources
redmine_tint_issues
redmineup_tags
redmine_view_issue_description
redmine_wiki_issue_fields
redmine_workload
redmine_x_assets
redmine_x_gantt
redmine_xlsx_format_issue_exporter
sidebar_hide
status_button
that_meeting
Thank you!
Hi @AndreiIf ,
Thank your very much for your quick response!
We will try to reproduce the error. Please be patient, since this may take a while.
Have a nice weekend!
Best Regards, Liane
Hello @AndreiIf, I updated your comments for better readability. 😃 Best regards, Markus
Solution will not be realized by @liaham or @mboremski since we normally do not use postgre. We need support from community here.
Same as #16!