From: Sven <sven.hoehn@posteo.de>
To: ipfire-artwork@lists.ipfire.org
Subject: Re: [IPFire Artwork] Bugzilla
Date: Wed, 26 Apr 2017 13:47:50 +0200 [thread overview]
Message-ID: <A80EEBB3-4FA7-45D6-9BA5-16AD23E35829@posteo.de> (raw)
In-Reply-To: <1493028708.3373.21.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
Hello.
Has someone already put a bug into the Redesign category?
Do I get a notification if someone put something in there?
Greetings,
Sven
> On 24. Apr 2017, at 12:11, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>
> Hi,
>
> On Mon, 2017-04-24 at 12:02 +0200, Maurice Gesswein wrote:
>> Hi,
>>
>> I'm going to write some bug reports related to dev.ipfire.org. As far as I see
>> there is no component in Bugzilla for dev.ipfire.org. There is only a general
>> "Web Site" component. Should I use that component for my reports and refer
>> to dev.ipfire.org?
>
> Yes, please use that one.
>
>> I also remember and see the umbrella bug "Big Website Relaunch". I assume that
>> bugs related to dev.ipfire.org should be somehow linked to that umbrella bug.
>> How does it work? I see nothing helpful on the "new bug" form. Is there a
>> hidden mechanism which links a new bug reports to that umbrella bug whenever I
>> refer to that by writing "#11314" (umbrella bug ID) in the summary?
>
> You can just add the bug ID in the "blocks" field. That will automatically
> connect the two bug reports.
>
> Sorry if I have not been clear about this :) Ask me if there is anything else I
> forgot to mention.
>
> -Michael
>
>>
>> Best,
>> Maurice
next prev parent reply other threads:[~2017-04-26 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPxcDEsoPsOj9RtjY4umt9intPTDHRJW3YzhRJNP4nMLwWeASA@mail.gmail.com>
2017-04-24 10:11 ` Michael Tremer
2017-04-26 11:47 ` Sven [this message]
[not found] <CAPxcDEtur+1+jGf-3zPpJ_0MNAKFDUp1b_CNm-rWRp8JRArsfQ@mail.gmail.com>
2017-05-03 19:12 ` Michael Tremer
2017-05-03 19:16 ` Sven
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=A80EEBB3-4FA7-45D6-9BA5-16AD23E35829@posteo.de \
--to=sven.hoehn@posteo.de \
--cc=ipfire-artwork@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox