I just tried this, it works! Thanks for your apply again.
This may be helpful for others, just share it:
I got two custom fields named as Customer and Contact. In Contact config
file, I set it basedon value to Customer( custom field id) via
SetBasedOn($id), then when I populate Contact values fro
Sorry for being annoying. Does anyone have any idea on this?
--
View this message in context:
http://requesttracker.8502.n7.nabble.com/How-to-get-Custom-Field-s-description-which-setted-by-ExternalValues-subroutine-tp53939p53955.html
Sent from the Request Tracker - User mailing list archive at
Hi,
Can some one point me to newbie SLA setup like example config.
If I need to setup any CF and need to run like rt-crontool etc.
Thanks in advance
Arun
--
www.opensourcer.net
--
RT Training in Seattle, June 19-20: http://bestpractical.com/training
Hi,
Are you talking about SLA extension? If not then take a look.
On Wed, May 22, 2013 at 2:39 PM, Arun ragini wrote:
> Hi,
>
> Can some one point me to newbie SLA setup like example config.
>
> If I need to setup any CF and need to run like rt-crontool etc.
>
> Thanks in advance
> Arun
>
> --
Hi,
This is description of a value that is not stored along with value on the
ticket or other object value is set on. The only way is to get list of
values, find one that was set on the object and get description. External
Custom Field Values are very sensitive to methods called on collection or
r
yes I'm talking about SLA extension,
I have gone through
https://github.com/bestpractical/rt-extension-sla/blob/master/README
after I create ticket and and own the ticket I don't get to see the Due
date/time etc.
My SLA config as follows
%RT::ServiceAgreements = (
Default => '4h',
You should use more accounts to test.
Have you checked logs?
Do you see SLA CF on tickets?
Do you see SLA CF set on tickets?
On Wed, May 22, 2013 at 2:45 PM, Arun ragini wrote:
> yes I'm talking about SLA extension,
>
> I have gone through
> https://github.com/bestpractical/rt-extension-sla/blo
I don't see SLA while creating tickets and I don't see them after creating
tickets.
I'm kind of confused I hoping to find some tutorial on how to configure SLA
for RT
On Wed, May 22, 2013 at 4:33 PM, Ruslan Zakirov wrote:
> You should use more accounts to test.
> Have you checked logs?
> Do you
If you don't see SLA custom field in RT (go to Tools -> Configuration ->
Custom Fields -> Select) then you didn't follow installation instructions
properly and just has config and code that is not executed as it's not
registered in the DB.
On Wed, May 22, 2013 at 3:26 PM, Arun ragini wrote:
> I
Hi Diaulas, can you tell me the user name that the rt command is looking for
since I put root (of rt) and tried some and other rt account as well, but I am
getting below error
Query:Status!='resolved' and Status!='rejected'
rt: Server error: Forbidden (403)
Thank you and Best Regards
Hi,
I have installed SLA extention using perl -MCPAN -e 'install
RT::Extension::SLA;'
asked me for RT.pm path I have provided it.
And extension got installed I verified SLA version is 0.07
as document mentioned I need to run db upgrade only prior to 0.0.6 (i
ignored it)
now coming to Tools->Conf
It's first time installtion and you have to run 'make initdb' that is not
executed by CPAN shell you used. At this moment we can not fully automate
installation via cpan shell.
On Wed, May 22, 2013 at 3:39 PM, Arun ragini wrote:
> Hi,
>
> I have installed SLA extention using perl -MCPAN -e 'ins
Sorry, didnt understand your message, but from your log I think you don’t have
RTSERVER variable,
Try to add on top of script:
export RTSERVER=your.rt.installation
if you got error try to execute a simple /usr/bin/rt ls TICKET_NUMBER
That script relies on output of RT CLI command.
De: Asanka
Let me try that. Thanks for all the help.
On Wed, May 22, 2013 at 5:20 PM, Ruslan Zakirov wrote:
> It's first time installtion and you have to run 'make initdb' that is not
> executed by CPAN shell you used. At this moment we can not fully automate
> installation via cpan shell.
>
>
> On Wed, Ma
On Tue, May 14, 2013 at 3:25 PM, Brent Wiese wrote:
> Is there a way to copy/paste, export, or some other means a ticket’s
> entire history?
>
$ /opt/rt3/bin/rt show ticket/123456/history
>
>
> ** **
>
> I searched around the archives and didn’t find anything that would work
> for me.**
We discovered a number of security vulnerabilities which affect both RT
3.8.x and RT 4.0.x. We are releasing RT versions 3.8.17 and 4.0.13 to
resolve these vulnerabilities, as well as patches which apply atop all
released versions of 3.8 and 4.0.
The vulnerabilities addressed by 3.8.17, 4.0.13,
I initially attempted to upgrade to 4.0.12 and that is when I first
identified the problem. I then went back to 3.8.10 and upgraded each
individual version and tested to see if I could log-out and then back in.
It was when I tried to go from version 3.8.16 to 4.0.0 when I first had
the issue. I int
RT 4.0.13 contains important security fixes.
http://download.bestpractical.com/pub/rt/release/rt-4.0.13.tar.gz
http://download.bestpractical.com/pub/rt/release/rt-4.0.13.tar.gz.asc
SHA1 sums
d09f0b9beed8f4e7972fd43d5597e78306d9acef rt-4.0.13.tar.gz
94d1de447301c9be728197572aff2d29944bc39e rt-4.
Hi,
You got an error and your upgrade failed. Which database do you use and
which version of the DB.
The fact that you don't have DelegatedBy column suggests that you did
something wrong when was copying RT3's DB or have DB with column dropped
already.
We had big thread on the list recently with
RT 3.8.17 contains important security fixes.
http://download.bestpractical.com/pub/rt/release/rt-3.8.17.tar.gz
http://download.bestpractical.com/pub/rt/release/rt-3.8.17.tar.gz.sig
SHA1 sums
4765c68f91a0e8e21ed0fd39397cd8e3970ca992 rt-3.8.17.tar.gz
a0aa9a3e284d4fc36ba7e6354d7e0772833f2a00 rt-3.
On Tue, May 7, 2013 at 2:24 PM, Ruslan Zakirov wrote:
>
>
>
> On Tue, May 7, 2013 at 1:25 PM, kjcsb wrote:
>
>> I would like to configure RT to automatically change the status of a
>> ticket
>> in certain cases. An example of this would be when a ticket is set to
>> "waiting on customer" response
On 05/22/2013 01:52 PM, Asif Iqbal wrote:
> Ramon Kagan wrote a RT::Action::SetStatus module
> http://lists.bestpractical.com/pipermail/rt-users/2005-February/028827.html
>
> You can place it at /opt/rt3/local/lib/RT/Action/SetStatus.pm and use
> it. You may have to run mkdir -p /opt/rt3/local/lib
Hi,
I am wondering if plugin would have problem if I perform general minor version
upgrade on 4.0.x?
Recently we intensively use more and more plugin which I am not sure if it will
drive the upgrade more complicated.
We are using RT-Extension-CommandByMail, RT-Extension-RepeatTicket and
RT-Ex
On Wed, May 22, 2013 at 5:49 PM, Thomas Sibley wrote:
> On 05/22/2013 01:52 PM, Asif Iqbal wrote:
> > Ramon Kagan wrote a RT::Action::SetStatus module
> >
> http://lists.bestpractical.com/pipermail/rt-users/2005-February/028827.html
> >
> > You can place it at /opt/rt3/local/lib/RT/Action/SetStatu
Hi,
I am trying to setup against ticket in a certain queue where a group of
custom fields show based on a value of another custom field (as a
combobox). This is so that it prompts users to fill out the relevant
custom fields only not all of the custom fields. I have all of the
custom fields a
On Thu, May 23, 2013 at 5:15 AM, Thomas Lau wrote:
> Hi,
>
> ** **
>
> I am wondering if plugin would have problem if I perform general minor
> version upgrade on 4.0.x?
>
They shouldn't. We work hard not to break backwards compatibility in minor
versions and avoid database changes as much a
26 matches
Mail list logo
