Re: Getting rid of the "wish" issue type

[Mike Kienenberger <mk...@gmail.com>]

On 8/17/06, Mike Kienenberger <mk...@gmail.com> wrote:
> I think we should get rid of the "wish" issue type.
>
> I don't see that we're likely to have someone surfing the jira issue
> tracker looking for things to do.
>
> If someone wants to wish for something, the user list (or maybe a wiki
> page) seems like a better place to do it.
>
> All this issue type is doing is collecting work that other people are
> not willing to do themselves.
>
> We already have a "new feature" type that people use when they plan to
> provide patches to implement their new feature.

No one objected to removing "Wish" as an issue type.
Unfortunately, that appears to be beyond my ability to change in the
JIRA system.

Looks like it is defined here:

Issue Type Scheme:  Apache Default Issue Type Scheme

So maybe it's not something we can change solely for our project.

Re: Getting rid of the "wish" issue type

[Mike Kienenberger <mk...@gmail.com>]

Thanks, Manfred.  I forgot to check for closed issues.
I'll take care of those, and make the change when I've done so.

On 9/22/06, Manfred Geiler <ma...@gmail.com> wrote:
> Just created the "MyFaces Issue Type Scheme" but were unable to assign
> it to "MyFaces Core" because there are still 6 "Test" and 3 "Wish"
> issues.
> The "Sub-Task" seems to be a special type and it looks like it is
> mandatory in some way.
>
> Mike, I just gave you jira-admin permissions. Feel free to reorganize
> the issue types according to your proposal (but please be careful
> because your admin permissions allow you to do really bad things not
> only in MyFaces but also in other Jira projects).
>
> Thanks,
> Manfred
>
>
>
> On 9/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > Yeah, I don't seem to have that level of JIRA privs.   I see a couple
> > other strange issue types we probably could also get rid of (Test,
> > subtask->subtask)
> >
> > On 9/22/06, Craig McClanahan <cr...@apache.org> wrote:
> > >
> > >
> > > On 9/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > > On 8/17/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > > > I think we should get rid of the "wish" issue type.
> > > > >
> > > > > I don't see that we're likely to have someone surfing the jira issue
> > > > > tracker looking for things to do.
> > > > >
> > > > > If someone wants to wish for something, the user list (or maybe a wiki
> > > > > page) seems like a better place to do it.
> > > > >
> > > > > All this issue type is doing is collecting work that other people are
> > > > > not willing to do themselves.
> > > > >
> > > > > We already have a "new feature" type that people use when they plan to
> > > > > provide patches to implement their new feature.
> > > >
> > > > No one objected to removing "Wish" as an issue type.
> > > > Unfortunately, that appears to be beyond my ability to change in the
> > > > JIRA system.
> > > >
> > > > Looks like it is defined here:
> > > >
> > > > Issue Type Scheme:  Apache Default Issue Type Scheme
> > > >
> > > > So maybe it's not something we can change solely for our project.
> > > >
> > >
> > > One approach to this would be to clone the "Apache Default Issue Type
> > > Scheme" into a "MyFaces Issue Type Scheme" and make any adjustments, then
> > > assign this scheme to the MyFaces project(s).  I did something like this for
> > > Shale (which shares a JIRA instance with Struts, but has slightly different
> > > requirements) and it has worked out pretty well.
> > >
> > > Craig
> > >
> > >
> >
>

Re: Getting rid of the "wish" issue type

[Manfred Geiler <ma...@gmail.com>]

Just created the "MyFaces Issue Type Scheme" but were unable to assign
it to "MyFaces Core" because there are still 6 "Test" and 3 "Wish"
issues.
The "Sub-Task" seems to be a special type and it looks like it is
mandatory in some way.

Mike, I just gave you jira-admin permissions. Feel free to reorganize
the issue types according to your proposal (but please be careful
because your admin permissions allow you to do really bad things not
only in MyFaces but also in other Jira projects).

Thanks,
Manfred



On 9/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
> Yeah, I don't seem to have that level of JIRA privs.   I see a couple
> other strange issue types we probably could also get rid of (Test,
> subtask->subtask)
>
> On 9/22/06, Craig McClanahan <cr...@apache.org> wrote:
> >
> >
> > On 9/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > On 8/17/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > > I think we should get rid of the "wish" issue type.
> > > >
> > > > I don't see that we're likely to have someone surfing the jira issue
> > > > tracker looking for things to do.
> > > >
> > > > If someone wants to wish for something, the user list (or maybe a wiki
> > > > page) seems like a better place to do it.
> > > >
> > > > All this issue type is doing is collecting work that other people are
> > > > not willing to do themselves.
> > > >
> > > > We already have a "new feature" type that people use when they plan to
> > > > provide patches to implement their new feature.
> > >
> > > No one objected to removing "Wish" as an issue type.
> > > Unfortunately, that appears to be beyond my ability to change in the
> > > JIRA system.
> > >
> > > Looks like it is defined here:
> > >
> > > Issue Type Scheme:  Apache Default Issue Type Scheme
> > >
> > > So maybe it's not something we can change solely for our project.
> > >
> >
> > One approach to this would be to clone the "Apache Default Issue Type
> > Scheme" into a "MyFaces Issue Type Scheme" and make any adjustments, then
> > assign this scheme to the MyFaces project(s).  I did something like this for
> > Shale (which shares a JIRA instance with Struts, but has slightly different
> > requirements) and it has worked out pretty well.
> >
> > Craig
> >
> >
>

Re: Getting rid of the "wish" issue type

[Mike Kienenberger <mk...@gmail.com>]

Yeah, I don't seem to have that level of JIRA privs.   I see a couple
other strange issue types we probably could also get rid of (Test,
subtask->subtask)

On 9/22/06, Craig McClanahan <cr...@apache.org> wrote:
>
>
> On 9/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > On 8/17/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > I think we should get rid of the "wish" issue type.
> > >
> > > I don't see that we're likely to have someone surfing the jira issue
> > > tracker looking for things to do.
> > >
> > > If someone wants to wish for something, the user list (or maybe a wiki
> > > page) seems like a better place to do it.
> > >
> > > All this issue type is doing is collecting work that other people are
> > > not willing to do themselves.
> > >
> > > We already have a "new feature" type that people use when they plan to
> > > provide patches to implement their new feature.
> >
> > No one objected to removing "Wish" as an issue type.
> > Unfortunately, that appears to be beyond my ability to change in the
> > JIRA system.
> >
> > Looks like it is defined here:
> >
> > Issue Type Scheme:  Apache Default Issue Type Scheme
> >
> > So maybe it's not something we can change solely for our project.
> >
>
> One approach to this would be to clone the "Apache Default Issue Type
> Scheme" into a "MyFaces Issue Type Scheme" and make any adjustments, then
> assign this scheme to the MyFaces project(s).  I did something like this for
> Shale (which shares a JIRA instance with Struts, but has slightly different
> requirements) and it has worked out pretty well.
>
> Craig
>
>

Re: Getting rid of the "wish" issue type

[Craig McClanahan <cr...@apache.org>]

On 9/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
>
> On 8/17/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > I think we should get rid of the "wish" issue type.
> >
> > I don't see that we're likely to have someone surfing the jira issue
> > tracker looking for things to do.
> >
> > If someone wants to wish for something, the user list (or maybe a wiki
> > page) seems like a better place to do it.
> >
> > All this issue type is doing is collecting work that other people are
> > not willing to do themselves.
> >
> > We already have a "new feature" type that people use when they plan to
> > provide patches to implement their new feature.
>
> No one objected to removing "Wish" as an issue type.
> Unfortunately, that appears to be beyond my ability to change in the
> JIRA system.
>
> Looks like it is defined here:
>
> Issue Type Scheme:  Apache Default Issue Type Scheme
>
> So maybe it's not something we can change solely for our project.
>

One approach to this would be to clone the "Apache Default Issue Type
Scheme" into a "MyFaces Issue Type Scheme" and make any adjustments, then
assign this scheme to the MyFaces project(s).  I did something like this for
Shale (which shares a JIRA instance with Struts, but has slightly different
requirements) and it has worked out pretty well.

Craig