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 - Ticket misconfiguration after adding AccountedTime #640

Open
lis975 opened this issue Feb 12, 2025 · 4 comments
Open

Bug - Ticket misconfiguration after adding AccountedTime #640

lis975 opened this issue Feb 12, 2025 · 4 comments
Labels
4 - verified This issue or pull request was verified.

Comments

@lis975
Copy link
Contributor

lis975 commented Feb 12, 2025

Environment

  • Server OS: Linux Rocky 8.4
  • Browser: Safari, Chrome
  • Znuny version: 7.1.3

Expected behavior

Added time units to ticket appear in ticket article. The other metadata stays intact.

Actual behavior

After adding Accounted time to ticket article some ticket data are distorted, and appear in Article details section instead of Ticket information window.

How to reproduce

Steps to reproduce the behavior:

  1. Go to ticket '...'
  2. Click on Communication->Note '...'
  3. Scroll down to Time unit '...'
  4. Insert some time units (as text or from the list)
  5. Save note.
  6. Ticket information widget no longer contains: Owner, Responsible, ClientID, accounted Time summary. These data are now visible in article details.

Additional information

As long as accounted time is inserted to ticket there is no way to restore proper metadata view. When you remove accounted time units right from the database, ticket is zoomed as usual... until next time accouting insertion.
The only extensions in system I have are from Znuny:
CloneDB
FAQ
GeneralCatalog
ImportExport
ITSMChangeManagement
ITSMConfigurationManagement
ITSMCore
ITSMIncidentProblemManagement
ITSMServiceLevelManagement
Survey
Znuny-AutoSelect
Znuny-DashboardWidgetSearchProfile
Znuny-DownloadAllAttachments
Znuny-EscalationSuspend
Znuny-ExtraSkins
Znuny-PrimarySecondary
Znuny-QuickClose
Znuny-ShowTicketUnlockTime

Screenshots

Image Image Image Image
@lis975
Copy link
Contributor Author

lis975 commented Feb 13, 2025

deinstaling [ITSMIncidentProblemManagement] 7.1.1 fixes the problem.

@rkaldung
Copy link
Member

rkaldung commented Feb 13, 2025

@lis975 I installed all add-ons (using Znuny 7.1.5 and not 7.1.3) and enabled dark skin but can't reproduce this. Are there any other changes regarding CSS?

@rkaldung rkaldung added the 4 - clarification The issue or pull requests needs more information. label Feb 13, 2025
@lis975
Copy link
Contributor Author

lis975 commented Feb 13, 2025

No, no changes at all, no changes done "by hand". The system was upgraded from version 6.5.x and has a lot of custom configuration settings due to it long life.
On my side, I have upgraded test system to version 7.1.5 and problem exists,

I have done some experiments,

  • just "hacked" 7.0.1 package of ITSMIncidentProblemManagement (just by adding 7.1.x to package head) and previous package version generates the same problem.
  • rpm -Uvh --force znuny-7.1.5-01.noarch.rpm to overwrite all files, then MIgrate-To_Znunt7.1 script, didn't solve the problem
  • instaled ITSMIncidentProblemManagement and set all its settings to default values

@rkaldung rkaldung added 3 - wait for contributor Contributor, it's your turn. and removed 3 - wait for contributor Contributor, it's your turn. labels Feb 13, 2025
@rkaldung
Copy link
Member

@lis975 Please drop me a line via community@znuny.org, and I will create an account for you at the vanilla system for you to verify. Please reference this issue here in the email.

@rkaldung rkaldung added 4 - verified This issue or pull request was verified. and removed 4 - clarification The issue or pull requests needs more information. labels Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - verified This issue or pull request was verified.
Development

No branches or pull requests

2 participants