The Bugtracker module is a simple tool to log issues during the developement process of a website. It has his own data scheme so it will not interfere with any other modules neither appear in node management or search engine.

Bugs can be logged, viewed, commented, deleted, and updated.
Each bug can be associated with a priority level and a type of bug. Updates are logged to see the progression of the bug.
A list of emails can be set to recieve a notification each time a new bug is logged.

CommentFileSizeAuthor
bugtracker.png23.22 KBmatthieu.symetris

Comments

joachim’s picture

joachim commented
Status: Needs review » Needs work

There are several issue tracker modules that already exist for Drupal. Have you taken a look at them, and can you explain how this one is different?

Also, you need to give a link to your sandbox.

matthieu.symetris’s picture

matthieu.symetris commented

I saw the Issue Tracking module that works with the Project module. I wanted to have a module that can track issues without any dependencies. This module also offers an on-page interface to log issues. That interface collect infos on: who logged the issue, if this person is logged in as a drupal user, what is his user agent, what is the url he visited etc.

That interface may be given to anonymous user if needed.

I also look at the To do list module, it creates a content-type for to-dos and I wanted my module to not interfere with node system.

The link to my sand box is: http://drupal.org/sandbox/matthieu.symetris/1151868

matthieu.symetris’s picture

matthieu.symetris commented
Component: new project application » module
Status: Needs work » Needs review
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

There is also:
http://drupal.org/project/casetracker - only depends on views
http://drupal.org/project/ticketing
Comparison of Project Management / Ticket Tracking modules

matthieu.symetris’s picture

matthieu.symetris commented

Casetracker module is very similar to this project but it does use the node system to create cases which is exactly one thing we'd like to avoid with our project.

And ticketing is more a 'post it' module than an issue tracking one.

Both of them associate the logged-in user the the logged entry.

The idea behing the bugtracker(our project) is to be used in the project that is in developoment and where the drupal user(loged-in) is not nececerely the actual user. It means that developers may be logged-in as an editor user but he wants the issue to be logged-in with his informations, not the ones of the account he is logged in.

None of the projects above have an on-page tracking form. This form log infos inputed by the user but it also log various information where the bug was logged. It litterally 'spies' the environnement where the bug was logged.
This is why I think this module can be used for different purpose than the ones you mentionned.

matthieu.symetris’s picture

matthieu.symetris commented

It's been a month and I had no news, is there someone taking care of this module at Drupal.org??? It's the first time I commit a module, I don't know how long it should take before having any news...

jthorson’s picture

jthorson commented

Mattieu,

As illustrated at this link, the current project application backlog is in the neighborhood of 7 weeks ... we are diligently working to clear out the queue, and appreciate your continued patience.

In the meantime, we are encouraging applicants to to chip in and help the process by performing a review of their own ... all that is needed is some basic knowledge of module development. The Code Review Group on groups.drupal.org is a great starting resource which can assist in the process; and some reviewers are willing to fast-track applications for those who have demonstrated their understanding of the code-review principles by performing reviews (as opposed to through a review of their own code).

matthieu.symetris’s picture

matthieu.symetris commented

Thank you very much for you answer, I'll be patient :)

svendecabooter’s picture

svendecabooter
he/him
Primary language Dutch
Location Gent
commented
Priority: Normal » Critical

Marking as critical as per http://drupal.org/node/894256
Sorry for the long wait.

joachim’s picture

joachim commented
Status: Needs review » Needs work

> Casetracker module is very similar to this project but it does use the node system to create cases which is exactly one thing we'd like to avoid with our project.

What are you using instead?

The screenshot in your original post looks interesting, and I can see that a tool for filing bugs *about the current site* is very useful.

However, like Dave Reid and myself said above, we have too many casetracker-type modules around already, duplicating functionality and more importantly, developer effort.

I would really like to see this module move towards being an add-on for an existing casetracker module. A perfect use-case for this would be for users of drupal.org to report problems with documentation directly from the documentation pages.

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs work » Needs review

Our module uses tables it creates to log informations.

I'm not sure I want to move data storage to the node system, I'll think about that. If this module extends an existing module, would you recommand to keep it separated from the target module or move it into the same project?

gapple’s picture

gapple
he/they
Primary language English
commented

This seems similar to feedback.module as well, though with more features.

joachim’s picture

joachim commented

> I'm not sure I want to move data storage to the node system, I'll think about that.

On D6 it's really the best option. Makings things nodes brings you the power of CCK, of comments, and a whole load of other things: flagging issues, voting on them, subscribing to them and so on.

> If this module extends an existing module, would you recommand to keep it separated from the target module or move it into the same project?

I'd say stay it its own project so you're free to develop it and it's not extra maintenance for the base project.

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs review » Needs work

Hi, the team I'm working with and I are going to discuss whether if we want to extend another module or if we'll only keep our module working to fit our specific need and withdraw it from drupal. I'll give you news next week. I'll switch status to need work the time we discuss it.

Thank you.

Anonymous’s picture

Anonymous (not verified) commented
Priority: Critical » Minor
Status: Needs work » Closed (won't fix)