|
agiletracplugin
|
| #49 |
TracAdmin will be able to view an existing installation of agile-trac to see if it meets their needs
|
9
10
|
8
|
|
1
|
|
3
|
|
12
|
|
| #44 |
TracAdmin should be able to install agile-trac onto an existing trac environment with predicable results.
|
13
18
|
8
|
|
3
|
|
5
|
|
16
|
|
| #72 |
Color notation of status on Iterations and Roadmap is missing in IE and Safari
|
18
|
5
|
|
0
|
|
3
|
|
8
|
|
| #102 |
Problem with Iterations View
|
21
|
0
|
|
0
|
|
0
|
|
0
|
|
| #80 |
Roadmap Error
|
18
|
0
|
|
0
|
|
0
|
|
0
|
|
| #92 |
Iteration iteration.id does not exist
|
19
|
1
|
|
0
|
|
1
|
|
2
|
|
| #79 |
Use labels for ticket stages in ticked new/edit menu
|
17
18
|
1
|
|
0
|
|
0
|
|
1
|
|
|
agile-trac.org
|
| #115 |
Allow wiki text for Iteration description
|
30
31
|
3
|
|
1
|
|
1
|
|
5
|
|
| #59 |
AgileTracAdmin? can receive email notification of ticket updates
|
11
|
8
|
|
0
|
|
3
|
|
11
|
|
| #132 |
EndUser? should be able to see how a story was resolved on the roadmap view and allow different resolutions to be visualised
|
|
3
|
|
0
|
|
1
|
|
4
|
|
| #903 |
EndUser? should see a stable ordering of tickets within a component in the work table based on the ticket id
|
|
1
|
|
0
|
|
1
|
|
2
|
|
| #60 |
AgileTracAdmin? can view website statistics
|
11
|
8
|
|
0
|
|
3
|
|
11
|
|
| #121 |
TracAdmin should be able to use an agile-trac that is patched to version 0.11.5
|
31
|
5
|
|
1
|
|
1
|
|
7
|
|
| #88 |
Allow to see Timeline + SVN changes
|
18
|
1
|
|
0
|
|
1
|
|
2
|
|
| #101 |
Cannot save changes to dates of completion
|
21
22
|
1
|
|
0
|
|
1
|
|
2
|
|
| #86 |
http://agile-trac.org does not work
|
18
|
1
|
|
0
|
|
0
|
|
1
|
|
| #105 |
Roadmap and iteration pages have ? and a red square for "sized" - is there a problem modifying completion stages after entering tickets
|
22
23
|
3
|
|
1
|
|
1
|
|
5
|
|
|
agiletrac patch to core
|
| #57 |
roadmap page throws error after install
|
15
17
|
1
|
|
1
|
|
0
|
|
2
|
|
| #107 |
Add support for Trac 0.11.4
|
23
24
25
31
|
3
|
|
1
|
|
1
|
|
5
|
|
| #130 |
TracAdmin should be able to use an agile-trac that is patched to version 0.11.7
|
|
3
|
|
0
|
|
1
|
|
4
|
|
| #91 |
The patch of 0.11.3 encountered a SQL error on querying past iterations
|
19
23
|
3
|
|
0
|
|
1
|
|
4
|
|
| #62 |
Error on Roadmap
|
15
|
0
|
|
0
|
|
0
|
|
0
|
|
| #74 |
trac.ini [ticket-workflow] resetted if modified
|
15
|
0
|
|
0
|
|
0
|
|
0
|
|
| #67 |
Some diff of ticket description are missing
|
19
22
|
1
|
|
0
|
|
1
|
|
2
|
|
| #82 |
TracAdmin should be able to use Agile-Trac with Trac 0.11.2
|
18
|
8
|
|
1
|
|
5
|
|
14
|
|
| #95 |
Roadmap errors after installing/upgrading to agile-trac
|
20
|
5
|
|
0
|
|
1
|
|
6
|
|
| #87 |
TracAdmin should be able to use Agile-Trac with Trac 0.11.3
|
18
|
5
|
|
1
|
|
3
|
|
9
|
|
| #85 |
MilestoneAdmin? can use a date picker to select a Due date for a milestone
|
18
|
1
|
|
0
|
|
1
|
|
2
|
|
|
completion stages
|
| #47 |
EndUser? understand the effect of choosing 'fixed' as a Resolution for tickets after installing agile-trac
|
13
18
|
0
|
|
1
|
|
0
|
|
1
|
|
| #75 |
Ticket becoming "sized" while it should become "closed: DONE"
|
15
19
23
|
3
|
|
0
|
|
1
|
|
4
|
|
| #73 |
Missing trailing space at end of 2 SQL statements
|
15
|
1
|
|
0
|
|
0
|
|
1
|
|
| #65 |
Roadmap error of "list index out of range"
|
13
|
1
|
|
0
|
|
1
|
|
2
|
|
| #84 |
TicketUser? can use a date picker to select completion stage progression dates
|
18
|
3
|
|
0
|
|
1
|
|
4
|
|
|
workflow
|
| #54 |
When updating ticket size I received this error
|
15
|
1
|
|
0
|
|
1
|
|
2
|
|
| #76 |
Once a ticket has been partial completed, it won't send notification mail.
|
16
19
23
|
5
|
|
0
|
|
3
|
|
8
|
|
|
documentation
|
| #108 |
Fixing setting size fields to 0 is unexpected
|
22
23
|
0
|
|
1
|
|
0
|
|
1
|
|
|
roadmap UI customisation
|
| #905 |
Roadmap and Iteration pages should render correctly in Chrome
|
|
1
|
|
0
|
|
1
|
|
2
|
|
| #28 |
TracAdmin can specify a default progress meter width as a configuration option
|
26
|
1
|
|
0
|
|
0
|
|
1
|
|
| #98 |
RoadmapUser? should be able to see an indication of what the estimated dates are based on
|
20
|
1
|
|
0
|
|
1
|
|
2
|
|
| #131 |
EndUser? should not be presented with overflow errors if agile-trac is mis-used such that we have small or 0 iteration completion rate
|
|
5
|
|
0
|
|
1
|
|
6
|
|
| #89 |
EndUser? should be able to view tickets in the Roadmap view grouped by component
|
18
|
3
|
|
0
|
|
1
|
|
4
|
|
| #90 |
ReluctantIeUser? should be able to enjoy a pleasant Roadmap despite the poor rendering of the IE browser
|
|
8
|
|
0
|
|
3
|
|
11
|
|
|
release planning
|
| #902 |
EndUser? can't see estimated dates when there is no historical data
|
|
1
|
|
0
|
|
1
|
|
2
|
|
| #39 |
TracAdmin will be able to set the milestone priority from the 'admin' panel
|
19
20
23
25
|
3
|
|
0
|
|
0
|
|
3
|
|
| #27 |
EndUser? can distinguish which tickets have been 'started' on the Roadmap and Iterations page
|
|
8
|
|
0
|
|
0
|
|
8
|
|
| #33 |
EndUser? will have the due date status reflect the expected completion date to make it more useful
|
19
22
23
|
3
|
|
0
|
|
0
|
|
3
|
|
| #29 |
EndUser? will have a visual indication of milestone priorities and their groupings
|
|
5
|
|
0
|
|
0
|
|
5
|
|
| #133 |
AgileAdmin? should be able to influence how previous iterations are used to calculate the points per completion rate
|
|
3
|
|
1
|
|
1
|
|
5
|
|
| #46 |
EndUser? should be able to differentiate between no expected milestone date because there is insufficient data and no date because the data says it will never be finished
|
12
19
|
3
|
|
0
|
|
0
|
|
3
|
|
| #125 |
Roadmap viewer should have the possibility of seeing the effect of parallel weighted work on milestones of equal priority
|
|
5
|
|
1
|
|
1
|
|
7
|
|
| #135 |
EndUser? should not see an empty Work Ticket Table if it is empty as this is just noise
|
|
1
|
|
0
|
|
1
|
|
2
|
|
| #134 |
EndUser? should be able to view the expected completion dates for a milestone on the milestone view
|
|
3
|
|
0
|
|
1
|
|
4
|
|
| #136 |
EndUser? should be shown an expected completion date for milestones even if they contain no work
|
|
1
|
|
0
|
|
1
|
|
2
|
|
|
iterations
|
| #904 |
EndUser? should be able to add or remove the current'y viewed ticket from an iteration
|
|
5
|
|
1
|
|
1
|
|
7
|
|
| #55 |
EndUser? should have iteration and roadmap end dates treated as being inclusive
|
12
17
|
3
|
|
0
|
|
1
|
|
4
|
|
| #45 |
EndUser? should have a visual indication of which iterations a ticket is associated with on the Roadmap view
|
30
|
8
|
|
0
|
|
3
|
|
11
|
|
| #99 |
IterationAdmin? should be able to associate wiki pages with an iteration for activities such as planning and evaluation
|
20
|
3
|
|
1
|
|
1
|
|
5
|
|
| #61 |
EndUser? should be prevented from crashing agile-trac with empty iteration dates
|
12
14
18
|
5
|
|
1
|
|
1
|
|
7
|
|
| #63 |
TracAdmin should be able to view the Iterations in the Admin section. admin_iterations.html template missing
|
12
|
1
|
|
0
|
|
1
|
|
2
|
|
| #64 |
EndUser? should be able to edit iterations from the iterations admin page
|
12
13
|
1
|
|
0
|
|
1
|
|
2
|
|
| #70 |
The filter "iteration" is missing in custom query links of the page "Iterations"
|
30
31
|
3
|
|
0
|
|
1
|
|
4
|
|
| #83 |
IterationAdmin? can use a date-picker to select iteration dates
|
17
|
5
|
|
0
|
|
3
|
|
8
|
|
| #93 |
EndUser? should have control over the display of the iteration work table, including what colums are shown and the default sort order
|
20
|
5
|
|
1
|
|
1
|
|
7
|
|
| #97 |
AgileAdmin? should be able to 'reset' points per iteration in the event of drastic team changes
|
20
|
3
|
|
1
|
|
1
|
|
5
|
|
|
ticket enhancements
|
| #103 |
How to Customize the stages
|
21
23
|
0
|
|
0
|
|
0
|
|
0
|
|
