View Issue Details

IDProjectCategoryView StatusLast Update
0001616SUMoNew Featurepublic2019-08-20 18:19
Reporterpoutnikg Assigned ToKyle_Katarn  
Status acknowledgedResolutionopen 
PlatformDesktopOSWindows Vista 64OS VersionHome Premium SP2
Product Version3.2 
Target VersionShort term 
Summary0001616: "Number of users" column
Description"Number of users" column

It could be useful for general overview to have an extra narrow column about number of users.

It would be useful for evaluation of confidentality of update info.
The item with user number less than implicitly 2 ( could be customized )
could be visually distinguished as not reliable info.

As a variant, only visual marking without extra column.
TagsNo tags attached.


related to 0002012 acknowledgedKyle_Katarn To distinguish soft with just one user 
related to 0004278 acknowledgedKyle_Katarn Update age 



2012-07-04 06:52

reporter   ~0000913

Last edited: 2012-07-04 06:52

Variant : To OK in update column could be added note like "Low sources", or just "???", if number of sources is <= N.

N could be configurable in settings, implicitly N=1.


2012-07-04 09:48

administrator   ~0000915



2012-08-09 08:51

reporter   ~0001066

Or, variant B,
at least to mark "single user" items
e.g. by blue question mark, instead of green OK.

I have plenty of such items.


2012-08-09 14:33

reporter   ~0001070

Good idea, especially quick visual markings.

"N of users" column may help to debug SUMo, too (although I guess it will be interesting only to a small fraction of users, so it better be made optional).


2013-12-23 22:54

administrator   ~0001557

Can be implemented using a dedicated script command, before being natively integrated in the query protocol.

Good candidate for next version


2015-07-05 23:23

administrator   ~0001919



2019-08-20 17:59

reporter   ~0003679

According to former European privacy law, the default value of proposal of note has to be at least 2, not 1. I don't know if there is such a clear definition with current European privacy law (GDPR). Without taking a closer look, that number might be unchanged as long as this data doesn't permit to identify an individual person, or larger until reaching that level of not being able to identify an individual person.

Issue History

Date Modified Username Field Change
2012-06-26 08:19 poutnikg New Issue
2012-06-26 22:28 Kyle_Katarn Assigned To => Kyle_Katarn
2012-06-26 22:28 Kyle_Katarn Status new => acknowledged
2012-07-04 06:52 poutnikg Note Added: 0000913
2012-07-04 06:52 poutnikg Note Edited: 0000913
2012-07-04 09:48 Kyle_Katarn Note Added: 0000915
2012-08-09 08:51 poutnikg Note Added: 0001066
2012-08-09 14:33 bytehead Note Added: 0001070
2013-12-23 22:54 Kyle_Katarn Note Added: 0001557
2013-12-24 14:03 Kyle_Katarn Relationship added related to 0002012
2015-07-05 23:23 Kyle_Katarn Note Added: 0001919
2017-03-21 19:53 Kyle_Katarn Relationship added related to 0004278
2019-08-20 17:59 wolf Note Added: 0003679
2019-08-20 18:19 Kyle_Katarn Target Version => Short term