Fullscreen
[Show/Hide Right Column]

Close
noteNote
This page is to document "what Tiki should do". For feature documentation (what Tiki does), please see corresponding page on doc site
(Cached)
Refresh Print

How to Submit a new item on the Wishlist

Close
Do you code? Maybe you could commit your fix directly? Read How to get commit access.

Please note: If you have observed a security problem, please read the Security page before submitting a wishlist item or discussing the problem in an open forum!


If your problem may be a general problem of understanding check the check the Tiki Documentation.

Before adding a tracker item please check if someone has reported the same issue. If so, please use the ratings and vote to express your support. You can also comment the tracker item with more information. You can check keywords to filter the items to a shorter list. You can also try out the dynamic filter.

If possible, please try to duplicate the bug on a clean install to make sure it's not a local configuration problem. You can use demo.tiki.org, where you can be logged in as admin.

If a bug is really old, it doesn't mean that no one cares. It could just be that no one else has that bug, suggesting user error :-) or a very special/rare configuration. So, once you are sure it's a real issue:

Add one item (bug, feature request, or others) per entry (unless they are very closely related); be as precise and pragmatic as possible. Assign to 1 or more categories as appropriate. Please do not put a high priority for no good reason.

You can also report a theme/CSS issue when a bug affects just a theme but not Tiki code in general.

You need to login to submit an item on the wishlist.

You may also want to read: How to Report Bugs Effectively by Simon Tatham.


Below are list of fields to fill in

Rating

The rating is the result of votes by you and other users. It is OK to vote for your own submission.

Subject

Please be descriptive. It is ok to start with the same of the feature. Ex.: Forum: problem with xyz

Priority


Be reasonable. Not everything can be top priority.

For a bug:

  • How bad is the bug?
  • How easy to fix?
  • Will data be lost?
  • Do you get and ugly/bad error message (from mysql or PHP)
  • Is there a workaround?
  • Is this a widely-used feature or configuration (vs a sub-feature)?
  • Does it prevent you from using the feature? (vs an annoyance)
  • Is is a new bug? (regressions are a higher pririoty because they are a disincentive to upgrading)


For a feature request (new feature or enhancement to an existing feature)

  • Will this be a popular feature which will attract lots of people to Tiki?
  • Is it easy to do?
  • Will it fit in well with the rest of the application? (some stuff just deserves to be there!)



If you assign too high, an admin will change your score and move it even lower! :-)

Feature

Check all that apply. This is used to filter items in the Keywords list, available on the right hand side. You can put your mouse over each word and have a bit more description what this feature is about. For more information about features, please see doc:features

Data type

We have one tracker for everything. Sometimes, a bug is also a feature request.

Bug
The feature is coded but it doesn't work. (obvious error message)

Bug (Conflict of two features)
Feature A works. Feature B works. But when you try both together, something goes wrong.

Bug (Regression)
Newly introduced bug during stabilization period (ex.: 1.9.7 -> 1.9.8). Sometimes, a bug (or security) fix introduces another bug. Also, minor feature enhancements happen even in stabilization mode. They are not supposed to cause issues (risky ones are done in development branch). But sometimes, some things slip through. These are high priority because people won't want to upgrade (vs a bug which has always been there).

Bug (Consistency)
As an all-in-one application, we come to expect that all parts of the system behave the same. These are often also usability issues (see below)

Bug (Usability)
the feature is coded but the way it's done, users are not able to accomplish their goals (ex.: interface too complex)

Community Projects
Something non-code related but should be taken care of. To get a feel of what belongs here, please check this page: Community Projects

Documentation (or Advocacy)
Will appear here: Documentation

Feature request
A new feature or an enhancement to an existing feature

Patch
If you are suggesting a fix to the code. You can also apply for SVN access to commit your fix directly.

Support request
Means you need help. Not necessarily a bug but you can't get the thing to work. Forums are better for this.

Version

Check all that apply.

A *.tiki.org site -> See DogFood

Problem

Describe the problem as best you can. If you are not using Linux and MySQL, please mention it as it could be related to less-used configurations.

Solution

Please indicate solutions. This can be pseudo-code or general ideas. Even better if you can supply a working patch (optional)

If the bug or feature relates specifically with one of the on-going projects in the list, tick the appropriate box. (optional)


Related:



Alias

Page last modified on Tuesday 03 January, 2012 06:06:27 UTC

SourceHistoryComments

Search Wishes (subject only) [toggle]

Categorize How to Submit a new item on the Wishlist

Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.