A project short name would be the best of the two options, I suppose. It could be set in the admin section of the project and would work essentially the same way as the alias in intertrac. I like that!
On Aug 21, 2016 4:38 PM, "RjOllos" <[email protected]> wrote: > > > On Sunday, August 21, 2016 at 11:22:45 AM UTC-4, RjOllos wrote: >> >> >> >> On Friday, August 12, 2016 at 3:11:02 PM UTC-4, Miguel Almeida wrote: >>> >>> I am trying to use the MultiProjectCommitTicketUpdaterPlugin >>> <https://trac-hacks.org/wiki/MultiProjectCommitTicketUpdaterPlugin>. >>> >>> The documentation says " By prepending the project name to the ticket >>> number in the approved InterTrac <https://trac-hacks.org/wiki/InterTrac> >>> fashion, you can add comments to tickets in specific projects only." >>> >>> >>> Given the following intertrac configuration: >>> >>> [intertrac] >>> tools.title = My Tools >>> tools.url = http://some/url >>> >>> I was under the impression that you'd be able to update ticket #99k with >>> the commit message: >>> >>> *foo (see tools:#99)*However, I discovered that, because my tools >>> project's name is "My tools project" (as seen in the corresponding trac's >>> admin section), this commit doesn't get added to ticket #99. >>> >>> If, however, I change the project name to "Tools", the commit message >>> will be added. >>> >>> >>> The documentation is a bit ambiguous, because it says "prepending the >>> *project >>> name*", but it also says "in InterTrac fashion". >>> >>> Am I missing something to be able to use my intertrac names or aliases >>> here, or will this tool only work with the actual project name? I was >>> hoping for the former, since the project names tend to be more verbose than >>> the intertrac aliases! >>> >>> All insights appreciated! >>> >>> Miguel >>> >> >> The plugin doesn't use intertrac configuration, instead it matches to the >> project name, which is configured through the [project] name option: >> https://trac.edgewall.org/wiki/TracIni#project-section >> >> See: https://trac-hacks.org/browser/multiprojectcommitticket >> updaterplugin/0.12/multicommitupdater/commitupdater.py? >> marks=240&rev=11453#L228 >> >> - Ryan >> > > > I'm not sure it would make sense to use the [intertrac] section to > configure this plugin. The CommitTicketUpdater is running for each > environment for which the hook is configured. The intertrac section is > commonly used to make a Trac environment aware of other environments, > whereas if the intertrac section was used for this plugin it would have to > be configured the same for every environment, and the environment would be > using the intertrac section to obtain configuration about itself. > > I also agree though that it doesn't make sense to use the [project] name > setting. Two options I can think of are: > * Add a [project] short_name option > * Use the Environment name: https://trac.edgewall. > org/browser/branches/1.2-stable/trac/env.py?rev=14977&marks=310#L309. The > Environment name is the string you use when creating the environment, i.e. > the directory name of the project: "trac-admin <name> initenv" > > - Ryan > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Trac Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/trac-users/62Eu-uJZWEw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/trac-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
