Opened 9 years ago
Closed 9 years ago
#11931 closed enhancement (fixed)
On BatchModify form workflow controls should be disabled until action is selected — at Version 2
| Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.1.4 |
| Component: | ticket system | Version: | 1.0.3 |
| Severity: | normal | Keywords: | batch-modify |
| Cc: | Branch: | ||
| Release Notes: |
The workflow controls in the batch modify section of the Query page are disabled until the associated action is selected. |
||
| API Changes: |
The |
||
| Internal Changes: | |||
Description
In the ticket action fieldset, the workflow controls are disabled until an action is selected.
The same is not true in the batch modify action fieldset.
Change History (4)
by , 9 years ago
| Attachment: | BatchModifyAction.png added |
|---|
by , 9 years ago
| Attachment: | TicketAction.png added |
|---|
comment:1 by , 9 years ago
| Milestone: | next-stable-1.0.x → 1.1.4 |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
comment:2 by , 9 years ago
| API Changes: | modified (diff) |
|---|---|
| Release Notes: | modified (diff) |
| Resolution: | → fixed |
| Status: | assigned → closed |
Committed to trunk in [13707].
Note:
See TracTickets
for help on using tickets.
Thimal Kempitiya proposed a patch for Bloodhound that has been added to log:rjollos.git:t11931, followed by some refactoring of the templates to eliminate duplicated code.
I'm unsure as to whether the find is actually needed. It seems it would only be necessary in the case that controls has some nested elements, which I can't entirely rule out so I've left the code.