Opened 18 years ago
Last modified 5 months ago
#7196 new enhancement
Tickets cannot have field-specific access control (read-only vs editable based on status)
| Reported by: | Markus.Staab | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | fieldrefactoring |
| Cc: | chealer@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
It would be nice to have the ability to define if a specific ticket field (property) should be:
- hidden
- readonly/disabled
- or editable
…based or whether the ticket is being created or edited.
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 this website (trac.e.org).
Also the Priority 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 (6)
comment:1 by , 18 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
| Type: | enhancement → task |
comment:2 by , 18 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 , 17 years ago
| Keywords: | fieldrefactoring added |
|---|---|
| Milestone: | → 0.13 |
| Type: | task → enhancement |
comment:4 by , 11 years ago
| Owner: | removed |
|---|---|
| Status: | reopened → new |
comment:5 by , 5 months ago
| Cc: | added |
|---|---|
| Description: | modified (diff) |
| Summary: | restrict ticket properties to add/edit only/... → Tickets cannot have field-specific access control (read-only vs editable based on status) |
I tried cleaning up the description doing my best to interpret your proposal; feel free to revise if I misunderstood. Please indicate at least 1 affected version.
This comment is from Philippe "Chealer" Cloutier. All of my comments and contributions in this ticket are offered under the terms of CC0 1.0 (unless otherwise noted).
dup of #7195 .. sorry browser send error page, so reload created the ticket twice