Modify ↓
#13515 closed defect (fixed)
Ticket notification failing with 'list' object has no attribute 'update'
| Reported by: | Jun Omae | Owned by: | Jun Omae |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.4.4 |
| Component: | ticket system | Version: | 1.4.3 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: |
Fixed notification failure when permission group is used in other than Cc field. |
||
| API Changes: | |||
| Internal Changes: | |||
Description
Reported at gmessage:trac-users:FM_1L9QFywQ/m/KPtZ2b0iAQAJ.
How to reproduce
trac-admin /path/to/tracenvinitenv 'My Project' sqlite:db/trac.dbpermission add anonymous TICKET_CREATE TICKET_MODIFYpermission add user1 group1
tracd -p 3000 /path/to/tracenv- Create new ticket with owner being
group1
Trac[web_ui] ERROR: Failure sending notification on creation of ticket #1: AttributeError: 'list' object has no attribute 'update'
Attachments (0)
Change History (5)
comment:1 by , 16 months ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 15 months ago
| Release Notes: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
follow-up: 4 comment:3 by , 7 months ago
r17650 references this ticket and is shown as eligible for merge to trunk. Is it applicable to trunk?
$ svn mergeinfo --show-revs eligible ^/branches/1.4-stable r17650
comment:4 by , 7 months ago
Replying to Ryan J Ollos:
r17650 references this ticket and is shown as eligible for merge to trunk. Is it applicable to trunk?
Ah, I forget to merge it to trunk. We should apply it to trunk (and 1.6-stable).
Note:
See TracTickets
for help on using tickets.
After the changes of #12808, permission group is able to use in Cc field. However, the permission group in also reporter, owner and updater is expanded to the members (actually, the
AttributeErrorraises).Proposed changes in [40a35bb4f/jomae.git] (jomae.git@t13515). In the proposal changes, permission group can be used in only Cc field.