View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007058 | mantisbt | bugtracker | public | 2006-05-08 17:53 | 2008-08-12 09:36 |
Reporter | vboctor | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Product Version | 1.0.3 | ||||
Summary | 0007058: Keep track of number of times an issue was viewed | ||||
Description | It would be useful to keep track of such information, display it in the issue view page (optional) and can be an optional column in the View Issues page. This can be used to sort issues by popularity. | ||||
Tags | No tags attached. | ||||
This seems like it would make things a little slow to constantly write to the database on a view of an issue -- not to mention it is not nessisarily a good indication of how popular an issue is, since people might just be looking at the issue to determin if it is applicable to what they are searching for. A better solution would be to use the count of the total users monitoring the issue to show how popular the issue is. |
|
With MySQL, an "insert delayed" can be used to speed up such view writes. Re: monitoring, I would venture to say that most people don't bother to monitor issues, such that most issues will go unmonitored, especially in a public implementation of Mantis. Why can't we have "Popular" (via # of views) and "Most monitored"? Further, if views are counted, there would need to be a way of avoid the "stuffing of the ballot box" by setting a threshold per IP address per time period. |
|
I'd like to add a "most popular bugs" to the summary page so I thought about what metrics to use to define "popular". IMHO, both number of monitors and number of views are not ideal for the reason you explained, so I looked at what we have already in the DB and used the number of notes to filter bugs. IMHO, this gives a nice idea of what users are interested in What do you think? |
|
If I order the three factors, I will order them as follows:
I agree that 1 and 2 are better metrics. I don't agree that Monitoring is not a good metric of popularity, I think both notes and monitors are good. The other thing that was raised several times is voting. However, the idea is how to control that users don't vote for all issues! With monitoring and notes, at least they get cc'd on future discussion relating to the issues :) |
|
Victor: please see the related bug 0008208 (patch ready...) where I used the number of history items (so includes both add notes and monitoring events) to score the bugs. About voting, I will search for open bugs and add my thoughts there |
|
Marked this as won't fix. I believe that 0008208 and 0000668 are more effective and efficient ways to reflect popularity. Although I believe that once voting is implemented, the query used for 0008208 must be revised. |
|