Modify ↓
#6516 closed defect (fixed)
Checking a property doesn't enable its field
| Reported by: | FranRuiz | Owned by: | CuriousCurmudgeon |
|---|---|---|---|
| Priority: | normal | Component: | BatchModifyPlugin |
| Severity: | major | Keywords: | |
| Cc: | FranRuiz | Trac Release: | 0.11 |
Description
Permissions are properly set, but when I check a property to batch-modify it, the field doesn't get enabled.
Besides, the Comment property always appears checked (and its field enabled)
Attachments (0)
Change History (8)
comment:1 follow-up: 2 Changed 15 years ago by
comment:2 Changed 15 years ago by
Replying to anonymous:
...we installed it primarily to move arbitrary groups of tickets between milestones.
Sorry, scratch this part from my previous comment - got confused which issue I was adding to.
comment:4 Changed 15 years ago by
comment:5 Changed 15 years ago by
| Owner: | changed from ashwin_phatak to CuriousCurmudgeon |
|---|---|
| Status: | new → assigned |
comment:6 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:7 Changed 15 years ago by
comment:8 Changed 15 years ago by
By the way, amazing timing - I was just doing the same fix independently when I noticed this commit.
Note: See
TracTickets for help on using
tickets.
I am also having this problem using BatchModifyPlugin 0.3 and Trac 0.11.5 running under Python 2.6.4 on Ubuntu 9.10. Tested with Firefox 3.0, 3.5; IE 7, 8. This essentially makes the plugin useless for us, as we installed it primarily to move arbitrary groups of tickets between milestones.
It worked perfectly with BatchModifyPlugin 0.2, Python 2.5, on Gentoo (that server is no longer running, so I cannot check what Trac version nor specific Gentoo version).