Edgewall Software
Modify

Opened 10 years ago

Last modified 5 years ago

#8637 new enhancement

"Add to CC" for anonymous with TICKET_APPEND permissions

Reported by: Sebastian Krysmanski <sebastian@…> Owned by:
Priority: normal Milestone: next-major-releases
Component: ticket system Version: 0.11.5
Severity: major Keywords: cc notify permission nosylist
Cc: itamarost@…, Ryan J Ollos Branch:
Release Notes:
API Changes:

Description

Currently when always_notify_updater is set to false an commenter/updater has to put himself/herself to the CC list of a ticket to be notified about future changes. However, to do so the user is required to have TICKET_MODIFY permissions. If an administrator only want the users to be able to comment on tickets (i.e. only grants TICKET_APPEND permissions) the user has no way of being notified about future changes.

So it would be nice to activate this checkbox even when the user only has TICKET_APPEND permissions.

Attachments (0)

Change History (13)

comment:1 by Ryan Ollos <ryano@…>, 10 years ago

Cc: ryano@… added

comment:2 by Christian Boos, 10 years ago

Milestone: 0.12

I agree, the fact that the "nosy list" for a ticket is currently implemented by doing a modification on the ticket itself is just an implementation detail. As you said, it makes sense to be able to "follow" a ticket when only having TICKET_APPEND permission.

comment:3 by Remy Blank, 10 years ago

Would it make more sense to implement a new module managing "nosy lists" for any kind of resource, separately from the resources themselves? That would allow notifications e.g. for wiki page changes.

in reply to:  3 comment:4 by Christian Boos, 10 years ago

Replying to rblank:

Would it make more sense to implement a new module managing "nosy lists" for any kind of resource, separately from the resources themselves? That would allow notifications e.g. for wiki page changes.

Well, yes, that's the grand plan behind the new notification scheme of 0.13.

Something that puts all of #1660, #6543 and #8621 together.

comment:5 by Remy Blank, 10 years ago

I would suggest we postpone this to 0.12.1.

in reply to:  5 comment:6 by Christian Boos, 10 years ago

Milestone: 0.12next-minor-0.12.x

Replying to rblank:

I would suggest we postpone this to 0.12.1.

No problem, I'm in a postponing mood today ;-)

comment:7 by Christian Boos, 9 years ago

Keywords: cc notify permission added
Milestone: next-minor-0.12.xunscheduled

comment:8 by Christian Boos, 9 years ago

Keywords: nosylist added

comment:9 by Christian Boos, 9 years ago

Milestone: unschedulednext-major-0.1X
Severity: normalmajor

comment:10 by Itamar Ostricher, 9 years ago

Cc: itamarost@… added

Just a small observation regarding permissions- while TICKET_APPEND is needed for commenting on a ticket, a user needs only TICKET_VIEW in order to follow a ticket (manually), so logically, a user with TICKET_VIEW should also be able to subscribe to the nosylist / cc (which isn't really considered a change to the ticket..)

comment:11 by Carsten Klein <carsten.klein@…>, 9 years ago

See also the patch over at #9900 which is a preliminary to this.

comment:12 by Carsten Klein <carsten.klein@…>, 9 years ago

I also figure that the ticket.html template needs some major refactoring. I have begun dividing it into ticket_view.html (a readonly representation with the ability to add comments/edit own comments, update the cc_entry for oneself provided that a valid email address is available in the session settings, and a ticket_modify.html template which will be suited for both TICKET_MODIFY and TICKET_ADMIN granted users.

In addition, I have added the TICKET_UPDATE_CC permission which will allow anonymous users to update the cc list. The TICKET_EDIT_CC permission was moved to TICKET_MODIFY.

TICKET_EDIT_CC will require additional Javascript and will present a scrollable list of persons to be notified on ticket change, supporting multi-selection for bulk removal of listeners. It will also feature an input text box for adding new persons to the list.

In addition, smaller templates for inclusion with the above will be made available, namely ticket_comments.html for the comments, a ticket_commons.html template for commonly used functions/macros, and so on.

I will open a new issue for this, once the refactoring has been done and a patch can be made available, which then will also be a preliminary to this.

comment:14 by Ryan J Ollos, 5 years ago

Cc: Ryan J Ollos added; ryano@… removed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.