Opened 3 years ago
Closed 3 years ago
#6777 closed defect (fixed)
TicketExtPlugin 0.3.2-r7739 disables "severity" and each custom fields by default
| Reported by: | augustinus | Owned by: | takanorig |
|---|---|---|---|
| Priority: | high | Component: | TicketExtPlugin |
| Severity: | critical | Keywords: | |
| Cc: | Trac Release: | 0.11 |
Description
I consider disabling "severity" a bug, since it's default field of trac.
Also setting every custom field unusable is inconvenient.
Attachments (0)
Change History (5)
comment:1 follow-up: ↓ 2 Changed 3 years ago by takanorig
- Status changed from new to assigned
comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 3 years ago by augustinus
Replying to takanorig:
I can use the default fields of trac in my environment(Trac 11.5).
e.g.: owner, component, priority
I can use them, too, except severity. It can be re-enabled by trac.ini setting, but still odd to me.
And I think that the default setting of custom fields is unusable better.
If a custom field is added, it is specified at each ticket type.
OK. I can live with that.
comment:3 in reply to: ↑ 2 Changed 3 years ago by takanorig
Replying to augustinus:
Replying to takanorig:
I can use the default fields of trac in my environment(Trac 11.5).
e.g.: owner, component, priority
I can use them, too, except severity. It can be re-enabled by trac.ini setting, but still odd to me.
Indeed, "severity" field is not used.
Sorry, I couldn't notice because I didn't use for that field.
I will fix it.
comment:4 Changed 3 years ago by takanorig
comment:5 Changed 3 years ago by takanorig
- Resolution set to fixed
- Status changed from assigned to closed


I can use the default fields of trac in my environment(Trac 11.5).
e.g.: owner, component, priority
And I think that the default setting of custom fields is unusable better.
If a custom field is added, it is specified at each ticket type.