#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 olemis):
Replying to [comment:3 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.
>
It's a combination of behavior and configuration . If configuration states
all fields are required then ticket fields immediately after quick create
shortcut have to be set . Indeed setting them afterwards (to default
value) is even correct action **if** they were supposed to be required
fields in first place. What we see is the effect of a previous failure
mode .
> 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.
This is correct , as long as fields are not required . If configuration
states that they will be required then not having them set in first place
is the right target to fix .
We have to take care of this checks too ... but IMO that's not what we see
happening in i.a.o these days . cmiiw
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/401#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
