Modify ↓
Opened 16 years ago
Closed 15 years ago
#8023 closed defect (duplicate)
Renaming the default milestone or severity causes it to lose default status
| Reported by: | Owned by: | Remy Blank | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | admin/web | Version: | 0.11.1 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Using WebAdmin, if I have a severity 'undefined' which is default, then rename it to '-', it is no longer default.
Actually, no severity has default marked, which makes the topmost be default. Same behaviour with Milestones.
Attachments (0)
Change History (4)
comment:1 by , 16 years ago
| Milestone: | → 0.11.4 |
|---|---|
| Owner: | set to |
comment:2 by , 16 years ago
comment:3 by , 16 years ago
Indeed. That explains the behaviour I'm seeing. I'm adding a reference to this ticket on #7850.
comment:4 by , 15 years ago
| Milestone: | next-minor-0.12.x |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Closing as a duplicate of #7850.
Note:
See TracTickets
for help on using tickets.
This sounds like a symptom of #7850.