Opened 14 years ago
Last modified 5 years ago
#8400 new enhancement
Trigger off ticket status not type
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Component: | DynamicFieldsPlugin |
| Severity: | normal | Keywords: | |
| Cc: | alillards, Steffen Hoffmann, duytscal | Trac Release: | 0.11 |
Description (last modified by )
It would be nice to hide or show fields based upon the ticket status. We have custom fields that need to be filled out based upon the status. If the ticket is fixed, some special fields are filled out. There are additional fields that need to be filled out if the ticket is in the verified state. Only showing the fields for a particular ticket status would be helpful.
Attachments (0)
Change History (13)
comment:1 Changed 13 years ago by
| Cc: | alillards added; anonymous removed |
|---|
comment:2 Changed 13 years ago by
comment:3 follow-up: 13 Changed 13 years ago by
| Cc: | Steffen Hoffmann added |
|---|---|
| Status: | new → assigned |
I appreciate this feature request. It's a bit tricky to implement though. The "state" is not like other fields. In fact, you may be talking about two different but interrelated fields:
- status (e.g., new, assigned, closed, etc.)
- resolution (fixed, duplicate, worksforme, etc.)
Neither of these are standard form fields so they would have to be handled as special cases. Will take some thought to figure out how to do this well.. sorry about that.
comment:4 Changed 12 years ago by
I am interested too. My idea is to hide a custom field when creating a new ticket, so that it's initial value is the default.
comment:5 Changed 9 years ago by
comment:19:ticket:7561 has requested the ability to use the copy_from rule on the status field.
comment:6 Changed 6 years ago by
| Owner: | Rob Guttman deleted |
|---|---|
| Status: | assigned → new |
comment:7 Changed 5 years ago by
| Description: | modified (diff) |
|---|---|
| Summary: | Trigger off ticket state not type → Trigger off ticket status not type |
comment:9 Changed 5 years ago by
| Cc: | duytscal added |
|---|
comment:10 Changed 5 years ago by
Is it possible, as a workaround, to mention on the doc/main page that the status field cannot be used in rules, so users don't lose time trying to get this working?
comment:11 Changed 5 years ago by
The wiki page is open for editing. Please contribute if you have suggestions. I hardly have time to maintain this plugin.
comment:13 Changed 5 years ago by
Replying to Rob Guttman:
Neither of these are standard form fields so they would have to be handled as special cases.
These fields are controlled by workflow actions, so we'll need to add support for setting workflow actions.
This enhancement would be great!