Thanks Sebb,
Look good to me.
regards
On Sunday, March 26, 2017, sebb wrote:
> I see.
>
> The existing "Version" field is intended to record the version to
> which the report applies.
>
> There is also an advanced field (click on "Show Advanced Fields")
> called "Target Milestone" whose hover t
I see.
The existing "Version" field is intended to record the version to
which the report applies.
There is also an advanced field (click on "Show Advanced Fields")
called "Target Milestone" whose hover text is:
"The Target Milestone field is used to define when the engineer the
bug is assigned
Hi,
@Felix, you read correctly but the nighlty might be confusing if we forget
to move the fix version once we release
Something like 3.2-SNAPSHOT might be clearer no?
Regards
On Saturday, March 25, 2017, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:
>
>
> Am 25. März 2017 13:50:0
Am 25. März 2017 13:50:01 MEZ schrieb sebb :
>On 25 March 2017 at 09:20, Philippe Mouawad
> wrote:
>> Hello,
>> What do you think of adding to bugzilla a new field "FIX VERSION"
>which we
>> would use to indicate in which version bug is fixed (JIRA has such
>field).
>>
>> We could then use a sear
On 25 March 2017 at 09:20, Philippe Mouawad wrote:
> Hello,
> What do you think of adding to bugzilla a new field "FIX VERSION" which we
> would use to indicate in which version bug is fixed (JIRA has such field).
>
> We could then use a search query to find all bugs fixed in any version but
> als
Am 25. März 2017 10:20:59 MEZ schrieb Philippe Mouawad
:
>Hello,
>What do you think of adding to bugzilla a new field "FIX VERSION" which
>we
>would use to indicate in which version bug is fixed (JIRA has such
>field).
>
>We could then use a search query to find all bugs fixed in any version
>bu
