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
70
71
72
73
74
75
76
77
|
<?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>Advanced editing</title>
<link rel="stylesheet" type="text/css" href="common/style.css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1" />
<link rel="home" href="index.html" title="WebIssues Manual" />
<link rel="up" href="webissues.work.html" title="Chapter 3. Working with issues" />
<link rel="prev" href="webissues.work.views.html" title="Filtering issues" />
<link rel="next" href="webissues.work.export.html" title="Printing and exporting" />
</head>
<body>
<div id="wrapper">
<div id="header">
<div id="header-top">
<div id="header-left">
<h1><img src="common/webissues.png" alt="WebIssues" id="logo" />WebIssues Manual</h1>
</div>
<div id="header-right">
<h2 class="subtitle">Version 1.1.5</h2>
</div>
</div>
<div id="infobar">
<div id="infobar-left"><a accesskey="h" href="index.html">Home</a> » <a accesskey="u" href="webissues.work.html">Working with issues</a></div>
<div id="infobar-right"></div>
</div>
</div>
<div id="body">
<div class="navlinks">
<div class="navleft">« <a accesskey="p" href="webissues.work.views.html">Filtering issues</a></div>
<div class="navright"><a accesskey="n" href="webissues.work.export.html">Printing and exporting</a> »</div>
<div class="clear"></div>
</div>
<div class="sect1">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="webissues.work.advanced"></a>Advanced editing</h2>
</div>
</div>
</div>
<p>It's possible to add a description to an existing issue and to edit or delete a description. Only the person who created the issue, and the administrator of the system or the project, is allowed to do that.</p>
<p>Comments can also be edited and deleted. This can be done by the user who created the comment, and the administrator of the system or the project, to which the issue belongs. An administrator may thus act as a moderator of descriptions and comments. Users without administrator privileges can't modify or delete descriptions and comments created by other users.</p>
<p>You can also change the name and description of the attachments, and to remove them. As with comments, this can be done by the user who created the attachment or by an administrator. You can't modify or replace the attached file — in order to do this, you need to remove the attachment and add the new file as a separate attachment.</p>
<p>To edit or delete a description, comment or attachment, click the <span class="guilabel">Edit</span> or <span class="guilabel">Delete</span> button in the upper right corner of the corresponding item in the issue details view. If the item has been edited, its last modification date and the person who edited it is displayed in addition to the creation date and author.</p>
<div class="figure">
<a id="id621130"></a>
<div class="figure-contents">
<div class="mediaobject">
<img src="images/ch03-fig22.png" alt="History after editing a comment" />
</div>
</div>
<div class="figure-title">Figure 3.24. History after editing a comment</div>
</div>
<p>Only system administrator or project administrator may delete an existing issue, using the <span class="guilabel">Delete Issue</span> command.</p>
<div class="warning">
<h3 class="title">Warning</h3>
<p>Deleting an issue is irreversible and causes its entire history to be lost, so you should only do it in special circumstances.</p>
</div>
<p>The administrator can also move an issue to another folder using the <span class="guilabel">Move Issue</span> command. The target folder must be of the same type as the issue being moved, because issues of various types can't be combined in a single folder. To move the issue to a folder belonging to another project, you must be an administrator of both projects, or the system administrator. The transfer operation is registered in the history of the issue.</p>
<p>Each user can clone an existing issue, creating a new issue in the same folder, or another folder of the same type. To clone the issue, select the <span class="guilabel">Clone Issue</span> command. The new issue by default has the same name, location and attribute values as the issue being cloned. If necessary, you can change these values, and then click <span class="guibutton">OK</span>. The new issue is in no way connected with the original issue, but you can create such connection using a link to the issue (see <a class="xref" href="webissues.work.issues.html#webissues.work.issues.comments" title="Comments and descriptions">the section called “Comments and descriptions”</a>). Also the history of changes won't be retained, and the comments and attachments won't be added to the cloned issue.</p>
<p>There are also no restrictions when it comes to editing the attributes of the issue. Each user can freely modify them, but all changes are permanently recorded by the system and the only way of undoing them is to edit them once again.</p>
</div>
<div class="navlinks">
<div class="navleft">« <a accesskey="p" href="webissues.work.views.html">Filtering issues</a></div>
<div class="navright"><a accesskey="n" href="webissues.work.export.html">Printing and exporting</a> »</div>
<div class="clear"></div>
</div>
</div>
<div id="footer">
<p class="copyright">Copyright © 2007-2017 WebIssues Team</p>
</div>
</div>
</body>
</html>
|
