1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Chapter 1. Introduction</title>
<link rel="stylesheet" href="common/style.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.74.0" />
<meta name="keywords" content="webissues, issue tracking, bug tracking, team collaboration, desktop client" />
<link rel="home" href="index.html" title="The WebIssues Client Manual" />
<link rel="up" href="index.html" title="The WebIssues Client Manual" />
<link rel="prev" href="index.html" title="The WebIssues Client Manual" />
<link rel="next" href="guide.html" title="Chapter 2. WebIssues Client Guide" />
</head>
<body>
<div id="wrapper">
<div id="content-wrapper">
<img id="header-logo" src="common/webissues.png" alt="WebIssues" />
<div id="header-title">The WebIssues Client Manual</div>
<div id="header-abstract">Desktop client for the <span class="application">WebIssues</span> system</div>
<div id="content">
<div id="content-right">
<div id="content-left">
<div id="header-links">
<a accesskey="h" href="index.html">Home</a>
</div>
<div class="navlinks">
<div class="navleft">« <a accesskey="p" href="index.html">The WebIssues Client Manual</a></div>
<div class="navright"><a accesskey="n" href="guide.html">WebIssues Client Guide</a> »</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a id="introduction"></a>Chapter 1. Introduction</h2>
</div>
</div>
</div>
<p><span class="application">WebIssues</span> is an open source, multi-platform system for issue tracking and team collaboration. It can be used to store, share and track issues with various attributes, comments and file attachments. The system is easy to install and use but has many capabilities and is highly customizable.</p>
<p>This is the <span class="application">WebIssues Client</span> application which requires a <span class="application">WebIssues Server</span> to communicate with.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="basic_concepts"></a>Basic Concepts</h2>
</div>
</div>
</div>
<p>The basic unit of data stored in the system is an <em class="firstterm">issue</em>. Depending on its type, an issue may represent a bug, task, requirement, document etc.</p>
<p>Each issue has specific <em class="firstterm">attributes</em>. Some attributes are common for all issues, including the name, date of creation and last modification and the name of the user who created and last modified the issue. In addition, each issue can have a number of user defined attributes. The values of these attributes can be plain text, numbers from given range, items from a dropdown list, date and time or user names.</p>
<p>Each issue may also contain any number of <em class="firstterm">comments</em> and <em class="firstterm">attachments</em>. A comment is a simple text note and an attachment can be any file with an optional description. Each issue remembers its full history, which includes all comments, attachments and changes of attribute values, with information who and when made the changes.</p>
<p>Issues are logically organized into <em class="firstterm">folders</em>. Each folder stores issues of a single type. A folder can be thought of as a database table, where each attribute is a column and each issue is a row. The contents of a folder can be filtered and sorted in any way.</p>
<p>Folders are organized into <em class="firstterm">projects</em>. Each project defines the access rights for individual users. This way the data stored in the system can be separated into sections accessible for different groups of users.</p>
</div>
</div>
<div class="navlinks">
<div class="navleft">« <a accesskey="p" href="index.html">The WebIssues Client Manual</a></div>
<div class="navright"><a accesskey="n" href="guide.html">WebIssues Client Guide</a> »</div>
</div>
<div id="copyright">
<p class="copyright">Copyright © 2007-2009 WebIssues Team</p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>
|
