On 11.11.2015 05:52, Serge Tumanyan wrote:
> Hello, Stefan.
> I want to request the following extension to bug tracker integration. Right
> now you can set the bugtraq:message property and get bug number edit box in
> commit, branch, import and all other dialogues. And get exactly the same
> addition to commit message that is contained in this property.
> I am using a very smart bug tracking system which allows to manipulate
> tickets from commit messages. So I would like to have different templates
> for at least commit and branch operations. For example when I start working
> on a ticket I want to create a branch for that and add 'accepted #[ticket]'
> to the log message that will set the exact ticket to accepted state. On the
> other hand when I have already merged all the changes back and want to
> commit them, I would like to get another text like 'Fixed #[ticket]' or 'See
> #[ticket]'. Unfortunally I failed to do this task. So if it is possible,
> could you please add some additional properties for such a task? I would
> suggest the following properties: bugtraq:messagecommit,
> bugtraq:messagebranch, bugtraq:messageimport and so on. These properties
> could have lower priority then original bugtraq:message property, so it can
> allow me to do the following task.
> assign bugtraq:message property to branches branch like 'Fixed #%BUGID%.
> Assign bugtraq:messagecommit property to trunk like 'See #%BUGID%'.
> Assign bugtraq:messagebranch property to trunk like 'Accepted #%BUGID%'.
> And get the following workflow.
> 1. Branch from trunk to branch inside branches and get addition to log
> message like: 'Accepted #[ticket]' moving ticket [ticket] to accepted state
> because trunk has bugtraq:messagebranch property and no bugtraq:message over
> 2. Fix issues and commit getting the following addition to log message:
> 'Fixed #[ticket]', moving [ticket] to fixed state. This will happen because
> property bugtraq:message set for the whole branches branch will have
> precedence over branched from trunk bugtraq:messagecommit property.
> 3. Merge changes back to trunk and commit the latest and the greatest
> changes to trunk getting addition to commit message like: 'See #[ticket]'
> adding to ticket [ticket] the same comment as in commit dialogue because no
> bugtraq:message property will have precedence over bugtraq:messagecommit in
> In addition it would be great to have a checkbox that will allow to disable
> all these additions for exactly one revision for cases that are out of range
> and need not have this addition for some reason.
So the priority order of the properties would be:
for normal commits, and
for creating a branch.
But I see a problem here: by automatically specifying whether a ticket
is fixed/accepted/whatever you can not change that manually.
For such integrations with bugtrackers I recommend using the
bugtraq:logregex properties instead. That way users have to write the
'trigger' parts manually, but they can do so as needed and they actually
see what's happening to the ticket.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-11-16 20:11:41 CET