Name of target project needed in change description text

[boftx@…]

The name of the project to which a ticket was moved needs to be in the change log text. The current text does not include this item and it is a major ommission from what is otherwise a very useful module for multi-projects.

Ideally, the new ticket ID would be a link.

Changed 65 minutes ago by jim ¶
  ■ status changed from new to closed 
  ■ resolution set to moved 
    moved to /ticket/10

[Jeff Hammel]

The full url of the project should be displayed if you have

[trac]
base_url =

set correctly

[boftx@…]

Does "base_url" need to be in a per project .ini file instead of the inherited .ini file? I placed the following in my common .ini file (example.com is faked):

    base_url = http://trac.example.com

and the resulting text in the ticket that I moved (on the original project) is:

Changed 19 seconds ago by jim ¶
  ■ resolution changed from fixed to moved 
    moved to  http://trac.example.com/ticket/11

I would expect to see, expecially since the name of the target project is already available in the list of targets:

Changed 19 seconds ago by jim ¶
  ■ resolution changed from fixed to moved 
    moved to  http://trac.example.com/PROJECT/ticket/11

The text of the resulting ticket on the target machine is fine, showing the origin ticket and URL.

[Jeff Hammel]

Replying to boftx@hotmail.com:

Does "base_url" need to be in a per project .ini file instead of the inherited .ini file? I placed the following in my common .ini file (example.com is faked):

    base_url = http://trac.example.com

and the resulting text in the ticket that I moved (on the original project) is:

Changed 19 seconds ago by jim ¶
  ■ resolution changed from fixed to moved 
    moved to  http://trac.example.com/ticket/11

I would expect to see, expecially since the name of the target project is already available in the list of targets:

Changed 19 seconds ago by jim ¶
  ■ resolution changed from fixed to moved 
    moved to  http://trac.example.com/PROJECT/ticket/11

The text of the resulting ticket on the target machine is fine, showing the origin ticket and URL.

Yes, this is how base_url works, which is to say that it must be specified on a per project basis. I agree that the behavior is less than desirable and advise ticketing on trac.edgewall.org

[boftx@…]

Confirmed, providing a value for "base_url" in each project's individual trac.ini file works as expected. Thanks for the insight. Opening a ticket on the Trac site to suggest that "base_url" be populated as part of the initenv command as that is when trac.ini is created with an empty "base_url" and trac-admin already has logic to handle inherited options.