Changes between Version 2 and Version 3 of OneRepoManyTracSitesPatch


Ignore:
Timestamp:
Aug 6, 2016, 10:22:29 PM (6 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • OneRepoManyTracSitesPatch

    v2 v3  
    55== Description
    66
    7 We have multiple repositories and multiple Trac sites.  Our users expressed a need to be able to update tickets on multiple Trac sites from a single commit comment in a repository.
     7This plugin allows you to update tickets on multiple Trac sites from a single commit comment in a repository.
    88
    9 For example, consider the commit:
     9We have multiple repositories and multiple Trac sites. For example, consider the commit:
    1010{{{
    1111Updated the foo to fix the bar.
     
    1515}}}
    1616
    17 Our problem was that ticket 71 existed in TracSiteA, and ticket 42 existed in TracSiteB.  On TracSiteA, the comment would be added to ticket 71 and 42, but ticket 42 on TracSiteA had nothing to do with the issue. Similarly on TracSiteB, the comment would be added to ticket 42, with an unknown link to the non-existent ticket 71 on that site.
     17Our problem was that ticket 71 existed in TracSiteA, and ticket 42 existed in TracSiteB. On TracSiteA, the comment would be added to ticket 71 and 42, but ticket 42 on TracSiteA had nothing to do with the issue. Similarly on TracSiteB, the comment would be added to ticket 42, with an unknown link to the non-existent ticket 71 on that site.
    1818
    19 This patch enables our users to commit thusly:
     19This patch enables our users to commit as follows:
    2020{{{
    2121Updated the foo to fix the bar.
     
    2525}}}
    2626
    27 The comments only get added to TracSiteA ticket 71 and TracSiteB ticket 42.  As some added gravy this patch also converts the comments so that the links take the user to the correct place.
     27The comments only get added to TracSiteA ticket 71 and TracSiteB ticket 42.
    2828
    29 For example, the source of the comment on ticket 71 of TracSiteA would appear as...
     29This patch also converts the comments so that the links take the user to the correct place. For example, the source of the comment on ticket 71 of TracSiteA would appear as follows:
    3030{{{
    3131Updated the foo to fix the bar.
     
    3434See [[http://mytracsite.com/TracSiteB/ticket/42|#42@TracSiteB]] as well
    3535}}}
    36 ...and the source of the comment on ticket 42 of TracSiteB would appear as...
     36
     37...and the source of the comment on ticket 42 of TracSiteB would appear as follows:
    3738{{{
    3839Updated the foo to fix the bar.
     
    4142See #42@TracSiteB as well
    4243}}}
    43 ... this way links created in the comment don't take our users to confusing places.
     44
     45This way links created in the comment don't take our users to confusing places.
    4446
    4547== !Bugs/Feature Requests
     
    6567Apply the patch to tracopt/ticket/commit_updater.py.
    6668
    67 Update your trac.ini file. Following the scenario in the description:
     69Update your `trac.ini` file. Following the scenario in the description:
    6870
    69 TracSiteA's ini has...
    70 {{{
     71TracSiteA's ini has the following:
     72{{{#!ini
    7173[ticket]
    7274commit_ticket_update_name_is_required = true
     
    7577TracSiteB = http://mytracsite.com/TracSiteB/ticket/
    7678}}}
    77 ...and TracSiteB's ini has...
    78 {{{
     79
     80And TracSiteB's ini has the following:
     81{{{#!ini
    7982[ticket]
    8083commit_ticket_update_name_is_required = true
     
    8386TracSiteA = http://mytracsite.com/TracSiteA/ticket/
    8487}}}
    85 
    8688
    8789== Recent Changes