Jtrac for windows

Net server-side controls and components to add defect bug tracking to your current ASP. NET website. Bosco is a rewrite of the popular Bugzilla defect tracking software in PHP. Among its goals are database-independence and ease of maintenance and modification. An API is also planned to allow external applications to work with Bosco's data. This repo is for the reporting of issues found within and when using Bash on Ubuntu on Windows.

It aims to be easy to install, maintain, and use. It does not have all the bells and whistles of a system like Bugzilla, but is feature-rich and extendable. A system for reporting, managing, and tracking bugs and other issues on multiple projects over the web.

Bug data are stored as native XML -- no database or mail server needed! JTrac is a generic issue-tracking web-application that can be easily customized by adding custom fields and drop-downs. Features include customizable workflow, field level permissions, e-mail integration, file attachments and a detailed history view. Mac app to simplify posting bug reports to Apple's Radar bug tracking system. It provides a global hotkey to open a window in which to enter a bug report, which can be easily submitted to Apple.

The code is in just as bad a state. The web scraping is done in one big method which chains xpaths together to plot a course through the web site, and currently it spits out all the logs I was using while trying to get something that could post to Radar.

We have large collection of open source products. Open source products are scattered around the web. Add Projects. Made in India. All trademarks and copyrights are held by respective owners. JTrac SingleBugs - A simple single person bug tracker Go Singlebugs is a sole developer focused bug tracking tool. It then uses git to figure out who might have caused the bug, dts bug-tracking-system bug-analysis defect-tracking.

Request Tracker - issue tracking system in CGI and Perl Perl Request Tracker is an enterprise-grade issue tracking system which thousands of organizations use for bug tracking, help desk ticketing, customer service, workflow processes, change management etc.

Trouble ticket express - Help desk software in Perl and CGI Perl It does everything from bug tracking and customer support to project management and to-do lists. Eventum - issue tracking system PHP Eventum is a user-friendly and flexible issue tracking system that can be used by a support department to track incoming technical support requests, or by a software development team to quickly organize tasks and bugs.

Net Defect Tracking Components Bug. JTrac Java JTrac is a generic issue-tracking web-application that can be easily customized by adding custom fields and drop-downs.

QuickRadar - Mac app to simplify posting bug reports to Apple's Radar bug tracking system. Objective-C Mac app to simplify posting bug reports to Apple's Radar bug tracking system. For convenience, the JTrac distribution contains a "wrapper. But first you have to download the Java Service Wrapper distribution separately.

Note that the Java Service Wrapper project supports other operating systems such as Linux or Mac also. Place some of the files from the Java Service Wrapper distribution into the JTrac folder structure as follows:. To install JTrac as a windows service, open a command prompt, change to the "jtrac" directory where you extracted the JTrac distribution and run the following command:. This will install a windows service called "JTrac-Jetty".

Note that this service is configured to automatically start when Windows starts, by default. To remove the service, you can use the following command:. The "wrapper. Look for the "-Djetty. When running as a service under the Java Service Wrapper, you can look at the "wrapper. Although in practice JTrac has been found to be extremely stable in production - to safeguard against hardware failures, you should regularly backup the database and stored attachments.

If you are using the JTrac distribution as-is, i. Of course, if you are using a different database you will have to backup the database separately. The "jtrac. Please refer to the " upgrading " section of this document. JTrac can be installed in a few minutes without having to type any commands and you don't even need to set-up a database.

Configuring an e-mail server for notifications is something easily done through the user interface. One of the reasons why many people choose JTrac over other open-source issue trackers or bug trackers is because of how easy it is to set up. JTrac is also written from the ground up to make use of the very best and latest in Java. JTrac is designed to be able to handle requirements management in the future and this an area where there is a clear lack of open source tools that support the needs of agile development teams.

JTrac also has flexible workflow capabilities and offers a rare level of control over field-level permissions. The presentation layer is using the Apache Wicket framework. The service layer uses the Spring Framework. Also the Acegi Security framework for Spring has been used. JTrac is effectively a "light-weight" Java EE application and any version 2. Hibernate is used for data persistence. This allows for JTrac to be database neutral and any database supported by Hibernate can be used. JTrac was completely re-written to use Spring and Hibernate - and the 2.

Of course, it is recommended that you change the default password as soon as possible! We welcome code contributions in the form of patches which you can submit here. JTrac has a detailed developer guide which can get you up and running even if you are new to Java development.

Do consider contributing a translation which is very easy to do and does not require any knowledge of Java at all. You can refer to this section of the developer guide for details. Read the section on interim builds on how you can help by testing the development builds.

HSQLDB is surprisingly resilient and we have an instance of JTrac running in the place where I work that over a span of 2 years has accumulated more than items across multiple spaces with around users.

The database file has grown beyond 10MB but there are still no signs of problems and the application screens still load fast.

But depending on what you are comfortable with, you can consider moving to another database if your usage is really high. JTrac provides an ample number of custom fields which can be used for all kinds of tracking needs. In very rare cases where people run out of custom fields, it is invariably for "free text" fields.

The limit on custom fields is primarily for performance reasons especially where filtered searches are involved. So when JTrac introduces the feature of being able to "tag" items, these kinds of things are likely to be covered. Anyway, if you really, really want more custom fields, the JTrac code is very clean and you can easily customize a version that meets your requirements. A few people have reported having done this and for example - this forum thread can help you get started.

We are just trying to use the SourceForge infrastructure as far as possible and the activity on the SourceForge trackers translates into higher rankings which is important for project visibility. At this point, we would rather not get into the details of hosting an instance of JTrac on the internet.

Have a look at our detailed developer guide and you will find that JTrac has one of the most developer-friendly set-ups among open-source projects. It will take you only a few minutes to be up and running no matter which Java IDE you use.

We actively encourage contributions and with your support JTrac can become better than it is today. Apart from using the forums you can also consider joining the JTrac mailing-list. In a future version of JTrac, the ability to even hide fields depending on the role and status will be implemented.

The design for this is already in place. JTrac will support "nested" items under a first-level "parent" item and the design and database schema for this is already in place. This will allow users to split tasks into sub-tasks and opens up other possibilities. One of the plans in the roadmap is to build JTrac into a full-fledged requirements capture tool complete with test-case management and traceability. JTrac can then be used to manage user-stories or use-cases for agile development teams.

Using Beanshell , users should be able to introduce custom routines to validate item data entered by a user. Even conditional validation across fields should be possible.

Again using Beanshell, users should be able to define routines to execute periodically, say at a pre-determined time every day. This would allow triggers for events such as slippage of a "due-date" field. This can be combined with e-mail notifications. Also a daily dashboard summary could be mailed out once the scheduler is in place. It would be handy to have attachments submitted through email also. Using a Java applet, it should be possible for the user to upload a screenshot directly from the system clipboard.

The user should be able to annotate e. There is a plan to embed a wiki-engine into JTrac. This will supplement the requirements management road map. Integration with Subversion has already been implemented using the JavaSVN library and this will enable effective integration of bug reports with commit history in the future.

A one-to-many data model for being able to tag items "Web 2. This would be ideal to track things such as mapping bugs to software release version numbers, associating keywords with items and to do all kinds of other cool stuff. RSS feeds will be introduced so that you can monitor new items and updates to items. Import from other issue tracking systems such as BugZilla to be considered. As of version 2. This needs to be improved by adding an admin screen that can browse and add users from an LDAP server.

Authorization using LDAP and allowing users to plug in custom authentication and authorization routines would be good to have as well. Mylyn previously known as Mylar integration in the form of a connector Eclipse plugin is currently being implemented. The database schema already has support for capturing planned vs actual effort against items. This needs to be implemented and obviously will open up a lot of possibilities. Although JTrac has an ' Excel Export ' feature that should suffice for all your reporting and charting needs, it would be good to have a reporting engine that allows the user to create custom reports and even schedule reports to be sent out over e-mail.

You would be able to see the time-stamp of the last uploaded binary when you access the above URL. Subscribers to The JTrac mailing-list would be notified whenever a new binary is available. This is not on a daily basis at the moment and happens only when significant changes or fixes are made in the development version. Interim builds are provided only as WAR files.

If you are using the embedded Jetty webapp-server, you have to replace the WAR that came along with the formal downloadable distribution. Details on how to do this are provided in the " upgrading " section of this document. In rare cases, there may be database schema changes. This will be made clear in the upload notification that is broadcast on the mailing-list. If you wish to retain existing data, you will have to run a database upgrade script.

Details on how to do this are also provided in the " upgrading " section of this document. Even if the database schema has changed, JTrac will re-create the database if one does not exist on startup. So when trying out the interim builds, this may be all that you really want to do.

Of course, you don't have to disturb your existing data at all since running a fresh instance of JTrac is as easy as extracting the distribution to a new directory. In some rare cases the database schema may have changed and a script for updating the database would then be provided. It may also happen that upgrading the Jetty version would be recommended in case you happen to be using the bundled Jetty webapp-server for deploying JTrac.

In case you are using the bundled Jetty server in the JTrac distribution, you should delete the contents of the folder called "work".

Note that Jetty expects a folder called "work" to exist when it starts, so ensure that you leave the empty "work" folder in place. If you are using another application server please follow the steps for removing temporary files corresponding to the server that you are using. If the JTrac release notes mention database schema changes, you need to additionally run an upgrade script before restarting the webapp-server with the new WAR in place.

No re-compilation is needed, therefore making it extremely easy for you to tweak them if required. Of course it is strongly recommended that you backup your old data before an upgrade. Please use the JTrac forums for help and for helping other users with your experiences. First, stop the server, JTrac should not be connected to the database. Get the right JDBC driver for your database.

Edit the connection params jdbc URL, username, password to match your database. The db folder will contain a "jtrac. There may also be a "jtrac. Otherwise, replace the "jtrac" part in the URL with the relative or absolute path of where the "jtrac. Execute the beanshell script from the command line. The database driver should be added to the classpath along with the beanshell jar. This is how the command would look like:.

If there were no errors, you can now upgrade the WAR don't forget to delete the temporary files and restart. If you are using the embedded Jetty web-app server, you can also choose to upgrade the JAR files that make up Jetty. This is optional, but is as simple as overwriting the contents of the "lib" directory with the corresponding files within the new distribution. You can easily check if the Jetty related JAR file versions have changed because the file-names clearly include the version numbers.

Using the Beanshell based approach above, it is relatively straightforward to port data into another database. First, you should start the application re-configured to point to the new database and let JTrac do the hard work of creating all the database tables.

It is not necessary for Jtrac to be shut-down before proceeding with the next step, but don't log-in yet! A Beanshell script called "jtrac-hsqldb-to-mysql.

You can execute this just like described in the previous section on upgrading. Note that you will need to have both the database drivers on the classpath in this case. You should of course edit the database connection parameters for database 1 and database 2 to suit your environment.

The JTrac development environment uses Maven 2 only for dependency management and generating and deploying the JTrac website hosted at SourceForge. Almost all other development actions clean, compile etc are fired through a detailed Ant script that is able to use the dependency information managed by Maven. Using Maven ensures that no binaries JAR files need to be checked into version control at all.

But if you are comfortable using Maven, the pom. You can even choose to use the maven-jetty-plugin by uncommenting the section in pom. If you get stuck or have any questions about setting up and getting started, feel free to use the JTrac forums for help. Maven 2 should be in your "PATH". You can test this out by opening a command prompt and trying to run the command "mvn".

If this is set, you are ready to move to the next step. Download the source code from SourceForge and extract it to a convenient location. Note that the source code is a separate download from the main binary and the file name will be of the form "jtrac-src-X. You could choose to check out the source code directly from the JTrac SourceForge Subversion repository. The downloaded source code should contain a sample "build. Actually the couple or so entries are optional and you will need them only if you want to use Tomcat instead of Jetty or use the JMeter script available for load-testing.

Open a command prompt and change to the "jtrac" folder. Run the following command:. This step will not only download all the required JAR files which may take time only for the first time , but also generate a standard properties file that will contain all the information required for the Ant build script to operate.

The file generated is called "build-deps. Note that you need to perform this step every time the "pom. This happens rarely and typically when newer versions of JTrac dependencies e. Spring and Hibernate are available. Keep watching for changes in the versions of JTrac dependencies or specifically changes to "pom.

If the command does not work, maybe you are not connected to the internet. Here's a tip that may help if you are behind an HTTP proxy. This has been reported to work even when the proxy requires NTLM authentication. You can append a parameter when running Maven commands as follows:.

Note that if your proxy port is different from the default 80, you will have to add an "http. If you are a NetBeans user you are ready to build and run JTrac! Just use the "Open Project" option from the "File" menu, browse to and select the "jtrac" folder. You should be able to open it as a valid NetBeans project. If you want to use Eclipse, that's easy as well. First you have to run the following command and Maven will then generate the Eclipse project descriptor files for you. That should create the ".

Now its just a matter of importing "Existing Project into Workspace" within Eclipse. Note that the Eclipse project descriptor files also need to be re-generated when JTrac dependencies change, i. Make sure you do this also if you ever run "mvn antprops:generate". Refer the Maven 2 documentation for details on how to do this. While debugging, if you would like to step through the source of dependencies as well, you can tell Maven to download sources for dependent jar files. Note that source may not be available for some jars.

You can explore all the Ant targets that are available. You can also try the "jetty-start" Ant target straight away that will compile, create and deploy the exploded war as well as boot a Jetty server. Note that this Ant target is smart enough to detect if Jetty is already running and will perform a shutdown if required before re-starting. When starting with freshly checked-out source code, the Ant script may prompt you for a JTrac Version and then create a "version.

This process is just to make the JTrac release process easier so it does not really matter what you type. You would typically need to do this only once in development mode. Maven has been configured to download the Jetty web server which drastically reduces the amount of setup that you need to do in order to set up your development environment.

Since JTrac creates the HSQLDB database if required on startup, you do not need to worry about installing, configuring and creating any database either. If you want to use Apache Tomcat instead of Jetty, just have "build.

By now, you may have noticed that because of the Ant script , you don't even need a Tomcat or Jetty plugin in either NetBeans or Eclipse. JTrac has full internationalization i18n support and you can easily add a new language without re-compiling JTrac. All you need to do is introduce a translated version of the existing "messages. Note that you will need to unzip the WAR file in order to add more files to it. You can refer the list of Java locale codes here.

You can look at the existing translations e. Note that JTrac needs to be restarted for changes to the properties files to take effect. However, switching the language for any user can easily be done anytime from the "Edit Your Profile" link on the options screen and this takes effect the instant the user saves his profile. You can also get the latest versions of the "messages.

We recommend that you submit translations as attachments on the JTrac patches tracker where we keep track of code contributions as well.

You can use this nice open-source tool called PRBEditor that really helps by showing the English and translated versions side by side on a single screen. It also takes care of handling special characters. Authors Peter Thomas. Table of Contents Preface 1.

Introduction 1. About 1. Release Notes: Version 2. Features 2. Easy to Install 2. Custom Fields 2. Custom Workflow 2. Detailed History View 2. Attachments Support 2. Custom Roles 2. Search Custom Fields 2. Dashboard 2. Search Across All Projects 2. Full Text Search 2. Export to Excel 2. Simple Navigation 2. Cross Referencing of Items 2. Read-Only Access 2. E-mail Integration 2. Multi-Language Support 2. Installation 3.

Prerequisites 3. Quick Installation 3. Security and Backup 3. Settings 3. Using only the WAR file 3. Custom Installation 3.

Edit the "jtrac-init. Set a Servlet context parameter 3. Using a different database such as MySQL 3. Changes to web. Changes to applicationContext-acegi-cas. Installing as a Windows Service 3. What to Backup 3. Upgrading 4. FAQ 4. Do we really need another issue tracker? What is the JTrac architecture like? Why start with version 2. What about 1. What is the username and password when you log in for the first time? How can I help? Can it cope? Why does JTrac have a limit on custom fields?

I really need more! How do I report bugs or feature requests? Why is JTrac not being used as the bug-tracker for this project? You should be eating your own dog food right? Do you have a list of users or references? Roadmap 5. Field-Level "Hide" Permissions 5. Nested Items 5. Custom Validation 5. Custom Scheduled Jobs 5. Submit By Email 5. Screenshot Capture 5. Saved Searches 5. Wiki Engine 5. Subversion Integration 5. Tags 5. RSS Feeds 5. Import from other tools 5. Single Sign On 5.

Eclipse Mylyn integration 5. Time Tracking 5. Custom Reports 6. Interim Builds 6. Overview 6.