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 2012/08/25 05:43:14 UTC
[Apache Bloodhound] #168: Include milestone field in quick create
ticket form
#168: Include milestone field in quick create ticket form
----------------------------------------+--------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Keywords: quick create ticket fields |
----------------------------------------+--------------------
Quite often we use ourselves milestones rather than versions in order to
schedule tickets . That field is not present in create ticket shortcut
which makes it not as quick as we might want to
''';)'''
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by olemis):
Replying to [comment:7 jdreimann]:
> ..or of course we just go back to the something like the initial drafts
for Quick Ticket, showing only Summary and Product fields and the option
to add further boxes in place.
I don't recall the details related to this initial draft . Is it something
like batch modify form in query view ?
> Maybe we should revisit this once #146 is implemented?
I'm working on #146 , but maybe we could have something like that before
it will be ready to use . That depends on the priorities .
'''PS:''' BTW ... where did batch modify section go ? I cannot see it in
[/query query UI].
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by olemis):
Replying to [comment:11 gjm]:
> Replying to [comment:9 jdreimann]:
> > Our current wiki article on Quick Ticket shows the mockup which I
believe we should still be working towards: Ui/QuickCreate.
> > The initial draft had the option to add further fields (using link and
a box for the description) on the 'Ticket has been created' confirmation
panel. At the time we thought this was too much so found a compromise in
the Ui/QuickCreate design.
>
> OK, I am getting a bit more sympathetic to the idea of including
Milestone as one of the categories that can be set by default.
;)
> On the assumption that such categorisations are sticky in some sense
(session based or by a temporary change in user defaults perhaps)
something like a preferences panel ?
[...]
> I was thinking of suggesting that we could have this displaying based on
whether a user has a specific permission to set a milestone on a ticket
but permission proliferation could be problematic too.
-1
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:12>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by rjollos):
''If'' milestone is added to the quick create form, n I agree with
comment:12 by gjm that it should only be shown if the user has
`MILESTONE_VIEW` permission. If the user doesn't have `MILESTONE_VIEW`,
then the select will be shown with no options, and it is useless
(trac:#8778 is related). Very recently I considered opening tickets
against Trac and Bloodhound suggesting that we hide the select when it
doesn't have any options, so after giving that some more thought I opened
trac:#10984 and provided a patch.
My preference is that the quick create does not have a milestone field
because I like it to be centered around issue reporting, not issue
scheduling, but as others mentioned this is going to be based on user
preference. Therefore, we could start by allowing the administrator to set
the default fields though a `trac.ini` option (as suggested in comment:2),
and later extend the behavior with a user preference that is stored in the
session data. I worked up a [attachment:t168-r1422184-1.patch quick patch]
to implement this behavior.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:15>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by rjollos):
Replying to [comment:17 gjm]:
> Eventually we might have to consider including some kind of
configuration for this but it might be better to wait for users to request
this.
The patch I provided is pretty straightforward though. Did you see any
reason to not make this change now?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:18>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by gjm):
Replying to [comment:18 rjollos]:
> Replying to [comment:17 gjm]:
> > Eventually we might have to consider including some kind of
configuration for this but it might be better to wait for users to request
this.
>
> The patch I provided is pretty straightforward though. Did you see any
reason to not make this change now?
I like the simplification that this brings but I think we need the list
comprehension to be conditional to avoid errors:
{{{
#!python
data['qct'] = {'fields' : [fields[k] for k in self.qct_fields
if k in fields]}
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:22>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by gjm):
I am not convinced that we should worry about providing the different
choices based on the Type, partially as I don't want to worry about
whether an admin would have a reason to change the Type names.
If we could provide the ability to link Types to the available fields so
that the admin could also adjust that if needed then that might work.
Olemis has already suggested making it configurable but I would prefer to
have the default behaviour as close to correct as we can before moving on
to that.
So, do we feel that we can justify the current chosen set of fields? If we
can, will users still get frustrated anyway?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by gjm):
Replying to [comment:8 olemis]:
> '''PS:''' BTW ... where did batch modify section go ? I cannot see it in
[/query query UI].
If it is missing then I would expect it to be due to your user missing the
associated permission.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by olemis):
Replying to [comment:17 gjm]:
> Replying to [comment:16 olemis]:
> > Replying to [comment:15 rjollos]:
> > >
[...]
> >
> > I wander what about priority field ?
>
> Priority should probably remain on the basis that it is fine for the
reporter to immediately give the impression of how important it is for
them. The alternative or complementary field, Severity, could also be used
in this way of course.
>
FWIW , I prefer severity . That field reflects more that its the
perception of a user . The priority should be assigned later by developers
considering their assessment and planned resolution strategy .
Nevertheless , it's a matter of names .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:20>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by rjollos):
I've been viewing the quick ticket create as providing functionality
similar to the [trachacks:SimpleTicketPlugin], which may provide some
context for my comments.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:19>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by olemis):
Replying to [comment:4 jdreimann]:
> Replying to [comment:3 gjm]:
> > I thought that the idea behind allowing the specification of a version
was that it is relatively clear which version a bug should be filed
against (the version that you are using).
>
> This screams out to me that the field should be shown depending on a
condition: If the Type is selected to be a Defect, show the Version field
to indicate which version is affected (label could be: ''Affects:'').
>
> If it's an enhancement or task the user shouldn't need to know which
version/milestone it will be dealt with in.
This is interesting but may be hard to implement and maintain . Maybe
there's a chance to show a checkbox (or whatever) allowing to switch
between versions and milestones selectors . This way both will be
available but only one will be in use and selected by users .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by jdreimann):
I believe asking for both Version and Milestone is contra-productive. The
idea behind asking for Version only was that it's a more fuzzy indicator,
which users could make a quick decision about. This may be more true for
Milestones, so we could ask for those instead, rather than in addition to
Versions.
Another option would be to drop that selector entirely, if it doesn't help
with the review of incoming tickets significantly enough.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Changes (by olemis):
* cc: olemis+bh@… (added)
* keywords: quick create ticket fields => quick create ticket fields
starter
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:14>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by rjollos):
Replying to [comment:20 olemis]:
> FWIW , I prefer severity . That field reflects more that its the
perception of a user . The priority should be assigned later by developers
considering their assessment and planned resolution strategy .
Nevertheless , it's a matter of names .
I've used this convention when working with QA teams. I think it is a
common and sensible convention.
Hearing more opinions just reinforces my feeling that we should have
sensible defaults and options for customization.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:21>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by gjm):
Replying to [comment:9 jdreimann]:
> Our current wiki article on Quick Ticket shows the mockup which I
believe we should still be working towards: Ui/QuickCreate.
> The initial draft had the option to add further fields (using link and a
box for the description) on the 'Ticket has been created' confirmation
panel. At the time we thought this was too much so found a compromise in
the Ui/QuickCreate design.
OK, I am getting a bit more sympathetic to the idea of including Milestone
as one of the categories that can be set by default. On the assumption
that such categorisations are sticky in some sense (session based or by a
temporary change in user defaults perhaps) I would say that this could be
nicer than having to post edit or batch modify. I still wonder how many
people want (or should want) to be setting the milestone to anything other
than its default though.
I was thinking of suggesting that we could have this displaying based on
whether a user has a specific permission to set a milestone on a ticket
but permission proliferation could be problematic too.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:11>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by olemis):
Replying to [comment:15 rjollos]:
>
[...]
> My preference is that the quick create does not have a milestone field
because I like it to be centered around issue reporting, not issue
scheduling,
I think you are definitely right . Quick create ticket is for users
reporting issues , whereas milestone field is for developers to schedule
when this will be solved . So (unless developers = users , like we are ;)
milestone field should not be there .
I wander what about priority field ?
> but as others mentioned this is going to be based on user preference.
I'd rather suggest not including it .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:16>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: closed
Priority: major | Milestone:
Component: ui design | Version:
Resolution: wontfix | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Changes (by gjm):
* status: new => closed
* resolution: => wontfix
Comment:
Closing this ticket as the consensus now appears to be that milestones
should not be available in the quick ticket dialog, at least not by
default.
Raised #310 to implement the enhancements from
attachment:t168-r1422184-1.patch and comment:22.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:23>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by olemis):
So I believe neither of them is final , so I suggest to add configuration
in TracIni in order to choose what ticket fields will be shown in quick
create shortcut dialog .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by jdreimann):
Replying to [comment:3 gjm]:
> I thought that the idea behind allowing the specification of a version
was that it is relatively clear which version a bug should be filed
against (the version that you are using).
This screams out to me that the field should be shown depending on a
condition: If the Type is selected to be a Defect, show the Version field
to indicate which version is affected (label could be: ''Affects:'').
If it's an enhancement or task the user shouldn't need to know which
version/milestone it will be dealt with in.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by jdreimann):
Replying to [comment:8 olemis]:
> Replying to [comment:7 jdreimann]:
> > ..or of course we just go back to the something like the initial
drafts for Quick Ticket, showing only Summary and Product fields and the
option to add further boxes in place.
>
> I don't recall the details related to this initial draft . Is it
something like batch modify form in query view ?
Our current wiki article on Quick Ticket shows the mockup which I believe
we should still be working towards: Ui/QuickCreate.
The initial draft had the option to add further fields (using link and a
box for the description) on the 'Ticket has been created' confirmation
panel. At the time we thought this was too much so found a compromise in
the Ui/QuickCreate design.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by gjm):
Replying to [comment:16 olemis]:
> Replying to [comment:15 rjollos]:
> >
> [...]
> > My preference is that the quick create does not have a milestone field
because I like it to be centered around issue reporting, not issue
scheduling,
>
> I think you are definitely right . Quick create ticket is for users
reporting issues , whereas milestone field is for developers to schedule
when this will be solved . So (unless developers = users , like we are ;)
milestone field should not be there .
I don't think that there is a distinction to be drawn between developers
as users and any other situation. In general I would expect developers who
raise tickets not to need to set a milestone either as it is quite likely
that there will be a subset of users who are expected to decide when a
ticket will be implemented.
>
> I wander what about priority field ?
Priority should probably remain on the basis that it is fine for the
reporter to immediately give the impression of how important it is for
them. The alternative or complementary field, Severity, could also be used
in this way of course.
>
> > but as others mentioned this is going to be based on user preference.
>
> I'd rather suggest not including it .
Eventually we might have to consider including some kind of configuration
for this but it might be better to wait for users to request this.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:17>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by jdreimann):
..or of course we just go back to the something like the initial drafts
for Quick Ticket, showing only Summary and Product fields and the option
to add further boxes in place. Maybe we should revisit this once #146 is
implemented?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+------------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: closed
Priority: major | Milestone:
Component: ui design | Version:
Resolution: wontfix | Keywords: quick create ticket fields starter
--------------------------+------------------------------------------------
Comment (by olemis):
milestone = milestone:"Release 4" (not available as milestone seems to be
closed)
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:24>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by gjm):
Replying to [comment:12 olemis]:
> Replying to [comment:11 gjm]:
> > Replying to [comment:9 jdreimann]:
> > > Our current wiki article on Quick Ticket shows the mockup which I
believe we should still be working towards: Ui/QuickCreate.
> > > The initial draft had the option to add further fields (using link
and a box for the description) on the 'Ticket has been created'
confirmation panel. At the time we thought this was too much so found a
compromise in the Ui/QuickCreate design.
> >
> > OK, I am getting a bit more sympathetic to the idea of including
Milestone as one of the categories that can be set by default.
>
> ;)
>
> > On the assumption that such categorisations are sticky in some sense
(session based or by a temporary change in user defaults perhaps)
>
> something like a preferences panel ?
Well, kind of. Personally I would expect a preferences panel to be a place
for more permanent changes but I suppose it is possible to use that. I am
really talking of what jdreimann has hinted at in his mockup.
> > I was thinking of suggesting that we could have this displaying based
on whether a user has a specific permission to set a milestone on a ticket
but permission proliferation could be problematic too.
>
> -1
I am not sure what you are saying here. Then again, the discussion of
conditional display of fields is probably beyond the scope of this ticket
anyway.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:13>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #168: Include milestone field in quick
create ticket form
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: quick create ticket fields
--------------------------+----------------------------------------
Comment (by gjm):
A fuzzy indicator? Interesting.
I thought that the idea behind allowing the specification of a version was
that it is relatively clear which version a bug should be filed against
(the version that you are using). Milestones on the other hand provide
some specification of when a ticket should be tackled which i consider to
be a question for post-creation categorisation.
The problem with this is communication and justification of these reasons
to the user and any frustration that it causes.
It should be remembered that we now have bulk ticket changing abilities
that we may be able to use to help with the further categorisation. Does
this help justify any decision?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker