View Issue Details

IDProjectCategoryView StatusLast Update
0004827SUMoNew Featurepublic2019-05-16 22:54
ReporterTM123 Assigned ToKyle_Katarn  
PrioritynormalSeverityminorReproducibilityhave not tried
Status acknowledgedResolutionopen 
Target VersionLong term 
Summary0004827: List number of users
DescriptionCould you make a column which lists the number of users for the products?
And perhaps also one for the number of users who reported that update (percentage would be fine)?

It could tell me already in advance how reliable could be a reported update.
And it is in my opinion also very interesting to see how common some applications are.

I know I can see that by clicking on get update form SUMo page, but doing that for hundreds of products...

TagsNo tags attached.

Activities

TM123

2018-04-30 15:03

reporter   ~0002893

There is still another reason for such a column.
If I am the only reporter of a software then I cannot trust SUMO if it tells me that the software is up-to-date.

wolf

2019-05-16 22:29

reporter   ~0003311

That's also my motivation to get some indication on reliability and on user base.

According to Kyle only the percentage is a reliable data, not the number of users where you still need to define what is taken into account and what not. I don't consider % as reliable for software tools with little user base (less than 10 users).

For user count you still have special cases like devices which were last online over a year ago, SUMo being uninstalled, a software tool getting an update and the software tool getting uninstalled. Shall a user count really take into account every device with SUMo installed even if that device was last online 10 years ago and possibly no longer exists?
So I think its a kind of active users within the last 12 months or so, ignoring devices which have last been online with contact to SUMo server longer before.

Kyle_Katarn

2019-05-16 22:54

administrator   ~0003314

I fully share your view @wolf.

Maybe % + a "reliability factor" could make sense. I'll check, but this is not a short term priority.

Issue History

Date Modified Username Field Change
2018-04-09 09:03 TM123 New Issue
2018-04-09 21:03 Kyle_Katarn Assigned To => Kyle_Katarn
2018-04-09 21:03 Kyle_Katarn Status new => acknowledged
2018-04-09 21:03 Kyle_Katarn Target Version => Long term
2018-04-30 15:03 TM123 Note Added: 0002893
2019-05-16 22:29 wolf Note Added: 0003311
2019-05-16 22:54 Kyle_Katarn Note Added: 0003314