Adds budgeting informations to Tickets

Description

Plugin, where you can add a bunch of budgeting informations. This is usefull when more than one person is working on a ticket. The generated report shows all tickets where a person is involved.

Screenshot: Adding new budgeting information

Screenshot: Showing budgeting info after ticket box

Milestone view will also show additional info, see screenshot.

In this plugin is also included a report, which shows all tickets in which users are involved, see screenshot.

Bugs/Feature Requests

There exists bugs and feature requests for BudgetingPlugin. If you have any issues, create a new ticket for BudgetingPlugin.

Download

Download the zipped source from here.

Or download precompiled Eggs:

• for Trac 0.12: ​Budgeting_Plugin-0.5.a4-py2.6.egg
• for Trac 0.13: ​Budgeting_Plugin-0.6.0-py2.6.egg

Source

You can check out BudgetingPlugin from http://trac-hacks.org/svn/budgetingplugin using Subversion, or browse the source:

• for Trac 0.12​
• trunk​ (also for Trac trunk)

Example

Configurable types in trac.ini:

[budgeting-plugin]
types = Doku|Impl|Info|Spezi|Test
default_cost = 2.0
default_estimation = 2.0
default_state = 0
default_type = Impl

Default configuration:

[budgeting-plugin]
# list of users, which should be excluded to show in the drop-down list; should be usable as SQL-IN list
exclude_users = 'anonymous','authenticated','tracadmin'
# indicates whether users should be retrieved from session or permission table; possible values: permission, session
retrieve_users = permission
# Types of work, which could be selected in select-box.
types = Documentation|Implementation|Specification|Test

Recent Changes

[13119] by framay on 2013-05-14 09:20:54

setting version to 0.6.3 since there have been quite a lot changes since last version change

[13060] by aleuhe on 2013-05-08 11:27:54

Fixed some bugs in changelog:

• doubled position in new or deleted tickets
• empty change comments if estimation, cost or status fields with value 0 or 0.00 are deleted (will be 0 again)

[12970] by aleuhe on 2013-04-12 15:27:15

• SQL injection prevented by using db_query and db_transaction with arguments for all values
• Changes in Budgeting rows are logged in ticket_change (one entry for new or deleted rows, multiple entries for changes values of a row)

Author/Contributors

Author: framay
Maintainer: framay
Contributors: aleuhe