[rt-users] Uploading image to Image CustomField via REST

2015-01-20 Thread andriusk
Is it possible to post image for ticket customfield via rest?



--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/Uploading-image-to-Image-CustomField-via-REST-tp59382.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.


Re: [rt-users] RT 4.2.9 Simple Search, Subject LIKE instead of Id =

2015-01-20 Thread Vladimir Nikolic
On 20. 01. 2015 02:41, Alex Vandiver wrote:
 On Mon, 19 Jan 2015 22:50:07 +0100 Vladimir Nikolic
 vladimir.niko...@amis.net wrote:
 Hello,

 after upgrade to 4.2.9 (from 4.2.2), we noticed that Simple Search by 
 Ticket id doesn't work.
 If I enter 783509 in Search box, Edit Search shows sql query:

 ( Subject LIKE 783502 ) AND (  Status = 'new' OR Status = 'open' OR 
 Status = 'resolved' OR Status = 'stalled' OR Status = 'rejected' OR 
 Status = 'deleted' )
 
 This does not occur on a stock RT 4.2.9.
 
 /usr/local/lib/perl5/site_perl/RT/Search/Simple.pm has lines:

  # Assume that numbers were actually defaults if we have other
  # limits
  if ($limits-{id} and keys %{$limits}  1) {
  my $values = delete $limits-{id};
  for my $value (@{$values}) {
  $value =~ /(\d+)/ or next;
  my ($key, @tsql) = $self-HandleDefault($1);
  push @{$limits-{$key}}, @tsql;
  }
  }

 which rewrites 'Id =' to 'Subject LIKE'.
 
 It only does so _if_ there are other limits -- as the comment
 describes.  This is so, in a stock RT, entering «rt 4» into the search
 box does not attempt to load ticket #4.
 
 
 Double-check that you do not have any customizations in this area.  For
 the following command, a stock RT 4.2.9 should return only the ID
 clause:
 
 perl -I/opt/rt4/lib -MRT=-init -MRT::Search::Simple \
  -le 'print RT::Search::Simple-new(TicketsObj =
 RT::Tickets-new(RT-SystemUser))-QueryToSQL(783502)'
 
 
  - Alex
 

Hello,
 perl -I/opt/rt4/lib -MRT=-init -MRT::Search::Simple \
  -le 'print RT::Search::Simple-new(TicketsObj =
 RT::Tickets-new(RT-SystemUser))-QueryToSQL(783502)'

returns ( Id = 783502 ), which is ok.

The problem is that $query consists of ticket id and various states -
new, open, resolved, stalled, rejected and deleted. These are other
limits and because of them search by id doesn't work.

sub QueryToSQL {
my $self = shift;
$RT::Logger-error(self $self\n);
my $query = shift || $self-Argument;
...

I don't know from where it gets all these states.

Regards,
Vladimir



Re: [rt-users] is Disable 2 a typo?

2015-01-20 Thread Marc Chantreux
On Tue, Jan 20, 2015 at 11:27:04AM -0500, Kevin Falcone wrote:
 ___Approvals is a very special queue, so it gets a special Disabled
 value.  It's there to stop people breaking it by accident (something
 which happened quite frequently in 4.0 and earlier). 

thanks for answering, Kevin

-- 
Marc Chantreux,
Mes coordonnées: http://annuaire.unistra.fr/chercher?n=chantreux
Direction Informatique, Université de Strasbourg (http://unistra.fr) 
Don't believe everything you read on the Internet
-- Abraham Lincoln


Re: [rt-users] CurrentUserEmail in search - better way instead copying Tickets_Local.pm

2015-01-20 Thread Daniel Schwager
Hi Kevin,

 Does
  Requestor = '__CurrentUser__'
 not work?

Oh - yes, this works!! I didn't know about this Requestor keyword. Great! 
Thank!

  I tried to just copy _parser() method - but perl cannot find
  variables from the base class Tickets.pm like FIELD_METADATA or %dispatch ..
 
 I suspect you failed to add package RT::Tickets; to the top of your
 Tickets_Local.pm (those variables are marked our so should be fine to
 use).

I added package RT::Tickets - but doesn't matter. I will use your suggested 
solution!

Thanks
Danny


smime.p7s
Description: S/MIME cryptographic signature


[rt-users] is Disable 2 a typo?

2015-01-20 Thread Marc Chantreux
hello, 

in the etc/initialdata sample from the rt distrib, i can read

@Queues = ({ Name  = 'General',  
 Description   = 'The default queue',
 CorrespondAddress = , 
 CommentAddress= , },  
   { Name= '___Approvals',   
 Lifecycle   = 'approvals',  
 Description = 'A system-internal queue for the approvals system',
 Disabled= 2, } ); 

But there is only 2 documented values (by documented, i meant
https://bestpractical.com/docs/rt/latest/RT/Queue.html#SetDisabled). 

so my question is: is there a point to use different values that the documented 
ones? what is it? 

regards.
-- 
Marc Chantreux,
Mes coordonnées: http://annuaire.unistra.fr/chercher?n=chantreux
Direction Informatique, Université de Strasbourg (http://unistra.fr) 
Don't believe everything you read on the Internet
-- Abraham Lincoln


Re: [rt-users] MoreAboutRequestorTicketList is ignored

2015-01-20 Thread Kevin Falcone
On Tue, Jan 20, 2015 at 12:42:52AM -0700, darthPaal wrote:
 Hello, I am running RT 4.2.9 and want to view all tickets in the 'More about
 the requestors' section. I have added the following line in my
 RT_SiteConfig.pm file:
 
 Set($MoreAboutRequestorTicketList, All);
 
 but the setting is ignored, its stil only active tickets that are listed.
 Any thoughts?

Please report this to the bugtracker.

http://bestpractical.com/rt/issues.html

-kevin


pgpbZrQPnIBlX.pgp
Description: PGP signature


Re: [rt-users] is Disable 2 a typo?

2015-01-20 Thread Kevin Falcone
On Tue, Jan 20, 2015 at 04:40:07PM +0100, Marc Chantreux wrote:
 
 so my question is: is there a point to use different values that the 
 documented ones? what is it? 

___Approvals is a very special queue, so it gets a special Disabled
value.  It's there to stop people breaking it by accident (something
which happened quite frequently in 4.0 and earlier).

Not a typo.

-kevin


pgpJzgadqRqVN.pgp
Description: PGP signature


Re: [rt-users] CurrentUserEmail in search - better way instead copying Tickets_Local.pm

2015-01-20 Thread Kevin Falcone
On Tue, Jan 20, 2015 at 03:45:36PM +, Daniel Schwager wrote:
 I would like to create a search finding all my requested tickets 
 without using my hard-coded email-adr.

Does
Requestor = '__CurrentUser__'
not work?

 Therefore, I overlayed Tickets.pm with Tickets_Local.pm, removing the use 
 ...
 and adding one line of code like described in 
 http://requesttracker.wikia.com/wiki/CurrentUserEmail.

I can't see how that code has ever been useful.  Page should probably
be deleted.

 Question: Is there a way not to copy the whole Tickets.pm but just 
 the relevant code snippet using callbacks/overaying/ 
 
 I tried to just copy _parser() method - but perl cannot find 
 variables from the base class Tickets.pm like FIELD_METADATA or %dispatch ..

I suspect you failed to add package RT::Tickets; to the top of your
Tickets_Local.pm (those variables are marked our so should be fine to
use).

-kevin


pgpDaBhXybh_f.pgp
Description: PGP signature


[rt-users] CurrentUserEmail in search - better way instead copying Tickets_Local.pm

2015-01-20 Thread Daniel Schwager
Hi,

I would like to create a search finding all my requested tickets 
without using my hard-coded email-adr.
 
Therefore, I overlayed Tickets.pm with Tickets_Local.pm, removing the use ...
and adding one line of code like described in 
http://requesttracker.wikia.com/wiki/CurrentUserEmail.

/opt/rt4/local/lib/RT/Tickets_Local.pm:2978
+ $value = $self-CurrentUser-EmailAddress if $value eq 
'__CurrentUserEmail__';

Now, it's possible execute a search-query like 
Requestor.EmailAddress = '__CurrentUserEmail__' AND Status = 'open'


Question: Is there a way not to copy the whole Tickets.pm but just 
the relevant code snippet using callbacks/overaying/ 

I tried to just copy _parser() method - but perl cannot find 
variables from the base class Tickets.pm like FIELD_METADATA or %dispatch ..

Is there a smoother way to implement this feature?

regards
Danny


smime.p7s
Description: S/MIME cryptographic signature


Re: [rt-users] setting a password for a user

2015-01-20 Thread Kevin Falcone
On Fri, Jan 16, 2015 at 02:56:42PM -0500, Boris Epstein wrote:
 I guess the question still remains, what is the rational behind me being 
 unable
 to do so just as a user with admin privileges.

RT requires an admin password to change another password so that
nobody can trick you into clicking on a link that would change (say
root's) password.  This was further mitigated by CSRF protections, but
still seems like a reasonable security precaution.

RT does not know your password when you use RT-Authen-ExternalAuth,
thus it cannot require you to enter it.

RT-Authen-ExternalAuth could be extended to make that additional query
and support it, however, that's nontrivial development and not
currently planned.  If it's something you require, patches are
welcome, or I'm happy to put you in touch with sales.

-kevin

 Here is a discussion I found on the topic:
 
 [5]http://www.gossamer-threads.com/lists/rt/users/99177


pgpZLmG_o_jUi.pgp
Description: PGP signature


[rt-users] about signatures

2015-01-20 Thread Eierschmalz, Bernhard
Hello,

I have 2 questions about signatures.


1.   For our non-request-tracker-mails I have a HTML-Template, to 
standardize all our outgoing email signatures (on the email server runs a 
program that attaches the template with filled in parameters for name phone 
number etc. to every email)
is it possible to use a HTML-Template like this also for emails sent through 
request tracker? (the problem is, the software only sees one email address for 
each queue, so I need to generate the signature directly in RT.



2.   In the moment our signatures are attached under the quoted text; many 
customers complain about this. Is it possible to place the signature between 
message and quoted text?


By the way: we use RT 4.2.8



Best regards,
Bernhard


[rt-users] Grant right to a special CF dependet on a specific queue ?

2015-01-20 Thread Daniel Schwager
Hi,

in short: Is it possible to grant SeeCustomField-rights for one CF dependent on 
a queue ?

Long: We have some (external, customer) privileged users working with their 
queue.
Also, we have a ticket CF named Summary. In their queue, the users are able 
to see/modify this CF.

Beside of this, our privileged user can also create tickets in other internal 
queues. 
I grant them the ShowTicket-right. Fine.

But they have also access/see the Summary-CF from tickets located in our 
internal queue - this is not fine.

Is it possible (for CF Summary) to
- grant SeeCustomField-right to our privileged users concerning tickets located 
in their queue but
- not grant SeeCustomField-right to tickets located in other queues?

regards
Danny


smime.p7s
Description: S/MIME cryptographic signature


[rt-users] Linking options default custom fields with fields

2015-01-20 Thread Marisol Rojas
good afternoon

I write because I like to know how to flirt options for a custom field to
field in the interface queue creating a new ticket (if applicable).

Thanks in advance, greetings !!