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.

Sign up for GitHub

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

Jump to bottom

We have changed the default ticket unlock behaviour in OTOBO 10.1. #1372

Closed
StefanRother-OTOBO opened this issue Oct 30, 2021 · 3 comments
Closed

We have changed the default ticket unlock behaviour in OTOBO 10.1. #1372

StefanRother-OTOBO opened this issue Oct 30, 2021 · 3 comments
Assignees
@StefanRother-OTOBO
Labels
enhancement New feature or request
Milestone
OTOBO 10.1.1

Comments

@StefanRother-OTOBO
Copy link
Contributor

We have changed the default ticket unlock behaviour in OTOBO 10.1. Now, the ticket is not only unlocked, but also handed over to the system user again. Thus, the behaviour is clearer, but it is no longer possible to read out who last edited the ticket. Please deactivate the config option Ticket::OwnerResetOnUnlock to restore the behaviour of the OTRS version 2-6 and OTOBO 10.
@StefanRother-OTOBO StefanRother-OTOBO added the enhancement New feature or request label Oct 30, 2021
@StefanRother-OTOBO StefanRother-OTOBO added this to the OTOBO 10.1 milestone Oct 30, 2021
@StefanRother-OTOBO StefanRother-OTOBO self-assigned this Oct 30, 2021
@StefanRother-OTOBO StefanRother-OTOBO changed the title We changed the default ticket unlock behaviour in OTOBO 10.1. We have changed the default ticket unlock behaviour in OTOBO 10.1. Oct 30, 2021
StefanRother-OTOBO pushed a commit that referenced this issue Oct 30, 2021
Issue #1372: We have changed the default ticket unlock behaviour and …
7c26a9b 
…the first- and lastname of the system user root@localhost.
@StefanRother-OTOBO
Copy link
Contributor Author

We need to execute bin/otobo.Console.pl to create new initial_insert scripts from scripts/database/otobo-initial_insert.xml. And perhaps we need to change the settings inside the OTOBO 10.1 upgrade script.

@bschmalhofer
Copy link
Contributor

@StefanRother-OTOBO : Do you mean scripts like scripts/database/otobo-schema.mysql.sql ? Those were not used in rel-10_0 and have been removed in rel-10_1.

@StefanRother-OTOBO
Copy link
Contributor Author

I have changed it to otobo-schema.xml, everything should be correct.

@bschmalhofer bschmalhofer modified the milestones: OTOBO 10.1, OTOBO 10.1.1 Dec 8, 2021
@bschmalhofer bschmalhofer mentioned this issue Oct 20, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StefanRother-OTOBO StefanRother-OTOBO

Labels
enhancement New feature or request
Projects
None yet
Milestone
OTOBO 10.1.1
Development

No branches or pull requests
2 participants
@bschmalhofer @StefanRother-OTOBO