I'm guessing... you don't have a JIRA account (and aren't signed in)? It's 
possible the admins have it set so that only JIRA users can submit items.

Dan



"Hawkins, Joel" <[EMAIL PROTECTED]> wrote on 07/10/2006 09:09:37 
AM:

> Create New Issue takes me to
> http://issues.apache.org/jira/secure/CreateIssue!default.jspa, which
> doesn't have Muse in the dropdown list. This is where I was before. 
> 
> Signed,
> Dejected in Detroit
> 
> 
> -----Original Message-----
> From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] 
> Sent: Monday, July 10, 2006 8:59 AM
> To: [email protected]
> Subject: RE: JIRA issues and M2
> 
> Hi Joel,
> 
> Looks like the link was broken - I've fixed it, and the mirrors should 
> update in half an hour or so. In the meantime, here's the URL:
> 
>         http://issues.apache.org/jira/browse/MUSE
> 
> From here you can "Create New Issue", and it should select "Muse" as the
> 
> target project by default. Let me know if this is still not working.
> 
> Dan
> 
> 
> 
> "Hawkins, Joel" <[EMAIL PROTECTED]> wrote on 07/10/2006
> 08:24:21 
> AM:
> 
> > Hi Dan,
> > 
> > I'm trying to enter some additional JIRAs for OSGi support and I'm
> > running into some problems. The issues link off of the muse issue
> > tracking page appears to be broken, and when I follow the link back
> from
> > one of your JIRA emails, I get an option to enter a new bug, but the
> > dropdown doesn't allow me to choose Muse as a target project. So my
> > question is, how are you entering JIRAs? 
> > 
> > Thanks,
> > Joel
> > 
> > -----Original Message-----
> > From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, July 10, 2006 12:12 AM
> > To: [email protected]
> > Subject: JIRA issues and M2
> > 
> > Hi everyone,
> > 
> > I've added all of the known features/bugs to JIRA so we can determine
> > what 
> > will go in M2 and the release. Right now I think "everything" can be
> in 
> > the code base by late August, but let me know if I've missed anything
> > (by 
> > adding it to JIRA!). Andrew added an entry for code generation on
> > Friday, 
> > so please reference his earlier updates for the docs and code he has 
> > surrounding that issue.
> > 
> > I'm not a JIRA admin, so I can't set versions for the items or create
> > new 
> > categories yet. I've asked Sal to help us temporarily by creating some
> > new 
> > version tags in the drop down menus, but I will need to be able to do
> > this 
> > on my own as we add new items and new milestones. For the immediate 
> > future, I'm hoping the number of items is small enough that we can
> keep
> > an 
> > email tally of who is doing what, by when.
> > 
> > I will send out my proposal for work-to-be-done (for M2) tomorrow. 
> > Joel/Dennis/Glen - I'm looking to you to tell me who is responsible
> for 
> > item 34 (OSGi support). Andrew and Oliver - I'm hoping you can talk
> and 
> > come to an agreement on what can be done on code generation for M2.
> All 
> > responsibilities for M2 must be declared by this Thursday, prior to
> our 
> > first conference call.
> > 
> > Remember, we want to publish M2 on 8/4/06, so all code changes need to
> > be 
> > in by 7/28/06. That means there's only two weeks between the last
> chance
> > 
> > for issue submission and code submission!
> > 
> > Dan
> > 
> > 
> > Dan Jemiolo
> > IBM Corporation
> > Research Triangle Park, NC
> > 
> > 
> > +++ I'm an engineer. I make slides that people can't read. Sometimes I
> > eat 
> > donuts. +++
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > The contents of this e-mail are intended for the named addressee only.
> 
> It 
> > contains information that may be confidential. Unless you are the
> named 
> > addressee or an authorized designee, you may not copy or use it, or 
> disclose 
> > it to anyone else. If you received it in error please notify us 
> immediately 
> > and then destroy it. 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> The contents of this e-mail are intended for the named addressee only. 
It 
> contains information that may be confidential. Unless you are the named 
> addressee or an authorized designee, you may not copy or use it, or 
disclose 
> it to anyone else. If you received it in error please notify us 
immediately 
> and then destroy it. 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to