Opened 17 years ago
Last modified 10 years ago
#7196 new enhancement
restrict ticket properties to add/edit only/...
| Reported by: | Markus.Staab | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | fieldrefactoring |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
would be nice to have the ability to define if a property should be readonly/disabled/not mentioned at all, if in ticket add-mode/edit-mode…
so e.g. the milestone field could be set to edit-mode, so the creator is not able to choose the value for it… this is the intended behavior on t.e.o.
also the priorty field should be set by a developer, so maybe also a restriction to some usertypes would be great..
such restriction would also make sense for other fields and also in other scenarios.
this would improve the user-experience and help also the developer team, because of less misfilled tickets
Attachments (0)
Change History (4)
comment:1 by , 17 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
| Type: | enhancement → task |
comment:2 by , 16 years ago
| Resolution: | duplicate |
|---|---|
| Status: | closed → reopened |
This would be helpful. I would like the Reporter field to be ReadOnly and set to the person currently modifing the ticket. Doesn't even need to be shown. Is this possible in the latest release (installed 30 Dec 2008).
I looked over the referenced duplicate ticket and found nothing relating to readonly status of an existing field. Not even anything for a custom field.
comment:3 by , 16 years ago
| Keywords: | fieldrefactoring added |
|---|---|
| Milestone: | → 0.13 |
| Type: | task → enhancement |
comment:4 by , 10 years ago
| Owner: | removed |
|---|---|
| Status: | reopened → new |
dup of #7195 .. sorry browser send error page, so reload created the ticket twice