View Issue Details

IDProjectCategoryView StatusLast Update
0021605mantisbtcustomizationpublic2016-08-19 08:41
Reportercproensa Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version1.3.1 
Summary0021605: user columns configuration precedence
Description

Currently seems like if these two configurations exists, for columns list:
1) user_xxx / All projects
2) All users / project_xxx

Configuration (1) takes precedence.
This may be intended, but giving priority to (2) may have a justification:

If a system-wide column list is defined for a project (different from all-projects defaults), may mean that some specific columns are important, as the administrator judged to include them. These columns may be custom fields that only make sense in those projects.

If a user has defined an all-projects configuration, may mean that the selected configuration is intended as a default for projects where there are not specific, relevant, columns.

So, the user saved "all projects defaults" would replace the system provided "all projects defaults", but not replace the system provided "single project defaults" (unless the user sets a "single project column-list"

I find this use case relevant, when creating project-specific custom fields, or plugin fields.
In this new config behaviour, there is a higher chance that the users will automatically see the new columns, without having to notify users to update their column list customization (even if they never modified that project specifically)

TagsNo tags attached.

Activities

cproensa

cproensa

2016-08-18 11:43

developer   ~0053854

I think the key here is that there are two concepts:

1) the settings i want to use when using view_all positioned at "all projects"
2) The settings i want to use for every project as default

These are not differentiated currently inthe application, as only (2) is managed.

dregad

dregad

2016-08-19 08:41

developer   ~0053864

So you're saying we should have

All U/All P > All U/P1 > U1/All P > U1/P1

instead of (currently)

All U/All P > U1/All P > All U/P1 > U1/P1

Configuration (1) takes precedence. This may be intended

I didn't look in detail, but I'm guessing this may be due to the standard config API behavior.

Your suggestion make sense, but the implementation may be tricky

Issue History

Date Modified Username Field Change
2016-08-14 13:28 cproensa New Issue
2016-08-18 11:43 cproensa Note Added: 0053854
2016-08-19 08:41 dregad Note Added: 0053864