Per-transaction reply/comment with quoting

Is there any particular reason RT 3.x doesn’t have the per-transaction
reply/comment links which start the update form out with a quoted copy
of the text of the given transaction?

–Bret

Is there any particular reason RT 3.x doesn’t have the per-transaction
reply/comment links which start the update form out with a quoted copy
of the text of the given transaction?

Sorry, to be clearer: as opposed to RT 2.x, which did do this. I found
myself going for those links for the first time under RT 3, and whoa,
they’re not there!

–Bret

Is there any particular reason RT 3.x doesn’t have the per-transaction
reply/comment links which start the update form out with a quoted copy
of the text of the given transaction?

Sorry, to be clearer: as opposed to RT 2.x, which did do this. I found
myself going for those links for the first time under RT 3, and whoa,
they’re not there!

Hmm. They were there in my 3.0.x installs and they are present in my
3.2.0 and 3.2.1 install. They are there on rt3.fsck.com which as
3.2-HEAD. Are you sure you have appropriate rights for corresponding
and commenting?

Michael
Michael S. Liebman m-liebman@northwestern.edu
http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”

Hmm. They were there in my 3.0.x installs and they are present in my
3.2.0 and 3.2.1 install. They are there on rt3.fsck.com which as
3.2-HEAD. Are you sure you have appropriate rights for corresponding
and commenting?

Since I can comment and correspond, I’d have to say yes!

Looking, I now see that I had ModifyTicket, but not CommentOnTicket and
ReplyToTicket. Adding those two gets me the links.

I guess I thought ModifyTicket included some of the other rights, based
on the description in the manual (and the behavior – I was perfectly
able to comment and reply, those links just didn’t appear).

Is this a bug?

–Bret

Hmm. They were there in my 3.0.x installs and they are present in my
3.2.0 and 3.2.1 install. They are there on rt3.fsck.com which as
3.2-HEAD. Are you sure you have appropriate rights for corresponding
and commenting?

Since I can comment and correspond, I’d have to say yes!

Looking, I now see that I had ModifyTicket, but not CommentOnTicket and
ReplyToTicket. Adding those two gets me the links.

I guess I thought ModifyTicket included some of the other rights, based
on the description in the manual (and the behavior – I was perfectly
able to comment and reply, those links just didn’t appear).

Is this a bug?

yes. bounce it to rt-bugs?

Are you sure you have appropriate rights for corresponding
and commenting?

Since I can comment and correspond, I’d have to say yes!

Looking, I now see that I had ModifyTicket, but not CommentOnTicket and
ReplyToTicket. Adding those two gets me the links.

I guess I thought ModifyTicket included some of the other rights, based
on the description in the manual (and the behavior – I was perfectly
able to comment and reply, those links just didn’t appear).

Is this a bug?

I’d say its more an attempt to correct some of the confusion related
to ModifyTicket. ModifyTicket has been a bit too broad in its
application. Allowing commenting and changing of custom fields
shouldn’t necessarily be related.

Michael
Michael S. Liebman m-liebman@northwestern.edu
http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”

I guess I thought ModifyTicket included some of the other rights, based
on the description in the manual (and the behavior – I was perfectly
able to comment and reply, those links just didn’t appear).

Is this a bug?

yes. bounce it to rt-bugs?

As implied by my other reply, I’d rather see the reply/comment
abilities get separated from the ModifyTicket right. I’d consider that
more of a bug and might make things easier for people who want to
allow editing of custom fields by self service.

Michael
Michael S. Liebman m-liebman@northwestern.edu
http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”

As implied by my other reply, I’d rather see the reply/comment
abilities get separated from the ModifyTicket right. I’d consider that
more of a bug and might make things easier for people who want to
allow editing of custom fields by self service.

That’s a level of change to rights that I’m not comfortable with during
a stable release series.

I’d say its more an attempt to correct some of the confusion related
to ModifyTicket. ModifyTicket has been a bit too broad in its
application. Allowing commenting and changing of custom fields
shouldn’t necessarily be related.

As implied by my other reply, I’d rather see the reply/comment
abilities get separated from the ModifyTicket right. I’d consider that
more of a bug and might make things easier for people who want to
allow editing of custom fields by self service.

I don’t necessarily disagree with you, although when I saw ModifyTicket
for the first time, I thought “nice, a ‘do what I mean’ setting”. But I
see your point in terms of having the rights be finer-grained.

I’d be happy with unambiguous documentation and consistent behavior
either way.

–Bret

As implied by my other reply, I’d rather see the reply/comment
abilities get separated from the ModifyTicket right. I’d consider that
more of a bug and might make things easier for people who want to
allow editing of custom fields by self service.

That’s a level of change to rights that I’m not comfortable with during
a stable release series.

That’s totally understandable. My concern is that fixing the “bug”
would take a step backwards and make future changes even more painful.

Michael
Michael S. Liebman m-liebman@northwestern.edu
http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”

That’s a level of change to rights that I’m not comfortable with during
a stable release series.

That’s totally understandable. My concern is that fixing the "bug"
would take a step backwards and make future changes even more painful.

If we change what the “ModifyTicket” right means, we’re going to have to
do a hell of a lot more work than just changing those two rights
clauses.

Bret Martin wrote:

I’d say its more an attempt to correct some of the confusion related
to ModifyTicket. ModifyTicket has been a bit too broad in its
application. Allowing commenting and changing of custom fields
shouldn’t necessarily be related.

As implied by my other reply, I’d rather see the reply/comment
abilities get separated from the ModifyTicket right. I’d consider that
more of a bug and might make things easier for people who want to
allow editing of custom fields by self service.
I find ModifyTicket most insecure right that RT has. ModifyTicket allow
unique tasks, but also allow some tasks that can be granted by other rights.

I don’t necessarily disagree with you, although when I saw ModifyTicket
for the first time, I thought “nice, a ‘do what I mean’ setting”. But I
see your point in terms of having the rights be finer-grained.

I’d be happy with unambiguous documentation and consistent behavior
either way.
Request Tracker Wiki
When we wrote this I scan code for Rights checks to be sure that
description is correct.