i have the same problem.

1. this happens if you are in "all projects"
2. the caption for the button is 'update columns ... for all projects' but it sets the columns for a selected project

i like this way to configure columns. there should be the possibility to set the columns for all projects AND for a selected project

The naming of the button "Update Columns as Global Default for All Projects" is a bit misleading because it does not update the columns for all Projects but only for the active (selected) project (dropdown in the right upper corner).

As far as I can see the button "Copy columns to" for a chosen project does not work too - no columns were updated/added when I checked table mantis_config_table afterwards...

Workaround: If you need to have columns set for all projects just set project_id in table mantis_config_table to 0 for the required fields...

This issue is marked as resolved many versions ago. I just installed version 1.1.2, created one project, and I got the same error when I tried to manage the configuration. dominik has it right: changing the mantis_config_table to 0 does the trick. I think this needs to be an installation issue, because the config table has a value of 20 in there for some reason right after installation. The error is caused by trying to find a project with id=20, which of course, doesn't exist. Changing the value to 0 or an existing project id makes the problem magically go away.

I investigated this error and found that
in manage_config_columns_set.php line 63 should change from

if ( $f_update_columns_as_my_default ) {
to
if ( $f_update_columns_as_my_default || $f_update_columns_as_global_default) {

This seems to fix it.

I don't think there is a relationship between configuration installation variables or DB entries and this issue.

My work-around is to update columns the way I want in another project (I have a test project for playing and things like this), then use "Copy Columns To" to copy to All Projects, then delete the entry for the test project on the "Configuration Report" screen. This way everything is done through the GUI (no touching source code, or manually doing anything to the database).

adding a working patch in the main repository is always better than a known workaround

This is still an issue - i'm just trying to work out from UI + code whether there's a 4th case:

i.e. I think at the moment we have:

a) user sets settings for themselves for 1 project
b) user sets setting for themselves for all projects
c) admin sets setting for all projects

Point 1: Case C is currently broken
Point 2: isn't there a case D - i.e. 'admin sets a setting for 1 project'

Paul

@grangeway: I'm not sure what your question is. Yes, admin can set settings for one project; that's part of my work-around in note 19811, and it works.

Which is supposed to take precedence, user's setting for all projects, or admin's setting for specific project?

Paul,
there are indeed 4 cases as you wrote:
a) user sets settings for themselves for 1 project
b) user sets setting for themselves for all projects
c) admin sets default setting for all projects
d) admin sets default setting for 1 project

I had a problem with case c. It was broken and the patch I posted earlier fixed it.
But it only made it work as expected for case c though and doesn't distinguish case d from c.

Looking at the code in manage_columns_inc.php I also see that case d is missing.

There should be an additional submit button name (in another "if" statement) to show the correct text on the Submit button for case d in manage_columns_inc.php and some code in manage_config_columns_set.php to handle it with elegance.

@olegos:
I believe that the precedence should be:

users settings for 1 project
user settings for all projects
admin default settings for 1 project
admin default settings for all projects

That's the meaning of having a default setting and letting your users play with it.
If you don't want your users to use their own view there are parameters to block their privilege to do so.

karotos:

I'm not sure I agree about precedence. Think about it this way. There is All Projects settings, and a project specific setting. Each one has a global default set by admin, and a user can customize them. So the system looks for project specific setting first, by the user or the admin, then for All Projects one. Makes sense to me. Also, if admin made a setting for one project different than the rest, there is probably a reason why. Maybe there is an important custom field that makes sense to display, or some of the default fields don't apply. Why should a user that customized his All Projects setting lose these project customizations by the admin?

The best solution is probably to give each user a choice. Maybe when All Projects is selected, there should be a checkbox for "Override global per-project settings with this one".

I also think it's important to show which of the four possible settings is currently being used.

@olegos:

Your patch breaks my functionality. I (as an admin) would like to be able to set the columns at project level for all users. With your patch I only will be able to set the DEFAULT for ALL PROJECTS.

What i need is a save button, to save the settings at projectlevel for all users. I dont wont to update the settings for all projects, because my projects may have unique columns.

I just want to save actual settings, so why is there no save button??

Maybee you should change line 209ff as follows, so the administator is able to change the columns for all users for a specific project:

<?php if ( $t_manage_page && current_user_is_administrator() ) { ?>

            <?php if($t_project_id == ALL_PROJECTS)  { ?>
            <input <?php echo helper_get_tab_index() ?> type="submit" class="button" name="update_columns_as_global_default" value="<?php echo lang_get( 'update_columns_as_global_default' ) ?>" />
            <?php } else { ?>
            <input <?php echo helper_get_tab_index() ?> type="submit" class="button" name="update_columns_for_current_project" value="<?php echo lang_get( 'update_columns_for_current_project' ) ?>: <?php echo project_»
            <?php } ?>

<?php } ?>