[rt-users] Fwd: Using getting stuck when choosing new Custom Lifecycle

[Ben Pintilie]

Hi All,

Im having a strange issue, I know I have missed a step, but cant see
where.  I have added in three new statuses, (aw-int aw-ext aw-qa) each new
status meaning "awaiting-xxx"  I have carried out the update to
RT_SiteConfig.pm as usual.  I have restarted RT and I can see the new
statuses.  If any user or admin selects a status, it saves and reports
correctly.  The issue is that we can not then change the status from any of
the new statuses to an original status.  i.e. from aw-ext TO stalled.

The new statuses have been added like this:


Set(%Lifecycles,
 default => {
initial   => [ 'new' ],
active  => [ 'open', 'aw-ext', 'aw-int', 'aw-qa', 'stalled'
],


<- AND HERE ->



 # from   => [ to list ],
new  => [qw(open aw-ext aw-int aw-qa stalled resolved
rejected deleted)],
open => [qw(new aw-ext aw-int aw-qa stalled resolved
rejected deleted)],
stalled  => [qw(new open aw-ext aw-int aw-qa rejected resolved
deleted)],
resolved => [qw(new open aw-ext aw-int aw-qa stalled rejected
deleted)],
rejected => [qw(new open aw-ext aw-int aw-qa stalled resolved
deleted)],
deleted  => [qw(new open aw-ext aw-int aw-qa stalled rejected
resolved)],
aw-ext   => [qw(new open aw-int aw-qa stalled rejected
resolved)],
aw-int   => [qw(new open aw-ext aw-qa stalled rejected
resolved)],
aw-qa=> [qw(new open aw-ext aw-int stalled rejected
resolved)],



<-AND HERE->



 actions => [
'new -> open'  => { label => 'Open It',  update =>
'Respond' },
'new -> resolved'  => { label => 'Resolve',  update =>
'Comment' },
'new -> rejected'  => { label => 'Reject',   update =>
'Respond' },
'new -> deleted'   => { label => 'Delete'
 },

'open -> stalled'  => { label => 'Stall',update =>
'Comment' },
'open -> resolved' => { label => 'Resolve',  update =>
'Comment' },
'open -> rejected' => { label => 'Reject',   update =>
'Respond' },
'open -> aw-ext'   => { label => 'AW-ext',   update => 'Comment' },
'open -> aw-int'   => { label => 'AW-int',   update =>
'Comment' },
'open -> aw-qa'=> { label => 'AW-qa',update =>
'Comment' },

'aw-ext -> stalled'  => { label => 'Stall',update =>
'Comment' },
'aw-ext -> resolved' => { label => 'Resolve',  update =>
'Comment' },
'aw-ext -> rejected' => { label => 'Reject',   update =>
'Respond' },
'aw-ext -> aw-int'   => { label => 'AW-int',   update =>
'Comment' },
'aw-ext -> aw-qa'=> { label => 'AW-qa',update =>
'Comment' },

'aw-int -> stalled'  => { label => 'Stall',update =>
'Comment' },
'aw-int -> resolved' => { label => 'Resolve',  update =>
'Comment' },
'aw-int -> rejected' => { label => 'Reject',   update =>
'Respond' },
'aw-int -> aw-ext'   => { label => 'AW-ext',   update => 'Comment' },
'aw-int -> aw-qa'=> { label => 'AW-qa',update =>
'Comment' },

'aw-qa -> stalled'  => { label => 'Stall',update =>
'Comment' },
'aw-qa -> resolved' => { label => 'Resolve',  update =>
'Comment' },
'aw-qa -> rejected' => { label => 'Reject',   update =>
'Respond' },
'aw-qa -> aw-ext'   => { label => 'AW-ext',   update => 'Comment' },
'aw-qa -> aw-int'   => { label => 'AW-int',   update =>
'Comment' },

'stalled -> open'  => { label => 'Open It'
  },
'resolved -> open' => { label => 'Re-open',  update =>
'Comment' },
'rejected -> open' => { label => 'Re-open',  update =>
'Comment' },
'deleted -> open'  => { label => 'Undelete'
 },



I have *NOT* Changed the approvals lifecycle

Can anyone point me to what I have missed, I know its human error, I just
cant see where!

Thanks
Ben

-- 


*T:* 01253 394911

*W:* blackpoolsixth.ac.uk

Blackpool Sixth, Blackpool Old Road, Blackpool, FY3 7LR

This email and any attachments are confidential and are intended solely for 
the use of the individual to whom it is addressed. If you are not the 
intended recipient of this email and its attachments, you must take no 
action based upon them, nor must you copy or show them to anyone. Please 
contact the sender if you believe you have received this email in error.  
Emails are not secure and cannot be guaranteed to be free of errors or 
viruses.  It is your responsibility to scan emails and attachments for 
viruses before opening them.


Any views or opinions expressed are solely those of the author and do not 
necessarily represent those of The Blackpool Sixth Form College.

Re: [rt-users] writing extensions for an old version

[Vinicius Fagundes]

Hello,

I tried this but the error remaining the same.

requires_rt '3.8.8';

Or

requires (RT=>'3.8.8');

Is there any other place that I also need to update?

About the upgrade we working to do that soon.

Thanks,

Vinicius Fagundes

Em 13 de fev de 2017 15:18, "Martin Wheldon"  escreveu:

Hi,

If you look in the Makefile.PL you will find somethink like this

requires_rt '4.0.0';

modify as required.

Can I suggest that you upgrade as v3.8 reached end of life in 2014.

Best Regards

Martin


On 2017-02-13 17:02, Vinicius Fagundes wrote:

> Hi,
>
> I'm starting to learn RT development. And I was designated to create a
> RT extension, but our RT version is too old (3.8). I couldn't find any
> documentation about how to do it for this version.
>
> I tried follow the current documentation but when I tried to run:
>
> perl Makefile.PL
>
> I got this error:
>
>  Error: This extension requires RT 4.0.0. Your installed version
> of RT (3.8.8) is too old.
>
> Is it possible write and run a Extension for this version? If so, how
> can I achieve that.
>
> Vinícius _Fagundes_
>

Re: [rt-users] Fwd: Using getting stuck when choosing new Custom Lifecycle

[Ben Pintilie]

Matt / Kyle,

Thanks for your fast replies.  This has fixed the issue and all is working
well.

I have just checked my notes going back about 10 years and this is the
first time I must have ever used a hyphen in a status!  I knew it was
something I did, I would never have found it.  Thanks for your help! :-)


Thanks
Ben

--
Ben Pintilie
Blackpool Sixth Form College
w: http://www.blackpoolsixth.ac.uk
e: ben.pinti...@blackpoolsixth.ac.uk

On 14 February 2017 at 14:34, Matt Zagrabelny  wrote:

> On Tue, Feb 14, 2017 at 8:14 AM, Dippery, Kyle 
> wrote:
> > In my own custom lifecycle, I have one hyphenated status ("in-use").  I
> don't remember why (perhaps this is the reason), but I have it in quotation
> marks as a key in our transitions array:
> >
> >  transitions => {
> >...
> >"in-use"  => [qw(allocated recycled stolen lost deleted
> surplussed destroyed-for-parts scattered-across-the-desert)],
> > }
> >
> > Your hyphenated ones aren't quoted in your array.  Perhaps that's the
> sticking point?  Perl might be trying to do math with the "-" before
> assigning to it.
>
> Guaranteed. You need to quote hash keys that contain hyphens.
>
> -m
>

-- 


*T:* 01253 394911

*W:* blackpoolsixth.ac.uk

Blackpool Sixth, Blackpool Old Road, Blackpool, FY3 7LR

This email and any attachments are confidential and are intended solely for 
the use of the individual to whom it is addressed. If you are not the 
intended recipient of this email and its attachments, you must take no 
action based upon them, nor must you copy or show them to anyone. Please 
contact the sender if you believe you have received this email in error.  
Emails are not secure and cannot be guaranteed to be free of errors or 
viruses.  It is your responsibility to scan emails and attachments for 
viruses before opening them.


Any views or opinions expressed are solely those of the author and do not 
necessarily represent those of The Blackpool Sixth Form College.

Re: [rt-users] writing extensions for an old version

[Vinicius Fagundes]

I have found. For anyone else who may have the same problem, to create a
extension for any deprecated version (RT <4.0)
it's necessary allow deprecated RT:

RTx ('RT-Extension-Example', {deprecated_rt=>1});

More About:
http://search.cpan.org/~alexmv/Module-Install-RTx-0.38/lib/Module/Install/RTx.pm



Vinícius *Fagundes*





2017-02-14 11:36 GMT-02:00 Vinicius Fagundes :

> Hello,
>
> I tried this but the error remaining the same.
>
> requires_rt '3.8.8';
>
> Or
>
> requires (RT=>'3.8.8');
>
> Is there any other place that I also need to update?
>
> About the upgrade we working to do that soon.
>
> Thanks,
>
> Vinicius Fagundes
>
> Em 13 de fev de 2017 15:18, "Martin Wheldon" <
> martin.whel...@greenhills-it.co.uk> escreveu:
>
> Hi,
>
> If you look in the Makefile.PL you will find somethink like this
>
> requires_rt '4.0.0';
>
> modify as required.
>
> Can I suggest that you upgrade as v3.8 reached end of life in 2014.
>
> Best Regards
>
> Martin
>
>
> On 2017-02-13 17:02, Vinicius Fagundes wrote:
>
>> Hi,
>>
>> I'm starting to learn RT development. And I was designated to create a
>> RT extension, but our RT version is too old (3.8). I couldn't find any
>> documentation about how to do it for this version.
>>
>> I tried follow the current documentation but when I tried to run:
>>
>> perl Makefile.PL
>>
>> I got this error:
>>
>>  Error: This extension requires RT 4.0.0. Your installed version
>> of RT (3.8.8) is too old.
>>
>> Is it possible write and run a Extension for this version? If so, how
>> can I achieve that.
>>
>> Vinícius _Fagundes_
>>
>

Re: [rt-users] Fwd: Using getting stuck when choosing new Custom Lifecycle

[Matt Zagrabelny]

On Tue, Feb 14, 2017 at 8:14 AM, Dippery, Kyle  wrote:
> In my own custom lifecycle, I have one hyphenated status ("in-use").  I don't 
> remember why (perhaps this is the reason), but I have it in quotation marks 
> as a key in our transitions array:
>
>  transitions => {
>...
>"in-use"  => [qw(allocated recycled stolen lost deleted surplussed 
> destroyed-for-parts scattered-across-the-desert)],
> }
>
> Your hyphenated ones aren't quoted in your array.  Perhaps that's the 
> sticking point?  Perl might be trying to do math with the "-" before 
> assigning to it.

Guaranteed. You need to quote hash keys that contain hyphens.

-m

[rt-users] Recovering Disabled Articles

[Matthew Coons]

Hello RT User group,

I'm curious if there is a way from RT to enable an article that has been
disabled? I don't see a way to search for disabled articles in RT, and
Googling this question does not return any helpful ideas.

Thoughts?

Matt Coons
Incident Responder and Threat Analyst
Information & Infrastructure Assurance (IIA)
University of Michigan

734-764-4105
coo...@umich.edu

Re: [rt-users] Fwd: Using getting stuck when choosing new Custom Lifecycle

[Dippery, Kyle]

In my own custom lifecycle, I have one hyphenated status ("in-use").  I don't 
remember why (perhaps this is the reason), but I have it in quotation marks as 
a key in our transitions array:

 transitions => {
   ...
   "in-use"  => [qw(allocated recycled stolen lost deleted surplussed 
destroyed-for-parts scattered-across-the-desert)],
}

Your hyphenated ones aren't quoted in your array.  Perhaps that's the sticking 
point?  Perl might be trying to do math with the "-" before assigning to it.

--
Kyle Dippery
Engineering Computing Services
219 RMB
859-257-1346


From: rt-users  on behalf of Ben 
Pintilie 
Sent: Tuesday, February 14, 2017 8:29 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Fwd: Using getting stuck when choosing new Custom   
Lifecycle

Hi All,

Im having a strange issue, I know I have missed a step, but cant see where.  I 
have added in three new statuses, (aw-int aw-ext aw-qa) each new status meaning 
"awaiting-xxx"  I have carried out the update to RT_SiteConfig.pm as usual.  I 
have restarted RT and I can see the new statuses.  If any user or admin selects 
a status, it saves and reports correctly.  The issue is that we can not then 
change the status from any of the new statuses to an original status.  i.e. 
from aw-ext TO stalled.

The new statuses have been added like this:


Set(%Lifecycles,
 default => {
initial   => [ 'new' ],
active  => [ 'open', 'aw-ext', 'aw-int', 'aw-qa', 'stalled' ],


<- AND HERE ->



 # from   => [ to list ],
new  => [qw(open aw-ext aw-int aw-qa stalled resolved rejected 
deleted)],
open => [qw(new aw-ext aw-int aw-qa stalled resolved rejected 
deleted)],
stalled  => [qw(new open aw-ext aw-int aw-qa rejected resolved 
deleted)],
resolved => [qw(new open aw-ext aw-int aw-qa stalled rejected 
deleted)],
rejected => [qw(new open aw-ext aw-int aw-qa stalled resolved 
deleted)],
deleted  => [qw(new open aw-ext aw-int aw-qa stalled rejected 
resolved)],
aw-ext   => [qw(new open aw-int aw-qa stalled rejected resolved)],
aw-int   => [qw(new open aw-ext aw-qa stalled rejected resolved)],
aw-qa=> [qw(new open aw-ext aw-int stalled rejected resolved)],



<-AND HERE->



 actions => [
'new -> open'  => { label => 'Open It',  update => 'Respond' },
'new -> resolved'  => { label => 'Resolve',  update => 'Comment' },
'new -> rejected'  => { label => 'Reject',   update => 'Respond' },
'new -> deleted'   => { label => 'Delete'},

'open -> stalled'  => { label => 'Stall',update => 'Comment' },
'open -> resolved' => { label => 'Resolve',  update => 'Comment' },
'open -> rejected' => { label => 'Reject',   update => 'Respond' },
'open -> aw-ext'   => { label => 'AW-ext',   update => 'Comment' },
'open -> aw-int'   => { label => 'AW-int',   update => 'Comment' },
'open -> aw-qa'=> { label => 'AW-qa',update => 'Comment' },

'aw-ext -> stalled'  => { label => 'Stall',update => 'Comment' 
},
'aw-ext -> resolved' => { label => 'Resolve',  update => 'Comment' 
},
'aw-ext -> rejected' => { label => 'Reject',   update => 'Respond' 
},
'aw-ext -> aw-int'   => { label => 'AW-int',   update => 'Comment' 
},
'aw-ext -> aw-qa'=> { label => 'AW-qa',update => 'Comment' 
},

'aw-int -> stalled'  => { label => 'Stall',update => 'Comment' 
},
'aw-int -> resolved' => { label => 'Resolve',  update => 'Comment' 
},
'aw-int -> rejected' => { label => 'Reject',   update => 'Respond' 
},
'aw-int -> aw-ext'   => { label => 'AW-ext',   update => 'Comment' },
'aw-int -> aw-qa'=> { label => 'AW-qa',update => 'Comment' 
},

'aw-qa -> stalled'  => { label => 'Stall',update => 'Comment' },
'aw-qa -> resolved' => { label => 'Resolve',  update => 'Comment' },
'aw-qa -> rejected' => { label => 'Reject',   update => 'Respond' },
'aw-qa -> aw-ext'   => { label => 'AW-ext',   update => 'Comment' },
'aw-qa -> aw-int'   => { label => 'AW-int',   update => 'Comment' },

'stalled -> open'  => { label => 'Open It'   },
'resolved -> open' => { label => 'Re-open',  update => 'Comment' },
'rejected -> open' => { label => 'Re-open',  update => 'Comment' },
'deleted -> open'  => { label => 'Undelete'  },



I have *NOT* Changed the approvals lifecycle

Can anyone point me to what I have missed, I know its human error, I just cant 
see where!

Thanks
Ben


T: 01253 394911

W: 

Re: [rt-users] Recovering Disabled Articles

[Matt Zagrabelny]

On Tue, Feb 14, 2017 at 8:14 AM, Matthew Coons  wrote:
> Hello RT User group,
>
> I'm curious if there is a way from RT to enable an article that has been
> disabled? I don't see a way to search for disabled articles in RT, and
> Googling this question does not return any helpful ideas.
>
> Thoughts?

What version of RT are you using?

We're on 4.2.11 and there is no disable option for articles - only
delete. And it does delete. I checked the database before and after
clicking the delete link. Afterwards, it is gone.

-m