Add Id to client and add possibility to create links to clients like : client:1

[BKV]

Hello,

Think that is a good idea to add Id field to client and make possible to create links using wikiprocessor like: client:1

Thanks.

[Colin Guthrie]

Client's don't actually have id's but yeah, adding a client:"Wibble Inc." link would make sense.

That said I don't actually have a client overview page on the frontend yet, so there is nowwhere this would link to!! I do plan on creating this tho' as well as providing client-specific time/cost statistics.

I also need to add in billing cycles per-client and inclusive development hours allocated to each client (this is due to my own personal needs but I'll try and make it as generic as possible).

[Colin Guthrie]

I see you actually suggested adding an id to client so that you could use it in the wiki processor... while this is sensible, I'm not sure of the worth. Milestones (for example), do not have ids, they just have names and the wikiprocessor there works fine. I guess a problem could arise if you rename a client, but to be honest, looking up the id each time would be a pain too.

Someone has asked me (#3973) to add a "ref" or "id" field to clients for external referencing (e.g. in another system) so perhaps it would make sense to add two processors

• client:"Big Corp."
• clientref:123

That way if you have references you use you can add them in and use them for linking, otherwise you can just use the name.

I think this covers all bases!

[anonymous]

I'd rather use the existing wiki-system for information about each client, then you don't need a separate client overview front end. Either by using the client name as a WikiPageName, or having a separate WikiPageName-field for each customer so you get both pretty names, and shorter WikiPageNames.

Name: International Mega Corporation. WikiPageName: MegaCorp.

Then perhaps a macro for fetching client info (for the client referenced on the wikipage) such as billing info, list of open tickets for this client, and so on?

Also, creating a processor for clientref:123 seems to be very close to the purpose of the RegexLinkPlugin?