|
1
|
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
<issues type="array" limit="2" total_count="3102" offset="0">
|
|
3
|
<issue>
|
|
4
|
<id>9184</id>
|
|
5
|
<project name="Redmine" id="1" />
|
|
6
|
<tracker name="Feature" id="2" />
|
|
7
|
<status name="New" id="1" />
|
|
8
|
<priority name="Normal" id="4" />
|
|
9
|
<author name="James Robertson" id="2373" />
|
|
10
|
<category name="Issues" id="2" />
|
|
11
|
<subject>Inline issue editing within list view/custom query</subject>
|
|
12
|
<description>It would be very helpful to be able to edit issues
|
|
13
|
directly within the issue list view.
|
|
14
|
|
|
15
|
For example, if the Priority column is included in the issue list/custom
|
|
16
|
query, as user could directly edit the priority of a particular
|
|
17
|
issue, perhaps by double-clicking on the priority of that issue and
|
|
18
|
being presented with an, inline, drop-down.
|
|
19
|
|
|
20
|
This would allow for quickly updating various aspects of several issues,
|
|
21
|
without having to "go into" each - which can be quite painstaking
|
|
22
|
process and a confusing one if several people are involved/watching
|
|
23
|
at once.
|
|
24
|
</description>
|
|
25
|
<start_date>2011-09-05</start_date>
|
|
26
|
<due_date></due_date>
|
|
27
|
<done_ratio>0</done_ratio>
|
|
28
|
<estimated_hours></estimated_hours>
|
|
29
|
<custom_fields type="array">
|
|
30
|
<custom_field name="Resolution" id="2">
|
|
31
|
<value></value>
|
|
32
|
</custom_field>
|
|
33
|
</custom_fields>
|
|
34
|
<created_on>2011-09-05T06:27:10+02:00</created_on>
|
|
35
|
<updated_on>2011-09-05T09:46:20+02:00</updated_on>
|
|
36
|
</issue>
|
|
37
|
<issue>
|
|
38
|
<id>9183</id>
|
|
39
|
<project name="Redmine" id="1" />
|
|
40
|
<tracker name="Feature" id="2" />
|
|
41
|
<status name="New" id="1" />
|
|
42
|
<priority name="Normal" id="4" />
|
|
43
|
<author name="James Robertson" id="2373" />
|
|
44
|
<category name="Issues planning" id="40" />
|
|
45
|
<subject>Update grouped tickets/issues using drag-and-drop</subject>
|
|
46
|
<description>When viewing a list of tickets that are grouped by some
|
|
47
|
field, it would be very useful to be able to drag-and-drop the
|
|
48
|
tickets between the groups and have that field of the ticket update.
|
|
49
|
|
|
50
|
This would go some way toward providing a simple set of tools to
|
|
51
|
support Agile processes, such as a task/scrum board. For example, at
|
|
52
|
a regular (daily) catch-up meeting, it would be easy to group issues
|
|
53
|
(Tasks or User Stories for example) the status and to update the
|
|
54
|
status quickly and visibly. Another example would be managing
|
|
55
|
priorities.
|
|
56
|
|
|
57
|
Nice to have: options to prevent drag-and-drop updates from generating
|
|
58
|
emails
|
|
59
|
|
|
60
|
Relates to ##8016
|
|
61
|
</description>
|
|
62
|
<start_date>2011-09-05</start_date>
|
|
63
|
<due_date></due_date>
|
|
64
|
<done_ratio>0</done_ratio>
|
|
65
|
<estimated_hours></estimated_hours>
|
|
66
|
<custom_fields type="array">
|
|
67
|
<custom_field name="Resolution" id="2">
|
|
68
|
<value></value>
|
|
69
|
</custom_field>
|
|
70
|
</custom_fields>
|
|
71
|
<created_on>2011-09-05T06:18:33+02:00</created_on>
|
|
72
|
<updated_on>2011-09-05T06:18:33+02:00</updated_on>
|
|
73
|
</issue>
|
|
74
|
</issues>
|