#401: Change to edit state should not set a component
-------------------------+-------------------------------------------------
Reporter: gjm | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: ui design | Version: 0.4.0
Resolution: | Keywords: ticket fields quick create ticket
| shortcut
-------------------------+-------------------------------------------------
Comment (by gjm):
I agree that the suggestion from olemis is good but is not strictly an
answer to the issue. The issue here is that when there are ticket fields
that are not given a value, I think we should not be setting them without
the user specifying the change.
I also think it is probably correct that when there are fields where there
is not a default available, the field should not be initialised with a
value. In our setup, for example, there is currently no default component.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/401#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
