Re: Does anybody think feedback saying "nothing changed" is useful?

Hi George:

In message <[email protected]>,
Georg Lehner writes:
>On 04/20/2017 07:21 PM, John P. Rouillard wrote:
>...
>> Some properties can be set to quiet by the roundup tracker
>> designer. This prevents changes to them from showing up in change
>> notes (sent via email), from being displayed in the history section of
>> the web interface and prevents the change from being listed in the
>> feedback banner.
>...
>> I am planning on changing to code to eliminate the "nothing changed"
>> notification. As a result when a user submits a form where all the
>> properties are quiet, the form is redisplayed with no banner. Just as
>> though the form had been submitted with no changes.
>>
>> Does anybody have any thoughts?
>...
>IMO your proposal improves consistency of behavior with respect to the
>'quiet' attribute of a property. The documentation should reflect the
>semantic of 'quiet' clearly. My attempt to summarize:
>
>  When a 'quiet' property is modified, Roundup does not trigger any user
>  visible side effect.
>
>Your reply to Thomas Arendsen Hein exposes the use case for 'quiet': UX 
>related properties, which should appear in the documentation too.

The doc/design.doc says:

   quiet=False:
      if set to True, changes to the property will not be shown to the
      user. This can be used for administrative properties that are
      automatically updated when a user makes some other change. This
      reduces confusion by the user and clutter in the display.
      The property change will not be shown in:

        - the change confirmation message when a change is entered
          in the web interface
        - the property change section of the change note email
          ("nosy email")
        - the web history shown at the bottom of an item page

I also just added (checkin 15440504fb04) the following to
doc/customizing.txt based on the commit log for checkin 8901cc4ef0e0:

* All properties support the following attributes:
   
   - ``required``: see `design documentation`_. Adds the property to
     the list returned by calling get_required_props for the class.
   - ``default_value``: see `design documentation`_ Sets the default
     value is the property is not set.
   - ``quiet``: see `design documentation`_. Suppresses user visible
     to changes to this property. The property change is not reported:
   
      - in the change feedback/confirmation message in the web
        interface
      - the property change section of the nosy email
      - the web history at the bottom of an item's page
   
    This can be used to store state of the user interface (e.g. the
    names of elements that are collapsed or hidden from the
    user). Making properties that are updated as an indirect result of
    a user's change (e.g. updating a blockers property, counting
    number of times an issue was reopened or reassigned etc.) should
    not be displayed to the user as they can be confusing.

Does that meet your documentation expectations?

>P.S.: great stuff, good to know it exists :)

Note that quiet properties are only available in the development
mainline that is still to be released.

To use the mainline you should be running python 2.7.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot