#11791 closed defect (duplicate)
internalization/customize of status
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | somenxavier@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Hi,
The status of one ticket is always "closed", "open", and so. I would like to internalizate or customize the status names as resolution names.
This is not a i18n issue. It's more general. Perhaps you want to replace "open" for "pending" or such.
Attachments (0)
Change History (3)
comment:1 by , 10 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
follow-up: 3 comment:2 by , 9 years ago
I think it's not a duplicated. All this stuff is about i18n. This bug is about customization of status of bugs. It's related to i18n but it's more general. I think it should be a way of customizing the name of status (and the steps from one status — but it's another bug) to another status in the web gui.
Why "open", "accept", "close", … Why not "created", "started", "finished". How to change if one trac user wants to change that? Is it possible?
comment:3 by , 9 years ago
Replying to anonymous:
I think it's not a duplicated. All this stuff is about i18n. This bug is about customization of status of bugs. It's related to i18n but it's more general. I think it should be a way of customizing the name of status (and the steps from one status — but it's another bug) to another status in the web gui.
Why "open", "accept", "close", … Why not "created", "started", "finished". How to change if one trac user wants to change that? Is it possible?
The changes proposed in #2045 should provide support for renaming the open and closed states.
A duplicate of #9799 and #9472.