You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2013/02/19 04:42:57 UTC
[Apache Bloodhound] #401: Change to edit state should not set a
component
#401: Change to edit state should not set a component
---------------------+-----------------
Reporter: gjm | Owner:
Type: defect | Status: new
Priority: major | Version: 0.4.0
Resolution: |
---------------------+-----------------
A ticket without a component appears to be automatically given one when
going to edit state.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/401>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #401: Change to edit state should not set a
component
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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
Re: [Apache Bloodhound] #401: Change to edit state should not set a
component
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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
-------------------------+-------------------------------------------------
Changes (by olemis):
* keywords: => ticket fields quick create ticket shortcut
* owner: => nobody
* component: => ui design
Comment:
JFTR , IMO this issue should be approached from a different perspective
i.e. «Set default component , milestone, ... if select field missing in
quick create ticket shortcut»
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/401#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #401: Change to edit state should not set a
component
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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 rjollos):
Replying to [comment:1 olemis]:
> JFTR , IMO this issue should be approached from a different perspective
i.e. «Set default component , milestone, ... if select field missing in
quick create ticket shortcut»
This issue seems separate from what gjm is describing, so I've made a
separate ticket: #416.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/401#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #401: Change to edit state should not set a
component
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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