<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.pp-international.net/wiki/index.php?action=history&amp;feed=atom&amp;title=Press_Work%2FRedmine</id>
	<title>Press Work/Redmine - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.pp-international.net/wiki/index.php?action=history&amp;feed=atom&amp;title=Press_Work%2FRedmine"/>
	<link rel="alternate" type="text/html" href="https://wiki.pp-international.net/wiki/index.php?title=Press_Work/Redmine&amp;action=history"/>
	<updated>2026-06-13T22:22:48Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.6</generator>
	<entry>
		<id>https://wiki.pp-international.net/wiki/index.php?title=Press_Work/Redmine&amp;diff=2647&amp;oldid=prev</id>
		<title>Admin Bastian: 1 revision imported</title>
		<link rel="alternate" type="text/html" href="https://wiki.pp-international.net/wiki/index.php?title=Press_Work/Redmine&amp;diff=2647&amp;oldid=prev"/>
		<updated>2017-12-15T10:30:28Z</updated>

		<summary type="html">&lt;p&gt;1 revision imported&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[Press Work|« Back to press work]]&lt;br /&gt;
&lt;br /&gt;
Each task for the PPI press team is reflected by a ticket in the [http://tasks.pp-international.net/projects/pr-team-tasks/ PPI Redmine]. We use Redmine rather than another tool (Pad or whatever) for several reasons. First of all Redmine&amp;#039;s intention is exactly what we use it for: it is a flexible project management web application. There are many advantages using such a system. Every team member can watch tickets, each step is documented and you can even attach files. Tickets can be assigned to other users with automatic notification by eMail on each update.&lt;br /&gt;
&lt;br /&gt;
The web frontend is very easy to use once you know the places of all the features. This guide&amp;#039;s intention is to help new team members to get started and old team members to bridge knowledge gaps.&lt;br /&gt;
&lt;br /&gt;
== Register ==&lt;br /&gt;
&lt;br /&gt;
Fill the [http://tasks.pp-international.net/account/register registration form], wait for the activation link, activate your account by clicking it and let the team leader know that your account is ready. He/She will grant access to the press team project.&lt;br /&gt;
&lt;br /&gt;
== Sorting &amp;amp; Filtering ==&lt;br /&gt;
&lt;br /&gt;
One of the most important features in Redmine is the capability to sort and filter tickets. This feature is located at the [http://tasks.pp-international.net/projects/pr-team-tasks/issues Issues page]. When accessing this page for the first time the default view is a simple list of all open tickets.&lt;br /&gt;
&lt;br /&gt;
=== Filtering ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;quot;Filters&amp;quot; part for filtering. It is located at the very top (1). The default filter is set to the status &amp;quot;open&amp;quot;. To add search criteria choose a filter in the drop down menu on the right (2). A new line with the selected column is added to the filter list. Now you can select a value in the drop down menu. You can add as many filter criteria as you want. To apply the new search criteria click on &amp;quot;Apply&amp;quot; (3).&lt;br /&gt;
&lt;br /&gt;
=== Sorting ===&lt;br /&gt;
&lt;br /&gt;
Just click on the column title (#, Tracker, Status, Priority, ...) you&amp;#039;d like to sort by. Clicking the title again changes the sort order.&lt;br /&gt;
&lt;br /&gt;
=== Advanced fun ===&lt;br /&gt;
&lt;br /&gt;
The columns can be configured by clicking on &amp;quot;&amp;gt; Options&amp;quot; on the top left (4). You can add or remove columns by selecting them and clicking on an arrow button (5). You can even group tickets by a column. This is configured by choosing a column in the drop down menu &amp;quot;Group results by&amp;quot; (6). Click on &amp;quot;Apply&amp;quot; after the selection is done (3).&lt;br /&gt;
&lt;br /&gt;
[[File:Screen_Shot_2012-06-24_at_2.16.55_PM.png|800px|thumb|none|Screen shot of the issues list]]&lt;br /&gt;
&lt;br /&gt;
 Hint: You can save a search (7). If you select the same criteria for the 10th time you probably want to use this feature.&lt;br /&gt;
&lt;br /&gt;
== Create a new ticket ==&lt;br /&gt;
&lt;br /&gt;
This is as easy as pie. Just click on [http://tasks.pp-international.net/projects/pr-team-tasks/issues/new New issue], write a subject, add a &amp;#039;&amp;#039;&amp;#039;good(!)&amp;#039;&amp;#039;&amp;#039; description and click on &amp;quot;create&amp;quot;. That&amp;#039;s it.&lt;br /&gt;
&lt;br /&gt;
[[File:Screen_Shot_2012-06-24_at_1.48.42_PM.png|800px|thumb|none|Screen shot of a new ticket]]&lt;br /&gt;
&lt;br /&gt;
== Status updates ==&lt;br /&gt;
&lt;br /&gt;
One of the most important information besides the current owner and a good ticket description is the current status. A ticket is updated by clicking on &amp;quot;Update&amp;quot; (1) at the top or bottom of a ticket. Please take care in updating the ticket whenever appropriate. Even if the status does not change you should provide additional information when it occurs. This is crucial when a ticket is handed over to another team member. Remember that this may happen at any time since this is voluntary work and we all have jobs and family. It&amp;#039;s better to update a ticket too often than too rarely. The target should be, that ach team member can be replaced at any time, and the person filling in knows exactly what is going on and what needs to be done. Click on Submit (2) to save changes to the ticket.&lt;br /&gt;
&lt;br /&gt;
You must update a ticket whenever its status changes.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;New&amp;#039;&amp;#039;&amp;#039; means that the ticket has been created but noone started working on it yet.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;In progress&amp;#039;&amp;#039;&amp;#039; means that the &amp;#039;&amp;#039;&amp;#039;current owner&amp;#039;&amp;#039;&amp;#039; is working on it. He is responsible for this task. If you overtake ownership of a ticket, always ensure that you change it to this status.&lt;br /&gt;
* You set the status &amp;#039;&amp;#039;&amp;#039;Feedback&amp;#039;&amp;#039;&amp;#039; if you can&amp;#039;t work on the ticket until an information is available or another task is done. This status must be set combined with a clear description on what exactly you are waiting for.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Resolved&amp;#039;&amp;#039;&amp;#039; means &amp;quot;work done&amp;quot;. If this is a press release it also means that the responsible persons according to the [[Press Work/Processes|processes]] have authorized the release and the process is completed. Do not set this status unless the job is really done and needs no further tasks apart from distribution!&lt;br /&gt;
* You never set a ticket to &amp;#039;&amp;#039;&amp;#039;Closed&amp;#039;&amp;#039;&amp;#039;. This status means archived. This is set by a leader during the next team meeting after a review of all resolved tasks.&lt;br /&gt;
* We rarely use the status &amp;#039;&amp;#039;&amp;#039;Rejected&amp;#039;&amp;#039;&amp;#039;. It signifies that the ticket wasn&amp;#039;t finished, i.e. because we don&amp;#039;t need it anymore.&lt;br /&gt;
&lt;br /&gt;
Please note that you can also update a ticket to add a comment, without changing the status. Always do this if you know of new important facts.&lt;br /&gt;
&lt;br /&gt;
[[File:Screen_Shot_2012-06-24_at_2.39.01_PM.png|800px|thumb|none|Screen shot of a ticket update]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Press work]]&lt;/div&gt;</summary>
		<author><name>Admin Bastian</name></author>
	</entry>
</feed>