Enumerated custom field of Projectid's

[SystemCorp]

Hi all

I've been doing some research on making changes to our MantisBT to support features requested by the users.

One of these features involves creating a custom field of Enumerated type, containing all the other Projects within the Database. Without looking too deeply into the database or the supported custom functions. It looks like it should be possible to use the projectid field, but I cannot work out how to reference it.

Can anyone point me in the right direction for this?

David

[SystemCorp]

Hi Guys,

Anyone have any ideas on how this can be done/is this possible?

[cas]

David,
what is the intention of this field? Do you want your users to select the project while reporting an issue? This will bring a number of issues since there are quite a num ber of things depending on this setting. First of all the list can only contain projects for which one is authorized, then depending on the project, categories may change, available developers, custom fields and so on.
So embedding this nicely will require some proper programming using ajax functions to make it seamless.
So possible yes but there is work to do

[SystemCorp]

Hi Cas,

Thanks for that, I thought that would be the case.

My bosses want to include Customer Relations into the MantisBT database, but to implement all the new fields they want for that without cluttering the actual bugtracking pages, I suggested a new project for the Customer Relations stuff with a little field to note which project it was for. This of course snowballed into a live enumerated list that has all the other projects listed so that they don't get mistakes.

Oh well, I guess its down to getting knee deep in code time.

[cas]

In that case, you'r better of creating a CRM plugin where you can connect customers to a variey of projects. No need to mess with core code, just use the data.

[SystemCorp]

My thoughts too, but they want it in Mantis directly so that its all in one program, and as quick as possible.

[cas]

By using a plugin, you can add functionality as if it were within Mantis. So directly updatable from any related issue.
This can be started pretty simple and extended over time. Normally this can be done without touching core programming.

[SystemCorp]

I'll look into that, at the moment they have given the go ahead to prototype some changes in Mantis itself, but if they aren't happy I'll offer them the option to build a plugin.

Cheers for all your help!