Modify ↓
#6657 closed defect (fixed)
milestones blocked by authz policy still visible when creating new tickets
Reported by: | Owned by: | Alec Thomas | |
---|---|---|---|
Priority: | normal | Milestone: | 0.11 |
Component: | general | Version: | 0.11b1 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Say that you have an authz policy file like the following:
[milestone:*] * =
That seems to work as expected - none of the existing milestones show up in the /roadmap
view anylonger. So far so good.
However, when you go to /newtickets
and view the "Milestone:" drop-down menu, all milestones are still visible (and therefore, selectable).
This feels rather wrong with respect to the general policy in Trac to only show to the user things that are actually available.
Attachments (0)
Change History (4)
comment:1 by , 17 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 17 years ago
Note:
See TracTickets
for help on using tickets.
…the result is that things can become a bit confusing after a user happens to assign a task to a milestone for which he or she has no access.