From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: Unexpected bugzilla behaviour
Date: Tue, 29 May 2012 11:12:41 +0100 [thread overview]
Message-ID: <1338286361.20169.101.camel@ted> (raw)
In-Reply-To: <1860364.RiBI5vjcRR@helios>
On Tue, 2012-05-29 at 10:57 +0100, Paul Eggleton wrote:
> On Monday 28 May 2012 11:39:46 Gary Thomas wrote:
> > I was making a reply to bug #1570 and the next thing I know I had
> > a full-up page for bug #1587 where I errantly added an attachment.
> >
> > My recall was that bugzilla would stay with the bug you're working
> > on - I could make a comment and then add an attachment without leaving
> > the same bug report. That doesn't seem to be the case now and it
> > left me not only confused but putting comments and attachments in
> > the wrong place.
> >
> > Did this change with the bugzilla "upgrade"?
>
> AFAIK Bugzilla has always had this mis-feature. The worst thing is it's not
> consistent - if you didn't have a bug "list" (previous search results) then it
> will stay on the current bug.
>
> I've even heard of a Firefox add-on that will override this behaviour, but I
> never looked into it.
Its always done this but there is an option in your preferences to stop
it doing it. I know I set that a while ago for me and it is still set
after the upgrade...
Cheers,
Richard
prev parent reply other threads:[~2012-05-29 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 17:39 Unexpected bugzilla behaviour Gary Thomas
2012-05-29 9:57 ` Paul Eggleton
2012-05-29 10:12 ` Richard Purdie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1338286361.20169.101.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=paul.eggleton@linux.intel.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.