Many projects (like SourceForge itself) use more than one tool for bug reporting and feature requests, but this is confusing.
In Issues you can report bugs and ask for a new feature in the same issue tracker, you just need to change Type field to "Enhancement" if you want to ask for a new feature.
The difference between a bug and a missing feature seems to be not so clear to all users, too.
More than this, the term "bug" is not so common between non tech savvy users, so "problem" appears a better wording.
"Feature request" is well understandable, but is a two words string, so I prefer using "Enhancement" because it's a single word.
Last edit: Zangune 2025-05-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Switched from wont-fix to rejected.
Hardly ever people should use "wont-fix" (at least when dealing with copyleft projects), because circumstances or developers or anything else can change in the future. In general, we can't say too much about the future.
Last edit: Zangune 2025-05-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Switched from "Problem" to "defect".
A problem is something that causes you trouble, a defect is something that does not work as it should. The right place to discuss a problem of the project that is not a defect is a new argument in the discussion board, so tickets about problems that are not defects and that are opened into the issue tracker should be set to invalid.
In example, check issue SmartScreen and browsers protections block ARZ: I can't fix that, because it does not depend on me, so this is not a defect of my program.
Last edit: Zangune 2025-05-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Switched from "Priority" to "Gravity".
The priority is about the order of execution, the gravity is about how muc h the issue impacts on the program functionalities.
"Severity" sounds good, too; sadly changing the fields name is not handy, so I will keep "Gravity", at least for now.
Last edit: Zangune 2025-04-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe that "Open with high severity" is more descriptive, in this case I have to could use "mid" instead of "medium" because of the word length, like above. I hope this will be fixed by SourceForge.
Drawback: two lines for each string.
Last edit: Zangune 2016-10-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Probably, I will move this discussion elsewhere, in example in my profile as a guide on how to setup a project.
A first attempt is "How to setup a tracker on SourceForge"; it is a work in progress, you shouldn't use it for now it's incomplete, use with care.
Last edit: Zangune 2022-09-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Indeed, the default "discussion" would be better than the word "forum", anyway I do not plan to change this soon (if I do that, then I should update the documentation, too). An idea is to change the forum URL with a redirect to the discussion URL. In example:
http://sf.net/p/arz/f
to redirect to:
http://sf.net/p/arz/discussion
No, at least not here on SourceForge, at least not for now. It seems that the link has to be at least 3 characters long, so f cannot be a redirection.
It's not a good practice to break links, so I will keep "Forum" and "f".
A single discussion can be called "argument" and the title can be called "summary".
Last edit: Zangune 2025-05-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Generally speaking, maybe the short versions of the URLs are not that good, or at least they should be just a redirect to a full path (they cannot, read before).
Anyway, SourceForge uses "p" instead of "projects" in URLs when you are in a tool page (in example in this forum).
Last edit: Zangune 2025-05-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Many projects (like SourceForge itself) use more than one tool for bug reporting and feature requests, but this is confusing.
In Issues you can report bugs and ask for a new feature in the same issue tracker, you just need to change Type field to "Enhancement" if you want to ask for a new feature.
The difference between a bug and a missing feature seems to be not so clear to all users, too.
More than this, the term "bug" is not so common between non tech savvy users, so "problem" appears a better wording.
"Feature request" is well understandable, but is a two words string, so I prefer using "Enhancement" because it's a single word.
Last edit: Zangune 2025-05-22
Switched from wont-fix to rejected.
Hardly ever people should use "wont-fix" (at least when dealing with copyleft projects), because circumstances or developers or anything else can change in the future. In general, we can't say too much about the future.
Last edit: Zangune 2025-05-22
Switched from build to revision.
Last edit: Zangune 2025-05-21
Switched from alpha and beta to draft and testing, labels in code updated accordingly.
Switched from "Problem" to "defect".
A problem is something that causes you trouble, a defect is something that does not work as it should. The right place to discuss a problem of the project that is not a defect is a new argument in the discussion board, so tickets about problems that are not defects and that are opened into the issue tracker should be set to invalid.
In example, check issue SmartScreen and browsers protections block ARZ: I can't fix that, because it does not depend on me, so this is not a defect of my program.
Last edit: Zangune 2025-05-22
Switched from "Priority" to "Gravity".
The priority is about the order of execution, the gravity is about how muc h the issue impacts on the program functionalities.
"Severity" sounds good, too; sadly changing the fields name is not handy, so I will keep "Gravity", at least for now.
Last edit: Zangune 2025-04-01
Indeed "severity" is too long for SourceForge, graphical demonstration:Last edit: Zangune 2025-05-21
Maybe that "Open with high severity" is more descriptive, in this case I
have tocould use "mid" instead of "medium" because of the word length, like above.I hope this will be fixed by SourceForge.Drawback: two lines for each string.
Last edit: Zangune 2016-10-13
Probably, I will move this discussion elsewhere, in example in my profile as a guide on how to setup a project.
A first attempt is "How to setup a tracker on SourceForge";
it is a work in progress, you shouldn't use it for nowit's incomplete, use with care.Last edit: Zangune 2022-09-19
Indeed, the default "discussion" would be better than the word "forum", anyway I do not plan to change this soon (if I do that, then I should update the documentation, too).
An idea is to change the forum URL with a redirect to the discussion URL.In example:to redirect to:No, at least not here on SourceForge, at least not for now. It seems that the link has to be at least 3 characters long, so
fcannot be a redirection.It's not a good practice to break links, so I will keep "Forum" and "f".
A single discussion can be called "argument" and the title can be called "summary".
Last edit: Zangune 2025-05-22
Generally speaking, maybe the short versions of the URLs are not that good,
or at least they should be just a redirect to a full path(they cannot, read before).Anyway, SourceForge uses "p" instead of "projects" in URLs when you are in a tool page (in example in this forum).
Last edit: Zangune 2025-05-21
Things like the text lenght may not apply anymore, due to the new SourceForge style (about January 2018).