Opened 18 years ago
Last modified 7 years ago
#858 new enhancement
Listing changesets using the svn bugtraq properties
Reported by: | Owned by: | anybody | |
---|---|---|---|
Priority: | normal | Component: | Request-a-Hack |
Severity: | normal | Keywords: | |
Cc: | Bhuricha Deen Sethanandha | Trac Release: | 0.11 |
Description
It's very important for us to be able to see all related code changes on a ticket. As well, from code to be able to see what the related tickets are.
We're currently using the svn bugtraq properties on commit to link changesets to tickets:
- Property bugtraq:warnifnoissue set to true
- Property bugtraq:number set to true
- Property bugtraq:label set to Ticket:
- Property bugtraq:url set to http://domain.com/trac/ticket/%BUGID%
- Property bugtraq:message set to Ticket: #%BUGID%
As well, we're using the post-commit hook to get the changesets referenced in the tickets.
This means that on commit we have to enter the ticket number twice, once on the bugtraq property field and the other by placing "re #" in the message. Obviously this is clumsy and non-ideal.
We'd love to have a post commit hook that uses the bugtraq property to update the ticket with the changeset number in a fashion similar to the above post commit hook. That way we'd only have to enter it once.
Another dream item would be a way to list a tickets referenced changesets in one area instead of having them strewn through the notes but now I'm just dreaming....
Attachments (0)
Change History (3)
comment:1 Changed 17 years ago by
Cc: | Bhuricha Deen Sethanandha added; anonymous removed |
---|---|
Trac Release: | 0.9 → 0.11 |
comment:2 Changed 17 years ago by
Simpler but not as good solution is to just add a paragraph with Changesets: to the description section of the ticket. The plugin could update that paragraph with revision that relate to it.
comment:3 Changed 7 years ago by
Severity: | blocker → normal |
---|
I also like to have this feature. Can you tell me more about the bugtraq. I think it is possible to implement as plugin that create custom field called "Changesets". On post-commit-hook, it will search for ticket number and update the changesets field with the revision number.
However, we will need to wait for http://trac.edgewall.org/ticket/1791 to be implemented so that the revision number become link to the source code in the code browser. This could be possible for Trac 0.11