Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
seminar presentation
Active In SP

Posts: 582
Joined: Apr 2010
19-05-2010, 10:51 AM


This project and implimentation provides Bug Tracking, Help Desk Ticketing, issue raising, search facility, help info, issue resolution. Issues related to software project and implimentations can be raised, tracked and resolved by Employees of different departments. Resolved issues can be allowed to access from Knowledge Base as Knowledge elements. The different groups and representatives can interact each other through this System.

The issue tracking system does all the jobs that are done in conventional system. But, here, everything is done in more formal and efficient manner. All the users of organization can interact with each other through the Issue Tracking System. This system acts as an interface between the employees thereby enabling them to forward their issues to the centralized Issue tracking system. Hence, making the work easy for both the issue raiser and the resolver. It totally avoids the involvement of middlemen in getting resolution for a particular issue.
The Issue Tracking system is an intranet application, which provides information about issues in software project and implimentations, in detail. This product develops a system that can be used by all the departments of a software organization. In the conventional method, all the issues are dealt manually .The progress of the issues are also checked in person, which is a tedious task. Here, in Issue Tracking, it fulfills different requirements of administrator and employees of a software development organization efficiently. The specific purpose of the system is to gather and resolve issues that arise in different project and implimentations handled by the organization.

Generally, in an organization, various issues like complaints of employees, Suggestions, conflicts between peers, applications, proposals, objections and requests have to be passed via the HR Department or the Head of the concerned Department. This traditional system of resolving issues and conflicts involves lot of manual work to be put in, and also it
Use Search at http://topicideas.net/search.php wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion
Active In SP

Posts: 1,124
Joined: Jun 2010
13-10-2010, 04:07 PM

Mantis Bug Tracker Developers Guide

Contributing to MantisBT
MantisBT uses the source control tool Git1 for tracking development of the project and implimentation. If you
are new to Git, you can find some good resources for learning and installing Git in the
Initial Setup
There are a few steps the MantisBT team requires of contributers and developers when
accepting code submissions. The user needs to configure Git to know their full name (not
a screen name) and an email address they can be contacted at (not a throwaway address).
To set up your name and email address with Git, run the following commands, substituting
your own real name and email address:
$ git config --global user.name "John Smith"
$ git config --global user.email "jsmith@mantisbt.org"
Optionally, you may want to also configure Git to use terminal colors when displaying
file diffs and other information, and you may want to alias certain Git actions to shorter
phrases for less typing:
$ git config --global color.diff "auto"
$ git config --global color.status "auto"
$ git config --global color.branch "auto"
$ git config --global alias.st "status"
$ git config --global alias.di "diff"
$ git config --global alias.co "checkout"
$ git config --global alias.ci "commit"
Cloning the Repository
The primary repository for MantisBT is hosted and available in multiple methods depending
on user status and intentions. For most contributers, the public clone URL is
git://mantisbt.org/mantisbt.git. To clone the repository, perform the following from your
target workspace:
$ git clone git://mantisbt.org/mantisbt.git
If you are a member of the MantisBT development team with write access to the repository,
there is a special clone URL that uses your SSH key to handle access permissions and
allow you read and write access. Note: This action will fail if you do not have developer
access or do not have your public SSH key set up correctly.
$ git clone git@mantisbt.org:mantisbt.git
After performing the cloning operation, you should end up with a new directory in your
workspace, mantisbt/. By default, it will only track code from the primary remote branch,
master, which is the latest development version of MantisBT. For contributers planning to
work with stable release branches, or other development branches, you will need to set up
local tracking branches in your repository. The following commands will set up a tracking
branch for the current stable branch, master-1.2.x.
$ git checkout -b master-1.2.x origin/master-1.2.x
Chapter 1. Contributing to MantisBT
Maintaining Tracking Branches
In order to keep your local repository up to date with the official, there are a few simple
commands needed for any tracking branches that you may have, including master and
First, you’ll need to got the latest information from the remote repo:
$ git fetch origin
Then for each tracking branch you have, enter the following commands:
$ git checkout master
$ git rebase origin/master
Alternatively, you may combine the above steps into a single command for each remote
tracking branch:
$ git checkout master
$ git pull --rebase
Preparing Feature Branches
For each local or shared feature branch that you are working on, you will need to keep it
up to date with the appropriate master branch. There are multiple methods for doing this,
each better suited to a different type of feature branch. Both methods assume that you have
already performed the previous step, to update your local tracking branches.
Private Branches
If the topic branch in question is a local, private branch, that you are not sharing with other
developers, the simplest and easiest method to stay up to date with master is to use the
rebase command. This will append all of your feature branch commits into a linear history
after the last commit on the master branch.
$ git checkout feature
$ git rebase master
Do note that this changes the commit ID for each commit in your feature branch, which
will cause trouble for anyone sharing and/or following your branch. In this case, if you
have rebased a branch that other users are watching or working on, they can fix the resulting
conflict by rebasing their copy of your branch onto your branch:
$ git checkout feature
$ git fetch remote/feature
$ git rebase remote/feature
Public Branches
For any publicly-shared branches, where other users may be watching your feature
branches, or cloning them locally for development work, you’ll need to take a different
approach to keeping it up to date with master.
To bring public branch up to date, you’ll need to merge the current master branch,
which will create a special "merge commit" in the branch history, causing a logical "split" in

Chapter 1. Contributing to MantisBT
commit history where your branch started and joining at the merge. These merge commits
are generally disliked, because they can crowd commit history, and because the history is
no longer linear. They will be dealt with during the submission process.

For more information about this article,please follow the link:

Important Note..!

If you are not satisfied with above reply ,..Please


So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page
Tagged Pages: bug tracker,
Popular Searches: y2k bug powerpoint presentation, bug tracker, 2k38 bug, spy bug seminar, pdf for bug tracker, biotech branches, what is bug tracker pdf,

Quick Reply
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  MEDI TRACKER FULL REPORT study tips 0 316 26-06-2013, 12:19 PM
Last Post: study tips
  WEB PORTAL FOR BUG TRACKER PPT study tips 0 352 20-06-2013, 04:40 PM
Last Post: study tips
  Effort Tracker System Electrical Fan 9 6,104 11-03-2013, 09:30 AM
Last Post: study tips
  BUG TRACKING SYSTEM REPORT project girl 0 349 08-02-2013, 03:44 PM
Last Post: project girl
  DEVELOPMENT OF EFFORT TRACKER SYSTEM ABSTRACT project girl 0 346 28-01-2013, 09:33 AM
Last Post: project girl
  Training Tracker report project girl 0 494 02-11-2012, 05:55 PM
Last Post: project girl
  Appraisal Tracker system seminar flower 0 475 29-09-2012, 03:15 PM
Last Post: seminar flower
  Automated Duplicate Detection for Bug Tracking Systems seminar flower 0 358 29-09-2012, 11:03 AM
Last Post: seminar flower
  Design and development of a Skill and Activity Tracker System (SATS) seminar flower 0 644 14-09-2012, 04:21 PM
Last Post: seminar flower
  User friendly ,feature-rich, practical Appraisal Tracker seminar flower 0 456 14-09-2012, 01:22 PM
Last Post: seminar flower