Search found 42 matches
- 30 Aug 2023, 23:14
- Forum: Help
- Topic: Process management issues
- Replies: 0
- Views: 2679
Process management issues
I am encountering a few issues. Firstly, notifications that I have set up are missing some information. Secondary notification is missing the following: Which user was affected: _____ What was the wave number: _____ Notification back to the user is not showing the "What was the wave number:&quo...
- 22 Aug 2023, 16:39
- Forum: Help
- Topic: New Ticket panel on dashboard
- Replies: 1
- Views: 1169
Re: New Ticket panel on dashboard
I was able to resolve this. Somehow the user did something with the filtering on that portion of the dashboard and It took me some time to realize it.
Is there a way to disable that feature?
Is there a way to disable that feature?
- 18 Aug 2023, 16:00
- Forum: Help
- Topic: New Ticket panel on dashboard
- Replies: 1
- Views: 1169
New Ticket panel on dashboard
We use AD to control access to roles/groups in otrs. I have a user that is not seeing any new tickets in the new ticket portion of the dashboard for a certain queue. I have removed the user from the role and then re-added but it still does not show up. I have added the role to myself and another sup...
Re: LDAPS
FYI I finally found the issue with the Config.pm this line was the issue $Self->{'Customer::AuthModule'} = 'Kernel::System::CustomerAuth::LDAP'; Should be $Self->{'Customer::AuthModule'} = 'Kernel::System::Auth::LDAP'; Sorry, but this is weird. It is always like this: - Agents: $Self->{'AuthModule'...
Re: LDAPS
FYI I finally found the issue with the Config.pm
this line was the issue
$Self->{'Customer::AuthModule'} = 'Kernel::System::CustomerAuth::LDAP';
Should be
$Self->{'Customer::AuthModule'} = 'Kernel::System::Auth::LDAP';
this line was the issue
$Self->{'Customer::AuthModule'} = 'Kernel::System::CustomerAuth::LDAP';
Should be
$Self->{'Customer::AuthModule'} = 'Kernel::System::Auth::LDAP';
Re: LDAPS
$Self->{'Customer::AuthModule'} = 'Kernel::System::CustomerAuth::LDAP'; $Self->{'Customer::AuthModule::LDAP::Host'} = 'ldaps://ad.domain.com'; $Self->{'Customer::AuthModule::LDAP::BaseDN'} = 'ou=All Users,dc=ad,dc=domain,dc=com'; $Self->{'Customer::AuthModule::LDAP::UID'} = 'sAMAccountName'; $Self->...
Re: LDAPS
RemoteAddress: RequestURI: /otrs/customer.pl Traceback (6443): Module: Kernel::System::CustomerUser::LDAP::new Line: 73 Module: Kernel::System::CustomerUser::new Line: 89 Module: Kernel::System::ObjectManager::_ObjectBuild Line: 306 Module: Kernel::System::ObjectManager::Get Line: 200 Module: Kernel...
Re: LDAPS
I was revisiting this issue and I was able to change ldap to ldaps in the config. Once doing that the agents were able to log in without any issues but the customers (ad users) were not able to login. Both agents and customers are using the same ldap server. Customers get the following after they en...
Re: LDAPS
I commented out the port designations and I was still able to log in with it using ldaps://ad.domain.com. I tried to verify that it was using ldaps on the ad server but I only saw a connection to port 389 from my otrs server. Is there a way I can verify that it is using ldaps (636) instead of ldap (...
Re: LDAPS
That did not seem to work. I replaced all instances of LDAP::Host to ldaps://______
Re: LDAPS
I will try that. Our current config didn't specify http in the hostname option that is why I asked
example
$Self->{'Customer::AuthModule::LDAP::Host'} = 'local.domain.com';
example
$Self->{'Customer::AuthModule::LDAP::Host'} = 'local.domain.com';
LDAPS
I'm trying to figure out what places need to be changed in my config to use ldaps instead of ldap. I see a couple of spots where the ldap port is defined (389). Do I just change those to ldaps port (636) # Net::LDAP new params (if needed - for more info see perldoc Net::LDAP) Params => { port => 389...
- 30 Jan 2023, 18:19
- Forum: General
- Topic: agent access
- Replies: 1
- Views: 678
agent access
Is it possible to allow an agent accesss to only tickets assigned to them in a queue without having full access to the rest of the tickets in the queue?
otrs 6.0.33
otrs 6.0.33
- 31 May 2022, 23:48
- Forum: Help
- Topic: Keep state on reply
- Replies: 10
- Views: 811
Re: Keep state on reply
I am trying to set certain queues to keep the state when the user replies. But on the flip side I still want customers to be able to re-open a ticket that is closed by replying to an email from the ticket thread. Hi David, This should do the trick: 1.) Create a new dynamic field for the ticket, typ...
- 31 May 2022, 21:52
- Forum: Help
- Topic: Keep state on reply
- Replies: 10
- Views: 811
Re: Keep state on reply
I am trying to set certain queues to keep the state when the user replies. But on the flip side I still want customers to be able to re-open a ticket that is closed by replying to an email from the ticket thread. Hi David, This should do the trick: 1.) Create a new dynamic field for the ticket, typ...
- 31 May 2022, 19:46
- Forum: Help
- Topic: Keep state on reply
- Replies: 10
- Views: 811
Re: Keep state on reply
ok just wanted to make sure. I will update with results.
- 31 May 2022, 19:39
- Forum: Help
- Topic: Keep state on reply
- Replies: 10
- Views: 811
Re: Keep state on reply
Is this in addition to the previous response from hkais? I am trying to set certain queues to keep the state when the user replies. But on the flip side I still want customers to be able to re-open a ticket that is closed by replying to an email from the ticket thread. Hi David, This should do the t...
- 21 May 2022, 20:39
- Forum: Help
- Topic: Keep state on reply
- Replies: 10
- Views: 811
Re: Keep state on reply
We have certain states that we want to keep tickets in until ready for the next state (wip, qa, ready for production). Every time there is a reply the state changes. We have to change it back every time and it’s becoming tedious. On the flip side we still want the customer to be able to re-open the ...
- 20 May 2022, 21:24
- Forum: Help
- Topic: Keep state on reply
- Replies: 10
- Views: 811
Keep state on reply
I am trying to set certain queues to keep the state when the user replies. But on the flip side I still want customers to be able to re-open a ticket that is closed by replying to an email from the ticket thread. I was able to create a postmaster filter that kept the state by filtering the email add...
- 08 May 2020, 19:39
- Forum: Help
- Topic: Allow customer read only to all tickets in queue
- Replies: 1
- Views: 787
Re: Allow customer read only to all tickets in queue
I was doing some more research and would this be something that company tickets could handle?
- 07 May 2020, 17:28
- Forum: Help
- Topic: Allow customer read only to all tickets in queue
- Replies: 1
- Views: 787
Allow customer read only to all tickets in queue
currently using OTRS 6.0.25 internal agents/customers are synced with AD We do have external customers as well I want to make a queue and sub queues read only to internal agents/customers only. Is it possible to create groups for customers and in turn give them read only access in this fashion even ...
- 20 Apr 2020, 19:48
- Forum: Help
- Topic: Tickets going to raw instead of default queue
- Replies: 8
- Views: 2802
Re: Tickets going to raw instead of default queue
This ended up being a bad postfix filter that was not properly configured that was sending messages to the raw queue
- 15 Jan 2020, 21:21
- Forum: Help
- Topic: Tickets going to raw instead of default queue
- Replies: 8
- Views: 2802
Re: Tickets going to raw instead of default queue
We are using postfix to get emails into OTRS. This particular issue is only happens with the tickets submitted from our web form that has the X-OTRS-Queue assigned. We don't allow our regular users to send emails to these particular queues so we use the headers to direct them to the desired queue ba...
- 15 Jan 2020, 20:02
- Forum: Help
- Topic: Tickets going to raw instead of default queue
- Replies: 8
- Views: 2802
Re: Tickets going to raw instead of default queue
we are not using a fetch account to pull in tickets. so this is not applicable.
- 15 Jan 2020, 19:49
- Forum: Help
- Topic: Tickets going to raw instead of default queue
- Replies: 8
- Views: 2802
Re: Tickets going to raw instead of default queue
I am tracking this down further and it appears that OTRS is not following the X-OTRS-Queue set in the mail header to assign the ticket to the correct queue. These come from a web form and the mail header is assigned based on the form used.
Where would I look next to resolve this issue?
Where would I look next to resolve this issue?
- 30 Dec 2019, 16:26
- Forum: Help
- Topic: Tickets going to raw instead of default queue
- Replies: 8
- Views: 2802
Tickets going to raw instead of default queue
I'm having an issue where new tickets that are coming into the raw queue instead of the assigned default queue. This has been working correctly for some time but something changed and I can't seem to track down what could be causing it. system config setting Core::PostMaster PostmasterDefaultQueue i...
- 13 Feb 2019, 22:28
- Forum: General
- Topic: [Solved] Re-assign ticket without having ownership
- Replies: 3
- Views: 1688
[Solved] Re: Re-assign ticket without having ownership
I was able to figure out how to use GenericAgent to accomplish what I needed.
Search for ticket by number and then change assignments that I needed in the Generic Agent definitions. Manually run the generic agent after making config changes
Search for ticket by number and then change assignments that I needed in the Generic Agent definitions. Manually run the generic agent after making config changes
- 13 Feb 2019, 16:11
- Forum: General
- Topic: [Solved] Re-assign ticket without having ownership
- Replies: 3
- Views: 1688
Re: Re-assign ticket without having ownership
That should have been move queues without having to take ownership. Some of our managers are wanting to be able to move tickets to different queues without having to take ownership, move the queue and then assign the ticket to the agent that will work on it.
- 11 Feb 2019, 17:41
- Forum: General
- Topic: [Solved] Re-assign ticket without having ownership
- Replies: 3
- Views: 1688
[Solved] Re-assign ticket without having ownership
I am wondering if it is possible to give a few users the ability to change the owner of a ticket without having to go through the process of changing the ownership to themselves and then assign it to the required agent.
- 20 Apr 2017, 17:35
- Forum: Help
- Topic: Process management Transition Actions
- Replies: 0
- Views: 1048
Process management Transition Actions
I have a transition action that sets a dynamicfield value to the <OTRS_TICKET_OWNER> but only works when I reject a process. When I approve the first step of the process it sets the owner to root. They both use the same action. approval history Screen Shot 2017-04-20 at 11.23.08 AM.png reject histor...
- 31 Mar 2017, 22:56
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
I will try that route. Thank you for all of your help. I appreciate it.
- 31 Mar 2017, 22:29
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
No I do not.
- 31 Mar 2017, 21:00
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
I can't find anywhere in the process that is changing that dynamicfield value PM1AssignedRep. I only see that dynamic field referenced 2 times --- Activities: Activity-031175fffa45d413ffeb021984bbd898: ActivityDialogs: - ActivityDialog-0be5be36d0321d7d0db33f2335c3188a - ActivityDialog-80148b408520e9...
- 31 Mar 2017, 20:27
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
I did notice that in looking through it. I will have to look at the process and see if I can see something.
- 31 Mar 2017, 19:47
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
sorry this is new to me so took me a bit to find it. History of Ticket#10772102 — Sales Policy Request - test (Test) Close dialog History Content ACTION COMMENT ZOOM USER CREATETIME NewTicket New Ticket [10772102] created (Q=Customer.Service;P=3 normal;S=new). - Ticket System 03/30/2017 12:04:03 (-4...
- 31 Mar 2017, 17:43
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
do you mean this
- 31 Mar 2017, 15:57
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
The field is not blank when submitting the request
The field is not showing either when I open the ticket view
But it is on the other process ticket view
- 31 Mar 2017, 15:18
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
Here is the code source of the notification Not working Source Code A New Sales Policy Change request has been Auto Approved.<br /> <br /> <strong>New or Change:</strong> <OTRS_TICKET_DynamicField_PM1ChangeType><br /> <strong>Account Number:</strong> <OTRS_TICKET_DynamicField_PM1AccountNumber><br />...
- 31 Mar 2017, 14:43
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
Sorry here is the dynamic field config. Like I mentioned before this does work for one process management notification but not the other.
- 31 Mar 2017, 14:26
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
Re: DynamicField issue
Which configs do you need to see DynamicFields::Driver::Registration 7 DynamicFields DynamicFields::ObjectType::Registration 2 DynamicFields Frontend::Admin::ModuleRegistration 6 DynamicFields Frontend::Agent::Preferences 2 DynamicFields Here is the notification text field in question <OTRS_TICKET_D...
- 30 Mar 2017, 20:20
- Forum: Help
- Topic: DynamicField issue
- Replies: 18
- Views: 5696
DynamicField issue
I have a dynamic field I am sharing between process management processes. I'm only able to display the value on ticket notifications for one of the processes. It is setup as a ticket dynamic field. When I pull up the ticket in OTRS for the first process I don't even see the field listed in the reque...