Re: [sv-bc] master issues

From: Neil Korpusik <neil.korpusik@oracle.com>
Date: Tue Feb 03 2015 - 16:14:12 PST
Hi Shalom,

I took a look and came up with a possible solution.

There is a Mantis field called "Fixed in Version". We could come up with a
dummy "version" whose sole purpose is to flag this set of mantis items.
Since we are able to define the set of versions being tracked, we should be
able to use a somewhat arbitrary string. Something like the following
could be used. I see that we already have a couple of versions defined which
contain a blank character, so the following should be legal for the
"Product Version" field.

    Master Issues


Neil



On 02/03/15 01:11, Bresticker, Shalom wrote:
> Hi,
>
> A long time ago, when I started creating master issues in Mantis, mostly
> for SV-BC, I looked for a way to give them a special classification that
> could be used as a filter in searches. Originally there was nothing.
>
> Eventually, ‘block’ appeared as an option in Severity. It sounded to me
> like it meant ‘a block of issues’, which was what I was looking for. I
> started changing the master issues to ‘block’. I did not understand why
> it is in Severity, but there is not always logic in these things.
>
> A few months ago, it came to my attention that the meaning of ‘block’ as
> a severity was intended to be like ‘showstopper’, i.e., ‘blocks completion’.
>
> Does anyone have a suggestion what I should do with these master issues?
>
> Thanks,
>
> Shalom
>
> Shalom Bresticker
> Communications & Storage Infrastructure Group Design Automation
>
> Intel Jerusalem, Israel
> +972 2 589 6582 (office)
> +972 54 721 1033 (cell)
> http://www.linkedin.com/in/shalombresticker
>
> The devil is in the details.
>
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Tue Feb 3 16:14:27 2015

This archive was generated by hypermail 2.1.8 : Tue Feb 03 2015 - 16:14:43 PST