BugNET

Open source issue tracking & project management
Welcome to BugNET Register | Login |

Welcome to BugNET!

Welcome to the official community and development site for the BugNET open source project. From downloads to documentation, bugnetproject.com offers a comprehensive base of information, resources, and support.

BugNET is an issue tracking and project issue management solution built using the ASP.NET web application framework. Email notifications, reporting and per project configuration of fields and values allows efficient management of bugs, feature requests, and other issues for projects of any scale.

Latest News & Announcements

The holidays have come fast, and some have past already.   Before they are all but gone we would like to wish everyone happy holidays and best wishes in the new year!!

We look forward to furthering the project in the new year and making it the best possible.

The BugNET team.

The new build of BugNET has been posted in the downloads section.  This is the first beta 0.8 release which has fixed many issues in the next major release of the issue tracker.  For those who are new to BugNET you can find an excellent blog post of what the 0.8 release has added in terms of overall functionality and improvements to the project.

We invite you to download this latest beta, test it and provide your feedback in our forums and issue tracker to help us release the final version as soon as possible.

You may notice with the amount of new features and the documentation regarding them lacking.  Please be patient as we fill in these gaps and work to document the new and existing features. ...

Read More »

If you are looking to get started developing with BugNET, or any other .NET web application, Microsoft has released a tool to install IIS, Visual Web Developer 2008 and SQL Server 2008. This should help users get started coding much easier than before.

Read More »

Finally BugNET DotNetNuke integration has arrived! Peter Donker from Bring2Mind has released a slick DotNetNuke (DNN) module.

The features look really useful... Great work Peter!

Read More »

This article will explain which areas of BugNET are affected by lost machine keys, and how to rebuild a BugNET system without it. In the end you should have a fully fledgedsystem under control of  "admin" and will then need to reset the users passwords to allow them to login.

I present two techniques, one will require some minor code to be written, and the other some SQL scripting. I have used the SQL technique on a hosted box with success....

Read More »

Membership

Membership Membership:
Latest: jeldridge
New Today: 2
New Yesterday: 1
Overall: 879
People Online People Online:
Visitors: 22
Members: 0
Total: 22

Latest Posts


BugNET-0.7.899-Source Solution made with VS 2008 Hi all, I'm trying to compile the source code for v0.7.899 and when I open it with VS 2005, it sends me a message because the Solution was made with VS 2008. <font color='#999999'>Microsoft Visual Studio Solution File, Format Version 10.00 # Visual Studio 2008 Project(';{2150E333-8FDC-42A3-9474-1A3956D46DE8}';) = ';Solution Items';, ';Solution Items';, ';{0982E04B-111E-4861-8B21-A2138A657EF7}'; ProjectSection(SolutionItems) = preProject Common\GlobalAssemblyInfo.cs = Common\Glob...</font>

Issues count on the page I`ve changed the issues count per page to 25 but it still shows me only ten per page. How to fix it? &#160; PS: 0.8.99 Thanks.

BugNET 0.8 Beta - Cannot Create Categories I installed the BugNET 0.8 Beta and am attempting to set up a project. Thus far I can do everything except create Categories. When I click the Add Category link nothing happens and I see that a JavaScript Error was thrown. The error is on line 315, Char 9, 'tree' is null or not an object The error is in ../Administration/Projects/EditProject.aspx. &#160;

DB Referential Integrity userid excludedHi guys Theres one or two bugs regarding referential integrity especially with UserID (eg BGN791 & BGN719). I note in the ORD in the docs, that UserID is not FK'd to the aspnet_users table. Is this on purpose? I am aware that the app should capture exceptions nicely - but i like the DB to lock this stuff down. thoughts?

stored proc needs [dbo] prefix Only one stored proc does not have [dbo] as the prefix in it's CREATE Procedure statements in the install scripts. BugNet_Bug_GetBugFixedInVersionCountByProject This means that&#160; it gets created in the sql 2005 default schema which may not be dbo if you use shared hosting. This can cause a few problems. 1) If it's called with the dbo prefix dbo.BugNet_Bug_GetBugFixedInVersionCountByProject, it will not be found. 2) If you manually delete all your BugNet database objects in the dbo schema, this object/proc in another schema gets missed resulting in a subsequent failure of the install script when you re-install.&#160; Because that proc will exist in your default schema still. This happenend to me last week on a re-install situation. Thanks Rick Hubka

POP3 Issues I'm configuring the tool to read POP3 (from Exchange 2007). &#160; This is the error I am getting.&#160; Any ideas? &#160; <span id='ctl00_Content_gvLog_ctl04_MessageLabel' style='font-weight: bold; font-style: italic'>Mailbox Reader Error - <span id='ctl00_Content_gvLog_ctl04_LoggerLabel' style='font-weight: bold; font-style: italic'>BugNET.POP3Reader.MailboxReader <span id='ctl00_Content_gvLog_ctl04_ExceptionLabel'>Lesnikowski.Client.ServerException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.24:110 at Lesnikowski.Client.TcpTextClient.Connect(String host, Int32 port, Boolean useSSL) at Lesnikowski.Client.Pop3.Connect(String host) at BugNET.POP3Reader.MailboxReader.ReadMail() &#160; &#160;

[Request] Create issue button It`s will be useful to have a 'Create issue' button in the issue viewer page. Sometimes you are viewing an issue and need to create another one, so you need to return back and click the button. It`s will be useful on bulk issue creation. &#160; Thanks.

Project/Version Reported in vs. Project/Version resolved in Hi guys - I have a scenario, and I wanted to get your input on the way Bugnet 0.7 should work and any roadmap improvements&#160; that impact on this. Scenario: User reports bug in perceived version of the&#160;main application&#160;(eg. version 1.3.45) 'Triage' assign this bug a priority and to a developer The developer's investigation&#160;shows that bug was found in the&#160;reporting component that is shared across many projects (eg. version 2.6.0.0) Whats the workflow from this point onwards? The main application does not have a bug and should not be upversioned - so resolved in version is still 1.3.45 I think that bug should be&#160;re-raised&#160; or something into the reporting component, this should then be triag'd by the reporting team and then fixed, upversioned, deployed, THEN the bug should be retested and resolved or something and marked as fixed in 1.3.45. If this is the case, how can i achieve this in BugNet without copying and pasting information everywhere. Your thoughts on this would be much appreciated. Kieron

Latest Tweets

Dec 12, 2008 1:03 PM - BugNET 0.8.99.0 (Beta 1) has been released! http://tinyurl.com/5zql9w

Dec 08, 2008 9:41 PM - Some critical bugs have been found at the last minute that will delay the first beta to be released.

Dec 01, 2008 -3:03 AM - BugNET 0.8 Beta 1 will be released at the end of this week.

Nov 28, 2008 10:15 PM - just checking out Microsoft's new asp.net charting control. It could be very useful for reports in BugNET. http://tinyurl.com/5nesrq

Nov 27, 2008 9:18 PM - add, edit and delete of roles is now working properly in 0.8.