Project

General

Profile

Actions

Improvement #164

closed

Bug #163: Treatment of project custom fields

Revise the treatment of object custom fields

Added by liaham about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
02/18/2021
Due date:
% Done:

100%

Estimated time:
Compatible Redmine Version:

Description

Think about:

  • What should an authorized user be allowed to change in a project?
  • What should the administrator be allowed to change in the admin area (project type, project custom field)?

Ideas:

  • The administrator can delete contents of project custom fields stored in all projects belonging to a specific project type.
  • The administrator can deactivate a project custom field in a project type if all underlying objects have no values stored.
  • If the administrator tries to disable a project type in a certain project custom field, he will get an error when the project type has projects with stored values for that field. What means he has to delte the values first.
  • An authorized user is allowed to change the project type if
    • the underlying project custom field is empty
    • the project has no guest and host projects

Related issues 1 (0 open1 closed)

Related to Redmine Project Types - Bug #157: Unchecked custom fields of projects are still displayed on project index page tableClosedliaham02/12/2021

Actions
Actions #1

Updated by liaham about 4 years ago

  • Related to Bug #157: Unchecked custom fields of projects are still displayed on project index page table added
Actions #2

Updated by liaham about 4 years ago

  • Target version changed from 4.1.0 to unplanned
Actions #3

Updated by liaham about 4 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions #4

Updated by liaham about 4 years ago

  • Target version changed from unplanned to 4.0.0
Actions

Also available in: Atom PDF