Re: [ANN] Changing the default bug view for BMO

[David Lawrence]

Unfortunately, we will need to postpone the changeover and it will not
be happening tomorrow as announced. Due to some unplanned changes
related to security and also some blockers are still being worked on, it
has taken longer then expected to bring you the best possible experience
for the new default bug page.

Also special thanks to Marco Zehe for his invaluable feedback and
testing for some remaining accessibility issues with the new modal bug page.

Will keep you posted.
dkl

On Friday, January 13, 2017 at 5:04:35 PM UTC-5, dlaw...@mozilla.com
 wrote:
> Due to some fixes that are taking longer than expected so we are going
to push the cutover date to January 30th, 2016. Sorry for the delay.
>
> Follow along at:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1150541

>
> Thanks
> BMO Team
>
> On Friday, January 6, 2017 at 12:11:50 PM UTC-5, dlaw...@mozilla.com
 wrote:
> > Announcement: Changing the default bug view for BMO
> >
> >As some of you may already know, and maybe even have been using
it for a while, the BMO [1] team has been working on a new bug view page
((a.k.a show_bug.cgi) for some time [2] . The older, stock bug form was
not well laid out and was difficult to understand, with all of the
fields visible regardless of how often they were used. The stock form
was originally designed to  display all of a bug’s data , and users had
to adapt their workflows accordingly.. The BMO team designed a 
completely new and more efficient view for the workflows of the majority
of BMO users.
> >
> >The new bug-editing form has been added to BMO alongside the
stock form and can be enabled by toggling a user preference [3]. We have
been incrementally improving it and collecting feedback by those brave
enough to use it early on. The new form is using more modern design
practices and therefore is easier for us to improve and expand on. Any
new enhancements will be done only on the new form going forward. It was
code named ‘Bug Modal’ due to the modular layout of the page. Each
submodule can be collapsed out of view and expanded when needed.
> >
> >At this time we feel that the form is feature complete and ready
to become the new default bug form for BMO. We have been tracking the
final blockers in a bug report [4], and the last blockers are being
wrapped up this week. We wanted to let everyone know of the coming
changeover in advance so that we can get last-minute feedback. The
older, stock bug view form will still be around, and we will update the
user preference to let users switch back to the old one[3]. In the
future, we will be removing the old form altogether after fixing a few
more bugs[6], and we will make another announcement beforehand. Removing
the old code will make it easier on us from a maintenance standpoint.
> >
> >Barring any issues with landing the last blockers, we are hoping
to do the changeover on January 16th, 2017. Until then, if this is the
first time you have heard of this new feature,  go ahead and give it a
try. Any bugs, comments, or ideas for improvement of the modal form can
be reported in BMO [5].
> >
> > Thanks!
> > BMO Team
> >
> > [1] https://bugzilla.mozilla.org
> > [2] https://globau.wordpress.com/2015/03/31/bmo-new-look/

> > [3]
https://bugzilla.mozilla.org/userprefs.cgi?tab=settings#ui_experiments_row

> > [4] https://bugzilla.mozilla.org/show_bug.cgi?id=1150541

> > [5]
https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=User%20Interface:%20Modal

> > [6] https://bugzilla.mozilla.org/show_bug.cgi?id=1273046


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

ANN: Finally changing the default bug view for BMO on March 1st, 2017

[David Lawrence]

tl;dr

   On March 1st, 2017, the BMO Team is going to make another attempt at
changing the default bug view to the new modal view that has been in
development for a while. For those who would like to use the old form,
instructions on how to switch back are below in the background
information. The old form will however be removed one day so please try
to use the new one and make suggestions on how it can be improved.

Thanks!

Background:

As some of you may already know, and maybe even have been using it
for a while, the BMO [1] team has been working on a new bug view page
(a.k.a show_bug.cgi) for some time [2] . The older, stock bug form was
not well laid out and was difficult to understand, with all of the
fields visible regardless of how often they were used. The stock form
was originally designed to  display all of a bug’s data, and users had
to adapt their workflows accordingly.. The BMO team designed a
completely new and more efficient view for the workflows of the majority
of BMO users.

The new bug-editing form has been added to BMO alongside the stock
form and can be enabled by toggling a user preference [3]. We have been
incrementally improving it and collecting feedback by those brave enough
to use it early on. The new form is using more modern design practices
and therefore is easier for us to improve and expand on. Any new
enhancements will be done only on the new form going forward. It was
code named ‘Bug Modal’ due to the modular layout of the page. Each
submodule can be collapsed out of view and expanded when needed.

At this time we feel that the form is feature complete and ready to
become the new default bug form for BMO. We have been tracking the final
blockers in a bug report [4], and the last blocker(s) are being wrapped
up this week. We wanted to let everyone know of the coming
changeover in advance so that we can get last-minute feedback. The
older, stock bug view form will still be around, and we will update the
user preference to let users switch back to the old one [3]. In the
future, we will be removing the old form altogether after fixing a few
more bugs [6], and we will make another announcement before doing so.
Removing the old code will make it easier on us from a maintenance
standpoint.

Barring any issues with landing the last blocker(s), we are hoping
to do the changeover on March 1st, 2017. Until then, if this is the
first time you have heard of this new feature,  go ahead and give it a
try. Any bugs, comments, or ideas for improvement of the modal form can
be reported in BMO [5].
Thanks!
BMO Team

[1] https://bugzilla.mozilla.org
[2] https://globau.wordpress.com/2015/03/31/bmo-new-look
[3]
https://bugzilla.mozilla.org/userprefs.cgi?tab=settings#ui_experiments_row
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=1150541
[5]
https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=User%20Interface:%20Modal
[6] https://bugzilla.mozilla.org/show_bug.cgi?id=1273046


-- 
David Lawrence
d...@mozilla.com
bugzilla.mozilla.org
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

ANN: Default bug view for BMO changed today!

[David Lawrence]

   Today, the BMO Team changed the default bug view to the new modal
view that has been in development for a while. For those who would like
to use the old form, instructions on how to switch back are below in the
background information. The old form will, however, be removed one day,
so please try to use the new one and make suggestions on how it can be
improved.

As some of you may already know, and maybe even have been using it
for a while, the BMO [1] team has been working on a new bug view page
(a.k.a. show_bug.cgi) for some time [2] . The older, stock bug form was
not well laid out and was difficult to understand, with all of the
fields visible regardless of how often they were used. The stock form
was originally designed to  display all of a bug’s data, and users had
to adapt their workflows accordingly. The BMO team designed a completely
new and more efficient view for the workflows of the majority of BMO users.

The new bug-editing form has been added to BMO alongside the stock
form and can be enabled by toggling a user preference [3]. We have been
incrementally improving it and collecting feedback by those brave enough
to use it early on. The new form is using more modern design practices
and therefore is easier for us to improve and expand on. Any new
enhancements will be done only on the new form going forward. It was
code named ‘Bug Modal’ due to the modular layout of the page. Each
submodule can be collapsed out of view and expanded when needed.

At this time we feel that the form is feature complete and has now
become the new default bug form for BMO. We have finished all the
blockers in our tracking bug report [4]. The older, stock bug view form
will still be around, and you can use the user preferences form to
switch back to the old one [3]. In the future, we will be removing the
old form completely after fixing a few more bugs [6], and we will make
another announcement before doing so. Removing the old code will make it
easier on us from a maintenance standpoint. Any bugs, comments, or ideas
for improvement of the modal form can be reported in BMO [5].

Thanks!
BMO Team

[1] https://bugzilla.mozilla.org
[2] https://globau.wordpress.com/2015/03/31/bmo-new-look
[3]
https://bugzilla.mozilla.org/userprefs.cgi?tab=settings#ui_experiments_row
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=1150541
[5]
https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=User%20Interface:%20Modal&format=__default__
[6] https://bugzilla.mozilla.org/show_bug.cgi?id=1273046
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: ANN: Default bug view for BMO changed today!

[David Lawrence]

Thanks for the feedback. Please file this as a bug if you haven't
already, outlining the proposed workflow change. I could see how
automatically exposing the milestone form field when resolving a bug
could be useful for a lot of people.

Thanks
dkl

On 3/2/17 3:13 AM, Jörg Knobloch wrote:
> On 01/03/2017 21:47, David Lawrence wrote:
>> Today, the BMO Team changed the default bug view to the new modal
>> view that has been in development for a while.
> 
> I like the fact that you can now change the Product in one step.
> 
> Sadly when resolving a bug, there's now an additional click necessary on
> "Edit Bug" to set the Target Milestone. And at least once I had to click
> once more to expand the Tracking section.
> 
> Sorry, some people have never happy with progress ;-)
> 
> Jörg.
> 
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform

-- 
David Lawrence
d...@mozilla.com
bugzilla.mozilla.org
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

BMO Version Upgrade Testing and Feedback Needed by April 25th, 2016

[David Lawrence]

Greetings,

The Mozilla Bugzilla Team (B-Team) is happy to announce the test release
of the next version of bugzilla.mozilla.org (BMO) based on the upstream
Bugzilla code base. Although we have backported a lot of cool stuff over
the years from upstream, it is still beneficial for Mozilla to run a
more modern version of Bugzilla. This will allow for easier porting of
new features to the BMO code base, as well as allowing upstream to use
some BMO customizations.

We are hoping to have the upgrade completed by April 25, 2016. Please
let us know if that date will have any negative impact on development
schedules.

Please test drive at https://bugzilla-merge.allizom.org.

The main areas of focus for our test releases are stability,
performance, and reliability. Functionality that currently works in our
code base installed at https://bugzilla.mozilla.org should continue to
work as expected in the new version. Please let us know of any
customizations that may be missing as well. There are also numerous new
features/fixes that are part of the upstream code base, such as Markdown
support in comments and better HTML5 support, to name a couple.

Also, please test your various scripts and third-party applications,
such as dashboards, that use the XMLRPC/JSON/REST APIs with the test
server to make sure they continue to function properly.

The database is a sanitized snapshot of the live database so should be
useful for testing to make sure the information is displayed properly
and changeable. Please ping someone in #bteam IRC channel to set your
password as passwords have been removed.

Also note, email has been disabled so that unnecessary spam is not sent
out. So feel free to make changes to bugs to verify proper working order.

We are asking for anyone who has a few spare minutes to get involved and
provide testing and feedback.

Please file bug reports in the production BMO system at
https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&version=development


Thanks,
The Mozilla Bugzilla Team
https://wiki.mozilla.org/BMO
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

BMO Version Upgrade Testing and Feedback Needed by May 2nd, 2016

[David Lawrence]

My apologies. We will need to move this out a week to accommodate the
new Firefox release on April 26th. We do not want our migration to
interrupt the release process so better to do it after.

More time for quality testing and feedback! :)

Thanks
dkl


 Forwarded Message 
Subject: BMO Version Upgrade Testing and Feedback Needed by April 25th, 2016
Date: Mon, 11 Apr 2016 19:58:53 -0700 (PDT)
From: dlawre...@mozilla.com
To: mozilla-tools-...@lists.mozilla.org
Newsgroups: mozilla.tools.bmo

Greetings,

The Mozilla Bugzilla Team (B-Team) is happy to announce the test release
of the next version of bugzilla.mozilla.org (BMO) based on the upstream
Bugzilla code base. Although we have backported a lot of cool stuff over
the years from upstream, it is still beneficial for Mozilla to run a
more modern version of Bugzilla. This will allow for easier porting of
new features to the BMO code base, as well as allowing upstream to use
some BMO customizations.

We are hoping to have the upgrade completed by April 25, 2016. Please
let us know if that date will have any negative impact on development
schedules.

Please test drive at https://bugzilla-merge.allizom.org.

The main areas of focus for our test releases are stability,
performance, and reliability. Functionality that currently works in our
code base installed at https://bugzilla.mozilla.org should continue to
work as expected in the new version. Please let us know of any
customizations that may be missing as well. There are also numerous new
features/fixes that are part of the upstream code base, such as Markdown
support in comments and better HTML5 support, to name a couple.

Also, please test your various scripts and third-party applications,
such as dashboards, that use the XMLRPC/JSON/REST APIs with the test
server to make sure they continue to function properly.

The database is a sanitized snapshot of the live database so should be
useful for testing to make sure the information is displayed properly
and changeable. Please ping someone in #bteam IRC channel to set your
password as passwords have been removed.

Also note, email has been disabled so that unnecessary spam is not sent
out. So feel free to make changes to bugs to verify proper working order.

We are asking for anyone who has a few spare minutes to get involved and
provide testing and feedback.

Please file bug reports in the production BMO system at
https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&version=development

Thanks,
The Mozilla Bugzilla Team
https://wiki.mozilla.org/BMO
___
tools-bmo mailing list
tools-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/tools-bmo


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Triage Plan for Firefox Components

[David Lawrence]

I used to think it should be called "Abstract". Sort of a summarization
of the bug itself.

dkl

On 04/12/2016 05:02 PM, Emma Humphries wrote:
> This is probably a field that could stand to be re-labled, as I was
> blithely thinking (and I would guess others are) that it was for features,
> only.
> 
> -- Emma
> 
> On Tue, Apr 12, 2016 at 1:01 PM, Mark Côté  wrote:
> 
>> On 2016-04-07 2:50 AM, L. David Baron wrote:
>>> (I'd much rather a bug report be editable text, with history
>>> available, for answers to these or similar questions -- rather than
>>> a stream of permanent comments.  But we seem stuck with the horrid
>>> stream-of-comments Bugzilla format, which means I try to ignore the
>>> comments as much as I can.  Then again, a 200 character summary is
>>> often good enough to answer the above 5 questions.  As with the rest
>>> of the Internet, don't read the comments.)
>>
>> Meant to reply to this earlier... BMO has a User Story field that sounds
>> like it does exactly what you want.  It's an editable field that keeps
>> history (admittedly not in an easy-to-read way, but that could be
>> improved).  Despite the name of the field, I've found it useful for
>> summarizing the current state of the discussion in the bug (sometimes
>> along with the "obsolete" comment tag).
>>
>> Mark
>>
>> ___
>> dev-platform mailing list
>> dev-platform@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-platform
>>
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
> 

-- 
David Lawrence
d...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Target Milestone field in bugzilla

[David Lawrence]

On 01/09/2014 12:47 PM, Gavin Sharp wrote:
> It should be possible to have the field label change only for a
> specific set of products, in theory. Having the ability to customize
> on a per-product basis like this would make a lot of these proposals
> easier. I think we should ask our b.m.o devs (dkl, glob) to determine
> the feasibility of that solution.

Currently Bugzilla does not support relabeling of fields in the UI based
on some criteria. They are pretty well hard coded with the names. It would
be a non-trivial amount of work to add the support and it would definitely
not be something we could shift upstream. So we would need to maintain the
customization going forward.

With the build out work we are doing with the webservices API, it seems to
me it would be more appropriate to just incorporate the name changes in the
various third party UIs and dashboards that the different teams use. They
can change the milestone values using the alternative UI.

dkl


-- 
David Lawrence
d...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

BzAPI Compatibility API has been rolled out to production BMO

[David Lawrence]

  Until recently, Bugzilla supported only older Web technologies, namely XMLRPC 
and JSONRPC. The BMO team created a new REST API
in the summer of 2013 to provide a modern Web interface to Bugzilla.

  Prior to the native REST API[1], a separate proxy service called BzAPI[2] was 
created that provided a REST API using data
obtained through the older RPC interfaces as well as various other Bugzilla 
data sources, including CSV representations. This
was a great interim solution, but now that we have a native API, and since the 
system hosting the proxy is not maintained by
Mozilla IT, the BzAPI service will need to be decommissioned at some point. 
Check out the wiki page[3] for the differences
between BzAPI and the native API.

  To ease the transition, we have created a native BzAPI compatibility layer 
(bug 880669[4]) that acts almost exactly the same
as BzAPI but will translate the queries to the native API layer. Thus clients 
who currently use BzAPI will just need to change
the REST URL to the built-in API[5], which is slightly different from the 
native one[6].

  Even though we've done our own testing, we are interested in having more 
people test the compat API by changing their
dashboards, scripts, apps, etc. to point to the compat API URL instead of the 
BzAPI proxy. Then try to see if anything doesn't
display properly, is missing, or generates an error of some kind. We have a 
component[7] in Bugzilla under the BMO product that
we would like people to use to let us know. You can also browse[8] for bugs 
that have already been submitted.

  We plan to leave the compat API in place for the foreseeable future, but we 
do not plan to make any major changes or
enhancements to it. We will be working to enhance the native REST API instead 
with the upstream Bugzilla community. So any
requests for improvements or new features will need to be directed the native 
API component[9].

Thanks
Mozilla BMO Team

[1] https://wiki.mozilla.org/BMO/REST
[2] https://wiki.mozilla.org/Bugzilla:REST_API
[3] https://wiki.mozilla.org/Bugzilla:API_Comparison
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=880669
[5] https://bugzilla.mozilla.org/bzapi
[6] https://bugzilla.mozilla.org/rest
[7] 
https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Extensions%3A%20BzAPI%20Compatibility
[8] 
https://bugzilla.mozilla.org/buglist.cgi?product=bugzilla.mozilla.org&component=Extensions%3A%20BzAPI%20Compatibility
[9] 
https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=WebService
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Unplanned Phabricator Update - April 30th 2019 between 14:00 and 15:00 UTC

[David Lawrence]

Due to missing the normal update window normally on Mondays, we will be 
deploying a Phabricator [1] update
to add new functionality tomorrow April 30th between 14:00 and 15:00 UTC 
(10:00am ET).


Upgrades usually have no visible impact on the user; however, some 
updates may cause Phabricator to be partially unavailable

during this window.

If you have any questions about this, we’re available in #phabricator on 
slack for any questions and concerns.



Regards,


David Lawrence

Engineering Workflow Team.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Unplanned Phabricator Update - Thursday May 2nd 2019 between 14:00 and 15:00 UTC

[David Lawrence]

Due to issue discovered with the last update, we will be
deploying a Phabricator [1] update to fix the issue on Thursday
May 2nd between 14:00 and 15:00 UTC (10:00am ET). 

Upgrades usually have no visible impact on the user; however, some
updates may cause Phabricator to be partially unavailable
during this window.

If you have any questions about this, we’re available in #phabricator
on slack for any questions and concerns.

Regards,

David Lawrence
Engineering Workflow Team.


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Unplanned Phabricator Update - June 4th 2019 between 14:00 and 15:00 UTC

[David Lawrence]

Due to missing the normal update window normally on Mondays, we will be 
deploying a Phabricator  update
to add new functionality tomorrow June 4th between 14:00 and 15:00 UTC 
(10:00am ET).


Upgrades usually have no visible impact on the user; however, some 
updates may cause Phabricator to be partially unavailable

during this window.

If you have any questions about this, we’re available in #phabricator on 
slack for any questions and concerns.



Regards,


David Lawrence

Engineering Workflow Team.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

[ANNOUNCEMENT] bugzilla.mozilla.org outage: November 9th, 11:00 AM EST (16:00 UTC)

[David Lawrence]

Bugzilla.mozilla.org will be down for maintenance work on Saturday, 
November 9th, from 11:00 AM EST (16:00 UTC) for approximately four hours.



Various maintenance tasks will be performed during that time period such 
as upgrading of the database to a newer version of MySQL on RDS.



If any issues occur requiring a longer outage, notifications will be 
sent to the appropriate lists and Slack channels. Slack channel #bmo can 
also be used for any concerns or questions.



Thanks

BMO Team

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Phabricator Update Moved to Tuesday 10:00 AM EST

[David Lawrence]

Normally we do Phabricator release updates for 
phabricator.services.mozilla.com on Mondays at 10:00 AM EST. This coming

weeks update will occur Tuesday at the same time instead.

Thanks
dkl

--
David Lawrence
d...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200211.1)

https://bugzil.la/1613686 : Improper encoding of content-type, 
content-transfer-encoding for security reports causes content to not be 
displayed properly
https://bugzil.la/1556727 : Replace “Email sent to” message with a toast 
notification
https://bugzil.la/1611281 : Double-escaping of '<' in code areas
https://bugzil.la/1611494 : Bugzilla custom email headers are getting mashed 
together
https://bugzil.la/1612287 : Issue with negation operator in query search

-- 
David Lawrence
d...@mozilla.com

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

happy bmo push day!

https://bugzil.la/1612290 : Provide self-service UI for users to
reactivate their account after being disabled due to bouncing

One notable change that was pushed live to production today was the
ability to self-service your own account if you get blocked due to email
bouncing issues. Now if your email bounces, instead of not being able to
login completely, your email notifications will be temporarily disabled
but you will still be able to login. You will see a banner message
stating that your email has been disabled with a link to a page where
you can turn it back on.

The linked page will display the error messages returned from the
upstream mail relay and display a form to turn on your email. Please do
not enable email if you are not sure the bouncing issue has been resolved.

A internal counter will allow you to reactivate your email notifications
up to five times in a thirty day period. On the fifth time, your account
will be disabled for login and you will need an admin to reactivate the
account similar to the process before.

This new feature should hopefully help BMO admins to not have to deal
with the majority of intermittent email bounce issues and instead allow
the user to admin their own account when they happen.

The following other changes have been pushed to bugzilla.mozilla.org
<http://bugzilla.mozilla.org>:

https://bugzil.la/1617358 : Extra slash in the "phabricator review
requests" link's url on the BMO dashboard
https://bugzil.la/1591549 : Hide bugs in dependencies and regression
fields from users without access
https://bugzil.la/1237874 : File size unit always plural: "1 bytes"
https://bugzil.la/1599865 : Bug description is erased during page load,
leading to dataloss during Firefox session restore
https://bugzil.la/1472757 : Comment field empty after clicking "go back
page"
https://bugzil.la/1614634 : 13 hours ago wasn't "1 day ago"

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200226.1
<https://github.com/mozilla-bteam/bmo/tree/release-20200226.1>)

-- 
David Lawrence
d...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200401.1)

https://bugzil.la/1621662 : Remove option for using Vagrant for BMO development 
and support Docker as primary method
https://bugzil.la/1621160 : First row of stagger column headers will be hidden 
when table header becomes sticky
https://bugzil.la/1621278 : Make bug IDs on search results proper bug links
https://bugzil.la/1622956 : Update contact emails and URLs
https://bugzil.la/1344094 : Add a link to a wiki.mozilla.org page describing 
how to request a keyword
https://bugzil.la/1623727 : Graphviz needs to be installed in bmo-slim base 
container to allow showdependencygraph.cgi to work properly
https://bugzil.la/849902 : my dashboard should be able to refresh on its own
https://bugzil.la/1370492 : "Assigned to you" in My dashboard should show bugs 
priority
https://bugzil.la/1183759 : keyword suggestions should not show keywords which 
have been already selected
https://bugzil.la/1410994 : Add utility for mass-disabling stale accounts


dkl
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

BMO Down for Maintenance Saturday April 18th starting at 9:00 AM EDT (1:00 PM UTC)

[David Lawrence]

  BMO (bugzilla.mozilla.org) will be down for database maintenance this 
Saturday, April 18th. The maintenance will
start around 9:00 AM EDT (1:00 PM UTC). We do not expect it go longer 
than 4 hours but will keep everyone posted if it

ends up taking longer.

  This outage will of course affect other systems that rely on BMO such 
as Phabricator and Lando. So you may see

some issues with those systems as well.

Thanks
David Lawrence
BMO Team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

[ANNOUNCEMENT] BMO development instance bugzilla-dev.allizom.org will have its data refreshed on Friday May 8th

[David Lawrence]

The database for bugzilla-dev.allizom.org, which is our testing instance 
of BMO, has data that was last synchronized from

production on July, 2017.

On Friday, May 8th, we will be switching over to a newer import of test 
data that is more in sync with data from production.
The data is of course sanitized and all private information has been 
removed. This also includes passwords which means you
will need to do a password reset for your account if you want to access 
bugzilla-dev.allizom.org for testing. To make things
more complicated, all email is normally disabled for the system so a BMO 
administrator will need to reset the password for you.


To access your account on bugzilla-dev.allizom.org after May 8th, 
contact a BMO administrator either in #bmo on Slack, or
#bugzilla.mozilla.org on Matrix. You can also email 
bmo-m...@mozilla.com.  We will be happy to help.


Thanks
BMO Team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200429.1)

https://bugzil.la/1631051 : The current setting of the auto-refresh button in 
My dashboard should be stored
https://bugzil.la/1631971 : Create link to Matrix support channel for each 
product
https://bugzil.la/1632038 : Remove number of people from bug update toast 
notification
https://bugzil.la/1632624 : When adding vars to the fields data that is logged 
to stack driver, convert to a JSON string
https://bugzil.la/1632994 : [Bugzilla.App] Can't use an undefined value as a 
subroutine reference at /app/Bugzilla/Error.pm line 94.
https://bugzil.la/1633848 : Fix possible areas where memory leak can occur in 
the PhabBugz daemon code
https://bugzil.la/1623009 : Long password denial of service in 
bugzilla.mozilla.org

Thanks
BMO Team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200511.1)

https://bugzil.la/1633846 : Enable retries for uploading attachments to S3 when 
an error occurs
https://bugzil.la/1636549 : Guided Bug Helper extension filing bugs with 
'normal' instead of '--' severity.
https://bugzil.la/1634342 : change links for security approval documents to 
source docs
https://bugzil.la/1594066 : reproducible "Can't use ARRAY(0x17340610) as a field 
name." when Custom Search used
https://bugzil.la/1635332 : [SECURITY] Upgrade Mojolicous to 8.42
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200526.1)

https://bugzil.la/1638022 : Phabbugz should not try to set needs-review when 
the revision is closed or abandoned
https://bugzil.la/1639311 : Attaching a file with emojis breaks them
https://bugzil.la/1639903 : Fix `Use of uninitialized value in pattern match 
(m//) at /app/Bugzilla/App.pm line 71`
https://bugzil.la/1639902 : Fix `Use of uninitialized value in string eq at 
/app/Bugzilla/Bug.pm line 4674`

dkl
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200603.1)

https://bugzil.la/1641249 : Enable the crash signature field for the Focus and 
Fenix Stability components
https://bugzil.la/1641897 : Cleanup old severity values in custom forms and 
other places
https://bugzil.la/1641117 : Add Sentry to the list of See Also URLs.
https://bugzil.la/1642654 : Add ability for users to reactivate their own 
account when disabled from inactivity


David Lawrence
d...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200624.1)

https://bugzil.la/1643821 : Add code to generate_conduit_data.pl to create an 
oauth2 client for Phabricator when used for development
https://bugzil.la/1645455 : Can't attach some text, 500 internal server error
https://bugzil.la/1646559 : Phabricator to BMO OAuth2 authentication fails to 
work properly due to CSP protections

David Lawrence
d...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200722.1)

https://bugzil.la/1645768 : Please add 'See Also' support for GitLab
https://bugzil.la/1651591 : BMO attempts to preload FiraSans, which was 
replaced with FiraGO in May 2019
https://bugzil.la/1652863 : setting the needinfo flag when filing a new bug in 
Core or Toolkit does not cause the textbox for user information to pop up


dkl

David Lawrence
dklaw...@gmail.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200805.1)

https://bugzil.la/1643526 : Attachment comments don't render markdown,
but their preview does
https://bugzil.la/1654456 : [needinfo] Provide instructions and
guidance when needinfo is requested of the bug's reporter
https://bugzil.la/1654370 : Remove remaining code that references
Firefox OS from BMO code base
https://bugzil.la/1655808 : Send guided bug flow users to GitHub for
Fenix issues

-- 
David Lawrence 
Mozilla, Inc.

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200908.1)

https://bugzil.la/1657542 : During recent bmo deployment, emails were delivered 
to a file instead of SES which caused interruption of email service
https://bugzil.la/1658622 : "product responsibilities" on editusers should 
include Triage Owner
https://bugzil.la/1588661 : Design for WebHooks
https://bugzil.la/1659177 : Replace mozillians.org with people.mozilla.org in 
Reps Mentorship From
https://bugzil.la/1649841 : Include data-review? requests in notification count
https://bugzil.la/1658317 : Make scopes more descriptive and user friendly when 
authenticating to BMO using OAuth2
https://bugzil.la/1657778 : Offer link to Bugzilla for filing security issues 
in Fenix and iOS
https://bugzil.la/1658846 : Allow users to enable and disable their webhooks
https://bugzil.la/1658845 : Allow users to see their own queue for their 
webhooks
https://bugzil.la/1662747 : Version number not visible in bug query results 
because of Long version numbers
(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200910.1)

https://bugzil.la/1658841 : Webhooks should include comments added to a bug
https://bugzil.la/1661042 : Add a new table profile_iam to contain mappings 
between BMO accounts and LDAP accounts

dkl
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

happy bmo push day!

[David Lawrence]

the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200928.1)

https://bugzil.la/1665916 : Remove block severity from blocklist bug creation 
template
https://bugzil.la/1665891 : Overlaid image viewer is not full in height
https://bugzil.la/1666292 : Blue "New comments" popup not clickable
https://bugzil.la/1666917 : Remove code from PhabBugz extension dealing with 
auth delegation since it is no longer used
https://bugzil.la/1667201 : Replace Reps profile with Community Portal profile 
in Reps Budget and Swag forms
https://bugzil.la/1667321 : release tracking report hardcodes old date ranges

dkl

David Lawrence
Bugzilla Senior Software Engineer
d...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

[OUTAGE] Phabricator (phabricator.services.mozilla.com) to be down for maintenance on Sat Mar 13th at 12:00 PM EST (17:00 UTC)

[David Lawrence]

On Saturday, March 13th, at 12:00PM EST (17:00 UTC), Phabricator will be 
taken down for a period

of two hours for database maintenance.

A recent upstream migration requires a change to one of the larger 
tables that could cause Phabricator
to be unresponsive. So we decided best to do the changes during off 
hours. Also, taking the system
down will allow us to roll back to a database backup if  any issues 
occur.


Systems affected:
* https://phabricator.services.mozilla.com - Phabricator will be 
unavailable during the database upgrade.
* https://lando.services.mozilla.com - Lando requires access to 
Phabricator for various tasks so it

  should not be used during the outage.
* https://bugzilla.mozilla.org - Bugzilla displays current revision data 
in some bug reports so that

  functionality could be affected.

For any comments or questions, you can find us in #phabricator on Slack.

Thanks
Phabricator Team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform